md2vim
lsp-trouble.nvim
| md2vim | lsp-trouble.nvim | |
|---|---|---|
| 5 | 4 | |
| 73 | 384 | |
| - | - | |
| 0.0 | 6.7 | |
| almost 2 years ago | almost 3 years ago | |
| Go | Lua | |
| 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.
md2vim
-
Vim doc to markdown
I'm writing markdown documentation and converting it to vim doc via https://github.com/FooSoft/md2vim. Here's an example:
-
[vent] I really hate that most neovim plugins don't provide docs...
There are utilities such as https://github.com/FooSoft/md2vim that can convert between markdown and vimdoc. One could keep documentation in the readme and then use this to convert to vimdoc?
- Feline.nvim version 0.1 released
-
LSP Trouble: A pretty diagnostics list to help your solve all the trouble your code is causing.
You might be interested in md2vim , babelfish.nvim :)
-
Noticing a lot of new *.nvim plugins do not have help files
md2vim
lsp-trouble.nvim
-
Trouble: Just pushed a big update with support for lsp references, location lists and quickfix lists
Just added Telescope actions support. Works with any search results in Telescope. Pretty cool :)
-
How to change icons and colors, to make my LSP diagnostics look better?
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.
-
LSP Trouble: A pretty diagnostics list to help your solve all the trouble your code is causing.
I created a little plugin that shows a pretty list of LSP diagnostics.
What are some alternatives?
nvim-hclipboard - Hijack your clipboard in Neovim
trouble.nvim - 🚦 A pretty diagnostics, references, telescope results, quickfix and location list to help you solve all the trouble your code is causing.
lualine.nvim - A blazing fast and easy to configure Neovim statusline written in Lua
toggle-lsp-diagnostics.nvim - Neovim plugin for toggling the LSP diagnostics.
nvim-libmodal - Create new "modes" for Neovim!
lspsaga.nvim - improve neovim lsp experience [Moved to: https://github.com/nvimdev/lspsaga.nvim]
panvimdoc - Write documentation in pandoc markdown. Generate documentation in vimdoc.
nvim-lsp-smag - Seamless integration of language server locations into NeoVim
tree-sitter-lua - Neovim Tree Sitter Lua Grammar & Library
bufferline.nvim - A snazzy bufferline for Neovim
nvim-lua
nvim-lspfuzzy - A Neovim plugin to make the LSP client use FZF