Skip to content
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

Feature request: continue-mod-list for caps-word #1410

Open
urob opened this issue Jul 30, 2022 · 2 comments · May be fixed by #1451
Open

Feature request: continue-mod-list for caps-word #1410

urob opened this issue Jul 30, 2022 · 2 comments · May be fixed by #1451

Comments

@urob
Copy link
Contributor

urob commented Jul 30, 2022

The current behavior is that caps-word continues on all mod. It would be useful to add a configuration option that allows the user to specify for which mods caps-word continues and for which it is deactivated.

Relatedly, would deactivating caps-word on mod-presses be a more sensible default?

@urob
Copy link
Contributor Author

urob commented Aug 5, 2022

Upon further consideration, having a complete continue-mod-list might be overkill. In most use cases, a simple ignore-modifiers property that can be turned on or off by the user should be enough. To that effect, I added a PR implementing that feature: #1422

@urob
Copy link
Contributor Author

urob commented Sep 10, 2022

This is fixed by #1451 (which superseded #1422). With the PR one can use /delete-property ignore-modifiers/ and then use continue-list to specify for which modifiers caps-word is not cancelled. For example, to continue caps-word on shift but cancel it with all other modifiers, one would add the following to the user-config:

&caps_word {
    /delete-property/ ignore-modifiers;
    continue-list = <UNDERSCORE  BACKSPACE DELETE LSHFT RSHFT>;
};

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant