filemanager-plugin
vim-which-key
filemanager-plugin | vim-which-key | |
---|---|---|
2 | 25 | |
205 | 1,902 | |
- | - | |
0.0 | 6.0 | |
4 months ago | 4 months ago | |
Lua | Vim Script | |
MIT License | 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.
filemanager-plugin
-
Micro – a modern and intuitive terminal-based text editor
I tried Micro on for size for a few months earlier this year. I like it a lot, but stopped using it over time. Any time I reach for a text editor I kind of muscle memory open vim if it's something quick or VS code if it's a larger project.
Micro is like nano re-built for the 2020's. It feels really natural to use with sane key bindings and text selection. I like that it's written in Go and has a nice plugin framework. I might have used it more if a file manager / code tree off to the side was a built-in feature. I found a plugin that could do it, but I had some hassles with it iirc - https://github.com/NicolaiSoeborg/filemanager-plugin
-
Is there a cli text editor with VSCode bindings?
Except for the last two things, micro should support everything. There is a plugin for an explorer, but it seems to have problems with a current version of micro (https://github.com/NicolaiSoeborg/filemanager-plugin)
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?
micro-editor - A modern and intuitive terminal-based text editor
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.
FTerm.nvim - :fire: No-nonsense floating terminal plugin for neovim :fire:
bufferline.nvim - A snazzy bufferline for Neovim
toggleterm.nvim - A neovim lua plugin to help easily manage multiple terminal windows
tokyo-night-vscode-theme - A clean, dark Visual Studio Code theme that celebrates the lights of Downtown Tokyo at night.
VSCode-keybindings-for-micro-editor-and-tty - Visual Studio Code-like Keybindings for micro editor
emacs-which-key - Emacs package that displays available keybindings in popup
nvim-fzf - A Lua API for using fzf in neovim.
telescope.nvim - Find, Filter, Preview, Pick. All lua, all the time.
yori - Yori is a CMD replacement shell that supports backquotes, job control, and improves tab completion, file matching, aliases, command history, and more.
vim-rsi - rsi.vim: Readline style insertion