You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In Alfred, each workflow "claims" its alias.
It would be nice to have an option for "claiming" an alias by default in the manifest, for example by adding an "alias" key on Command API.
This can appear as a suggestion, or be applied automatically unless it's already taken.
The same should be applied to hotkeys, allowing extensions to recommend the default hotkey for a command, and allow the user to remove that / set alternative if there's a collision.
Describe the feature and the current behavior/state.
n/a - doesn't exist
Will this change the current API? How?
No change.
Who will benefit from this feature?
In general, the user community will benefit from better standardization.
For example, more "how do I do X?" queries can be answered with "the default hotkey is this and that!"
The text was updated successfully, but these errors were encountered:
selfish
changed the title
[API Feature Request]
[API Feature Request] Manifest - set default allias and hotkey for commands
Nov 12, 2021
selfish
changed the title
[API Feature Request] Manifest - set default allias and hotkey for commands
[API Feature Request] Manifest - set default alias and hotkey for commands
Nov 20, 2021
Hey, thanks for your response!
I think it's natural to have collisions here.
Similarly in Alfred, each extension can declare the default binding, but it will only be set if it's available.
I think this should be optional or even should ask the user if the recommended hotkeys should be set, replaced, etc.
I would also mention that in Raycast it's SO easy and fun to customize and control hotkeys, that this really shouldn't be much of a problem.
In Alfred, each workflow "claims" its alias.
It would be nice to have an option for "claiming" an alias by default in the manifest, for example by adding an "alias" key on Command API.
This can appear as a suggestion, or be applied automatically unless it's already taken.
The same should be applied to hotkeys, allowing extensions to recommend the default hotkey for a command, and allow the user to remove that / set alternative if there's a collision.
Describe the feature and the current behavior/state.
n/a - doesn't exist
Will this change the current API? How?
No change.
Who will benefit from this feature?
In general, the user community will benefit from better standardization.
For example, more "how do I do X?" queries can be answered with "the default hotkey is this and that!"
The text was updated successfully, but these errors were encountered: