dotfiles
helix-vim
Our great sponsors
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
dotfiles
- Notes on Text Editing
- Notes on Text Editing: Why Modality and Chording?
-
Helix: Release 23.03 Highlights
I vastly prefer Vim's way of action+selection to kakoune's selection+action. Tried kakoune in the past for a few days and this decision was constantly getting in my way.
Here is a short write-up (not mine) about why kakoune model is not that appealing: https://github.com/noctuid/dotfiles/blob/master/emacs/editin...
- Why Not Kakoune?
helix-vim
-
Notes on Text Editing
I tried to re-learn from Vim to Helix but failed. No sure if this is a muscle memory problem or perhaps article is right about cons Kakoune-like approach for me. Even adapting with something https://github.com/LGUG2Z/helix-vim did not work. So if you like Helix it probably a good thing that you did not learn the vim at the time.
- Helix-Vim (Readme.md)
- Ask HN: Should you add a LICENSE to example configuration repos?
- Keymap and configuration questions
-
Even more hindsight on Vim, Helix and Kakoune
Not that they're inherently worse, just different - I'm perfectly happy with vim motions and relearning to type is pretty low on my list of priorities. Luckily there is a compatibility hack, not perfect but it's close enough: https://github.com/LGUG2Z/helix-vim
- What editor are you using for Rust?
-
Helix: Release 23.03 Highlights
I want to like Helix, I really, really want to. It's lean, fast, polished, purely console based so it fits my workflows perfectly... but the almost-like-vim-but-not-really key bindings are a deal breaker. I just can't make the switch.
If Helix were completely different in this regard, like Emacs is, I could handle--and I know because I use both vim and Emacs regularly pretty fluently. But Helix is way too close to the vim keybindings to discern it from a memory muscle perspective. I use vim keybindings everywhere else (zsh, all readline-based apps via a setting in ~/.inputrc, VSCode), so getting used to slight differences in just one editor is extremely hard because I can't just drop all other apps.
I recently tried this: https://github.com/LGUG2Z/helix-vim which attempts to provide vim mappings to Helix. It's funny how the description in the page describes my progression almost 100%. And while it makes things slightly better, it's still not accurate enough to make this a non-issue.
-
Helix editor 23.03 released!
https://github.com/LGUG2Z/helix-vim somebody on the internet has you covered
- How to config default VIM keys?
-
The extensible vi layer for Emacs
There is this configuration: https://github.com/LGUG2Z/helix-vim
This switches most keybinds to be vi-like.
What are some alternatives?
copilot.el - An unofficial Copilot plugin for Emacs.
helix - A post-modern modal text editor.
vis - A vi-like editor based on Plan 9's structural regular expressions
zsh-vi-mode - 💻 A better and friendly vi(vim) mode plugin for ZSH.
meow - Yet another modal editing on Emacs / 猫态编辑
LunarVim - 🌙 LunarVim is an IDE layer for Neovim. Completely free and community driven.
emfy - A dark and sleek Emacs setup for general purpose editing and programming
dance - Make your cursors dance with Kakoune-like modal editing in VS Code.
neovim - Vim-fork focused on extensibility and usability
which-key.nvim - 💥 Create key bindings that stick. WhichKey is a lua plugin for Neovim 0.5 that displays a popup with possible keybindings of the command you started typing.