29

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<...


14

You can easily move between errors by adding some key bindings to ale's <Plug> mappings (see :h <Plug>). 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 ...


5

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 |...


4

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


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


4

The ALE plug-in requires Vim 8 or NeoVim 0.2.0+. If you open a file in the Vim command-line with Ale loaded (vim /path/to/file.py or similar), it will produce an error like the one below: ALE requires NeoVim >= 0.2.0 or Vim 8 with +timers +job +channel I suggest you install a more recent version of Vim or NeoVim to get Ale to work. You might also want to ...


3

Vim currently supports assigning sign priorities (https://vimhelp.org/sign.txt.html#sign-priority). The plugins placing the signs need to use the newer sign APIs.


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. By ...


3

One thing you should be aware of: flake8 invokes pycodestyle and pyflakes. So configuring ale to run flake8 and either of those two will lead to duplicate warnings: https://github.com/dense-analysis/ale/issues/888


2

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 ...


2

Two issues: let g:ale_lint_on_insert_leave doesn’t have an assignment, so vim tries to display the value (which is unset, so the variable doesn’t exist). Add = {val} where {val} is whatever you want to set it to. Ale doesn’t manage installing programs for you. You still need to have flake8/pylint executables somewhere ale can find them (generally, this ...


2

In the absence of a more elegant fix, I disabled ALE for markdown files as explained in ALE issue 371, by adding this to my ~/.vimrc: " Disable ale for some file extensions let g:ale_pattern_options = { \ '.*\.md$': {'ale_enabled': 0}, \ '.*\.Rmd$': {'ale_enabled': 0}, \}


2

I finally resolved this by installed python-language-server globally like this: sudo -H pip install python-language-server I don't know how popular a solution this will be, but it works for me, so I'm happy. Since the ale documentation for ALEGoToDefinition says Jump to the definition of a symbol under the cursor using the enabled LSP linters for the ...


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

Knowing from :help ale-python-pylint that we want to adjust g:ale_python_pylint_options to include --rcfile, I would drop let g:ale_python_pylint_options = '--rcfile '.<filename> in wherever the right place is for you. That could be wherever you configure ALE, if a single setting is right; or, it could be in an ftplugin (use b:…) if you need to change ...


1

Well, bandit and mypy are not found, so not run at all. flake8, pycodestyle, and pylint run. Flake8 and Pylint don't have output, and the style stuff is from pycodestyle. If you want a more "compiler"-like experience, you'll need to enable and possibly install other linters (which ones to use is a bit of a personal preference; I have them all ...


1

Based on :help rubocop, I would do let g:ale_ruby_rubocop_executable = 'bundle' in your config somewhere: g:ale_ruby_rubocop_executable *g:ale_ruby_rubocop_executable* *b:ale_ruby_rubocop_executable* Type: String Default: `'rubocop'` Override the invoked rubocop binary. Set this to `'...


1

Welcome to Vi and Vim! I think the javac linter is like a single-file compile, so it doesn't work well for whole-projects. I would suggest either setting up one of the many java build tools (maven, gradle, ant, etc.?) or using a linter that works with projects (probably eclipselsp does) This was the answer, from D. Ben Knoble. I had to get rid of the javac ...


1

I found a solution. For example: I open Vivado at D:\Vivado_Projects\WorkSpace, when I click to open verilog source file in gvim, execute :cd, then I get D:\Vivado_Projects\WorkSpace, so there if include error. If enable set autochdir, the work directory will change to file location, then include error will disappear after using :w. Finally I write a batch ...


1

Go to your coc-settings.json file and implement these changes. It fixed the whitespace related issues for me. "markdownlint.config": { "default": true, "whitespace": false }, Source: Markdown Lint Rules from GitHub Repo Marus's Blog Talking about Linting Markdown Syntax Screenshot: Notice how there are no warnings ...


1

Here's the answer I found for Neovim. First, Neovim will display up to nine signs in the gutter by default, so plugins don't have to fight over sharing just one or two columns. Second, there is sign-id metadata associated with each sign so Neovim can tell which plugin the sign belongs to. Finally, a signpriority option has been proposed. This would ...


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

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 ...


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