24

ALE has many commands that can navigate linting errors, and :ALENext works great for this operation. By default, ALE maps no bindings, I assume to allow for non-clashing customization. In your ~/.vimrc (or ~/.config/nvim/init.vim for NeoVim), I use: nmap <silent> <leader>aj :ALENext<cr> nmap <silent> <leader>ak :ALEPrevious<...


13

You can easily move between errors by adding some Plug key bindings. In this example use Ctrl+j to go to next error and Ctrl+k to go to the previous error. nmap <silent> <C-k> <Plug>(ale_previous_wrap) nmap <silent> <C-j> <Plug>(ale_next_wrap)


5

As you can read from :h 'termguicolors': 'termguicolors' 'tgc' boolean (default off) global Enables 24-bit RGB color in the TUI. Uses "gui" :highlight attributes instead of "cterm" attributes. So your highlighting command can not work since it doesn't provide a guifg attribute. I think the following should do the trick: highlight ...


4

Found it. Turns out it was not Ale doing it, but rather LanguageClient-neovim. The setting to turn it off is let g:LanguageClient_useVirtualText = 0


3

From the eslint documentation we can read Note: If you have a personal configuration file in your home directory (~/.eslintrc), it will only be used if no other configuration files are found. Since a personal configuration would apply to everything inside of a user’s directory, including third-party code, this could cause problems when running ESLint. ...


3

Ralf mentions in the comments disabling ALE's sign column with let g:ale_set_signs = 0 but you can also disable signs entirely with set signcolumn=no or have them in the number column with set signcolumn=number


2

In your ALEInfo output, it shows that ALE is using the variables from your latex autogroup. (Line 38: let b:ale_fixers = ['latexindent', 'remove_trailing_lines', 'trim_whitespace']) Each of your autogroups are being loaded and b:ale_fixers is being overridden each time. You could add something like the following to each of your augroups: au FileType *.py ...


1

ALE doesn't seem to support prettier for Ruby in its default configuration. Though it offers enough hooks for you to use a different executable (such as rbprettier) or to pass it additional arguments (such as --parser ruby). You can override these with buffer-local variables b:ale_javascript_prettier_executable and b:ale_javascript_prettier_options. See ...


1

Since I ran this linter as an external command and it gave me the same delay to go through the file, I assume it is just really slow. So that's a shame... P.S If you got any solutions on how to fight this delay in large files please feel free to comment below. Thanks Edit: I now use ccls linter, it is fast (at the cost of big cache for every project, but ...


1

Add let g:ale_python_pyflakes_executable = 'pyflakes3' to your .vimrc and be at peace


1

It turns out this was easier than expected. It just boils down to installing the pip and apt packages for pylint and flake8, i.e.: sudo apt install pylint sudo apt install flake8 pip install pylint pip install flake8 This of course needs to use pip-python3 instead of pip if you've configured YCM with Python3. From there, I just install the YCM and w0rp/ale ...


1

1) didn't work because eslint is a typescript linter, you should pick a php linter. 2)indent is not a an error, take a look at ale option of your linter, it can be turned off most of the time.


1

I just found out that only flake8, mypy and pylint are enabled by default. I was trying to find out before but couldn't until someone pointed to https://github.com/w0rp/ale/blob/master/doc/ale.txt#L1438 or :help ale_linters In order to enable new linters, I need to set: let g:ale_linters = {'python': ['pycodestyle']} The doc above has this part: The |...


1

It's important to note that ALE is not itself a linter, it is an interface to "supported [...] tools which have been correctly installed." Given that you've only described installing ALE, and that you refer to "ALE [not checking] out the real wrong syntax," I think you may have missed a step. See Supported Languages and Tools for a handful of HTML linters ...


1

Unfortunately there is no easy way to fix this at the moment, the OP has opened a vim-go issue and we agree that this is something vim-go can do better. Now we just need someone to spend time fixing it :-) In the meanwhile, you can do some things to use ALE and vim-go simultaneously. Setting g:go_list_type = 'locationlist' will make vim-go always use the ...


Only top voted, non community-wiki answers of a minimum length are eligible