Support for code quality tools are provided by the ALE plugin. These are supported for PHP:. - Source: dev.to / 3 months ago
Hello Everyone! W0rp here. I thought I'd ask on Reddit if there's anyone out there would like to help maintain ALE. It would be nice to have another willing volunteer who is up for providing relevant feedback on PRs, answering common questions, merging good PRs, and managing GitHub issues. I'll mention to anyone interested that I have a general policy of never closing issues, no matter how old, unless they are... Source: 6 months ago
Ctrl-X Ctrl-L is line based completion, see :help CTRL-X_CTRL-L for details. :help ins-completion gets the useful docs, Vim's own docs are very good and worth spending some time learning how to use, so you can learn Vim itself better. Another favorite of mine is 'gf' to open the filename under the cursor, very useful combined with ^X ^F. Omni completion is also useful: https://vim.fandom.com/wiki/Omni_completion... - Source: Hacker News / 7 months ago
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. - Source: Hacker News / 10 months ago
At some of those syntax things neovim behaves better, and like. But there is https://github.com/dense-analysis/ale. Source: 10 months ago
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('')). Source: 11 months ago
You might need a formatter to do this, take a look at ALE, but I would suggest just get used to the format your team prefers. Source: 12 months ago
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 [2] https://github.com/dense-analysis/ale. - Source: Hacker News / about 1 year ago
I typically use mypy. It's been around for over a decade, is available in many package repos, and has pretty good integration with vim lint plugins such as ALE (https://github.com/dense-analysis/ale). - Source: Hacker News / about 1 year ago
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. Source: about 1 year ago
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! Source: about 1 year ago
To replace coc and ale, you'll probably need to install more than two plugins. Neovim is in fact well known for its built-in LSP, which can be configured in many ways. The quickest one is by using lsp-zero, which sets up automatically language servers and autocompletion, without you having to write everything on your own. Alternatively, you can manually set up mason, nvim-cmp, null-ls and more, to achieve a... - Source: dev.to / over 1 year ago
If you're looking for IDE-level language assistance, I can't help you, but since you mentioned nvim: I use regular vim with CoC / Conquer of Completion (vim plugin; LSP server, may not strictly be necessary for nvim), Solargraph (Ruby Gem; language server), and Rubocop (also a Gem) for linting. I previously/still use ALE (vim plugin; Asynchronous Lint Engine) because I haven't gotten CoC+Solargraph to play nice... - Source: Hacker News / over 1 year ago
With the right LSP I believe this should be possible with ALE. Source: over 1 year ago
I'm still on original Vim because of various gVim features not yet satisfactorily replicated in any Neovim frontend I'm aware of, but I use ALE for any kind of static analysis not covered by something like coc.nvim and configuring the backends I wanted was a simple as:. Source: over 1 year ago
If you use vim, the ALE plugin will run rust-analyzer continuously on your buffer, no need to save constantly. Most IDEs have similar functionality, often via plugins/extensions. Source: over 1 year ago
The panel at the bottom is your status line. There are several nice status line plugins like airline, powerline, lightline (what I use). By default it shows basic details like file name, git branch, file type, line and column number, etc. To enable syntax errors and warnings on status line (and all over the file) I use ALE and lightline-ale. Source: over 1 year ago
ALE Provides advanced syntax highlighting via integration with external tooling, either by invoking external tools directly and nicely collating the results, or by interfacing with standard language-server-protocol servers just like VSCode does. There are other options for this (coc is extremely popular for example), but I started out using Syntastic before LSP was a major thing, so ALE is what I use out of... Source: over 1 year ago
For autocomplete, there are a bunch of lsp clients for Vim and Neovim ships with one, you may want to check: coc, ycm, ale, vim-lsp, cmp, nvim-lspconfig. Source: over 1 year ago
I have just started using vim and already really like it. As I mainly want to use it for Python, I was trying to set up some relevant plugins (so far ale) using vundle. I have cloned the Vundle and ale folder into ~/.vim/bundle. But when I run :Pluginstall in my .vimrc get the errors:. Source: over 1 year ago
I'm in the same boat, except I don't like vim-R. I have made neovim more IDE-like with ale linting (flake8) and fixing (black). That makes a huge difference. Source: almost 2 years ago
Do you know an article comparing ale to other products?
Suggest a link to a post with product alternatives.
This is an informative page about ale. You can review and discuss the product here. The primary details have not been verified within the last quarter, and they might be outdated. If you think we are missing something, please use the means on this page to comment or suggest changes. All reviews and comments are highly encouranged and appreciated as they help everyone in the community to make an informed choice. Please always be kind and objective when evaluating a product and sharing your opinion.