It is currently expected that UIs will figure out when to hide msg_history_show messages by themselves.

I think this is bad for two reasons:

• It makes UIs less similar, increasing the number of things to learn when going from one UI to another.
• It makes UIs different from the TUI, which offers a press ENTER prompt when the time to hide msg_history_show messages has come.

After [di

Hi! Thanks for the application. It looks promising. I found a little annoyance that took some time to investigate. I used neovim-qt and everything was fine. When I switched to neovide, everything worked smoothly except the colors were weird. After digging the issue, I realized that I have to add set termguicolors to init.vim to make colors nice. But why neovim-qt does not need it? `Neovi

Hi,

When I run my tests using the neovim strategy, it opens a new terminal but auto focus on the buffer. Then I have to press <C-o> to not close the buffer and go back to my split pane.

Is there a way to have it open but not switch my focus to the newly opened pane automatically?

While I quite like the information readily provided by g:lsp_diagnostics_float_cursor and g:lsp_diagnostics_echo_cursor, their automatic nature doesn't fit my workflow.

Would it be difficult to add an avenue to trigger them on-demand, similar to <plug>(lsp-hover) / :LspHover?

Along similar lines, would it be difficult to add a g:lsp... setting to have <plug>(lsp-next-diganostic)

Difficulty doing initial setup of the plugin
3rd party description of setup steps:
https://atlas-vim.readthedocs.io/vim/plugged/vim-ctrlspace/README/

• convert to plugin vim docs?
• create wiki pages on this repo?