You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Helix has this nice feature of cascading themes where you can refer to one of many supplied themes and only override the few colors that you don't like (but no one stops you from overriding/rewriting all the colors!)
Keybindings are arguably even more important that colors, so I'd suggest Helix to have a similar architecture:
Include a bunch of named "keybinding themes"
Allow users to refer to a keybinding theme via some inherit_keybinds = "vim_compat_mode" (or you could have a second version field ["vim_compat_mode","2.5"]
This has a few strong benefits:
Partially addresses the fundamentally unsolvable issue of different people requesting different keybinding defaults, so e.g., you could have a strict "vim-compatibility theme" that wouldn't require much learning from people coming from vim and is also easier that trying to find & copy&paste a config
Allows to continuously improve the default keybinds and not get stuck forever with the original h◀ mistakes since Helix can always carry the diffs with the default keybinding from old version 22.08, and any user upgrading and hating the changes introduced in version 23.03 can simply change a couple of numbers in his config to retain the old ones
Similarly, allows users to get updates from a given theme that you haven't overriden/pinned to a version once new/better commands become available
This discussion was converted from issue #6584 on July 26, 2023 15:04.
Heading
Bold
Italic
Quote
Code
Link
Numbered list
Unordered list
Task list
Attach files
Mention
Reference
Menu
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Helix has this nice feature of cascading themes where you can refer to one of many supplied themes and only override the few colors that you don't like (but no one stops you from overriding/rewriting all the colors!)
Keybindings are arguably even more important that colors, so I'd suggest Helix to have a similar architecture:
inherit_keybinds = "vim_compat_mode"
(or you could have a second version field["vim_compat_mode","2.5"]
This has a few strong benefits:
22.08
, and any user upgrading and hating the changes introduced in version23.03
can simply change a couple of numbers in his config to retain the old onesBeta Was this translation helpful? Give feedback.
All reactions