Replies: 9 comments 13 replies
-
Beta Was this translation helpful? Give feedback.
-
I've heard good things about caps lock, since it's in an ergonomic place on a lot of keyboards. By hardware map, do you mean that you do the mapping outside of applications? Can Helix even see a caps-lock press as an event? If this is more of a discussion, maybe I should move this out of the issue tracker, but I've been trying to bring coworkers into the world of modal-editing, and an app having ergonomic defaults for common keyboards would reduce a friction I've had. |
Beta Was this translation helpful? Give feedback.
-
I map it either on the OS level, or on my programmable keyboards I change that in the firmware. That way it works in all applications. |
Beta Was this translation helpful? Give feedback.
-
That makes a lot of sense for consistency across applications. Unfortunately, in an office where developers don't have admin privileges, it is going to cause some adoption difficulty. I've been trying alt+x for a day or so and feels like a finger twister. I'll play around and see what I can find. Does anyone have favorites? |
Beta Was this translation helpful? Give feedback.
-
Same, I change it system wide. I swap escape and caps (since caps is almost never pressed). As well as left alt and left control (so left thumb for ctrl and right thumb for alt).
Try to get permission is the best choice I think. The admin shouldn't get in your way and let you do stuff in ways that is inconvenient for you. @archseer Should we have a tips section like this in the wiki? Seemed like quite a few of us have a similar setup (keyboard, japanese, different layout) but people new to helix might not. Or maybe I can just convert this to discussion? |
Beta Was this translation helpful? Give feedback.
-
I agree this is definitely more of a discussion (and I missed that this project was using the Discussions feature). I guess the only thing that would elevate it to "issue" is if there is concern that the out-of-the-box experience is hindered by requiring the installation of other tools for ergonomics. Having a compromise back-up might let someone explore what the editor brings to the table and if they want to invest more effort. I think the friendlier selection-verb approach of Helix/Kakoune is a way to introduce more GUI centric users to modal editing, and and an un-ergonomic return-to-normal keycode might make them miss the point.
I 100% agree with you, but I've definitely been in office environments where the idea of installing an executable that's mission is to read keypresses raises eyebrows. |
Beta Was this translation helpful? Give feedback.
-
New to helix here. To avoid reaching for the
I am getting the following error when hx starts. Does anyone know why?
|
Beta Was this translation helpful? Give feedback.
-
(use this trick described in this issue #2612 to fix one issue with such keybinds) [keys.insert] #ⓘ
'j' = {f='normal_mode','j'={'f'=[':insert-output /bin/echo -n j','move_char_right','normal_mode']}}
# 'hij' + 'jf' cleanly exits after typing 'hij' instead of typing an extra jf
# the char movement was needed because otherwise you end up 1 char left with insert and with append-output at the end of the line you get an insert at the wrong line
Below is a copy&paste of my description of this method from #2612 (comment) Another workaround is to use a good keyboard remapping tool (like Karabiner on a Mac) to implement the workaround I use for the lack of on-hold functionality: basically, make some key like i
However, this is limited by:
(you can also do it for a key chord like jf, but I think it's more bug-prone due to the aforementioned limitations) Mac example: [keys.insert] #ⓘ
'A-}' = 'normal_mode' # some unused inconvenient shortcut, ideally free in any mode Goku Karabiner config snippet :applications {:wezterm ["^com\\.github\\.wez\\.wezterm$"]}
:main [
{:des " 🠿i⃣ ⟶ Normal Mode ⇧⎇] (@WezTerm instead of @Helix)" :rules [:wezterm
[:i nil nil
{:alone {:key :i :halt true} :delayed{:canceled[:i]} :held{:key :⇧⎇】 :repeat false}
:params{:alone 254 :held 255 :delay 255} }]
]}
] |
Beta Was this translation helpful? Give feedback.
-
Relevant FAQ entry to use "jj" or "jk": Not sure if you'd ever want to insert "jj" or "jk", but if so, you can still do it with "jj" or "jk". |
Beta Was this translation helpful? Give feedback.
-
On many modern keyboards, the escape key is an awkward reach, and mine definitely pulls me off the home row. In Vim, I typically would use Ctrl-c to return to normal mode (even though there are some functionality differences). In the remapping docs, there is an example of mapping Alt-x to move from insert to normal mode. Is that the recommended approach, i.e. does the long-term key strategy leave Alt-x clear, or is it likely to be consumed by some other function?
I didn't see any references to it in the Keymap Brainstorm or in any previously closed issues. I apologize if this has been previously litigated.
Beta Was this translation helpful? Give feedback.
All reactions