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
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?
The text was updated successfully, but these errors were encountered:
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
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:
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?
The text was updated successfully, but these errors were encountered: