-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comma separated shortcuts doesn't works #3
Comments
Looks like @bry4n doesn't have time. |
I think it would be less funky to append the scope to the method: shortcuts: {
'right, space': 'someMethod myScope'
} |
perhaps making a pull request would help @bry4n bring his insights |
Sorry! I have been busy. pull requests are welcome 👍 -- I can work on the fix this weekend. how about this: shortcuts: {
"o, enter <myscope>": "someMethod"
} That solution should be easier for me to update the regex pattern. |
i would find that very hard to parse - you have to check for a comma in the middle of a string IMO my way is easier to read, since the value currently doesn't take a list |
The question is to decides if having the ability to have a different scope per event is desired. Or if it would rather introduce unnecessary redundancies. Or maybe both could be supported. IMO and in my use cases it seems that it would introduce redundancies to have the scope defined with the event. |
+1 Is there a working accepted way to do this? |
Assigning multiple shortcuts on a single line separated by comma as in keymaster.js doesn't works.
I understand you support the scope feature of keymaster.js https://github.com/madrobby/keymaster/#scopes which make it ugly to supports multiple shortcuts and a scope.
Maybe the above could be supported for backwards compatibility but a more clean declaration could be promoted :
Let me know your thoughts and if you haven't time to implement it, I'll see if I have some for a fork-pull-request.
The text was updated successfully, but these errors were encountered: