helix-vim
which-key.nvim
helix-vim | which-key.nvim | |
---|---|---|
27 | 115 | |
860 | 4,501 | |
- | - | |
2.0 | 5.4 | |
3 months ago | 6 days ago | |
Lua | ||
- | Apache License 2.0 |
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.
which-key.nvim
-
Modeless Vim
There is a well known plugin for neovim to do this kind of behavior. You can even create your own hotkeys into that plugin and will help you navigate and memorize different hotkeys for the editor. The plugin is called whichkey, and this is their github https://github.com/folke/which-key.nvim
-
Visual Mode Issue + startuptime optimization
The menu most certainly comes from folke/which-key.nvim. Take a look into part of your config which sets it up.
-
How to Transform Vim to a Complete IDE?
By default, most of nvim packages have WhichKey plugin which shows popup with available commands. For instance, you press space or g and what for a second:
-
My Favorite Vim Oneliners for Text Manipulation
One of the recent innovations in the Vim space that I've appreciated a lot is which-key by folke for Neovim: https://github.com/folke/which-key.nvim
It makes keybindings in vim discoverable, it's quite magical. For example, press g and get a table of all the various commands that follow from there. Press mapleader and get a table of various commands from there, etc.
-
LazyVim
>The problem with that is that for some rarely used action one forgets...
Install https://github.com/folke/which-key.nvim and you will always have a popup that will tell you what keys to use next.
-
Resources for mastering vim motions
https://github.com/folke/which-key.nvim - it's like a cheat sheet in neovim!
- Is there a way to confine key remapping to particular files (.tex)?
-
Set it and forget it plugins?
folke/which-key.nvim will help with you with your key maps.
-
Named registers populated by unrecognized content
I recently started actively using which-key plugin that shows the contents of all registers when pressing ".
-
Should I learn lua? I am a vs code power user, which prevents me from completely adapting neovim, since I always find something is missing in neovim.
3) I'd recommend using Telescope, more specifically, :Telescope keympas. There's also which-key, which might be more intuitive, but I haven't used it.
What are some alternatives?
helix - A post-modern modal text editor.
NvChad - Blazing fast Neovim config providing solid defaults and a beautiful UI, enhancing your neovim experience.
zsh-vi-mode - 💻 A better and friendly vi(vim) mode plugin for ZSH.
vim-which-key - :tulip: Vim plugin that shows keybindings in popup
meow - Yet another modal editing on Emacs / 猫态编辑
LunarVim - 🌙 LunarVim is an IDE layer for Neovim. Completely free and community driven.
telescope.nvim - Find, Filter, Preview, Pick. All lua, all the time.
emfy - A dark and sleek Emacs setup for general purpose editing and programming
nvim-tree.lua - A file explorer tree for neovim written in lua
dance - Make your cursors dance with Kakoune-like modal editing in VS Code.
rest.nvim - A fast Neovim http client written in Lua