Public | Automated Build

Last pushed: 7 months ago
Short Description
A Docker image for running tests for ALE, a Vim plugin
Full Description

Asynchronous Lint Engine

ALE (Asynchronous Lint Engine) is a plugin for providing linting in NeoVim
and Vim 8 while you edit your text files.

ALE makes use of NeoVim and Vim 8 job control functions and timers to
run linters on the contents of text buffers and return errors as
text is changed in Vim. This allows for displaying warnings and
errors in files being edited in Vim before files have been saved
back to a filesystem.

In other words, this plugin allows you to lint while you type.

Table of Contents

  1. Supported Languages and Tools
  2. Usage
  3. Installation
    1. Installation with Pathogen
    2. Installation with Vundle
    3. Manual Installation
  4. Contributing
  5. FAQ
    1. How do I disable particular linters?
    2. How can I keep the sign gutter open?
    3. How can I change the signs ALE uses?
    4. How can I show errors or warnings in my statusline?
    5. How can I change the format for echo messages?
    6. How can I execute some code when ALE stops linting?
    7. How can I navigate between errors quickly?
    8. How can I run linters only when I save files?
    9. How can I use the quickfix list instead of the loclist?
    10. How can I check JSX files with both stylelint and eslint?
    11. Will this plugin eat all of my laptop battery power?

<a name="supported-languages"></a>

1. Supported Languages and Tools

This plugin supports the following languages and tools. All available
tools will be run in combination, so they can be complementary.

<!-- Keep the table rows sorted alphabetically by the language name, and the tools in the tools column sorted alphabetically by the tool name. That seems to be the fairest way to arrange this table. -->

Language Tools
ASM gcc
Ansible ansible-lint
AsciiDoc proselint
Bash -n flag, shellcheck
Bourne Shell -n flag, shellcheck
C cppcheck, gcc, clang
C++ (filetype cpp) clang, clangtidy, cppcheck, gcc
C# mcs
Chef foodcritic
CMake cmakelint
CoffeeScript coffee, coffeelint
Crystal crystal
CSS csslint, stylelint
Cython (pyrex filetype) cython
D dmd
Dockerfile hadolint
Elixir credo, dogma
Elm elm-make
Erb erb
Erlang erlc
Fortran gcc
Go gofmt -e, go vet, golint, gometalinter, go build, gosimple, staticcheck
Haml haml-lint
Handlebars ember-template-lint
Haskell ghc, hlint, hdevtools
HTML HTMLHint, proselint, tidy
Java javac
JavaScript eslint, jscs, jshint, flow, standard, xo
JSON jsonlint
Kotlin kotlinc see :help ale-integration-kotlin for configuration instructions
LaTeX chktex, lacheck, proselint
Lua luacheck
Markdown mdl, proselint, vale
MATLAB mlint
Nim nim
nix nix-instantiate
nroff proselint
OCaml merlin see :help ale-integration-ocaml-merlin for configuration instructions
Perl perl -c, perl-critic
PHP hack, php -l, phpcs, phpmd
Pod proselint
Pug pug-lint
Puppet puppet, puppet-lint
Python flake8, mypy, pylint
ReasonML merlin see :help ale-integration-reason-merlin for configuration instructions
reStructuredText proselint
RPM spec rpmlint (disabled by default; see :help ale-integration-spec)
Ruby brakeman, reek, rubocop, ruby
Rust rustc, cargo (see :help ale-integration-rust for configuration instructions)
SASS sass-lint, stylelint
SCSS sass-lint, scss-lint, stylelint
Scala scalac
Slim slim-lint
SML smlnj
SQL sqlint
Swift swiftlint
Texinfo proselint
Text^ proselint, vale
TypeScript tslint, typecheck
Verilog iverilog, verilator
Vim vint
Vim help^ proselint
XHTML proselint
YAML yamllint
  • ^ No linters for text or Vim help filetypes are enabled by default.

<a name="usage"></a>

2. Usage

Once this plugin is installed, while editing your files in supported
languages and tools which have been correctly installed,
this plugin will send the contents of your text buffers to a variety of
programs for checking the syntax and semantics of your programs. By default,
linters will be re-run in the background to check your syntax when you open
new buffers or as you make edits to your files.

The behaviour of linting can be configured with a variety of options,
documented in the Vim help file. For more information on the
options ALE offers, consult :help ale-options for global options and :help ale-linter-options for options specified to particular linters.

<a name="installation"></a>

3. Installation

To install this plugin, you should use one of the following methods.
For Windows users, replace usage of the Unix ~/.vim directory with
%USERPROFILE%\_vim, or another directory if you have configured
Vim differently. On Windows, your ~/.vimrc file will be similarly
stored in %USERPROFILE%\_vimrc.

<a name="installation-with-pathogen"></a>

3.i. Installation with Pathogen

To install this module with Pathogen,
you should clone this repository to your bundle directory, and ensure
you have the line execute pathogen#infect() in your ~/.vimrc file.
You can run the following commands in your terminal to do so:

cd ~/.vim/bundle
git clone https://github.com/w0rp/ale.git

<a name="installation-with-vundle"></a>

3.ii. Installation with Vundle

You can install this plugin using Vundle
by using the path on GitHub for this repository.

Plugin 'w0rp/ale'

See the Vundle documentation for more information.

<a name="manual-installation"></a>

3.iii. Manual Installation

For installation without a package manager, you can clone this git repository
into a bundle directory as with pathogen, and add the repository to your
runtime path yourself. First clone the repository.

cd ~/.vim/bundle
git clone https://github.com/w0rp/ale.git

Then, modify your ~/.vimrc file to add this plugin to your runtime path.

set nocompatible
filetype off

let &runtimepath.=',~/.vim/bundle/ale'

filetype plugin on

You can add the following line to generate documentation tags automatically,
if you don't have something similar already, so you can use the :help command
to consult ALE's online documentation:

silent! helptags ALL

Because the author of this plugin is a weird nerd, this is his preferred
installation method.

<a name="contributing"></a>

4. Contributing

If you would like to see support for more languages and tools, please
create an issue
or create a pull request.
If your tool can read from stdin or you have code to suggest which is good,
support can be happily added for it.

If you are interested in the general direction of the project, check out the
wiki home page. The wiki includes a
Roadmap for the future, and more.

If you'd liked to discuss the project more directly, check out the #vim-ale channel
on Freenode. Web chat is available here.

<a name="faq"></a>

5. FAQ

<a name="faq-disable-linters"></a>

5.i. How do I disable particular linters?

By default, all available tools for all supported languages will be run.
If you want to only select a subset of the tools, simply create a
g:ale_linters dictionary in your vimrc file mapping filetypes
to lists of linters to run.

let g:ale_linters = {
\   'javascript': ['eslint'],
\}

For all languages unspecified in the dictionary, all possible linters will
be run for those languages, just as when the dictionary is not defined.
Running many linters should not typically obstruct editing in Vim,
as they will all be executed in separate processes simultaneously.

This plugin will look for linters in the ale_linters directory.
Each directory within corresponds to a particular filetype in Vim, and each file
in each directory corresponds to the name of a particular linter.

<a name="faq-keep-signs"></a>

5.ii. How can I keep the sign gutter open?

You can keep the sign gutter open at all times by setting the
g:ale_sign_column_always to 1

let g:ale_sign_column_always = 1

<a name="faq-change-signs"></a>

5.iii. How can I change the signs ALE uses?

Use these options to specify what text should be used for signs:

let g:ale_sign_error = '>>'
let g:ale_sign_warning = '--'

ALE sets some background colors automatically for warnings and errors
in the sign gutter, with the names ALEErrorSign and ALEWarningSign.
These colors can be customised, or even removed completely:

highlight clear ALEErrorSign
highlight clear ALEWarningSign

<a name="faq-statusline"></a>

5.iv. How can I show errors or warnings in my statusline?

You can use ALEGetStatusLine() to integrate ALE into vim statusline.
To enable it, you should have in your statusline settings

%{ALEGetStatusLine()}

When errors are detected a string showing the number of errors will be shown.
You can customize the output format using the global list g:ale_statusline_format where:

  • The 1st element is for errors
  • The 2nd element is for warnings
  • The 3rd element is for when no errors are detected

e.g

let g:ale_statusline_format = ['⨉ %d', '⚠ %d', '⬥ ok']


<a name="faq-echo-format"></a>

5.v. How can I change the format for echo messages?

There are 3 global options that allow customizing the echoed message.

  • g:ale_echo_msg_format where:
    • %s is the error message itself
    • %linter% is the linter name
    • %severity is the severity type
  • g:ale_echo_msg_error_str is the string used for error severity.
  • g:ale_echo_msg_warning_str is the string used for warning severity.

So for example this:

let g:ale_echo_msg_error_str = 'E'
let g:ale_echo_msg_warning_str = 'W'
let g:ale_echo_msg_format = '[%linter%] %s [%severity%]'

Will give you:

<a name="faq-autocmd"></a>

5.vi. How can I execute some code when ALE stops linting?

ALE runs its own autocmd
event whenever has a linter has been successfully executed and processed. This
autocmd event can be used to call arbitrary functions after ALE stops linting.

augroup YourGroup
    autocmd!
    autocmd User ALELint call YourFunction()
augroup END

<a name="faq-navigation"></a>

5.vii. How can I navigate between errors quickly?

ALE offers some commands with <Plug> keybinds for moving between warnings and
errors quickly. You can map the keys Ctrl+j and Ctrl+k to moving between errors
for example:

nmap <silent> <C-k> <Plug>(ale_previous_wrap)
nmap <silent> <C-j> <Plug>(ale_next_wrap)

For more information, consult the online documentation with
:help ale-navigation-commands.

<a name="faq-lint-on-save"></a>

5.viii. How can I run linters only when I save files?

ALE offers an option g:ale_lint_on_save for enabling running the linters
when files are saved. This option is enabled by default. If you only
wish to run linters when files are saved, you can turn the other
options off.

" Write this in your vimrc file
let g:ale_lint_on_text_changed = 'never'
" You can disable this option too
" if you don't want linters to run on opening a file
let g:ale_lint_on_enter = 0

If for whatever reason you don't wish to run linters again when you save
files, you can set g:ale_lint_on_save to 0.

<a name="faq-quickfix"></a>

5.ix. How can I use the quickfix list instead of the loclist?

The quickfix list can be enabled by turning the g:ale_set_quickfix
option on. If you wish to also disable the loclist, you can disable
the g:ale_set_loclist option.

" Write this in your vimrc file
let g:ale_set_loclist = 0
let g:ale_set_quickfix = 1

If you wish to show Vim windows for the loclist or quickfix items
when a file contains warnings or errors, g:ale_open_list can be
set to 1. g:ale_keep_list_window_open can be set to 1
if you wish to keep the window open even after errors disappear.

let g:ale_open_list = 1
" Set this if you want to.
" This can be useful if you are combining ALE with
" some other plugin which sets quickfix errors, etc.
let g:ale_keep_list_window_open = 1

<a name="faq-jsx-stylelint-eslint"></a>

5.x. How can I check JSX files with both stylelint and eslint?

If you configure ALE options correctly in your vimrc file, and install
the right tools, you can check JSX files with stylelint and eslint.

First, install eslint and install stylelint with
https://github.com/styled-components/stylelint-processor-styled-components.

Supposing you have installed both tools correctly, configure your .jsx files so
jsx is included in the filetype. You can use an autocmd for this.

augroup FiletypeGroup
    autocmd!
    au BufNewFile,BufRead *.jsx set filetype=javascript.jsx
augroup END

Supposing the filetype has been set correctly, you can set the following
options in your vimrc file:

let g:ale_linters = {'jsx': ['stylelint', 'eslint']}
let g:ale_linter_aliases = {'jsx': 'css'}

ALE will alias the jsx filetype so it uses the css filetype linters, and
use the original Array of selected linters for jsx from the g:ale_linters
object. All available linters will be used for the filetype javascript, and
no linter will be run twice for the same file.

<a name="faq-my-battery-is-sad"></a>

5.xi. Will this plugin eat all of my laptop battery power?

ALE takes advantage of the power of various tools to check your code. This of
course means that CPU time will be used to continuously check your code. If you
are concerned about the CPU time ALE will spend, which will of course imply
some cost to battery life, you can adjust your settings to make your CPU do
less work.

First, consider increasing the delay before which ALE will run any linters
while you type. ALE uses a timeout which is cancelled and reset every time you
type, and this delay can be increased so linters are run less often. See
:help g:ale_lint_delay for more information.

If you don't wish to run linters while you type, you can disable that
behaviour. Set g:ale_lint_on_text_changed to never or normal. You won't
get as frequent error checking, but ALE shouldn't block your ability to edit a
document after you save a file, so the asynchronous nature of the plugin will
still be an advantage.

If you are still concerned, you can turn the automatic linting off altogether,
including the option g:ale_lint_on_enter, and you can run ALE manually with
:call ale#Lint().

Docker Pull Command
Owner
w0rp
Source Repository