helix-vim
Vim
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.
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.
Vim
- The IDEs we had 30 years ago and we lost
- The Loneliness of the Mid-Level Vimmer
-
Multiple Notepad++ Flaws Let Attackers Execute Arbitrary Code
I find the Vim extension for VS Code has macro support that is good enough for most of my use cases (if you’re a fan of Vim key bindings - obviously).
https://github.com/VSCodeVim/Vim/blob/master/ROADMAP.md#repe...
-
VSCode with Neovim?
that's why I just use https://github.com/VSCodeVim/Vim if I have to use VSCode
-
Can i change a with i and vice versa in command mode.
They have discussions enabled on the GitHub repository; eventually r/vscode might be of help.
-
Neovim vs VSCode Neovim - what are the tradeoffs?
What you would learn from using a neovim addon for VS Code covers most of the first point and some of the second - VSCode Vim lets you run neovim in a headless mode that relays keypresses to it, and emulates several popular addons. It also comes without quite as much hassle as comes from the second step of learning to configure vim/neovim yourself. Most VSCode extensions work pretty well out of the box, maybe requiring you to add the path to a compiler/interpreter that is not on your PATH.
-
Vim extension for VS Code lacks "virtualedit" option and cursor doesn't reach the end
The extension does have visualedit. You can check the list of supported features here: https://github.com/VSCodeVim/Vim/blob/HEAD/ROADMAP.md
-
How to achieve VSCode's vim like jsx and imports folding in doom emacs
I though VSCode's vim emulation had issues with code folding
-
I'm stuck between CB-GK-16 and 617, I like 617 more cause it looks better. Now the situation is I'm a programmer, I don't mind learning new bindings but is it worth it? If you have any experiences that would help me, please share them with me :)
Either I go with K552 or save for RK84 if not CB-GK-16 and both of these are pretty good choice that's certain, or I go with 617 Fizz and use VIM keybinding which Isn't an issue for me cause I've been using NeoVim for more than 1 year, you can grab my dotfiles if you want. Most people won't go with 60% cause they are used to arrow, home, end ... keys so am I with vs code but today I found out about vscodevim extension which enables vim keybinding , these keybindings pretty easy to use more than arrow, home, end .. keys if yo're a vim user like Shift + $ = end, Shift + 0 = home, in visual mode V to select text etc ...
- Undo (“u”) stopped working as intend – Issue #8157 – VSCodeVim/Vim
What are some alternatives?
helix - A post-modern modal text editor.
vscode-live-server - Launch a development local Server with live reload feature for static & dynamic pages.
zsh-vi-mode - 💻 A better and friendly vi(vim) mode plugin for ZSH.
vscode-neovim - Vim mode for VSCode, powered by Neovim
meow - Yet another modal editing on Emacs / 猫态编辑
NvChad - Blazing fast Neovim config providing solid defaults and a beautiful UI, enhancing your neovim experience.
LunarVim - 🌙 LunarVim is an IDE layer for Neovim. Completely free and community driven.
SpaceVim - A community-driven modular vim/neovim distribution - The ultimate vimrc
emfy - A dark and sleek Emacs setup for general purpose editing and programming
vimrc - The ultimate Vim configuration (vimrc)
dance - Make your cursors dance with Kakoune-like modal editing in VS Code.
coc-java - Java extension for coc.nvim