ale
nvim-lint
Our great sponsors
ale | nvim-lint | |
---|---|---|
133 | 28 | |
13,235 | 1,507 | |
0.6% | - | |
8.8 | 9.0 | |
2 days ago | 7 days ago | |
Vim Script | Lua | |
BSD 2-clause "Simplified" License | 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.
ale
-
A decent VS Code and Ruby on Rails setup
I saw no mention of RBS+Steep, the latter providing a LSP. I use it a lot and very much like it, although it's still young and needs love, but it's making good, steady progress! I've been very pleasantly surprised by some of the crazy things Steep can catch, completely statically!
You appear to be working on projects with Sorbet (which I tried to like but found it fell short in practice, notably outside of the app use case i.e it's mostly useless for gems) so it may be a tall order to try on those. Maybe you can give RBS+Steep a shot on some small project?
RBS: https://github.com/ruby/rbs
RBS collection (for those gems that don't ship RBS signatures in `sig`, integrates with bundler): https://github.com/ruby/gem_rbs_collection
Steep: https://github.com/soutaro/steep
VS Code: https://github.com/soutaro/steep-vscode
Sublime Text: https://github.com/sublimelsp/LSP
Vim (I'm working on it): https://github.com/dense-analysis/ale/pull/4671
-
Laravel code-quality tools
Support for code quality tools are provided by the ALE plugin. These are supported for PHP:
-
Embracing Common Lisp in the Modern World
I mostly agree, though I find Allegro and LispWorks severely lacking in areas too. The companies themselves don't seem to care much about their IDEs. Certainly not in the way JetBrains cares about IntelliJ.
Tucked away in the McCLIM project is Clouseau, which you can quickload and use as a normal user: https://codeberg.org/McCLIM/McCLIM/src/branch/master/Apps/Cl... One small cool thing it does is if you inspect a complex number it will also draw a little x-y vector. (Though trying it out again just now it's overlapping with the text... maybe I should file a bug, but I've only now just learned they moved off github, and I'm not going to make a codeberg account. Friction wins this round.) It does take a while to first compile and load all the dependencies, especially 3bz, another weakness of at least our free Lisps; AFAIK there's still no equivalent of make -j for compiling systems.
I'm a happy vim user (though there is some jank with slimv, admittedly, but it's mostly prevalent around multiple thread situations) and setup the command ,ci to call my own clouseau-inspect function; it just inspects a symbol with clouseau instead of slimv's inspector. Also have a janky watch/unwatch pair of functions that just refreshes the inspector every second. (https://github.com/Jach/dots/blob/master/.sbclrc#L113 if curious, some other junk in .swank.lisp and .vimrc too, and there's https://github.com/dense-analysis/ale/issues/4061 to call sblint on your project...)
But better forms of these sorts of graphical tools are what I hope to one day see more of and are how the free Lisps can close the gap in this area with the commercial Lisps. I believe there's not much Allegro can do that poking around SBCL can't do, but for many things it's just nicer to have a GUI. Want to explore all the symbols and values in a package? Easy enough to script that, but not as nice as just having a table of symbols, and even nicer if you can set watches on some of them. None of the tools need to be tightly integrated with a single IDE either, because all the stuff necessary to debug Lisp is in the running Lisp itself. It's just that the GUI situation continues to suck.
LSP has gotten more popular with other languages and editors, sometimes I wonder if the acronym was made as an inside joke because it's basically how Lisp + Slime/Swank have worked...
-
Static Analysis Tools for C
A similarly useful list is vim's famous ALE plug-in's list of supported linters:
* https://github.com/dense-analysis/ale/blob/master/supported-...
While less comprehensive¹, this is my go-to list when I start working with a new language. Just brew/yum/apt installing the tool makes it work in the editor²
¹this list mostly has foss,static analyzers, however anyone can contribute (mine was the gawk linting)
²alright,there are some. Tools that might need some setup
-
LazyVim
FWIW, I still use regular vim with ale [0] and it does everything I want. It formats files with Black and isort, shows ruff and pyright errors, supports jumping to definitions, and has variable information available on hover. I have collected my config over the past several years, but I pretty rarely encounter errors with it.
[0]: https://github.com/dense-analysis/ale [1] https://github.com/CGamesPlay/dotfiles/blob/master/files/.co...
-
How to configure vim like an IDE
At some of those syntax things neovim behaves better, and like. But there is https://github.com/dense-analysis/ale.
-
Vim users who work without any plugins, how does your vimrc look like?
I replace ALE with :!, like :! %. If the linter output is compatible with default errorformat , then I do :! % > /tmp/linter.txt then :cgetfile (or in one-go: :cgetexpr systemlist(''))
-
Vim or Emacs for C++ Coding?
I use vim for C++ coding, however it is a bit difficult to set up to make it productive. I use YouCompleteMe [0] for autocompletion, Vimspector [1] with the C++ plugin for debugging, ALE [2] for linting, along with a few other general plugins (such as NerdTREE for file view).
[0] https://github.com/ycm-core/YouCompleteMe
-
⚡ Neural - AI Code Generation for Vim
Disclaimer: Be mindful that the results may be unpredictable and the code generated should be carefully evaluated for correctness before use in production systems! Use a linting tool such as ALE to check your code for correctness.
-
Minimal setup for shellcheck as a compiler in Vim for linting bash scripts.
If you are interested in alternatives the ALE plugin https://github.com/dense-analysis/ale can automatically detect if tools like shellcheck are installed and will just magically lint your files continuously in the background with nice highlighting. Worth a look!
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.
-
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.
-
How to do syntax checking on languages that don't have an LSP server in neovim?
You could use null-ls as an interface between Neovim LSP client and this kind of tools. If this tools are linters, you could also use nvim-lint
-
rust-analyzer autocmd error AND custom nvim-lint error with cargo check
I have both https://github.com/simrat39/rust-tools.nvim and https://github.com/mfussenegger/nvim-lint configured and I started noticing something that was working before had suddenly become broken, and it's not clear what changes I've made to my config (https://github.com/Integralist/dotfiles/tree/main/.config/nvim) that would have caused this error.
What are some alternatives?
vim-lsp - async language server protocol plugin for vim and neovim
coc.nvim - Nodejs extension host for vim & neovim, load extensions like VSCode and host language servers.
YouCompleteMe - A code-completion engine for Vim
null-ls.nvim - Use Neovim as a language server to inject LSP diagnostics, code actions, and more via Lua.
nvim-lspconfig - Quickstart configs for Nvim LSP
syntastic - Syntax checking hacks for vim
vim-polyglot - A solid language pack for Vim.
neoformat - :sparkles: A (Neo)vim plugin for formatting code.
neomake - Asynchronous linting and make framework for Neovim/Vim
vim-lsp-cxx-highlight - Vim plugin for C/C++/ObjC semantic highlighting using cquery, ccls, or clangd
rust-analyzer - A Rust compiler front-end for IDEs [Moved to: https://github.com/rust-lang/rust-analyzer]
ESLint - Find and fix problems in your JavaScript code.