-
-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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: Option to make Caps Word behave like QMK #1706
Comments
@chalop For now, as a workaround, you can duplicate the layer which has all the same settings but the MINUS key is UNDERSCORE. And you replace
And on the DUPLICATED_LAYER, you activate macro instead of space, esc, and etc.
|
It's not an ideal solution, but it works really great! It also has the added benefit of turning on a status led on the adv 360 (since its technically just another layer) As for what the ideal solution would look like, I would need to get more familiar with zmk's syntax in order to suggest an api for it. I'll leave the issue open in case someone has a need to implement the qmk behavior on zmk. Thank you! |
In my humble opinion, it'd be better to let users configure this for their taste instead of just letting MINUS and UNDERSCORE the only special exception. For example, while (For those who wonder the reason: It's because I use Colemak layout. For input source language layout reasons, I can't but let ZMK-level layout be QWERTY and OS layout be Colemak, not the opposite way. So the OS does remapping under the hood, which means OS remaps ';' to 'o' and ':' to 'O'. That is why ':', not ';', should be inputted when using |
I'm working on a PR to improve caps word which will add
|
@joelspadin I think it's a great idea 👍 🎉 It would be elegant if, by |
I don't think that's really in scope for my set of changes. I'm just aiming for feature parity with QMK, which lets you fully customize which keys break a word and which keys are shifted. If you set |
Two quick thoughts: 1/ #1451 already provides full control over the 2/ I am wondering whether it would make sense to consolidate capsword with the approach taken in #1366 to provide a more general backend. See this comment for details: #1366 (comment) |
I'm not sure I like changing the default to be empty and adding flags to get back to the original behavior, because that would break any existing "zmk,behavior-caps-word" behaviors in people's config repos. The layer activation thing seems odd to add to caps word, but maybe I'm not understanding the use case. I think it would probably be easier to maintain multiple, focused behaviors rather than one behavior that tries to do everything. Some of the changes I have locally could be pulled out into common utility code for multiple "do this thing as long as I only press these keys" behaviors though. |
I figured that changes to the backend "zmk,behavior-caps-word" are fine as long as the frontend
The layer stuff is useful, e.g., to get a I agree that it's not really related to caps-word. But given that its implementation overlaps 99% with the caps-word backend, I thought it would be more code efficient to re-use the backend (which then should probably be renamed to something other than That said, I actually prefer @nickconway's |
What is "an OS layout"? Another (?) reason for modifying existing or creating a separate caps word macro is to add a proper support for other languages. For example, in Russian these keys should work with caps word, but don't (i.e., Russian support is currently broken):
And since using caps in general is rare, especially with some of those letters, I previously didn't even know that some letters don't work. So I'm also interested in this feature. |
That should have been "OS keyboard layout" |
They are called "OS keyboard layouts" because they are provided by your operating system. Usually they correspond to different languages, but you can have multiple layouts for the same language/locale, like US English and US International. Prepending "OS" helps to distinguish from firmware-based keyboard layouts, i.e. your keymap. |
On QMK's caps word, when you press the minus key it automatically converts it to an underscore (https://docs.qmk.fm/#/feature_caps_word). I was happy to see this key on ZMK too, but it doesn't behave the same.
How feasible would be to make the minus key is pressed it "shifts" it to underscore and caps word remains active? I posted on the discord if there was a way to make it but the post didn't gain any traction.
The text was updated successfully, but these errors were encountered: