nvim-lint
nvim-dap
Our great sponsors
nvim-lint | nvim-dap | |
---|---|---|
28 | 138 | |
1,578 | 4,771 | |
- | - | |
9.0 | 7.9 | |
9 days ago | 3 days ago | |
Lua | Lua | |
GNU General Public License v3.0 only | GNU General Public License v3.0 only |
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.
nvim-lint
-
Using nvim-lint as a null-ls alternative for linters
Personally, i think nvim-lint is the best alternative currently, specially so because it has no dependencies on external binaries. This guide assumes you already have your LSP set up with nvim-lspconfig (or an alternative like lsp-zero). You should also have an way to install the linters you are gonna need, i highly recommend Mason with mason-lspconfig.
-
This Week in Neovim #47: Archiving null-ls, native inlay hints, build.lua, flash.nvim, mini.files...
Try out https://github.com/mfussenegger/nvim-lint for linting tools, it integrates with nvim diagnostics module, might cover all use cases of null-ls for someone shopping around.
-
null-ls will be archived
People looking for alternative can check these projects: - nvim-lint - formatter.nvim
-
Does a language server replace ALE, syntastic, and the language plugin?
For linting, I would recommend nvim-lint. Again the same step as before, a little bit of setup code to register your linter and you're good to go!
-
ALE now supports Neovim's diagnostics API
This will be the third linting solution to make use of the [Neovim Diagnostic] module after null-ls and nvim-lint. All can co-exist, all have the pros and cons.
-
Linting with ALE with executables in virtual envs
I use nvim-lint (https://github.com/mfussenegger/nvim-lint), but I still don't know exactly how to achieve your goals with it. My hunch is that it should be somewhat straightforward, since Lua code could be used to provide the executable command (i.e. if in poetry project then cmd =poetry run ...else if ... then ... end)
- ALE alternative in Lua
-
Guide: Structuring Lua plugins
It's not obvious from the website, but this is the blog of GitHub user @mfussenegger, who is a Neovim core member, one of the primary maintainers of Neovim's LSP client implementation, and the other of several excellent plugins.
-
Code Linting
https://github.com/mfussenegger/nvim-lint works with the diagnostics API that was created after LSP was added, to allow non-LSP to use diagnostics API. Meaning you can see LSP and linting in the same interfaces if you use this API.
-
Improved Tcl support in Neovim
As part of my work-in-progress Neovim [plugin]([https://github.com/nat-418/tcl.nvim)(https://github.com/nat-418/tcl.nvim)) for Tcl development, I added support for Nagelfar syntax checking in the nvim-lint plugin. This provides inline checking for errors as seen in the attached screenshot. If anyone has any ideas on how to create a Tcl Language Server, or knows of a project already working on one, I would be very interested to know about it.
nvim-dap
-
I can't stand using VSCode so I wrote my own (it wasn't easy)
There are DAP extensions for both Vim (e.g. https://github.com/puremourning/vimspector) and NeoVim (https://github.com/mfussenegger/nvim-dap). I can't speak as to the experience in detail (I think I briefly played with nvim-dap a year or two ago), but I suspect that for most it will be good enough.
-
Can you get better dapui varibles?
https://github.com/mfussenegger/nvim-dap/issues/1062 https://github.com/mfussenegger/nvim-dap/issues/737
-
How to start using Neovim for c++ development and debugging
Also, you can set up debugger integration with https://github.com/mfussenegger/nvim-dap .
- Build and run in one task using asynctasks.vim
-
How can I debug Python code in neovim!
You could use nvim-dap with nvim-dap-python.
-
How to debug python code in neovim
I'd suggest starting with a Neovim distro that makes things work for you and as you get familiar you can transition to a more custom configuration as you see fit. If you want to do it by yourself then the most popular plugin for debugging in Neovim is nvim-dap and there is also an extension for Python to give you a more ready to go config instead of doing it yourself. You should read the docs of those 2 to see how you should customize accordingly your configuration.
-
How to configure vim like an IDE
(neovim only) nvim-dap
-
How to display variable values inline?
https://github.com/mfussenegger/nvim-dap + https://github.com/theHamsta/nvim-dap-virtual-text should be able to do it, I think?
- New Nightmare, the Hammerhead Worm
-
Q: Setting up typescript debugger for neovim?
If you want to debug types in TypeScript, you could use marilari88/twoslash-queries.nvim. If you would like to debug TypeScript/JavaScript code, then you need mfussenegger/nvim-dap, you could read this article: Debugging using DAP to understand how to set up it.
What are some alternatives?
null-ls.nvim - Use Neovim as a language server to inject LSP diagnostics, code actions, and more via Lua.
vimspector - vimspector - A multi-language debugging system for Vim
ale - Check syntax in Vim/Neovim asynchronously and fix files, with Language Server Protocol (LSP) support
LunarVim - 🌙 LunarVim is an IDE layer for Neovim. Completely free and community driven.
ESLint - Find and fix problems in your JavaScript code.
nvim-gdb - Neovim thin wrapper for GDB, LLDB, PDB/PDB++ and BashDB
diagnostic-nvim - A wrapper for neovim built in LSP diagnosis config
nvim-dap-python - An extension for nvim-dap, providing default configurations for python and methods to debug individual test methods or classes.
nvim-lspinstall - Provides the missing :LspInstall for nvim-lspconfig
CodeLLDB - A native debugger extension for VSCode based on LLDB
vscode-cpptools - Official repository for the Microsoft C/C++ extension for VS Code.