NeoClear.lua
toggle-lsp-diagnostics.nvim
| NeoClear.lua | toggle-lsp-diagnostics.nvim | |
|---|---|---|
| 4 | 5 | |
| 9 | 95 | |
| - | - | |
| 3.0 | 4.2 | |
| about 1 year ago | 15 days ago | |
| Lua | 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.
NeoClear.lua
-
How do you turn off the yellow highlighting after your done with the search?
Then how about this: I created a plugin for this(initially), lol. Now I get used to .
- Treesitter Folding plugin from a month or so ago
-
sumneko_lua now supports code formatting!
If you ever encountered any problem related to tree-sitter folding issue, the author kindly made a hotfix for an issue I opened there. It's very lightweight https://github.com/nyngwang/NeoClear.lua,
- If your tree-sitter behave strangely on edit/undo, here is a workaround
toggle-lsp-diagnostics.nvim
- How do you turn off the yellow highlighting after your done with the search?
-
How can I hide the hint diagnostic messages (shown in white text) for only Python? Using nvim-cmp and Pyright.
For files I didn't write and trigger many errors I toggle just all diagnostics, I use a plugin for that https://github.com/WhoIsSethDaniel/toggle-lsp-diagnostics.nvim
-
How disable and reenable builtin LSP (client)
Are enable/disable fairly new (also show())? I don't remember them when I was writing [toggle-lsp-diagnostics](https://github.com/WhoIsSethDaniel/toggle-lsp-diagnostics.nvim). I recall having to use display() (which was and remains undocumented AFAIK). I know about the vim.diagnostic / vim.lsp.diagnostic name switch, but I don't recall these functions being available in 0.5.0. I suppose what I'm asking is "do I need to use display() if I want to support 0.5.0?"
-
How to toggle inline LSP warnings/errors
You can try https://github.com/WhoIsSethDaniel/toggle-lsp-diagnostics.nvim.
What are some alternatives?
highlight-current-n.nvim - Highlights the current /, ? or * match under your cursor when pressing n or N and gets out of the way afterwards.
lsp-trouble.nvim - 🚦 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]
folding-nvim
nvim-lspconfig - Quickstart configs for Nvim LSP
dotfiles - 💻 neovim, fish, tmux, git, homebrew - my whole world
nvim-highlite - A colorscheme generator that is "lite" on logic for the developer.
nvim-treesitter - Nvim Treesitter configurations and abstraction layer
nvim-dap - Debug Adapter Protocol client implementation for Neovim
vim-sensible - sensible.vim: Defaults everyone can agree on
null-ls.nvim - Use Neovim as a language server to inject LSP diagnostics, code actions, and more via Lua.
EmmyLuaCodeStyle - fast, powerful, and feature-rich Lua formatting and checking tool.
neovim - Vim-fork focused on extensibility and usability