vim-which-key VS tokyonight.nvim

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.

Sounds like you want vim-which-key and coc.nvim.

> 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/

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.)

I think you mean a plugin which shows available key bindings as you type, which is what vim-which-key does.

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

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.

__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

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.

I have several production servers I work on that we use standard vim9 on to edit config files, etc. I love tokyonight.nvim and would love to be able to use it or something as close to it at possible with vim9, but have yet to be able to find anything. Any suggestions?

Tokyonight highlight file almost 1000 Lines

Looks like tokyinight.nvim.

This should come from DiagnosticVirtualTextError and usually the colorscheme you're using sets it. Check the documentation of your colorscheme to see if you can change highlight groups in your colorscheme or try to link the DiagnosticVirtualTextError to a different HighlightGroup or color. The colorscheme you're using seems to be linking DiagnosticVirtualTextError and keywords to the same HighlightGroup. Or you might try a different colorscheme which (hopefully) doesn't have problems like that. One I would suggest is Tokyonight, if you would like to check it out.

I think it 's tokyonight https://github.com/folke/tokyonight.nvim

So for tokyonight.nvim, when that folder is added to the rtp:

Tokyonight in dark mode

https://github.com/folke/tokyonight.nvim - my choice. Usually average 6 hours a day using it. Shell, nvim, etc.

looks like tokyonight