Improving home row shift for optimal layouts #375
gerhard-h
started this conversation in
Show and tell
Replies: 1 comment 1 reply
-
I tried your approach and that indeed works like a charm for most of my usecases, thanks a lot! I noticed, however, a slight problem - I guess that's a more general problem with all kinds of home-row mods - vim-like navigation does not work well with "hold" actions on |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
After setting up aliases
(tap-hold-release 1 140 j rsft )
and(tap-hold-release 1 140 f lsft )
you are done...But now typing "Fjord" rather fast and I ended up with "Ford".
Same for After, Often, Ajax,... they all require this double tapping.
I can not say if it is a bug or me messing up the timing, I didn't even realize there being a problem because [A-Z][fj] words a rare (1 in 300 in my example text)
But using a layout like Colemak, Dvorak,... f and j will be replaced with n,t,e,... and the probability changes to 1 in 8 (upper case words).
The solution I found is:
n (tap-hold-release 1 140 n (one-shot 500 rsft) )
and it works perfectly without any side effects.EDIT
When rolling (to slow) over the shift key causes
D
instead offd
for you(tap-hold 1 140 f (one-shot 500 rsft) )
may solve that as it favors rolling for some extra milliseconds.tap-hold's first timer parameter is still a little mysterious for me, but setting it very low, seems to make tap-hold and tap-hold-release to do very much the same otherwise.
EDIT tree month of typing practise have passed and I realize that I have learned the shift-timeings (without special training) and don't need the help of one-shot any more
(tap-hold 1 160 f lsft)
Beta Was this translation helpful? Give feedback.
All reactions