Frequency-based keymap modiƒew

[eugenesvk]

full info here

I'd like to show&tell about the modiƒew keymap that tries to break the chains ⛓ of dubious keycap-based mnemonics like f for find (or is it forward?) and instead maps the most frequent commands to the best keys, so f=👆🏻 moves forward by a word instead
It also attempts to convert most of the commands requiring modifiers into a chainable key sequence, hence its name: "few modifiers based on frequency(ƒ)" or modiƒew

Some of the design improvements:

• ⌂ Home keys are safe: all 8 of the home keys are movement commands, so to modify a buffer your fingers need to leave ⌂!
• Insert mode has a copy of most of the Normal mode commands (from key and ⇧key) on the sames keys, but with an extra ⌥ — no need to switch modes for just a single command!
• Space mode converts most of the commands requiring modifiers into a chainable key sequence with a "leader" key Space as the easiest to press. Its main layer mostly consists of commands that were assigned to ⎈ or ⇧ in the Normal mode, though via additional submodes any other command can also be chained (and if this feature request is implemented, this approach could also work nicely with repeatable commands that would not close the menu dialog command list upon execution)
• Differentiate between repeatable and single-press paired keybinds (left/right, back/forward, earlier/later etc.)
  • Repeatable keybinds should be on separate adjacent keys (just like ◀▶) instead of being on the same key with the second operation behind a ⇧’ed status, so char/word/line-based movements and in-/decrement are together rather than being on separate rows by default. This greatly simplifies going back and forth:
  • Single-press paired keybinds can remain with the opposite direction ⇧’ed, e.g. move to the beginning/end of a line a⭰ ⇧a⭲
• Bonus: the Cut/Copy/Paste commands' frequencies seem to allow having them together under 💍🖕👆 left hand bottom row with the common xcv, though Undo is too frequent to be left at a 🤙z (however, with ⎈ they all maintain the zxcv compatibility)

Now, to the layout itself: while it might be intimidating at first with all the icon jazz, it's a great reference point as you get used to it as you can get all the commands per mode in a single cheat sheet (the config file has the same icons to make the lookup a bit easier)

The full description of the design principles with all the modes (images and html layouts) as well as the config itself (and a tip on how to make updating it less of a chore) at this page https://eugenesvk.github.io/kbdHelix/

[well1791]

finally someone decided to do what actually makes sense!

[willfaught]

I read this post and your page, but I don't understand what the actual keymap is. What does "p" do, for example? Can you explain what the symbols mean?

[eugenesvk]

p opens the View sub-menu ☰👁
⇧p opens the same View sub-menu, but with a sticky mode ☰👁ₛ (this is not yet supported by Helix, see issue)
⎇p ensure_selections_forward which flips selection forward: cursor after anchor

You can hover over a button (or press the button on a keyboard with ⇧) to see a tooltip like this that lists the command names:

But these tooltips don't show command descriptions and they also don't work for custom command sub-menus like View since Helix doesn't support custom group names (see issue and issue), so for your example of p the tooltip is less helpful

However, you're not supposed to magically understand all this icon soup just by looking at it, these are cheat sheets, so they are meant to support you after you've got some understanding of the config itself, so the more basic way of learning is reading the config file, it groups commands by functon, for example:

• open the full config or the template for just the Normal mode at the #Ⓝ Move section
• keep the normal mode cheat sheet side-by-side
• read the config with comments on what some commands do and then match them to the cheat sheet buttons
• after some use you might only need the cheat sheets (with tooltips) to start associating ☰ with sub-menus and ☰👁 with a View sub-menu (that's what the eye is for)

Also you can search for 'p' or the ☰👁 icon in the config file to see what command it maps to and what that command does

[willfaught]

If the symbols aren't meant to explain your proposal, then can you give concrete examples of your general design improvements? For instance:

⌂ Home keys are safe: all 8 of the home keys are movement commands, so to modify a buffer your fingers need to leave ⌂!

What are the actual keys that you're referring to here (I count 11 keys on my QWERTY keyboard home row, not counting caps lock and return), and what do they do? And what do the other keys do instead? I don't want to hunt through code to figure this out, that's what posts like this are supposed to explain/summarize.

Insert mode has a copy of most of the Normal mode commands (from key and ⇧key) on the sames keys, but with an extra ⌥ — no need to switch modes for just a single command!

I don't follow what this means concretely. Do you mean that "w" from Normal mode somehow works in Insert mode too? How does that work if "w" inserts the letter w in insert mode? What does "with an extra [option key]" mean in this context? Are you saying that when in insert mode, you can have all the same normal mode commands by pressing [option key] first and then performing them?

Differentiate between repeatable and single-press paired keybinds (left/right, back/forward, earlier/later etc.)

Can you give an example? What scenario would be better in this case?

Edited

[eugenesvk]

If the symbols aren't meant to explain your proposal

Of course they are, that's why 🢔ω (move left by short word) represented with a left arrow and a letter resembling w in word, and big words are W so it's easier not to confuse

• ω and
• W vs
• w

they are just not meant to explain everything

, then can you give concrete examples of your general design improvements? For instance:

⌂ Home keys are safe: all 8 of the home keys are movement commands, so to modify a buffer your fingers need to leave ⌂!

What are the actual keys that you're referring to here (I count 11 keys on my QWERTY keyboard home row, not counting caps lock and return)

You only have 8 fingers on that row, their resting positions are 8 home keys

, and what do they do?

This is listed just 2 paragraphs below on the page (except for s), but the only summary part relevant to this design improvement is that it's not a destructive command! Otherwise it doesn't matter what the keys do, it matters for other design reasons, e.g., repeatable commands are co-located, that's why home keys with repeatable commands are listed in those other sections. But otherwise it just follows that frequent commands get to frequent keys, which explains why s is missing, the frequency principle has already been illustrated with other commands

And what do the other keys do instead?

which other keys?

I don't want to hunt through code to figure this out, that's what posts like this are supposed to explain/summarize.

Which it does - summarize. I mean, what you're essentially asking for is not summary, but to list all key, but then just the 8 home keys represent >20 commands if we count the modifiers and even more if we count other modes.
And that's exactly what the config file is — it's not code, but the full list of keys with commands and comments on what they do, you can read it from top to bottom instead of hunting, that's why it has comments and symbols in there and commands are grouped into sections!
The hunting comes later when you only need to check one key here and the tooltip (which lists commands, but not descriptions) is not enough. Or if you want to look up p instead of reading the section #Ⓝ Minor modes / menu dialogs which explains that View mode is mapped to p

(I'd like to add the descriptions to the tooltips as well as they can be more useful vs. just the command name, but these are harder to parse since this less structured data in the comments instead of key properties due to the limitations of Helix's config format, see this issue)

Insert mode has a copy of most of the Normal mode commands (from key and ⇧key) on the sames keys, but with an extra ⌥ — no need to switch modes for just a single command!

I don't follow what this means concretely. ... Are you saying that when in insert mode, you can have all the same normal mode commands by pressing [option key] first and then performing them?

So you do understand!

Differentiate between repeatable and single-press paired keybinds (left/right, back/forward, earlier/later etc.)

Can you give an example?

There are two sections (repeatable/single-press) with half a dozen examples. Have you checked the full info here page?

What scenario would be better in this case?

The scenario where you use them repeatedly to go back and forth as also explained in the linked page:

so char/word/line-based movements and in-/decrement are together rather than being on separate rows by default. This greatly simplifies going back and forth

[alexeymuranov]

A somewhat related/alternative/complementary idea: #9896.

[julien-h2]

Hey guys, great idea! I love it.

I note though, I think word-based navigation is outdated and should be deprecated. I would expect a modern keymap to provide a more modern way.

Word are quite arbitrary. They are well adapted for plaintext navigation but not so much when programming for instance.

I don't pretend to know what it the best solution here but I have found that jump to char (vim f) is more precise and faster than typing word/word/word... Also jump to char pair is very effective for navigating accross lines. this is extremely well implemented in flash.nvim because they make it repeatable, visually highlighted, and add optional labels to jump to the n-th match immediately.

[kirawi]

In Helix, navigation can be done through the syntax tree in addition to normal movement commands. It is limited but we have issues for expanding tree-sitter commands. The initial jump mode PR also included jumping to tree-sitter nodes, but I think this was deferred to the plugin system to not complicate the feature.