emacs-which-key VS tokyonight.nvim

I think which-key already solves exactly that: https://github.com/justbur/emacs-which-key

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

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

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.

which-key for the shortcut menus

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.

Thanks for confirming, I think it's an issue in which-key itself: https://github.com/justbur/emacs-which-key/pull/166

If you haven't already, definitely check out the package which-key.

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

Am I right in thinking this is quite similar to which-key?

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