-
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.
-
lsp-trouble.nvim
Discontinued 🚦 A pretty diagnostics, references, telescope results, quickfix and location list to help you solve all the trouble your code is causing. [Moved to: https://github.com/folke/trouble.nvim]
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
It doesn't seems to work :( it made the underline brown. The underline is less noticeable in other colorschemes though, that might be the problem? I'm using tokyonight.vim
Yeah, I might consider to switch back to CoC later. I was able to make a configuration which I'm comfortable with, it resembles CoC's behavior a bit, but I've found some sort of slowness in the startup process, like it sometimes takes a few seconds to load, sometimes a few diagnostics don't show. So far I have only tested it with rust-analyzer, let's see how everything goes. Anyways, I'm just giving the native LSP a try and also because of the hype I had with some plugins like lsp-trouble.nvim lol. And of course to make my neovim config to feel more lightweight. But maybe I should just wait that the LSP is mature enough.
Related posts
-
How to copy LSP diagnostics from folke/trouble to quickfix window?
-
Help with trouble.nvim
-
How can i get better looking errors?
-
How do I get neovim to only show LSP errors as underline squiggles and not in the gutter?
-
Is it possible to close todo-comment/trouble's floating window after pressing enter on an item?