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] An option to send specified key when button is pressed with a modifier #466

Open
rdtq opened this issue Jan 18, 2022 · 3 comments · May be fixed by #914
Open

[Feature request] An option to send specified key when button is pressed with a modifier #466

rdtq opened this issue Jan 18, 2022 · 3 comments · May be fixed by #914
Labels
enhancement New feature or request

Comments

@rdtq
Copy link

rdtq commented Jan 18, 2022

Description of problem:

I have a setup that turns HJKL into navigation arrows while holding f:

nav_f  (tap-hold 500 f (layer-toggle navigation))

Navigation works beautifully. However, what I noticed is that when I type capital F, 90% of times it comes out as lowercase f. Looking at kmonad debug output I noticed it's because of a particular way I type when I'm typing fast:

(press Shift, press letter, release Shift, release letter)

That's a tough habit to get rid of.

Possible solution:

Have an option to tap-hold to send specified key when button is pressed with a modifier:

nav_f  (tap-hold 500 f (layer-toggle navigation) :modifier-shift: f)
@ramonwenger
Copy link

I just wanted to open this exact same issue (having configured the same navigation layer myself).

Maybe the solution could also be for kmonad to detect if a modifier was pressed on the keydown event, as opposed to the keyup event, as it currently seems to be implemented. (This is just a guess on my part, maybe kmonad does this completely differently)

@slotThe slotThe added the enhancement New feature or request label Mar 24, 2022
@meain
Copy link

meain commented Apr 11, 2022

Here is a related issue: #50

This is the only thing that is kinda annoying thing for me at the moment.

@jchtt
Copy link

jchtt commented May 1, 2022

#256 is another related issue (duplicate?).

One way to address this is pull request #524 which I would love to get feedback on. If you're willing to compile your own version from this branch, you could give it a spin and tell me if that fixes it for you.

jokesper added a commit to jokesper/kmonad that referenced this issue Oct 27, 2024
This is a long standing issue, so it fixes a few things:
- fixes kmonad#256
- fixes kmonad#466 (duplicate of kmonad#256 or kmonad#111)
- fixes kmonad#523 (duplicate)
- fixes kmonad#705 (already closed)
- fixes kmonad#907 (duplicate)
- resolves kmonad#524 (original merge request, with conflicts)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants