-
Notifications
You must be signed in to change notification settings - Fork 119
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
Select word and line doesn't work on macos #3
Comments
Please check whether manually typing out these ZMK macros' keystrokes has the intended effect:
If those worked successfully, the problem may be timing: I think the macros might be emitting their synthetic keystrokes too rapidly for your system, so you can try increasing the
|
Could you explain what the cursor is supposed to do when I do &kp LG(RIGHT)? I think it might be an issue with the modifier key being used, because on mac, doing &kp LG(RIGHT) sends the cursor to the end of the line. So for example the extend_word_right highlights from where the cursor currently is to the end of the line. Mac also doesn't really use HOME or END, so the behaviour for those keys might be unexpected. Maybe could you also help me understand how the macro works? Say for "select word":
I suppose |
You are correct! ✅ Upon closer study of this listing, I see that "Go to next word" on macOS is Opt+Right instead of Cmd+Right. 😅 I naively assumed that, like Ctrl in Windows and Linux, a single modifier was used for both word-wise and line-wise motion in macOS too: that was the purpose of the As for understanding the select_word macro, it's just a custom shifted pair (like |
Thanks for the explanation! I modified the files accordingly as per the linked PR and have tested it to work on my own mac. |
In v32, the select word macro selects the entire line, while the select line macro selects the current line and everything below.
I'm still very new to the layout and the whole ZMK customisation, so I could use some advice on how to edit and test the macro.
The text was updated successfully, but these errors were encountered: