emacs-which-key
vim-which-key
Our great sponsors
emacs-which-key | vim-which-key | |
---|---|---|
37 | 25 | |
1,690 | 1,901 | |
- | - | |
7.8 | 6.0 | |
9 days ago | 3 months ago | |
Emacs Lisp | Vim Script | |
GNU General Public License v3.0 only | MIT License |
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.
emacs-which-key
-
Improving Emacs Isearch Usability with Transient
I think which-key already solves exactly that: https://github.com/justbur/emacs-which-key
-
Evil mode's kinda hacky
As for the "complicated keybindings general" -- I assume because remembering things like C-x C-s is hard because of the shifted keystrokes? I get that, and there is in fact a solution for less used keybindings which I love, called 'which-key' https://github.com/justbur/emacs-which-key
-
Should I start with vanilla Emacs?
I would recommend installing the which-key package, which is a fantastic discoverability aid. If you ever want an example config to get some inspiration, I have one here: Emacs Bedrock
-
Best emacs configs for Javascript and/or users who don't like to memorize keybindings?
Make sure you have which-key installed and turned on. When using a keybinding that has a prefix (like C-x or C-c), it displays all the keybindings that start with that prefix.
-
Doom -> vanilla emacs 29
which-key for the shortcut menus
-
Switched to Emacs a week ago, really thrilled so far. Looking for help on a few (somewhat advanced) questions.
there are some packages to help with the keybings, which-key shows a list of keybind and its command and (guru-mode)[https://github.com/bbatsov/guru-mode] enforces to use the "best" keybind, for exemple, it forces you to use C-n to move the cursor, blocking you to use the down key, and if you press the down key, it show a text in minibuffer to the best keybind.
-
Is anyone able to resize which-key side-window?
Thanks for confirming, I think it's an issue in which-key itself: https://github.com/justbur/emacs-which-key/pull/166
-
Too many keybindings
If you haven't already, definitely check out the package which-key.
-
Tell HN: Vim users, `:x` is like `:wq` but writes only when changes are made
> even though I'm a terminal user ... I really like the discoverability of GUIs, and that's where a good GUI is unbeatable by CLI.
CLI has poor discoverability? Sure; but even on the terminal, discoverability can still be good:
A couple of nice examples of discoverability in keyboard-focused programs:
- emacs' which-key[0]; there's a vim port[1] too. This shows you (some) of the available keybindings for the next input, and a short label. So you don't have to remember what `SPC h p ...` or all the options under `SPC f...`.. but it still helps to recall that `SPC h` is for 'help' related commands, `SPC f` for file related commands.
- emacs' magit[2][3]. Magit is so good at discoverability, that I'd rate it as the best tool for using git with. I've learned more about git from using it.
[0] https://github.com/justbur/emacs-which-key
[1] https://github.com/liuchengxu/vim-which-key
[2] https://magit.vc/
[3] https://emacsair.me/2017/09/01/magit-walk-through/
-
Creating and displaying cheatsheets of keybindings
Am I right in thinking this is quite similar to which-key?
vim-which-key
-
Vim distros: LunarVim, AstroVim, IdeaVim, … how they differ one each other?
The only Vim distro I'm aware of is SpaceVim (https://spacevim.org/). I just tested it for a short time but it couldn't compete with my hand crafted settings ;-) But I'm using some of the plugins of SpaceVim in my setup, eg. vim-which-key and vista.vim.
-
plugins for explorable interface and identifier highlighting
Sounds like you want vim-which-key and coc.nvim.
-
Tell HN: Vim users, `:x` is like `:wq` but writes only when changes are made
> even though I'm a terminal user ... I really like the discoverability of GUIs, and that's where a good GUI is unbeatable by CLI.
CLI has poor discoverability? Sure; but even on the terminal, discoverability can still be good:
A couple of nice examples of discoverability in keyboard-focused programs:
- emacs' which-key[0]; there's a vim port[1] too. This shows you (some) of the available keybindings for the next input, and a short label. So you don't have to remember what `SPC h p ...` or all the options under `SPC f...`.. but it still helps to recall that `SPC h` is for 'help' related commands, `SPC f` for file related commands.
- emacs' magit[2][3]. Magit is so good at discoverability, that I'd rate it as the best tool for using git with. I've learned more about git from using it.
[0] https://github.com/justbur/emacs-which-key
[1] https://github.com/liuchengxu/vim-which-key
[2] https://magit.vc/
[3] https://emacsair.me/2017/09/01/magit-walk-through/
- Is there a way to get a cheatsheet on-screen like nano has?
-
A Vim Guide for Advanced Users
Agreed, that's the only time I find missing Emacs' which-key. (Looks like there is https://github.com/liuchengxu/vim-which-key for this.)
-
Navigate through options of Plugins
I think you mean a plugin which shows available key bindings as you type, which is what vim-which-key does.
-
Helix: Post-Modern Text Editor
Just an extension.
It is https://github.com/liuchengxu/vim-which-key if you are interested.
>Were you also able to replicate the small popups that open when you press `m`, `g`, etc.?
Yes, although 'm' has a totally different meaning in vim (placing a mark), so there is no popup for that. But it works where there are actually sensible choices, even for marks it works and shows you every available one, which is pretty cool
-
Vim, infamous for its steep learning curve, often leaves new users confused where to start. Today is the 10th anniversary of the infamous "How do I exit Vim" question, which made news when it first hit 1 million views.
But again, that's not a specifically vim issue, its endemic to TUIs (hence bash completions and all the other hacks to make discoverability accesible). As well, there are some projects to ameliorate this in vim like the which-key family of plugins01 and others like them.
-
Is my understanding of Vim and Emacs correct?
__usability features__ Emacs has a lot of great ideas for usability, some of which have been copied to vim like which-key https://github.com/folke/which-key.nvim https://github.com/liuchengxu/vim-which-key
-
What is the biggest barrier of entry for learning vim?
Printing cheat sheets is helpful. At some point, make your own. which-key.nvim (or vim-which-key) is a plugin I wish I had found years ago. It gives you hints of next keys available to press. It's great for beginners, and experts. It's like the ultimate real-time cheatsheet.
What are some alternatives?
hydra - make Emacs bindings that stick around
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.
tokyonight.nvim - 🏙 A clean, dark Neovim theme written in Lua, with support for lsp, treesitter and lots of plugins. Includes additional themes for Kitty, Alacritty, iTerm and Fish.
bufferline.nvim - A snazzy bufferline for Neovim
k9s - 🐶 Kubernetes CLI To Manage Your Clusters In Style!
tokyo-night-vscode-theme - A clean, dark Visual Studio Code theme that celebrates the lights of Downtown Tokyo at night.
use-package - A use-package declaration for simplifying your .emacs
telescope.nvim - Find, Filter, Preview, Pick. All lua, all the time.
general.el - More convenient key definitions in emacs
vim-rsi - rsi.vim: Readline style insertion
evil-collection - A set of keybindings for evil-mode
hydra.nvim - Create custom submodes and menus