From db5fe5659f260f63cc777ea7c42575fd0e44bcde Mon Sep 17 00:00:00 2001 From: Donnie West Date: Fri, 18 Oct 2019 12:44:47 -0500 Subject: Allow the user to remove warnings from completions --- doc/ale.txt | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) (limited to 'doc') diff --git a/doc/ale.txt b/doc/ale.txt index f1c2efbb..173b2185 100644 --- a/doc/ale.txt +++ b/doc/ale.txt @@ -420,7 +420,9 @@ completion information with Deoplete, consult Deoplete's documentation. When working with TypeScript files, ALE by can support automatic imports from external modules. This behavior can be enabled by setting the -|g:ale_completion_tsserver_autoimport| variable to `1`. +|g:ale_completion_tsserver_autoimport| variable to `1`. ALE can also remove +warnings from your completions by setting the +|g:ale_completion_tsserver_remove_warnings| variable to 1. *ale-completion-completeopt-bug* -- cgit v1.2.3 From 4222f32cc4d2f04e2ea7764b72f9f2fe106c71d7 Mon Sep 17 00:00:00 2001 From: Donnie West Date: Tue, 29 Oct 2019 20:20:48 -0500 Subject: Include documentation item for removing warnings --- doc/ale.txt | 8 ++++++++ 1 file changed, 8 insertions(+) (limited to 'doc') diff --git a/doc/ale.txt b/doc/ale.txt index 173b2185..c1cf928b 100644 --- a/doc/ale.txt +++ b/doc/ale.txt @@ -644,6 +644,14 @@ b:ale_completion_enabled *b:ale_completion_enabled* See |ale-completion| +g:ale_completion_tsserver_remove_warnings *g:ale_completion_tsserver_remove_warnings* + + Type: Number + Default: `0` + + When this option is set to `0`, ALE will return all completion items, + including those that are a warning. Warnings can be excluded from completed + items by setting it to `1`. g:ale_completion_tsserver_autoimport *g:ale_completion_tsserver_autoimport* -- cgit v1.2.3 From 8c0b0f085f21d96216a337aa4fae027a3e391c99 Mon Sep 17 00:00:00 2001 From: Kevin Locke Date: Sun, 16 Feb 2020 14:03:41 -0700 Subject: Alias ps1 filetype to powershell Rather than requiring users to alias ps1 to powershell themselves, include it in s:default_ale_linter_aliases. Since [vim-ps1] is a popular (the only?) PowerShell ftplugin and there do not appear to be any other uses of ft=ps1 on vim.org, this seems like a safe and reasonable default. [vim-ps1]: http://www.vim.org/scripts/script.php?script_id=1327 Signed-off-by: Kevin Locke --- doc/ale-powershell.txt | 7 ------- doc/ale.txt | 1 + 2 files changed, 1 insertion(+), 7 deletions(-) (limited to 'doc') diff --git a/doc/ale-powershell.txt b/doc/ale-powershell.txt index c28ef9ea..485c9bd0 100644 --- a/doc/ale-powershell.txt +++ b/doc/ale-powershell.txt @@ -25,13 +25,6 @@ Installation Install PSScriptAnalyzer by any means, so long as it can be automatically imported in PowerShell. -Some PowerShell plugins set the filetype of files to `ps1`. To continue using -these plugins, use the ale_linter_aliases global to alias `ps1` to `powershell` - -> - " Allow ps1 filetype to work with powershell linters - let g:ale_linter_aliases = {'ps1': 'powershell'} -< g:ale_powershell_psscriptanalyzer_executable *g:ale_powershell_psscriptanalyzer_executable* diff --git a/doc/ale.txt b/doc/ale.txt index eafbc119..6fad01aa 100644 --- a/doc/ale.txt +++ b/doc/ale.txt @@ -1188,6 +1188,7 @@ g:ale_linter_aliases *g:ale_linter_aliases* \ 'csh': 'sh', \ 'javascriptreact': ['javascript', 'jsx'], \ 'plaintex': 'tex', + \ 'ps1': 'powershell', \ 'rmarkdown': 'r', \ 'rmd': 'r', \ 'systemverilog': 'verilog', -- cgit v1.2.3 From 6d502233d849600ecb2a08227299ffea2b2ea0c7 Mon Sep 17 00:00:00 2001 From: w0rp Date: Sun, 9 Aug 2020 02:28:47 +0100 Subject: Close #3267 - Add a general autoimport setting --- doc/ale.txt | 13 +++++++------ 1 file changed, 7 insertions(+), 6 deletions(-) (limited to 'doc') diff --git a/doc/ale.txt b/doc/ale.txt index 3b90e7e0..ef256752 100644 --- a/doc/ale.txt +++ b/doc/ale.txt @@ -418,11 +418,12 @@ The |ALEComplete| command can be used to show completion suggestions manually, even when |g:ale_completion_enabled| is set to `0`. For manually requesting completion information with Deoplete, consult Deoplete's documentation. -When working with TypeScript files, ALE by can support automatic imports -from external modules. This behavior can be enabled by setting the -|g:ale_completion_tsserver_autoimport| variable to `1`. ALE can also remove -warnings from your completions by setting the -|g:ale_completion_tsserver_remove_warnings| variable to 1. +ALE by can support automatic imports from external modules. This behavior can +be enabled by setting the |g:ale_completion_autoimport| variable to `1`. + +When working with TypeScript files, ALE can remove warnings from your +completions by setting the |g:ale_completion_tsserver_remove_warnings| +variable to 1. *ale-completion-completeopt-bug* @@ -692,7 +693,7 @@ g:ale_completion_tsserver_remove_warnings *g:ale_completion_tsserver_remove_warn including those that are a warning. Warnings can be excluded from completed items by setting it to `1`. -g:ale_completion_tsserver_autoimport *g:ale_completion_tsserver_autoimport* +g:ale_completion_autoimport *g:ale_completion_autoimport* Type: Number Default: `0` -- cgit v1.2.3 From 681ca5fee8612aae5fdcf032d7d12992d1f60a3e Mon Sep 17 00:00:00 2001 From: w0rp Date: Sun, 9 Aug 2020 03:18:21 +0100 Subject: Explain how to use ALE and coc.nvim together --- doc/ale.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'doc') diff --git a/doc/ale.txt b/doc/ale.txt index ef256752..c7664da0 100644 --- a/doc/ale.txt +++ b/doc/ale.txt @@ -246,7 +246,7 @@ A plugin might integrate its own checks with ALE like so: > function! WorkDone(buffer, results) abort " Send results to ALE after they have been collected. - call ale#other_source#ShowResults(buffer, 'some-name', a:results) + call ale#other_source#ShowResults(a:buffer, 'some-name', a:results) endfunction < -- cgit v1.2.3 From affeed7a87ce54aff9506c0069da1f9f23e3dd01 Mon Sep 17 00:00:00 2001 From: w0rp Date: Sun, 9 Aug 2020 04:19:14 +0100 Subject: Enable C flag parsing by default The options for parsing `make -n` and `compile_commands.json` flags are now enabled by default, so people can start getting better flags for their files by default. `compile_commands.json` flags are now preferred over `make -n` results, to make the options work better by default. --- doc/ale-c.txt | 14 +++++++++----- 1 file changed, 9 insertions(+), 5 deletions(-) (limited to 'doc') diff --git a/doc/ale-c.txt b/doc/ale-c.txt index efc26f93..53c141b3 100644 --- a/doc/ale-c.txt +++ b/doc/ale-c.txt @@ -37,7 +37,7 @@ g:ale_c_build_dir *g:ale_c_build_dir* g:ale_c_parse_compile_commands *g:ale_c_parse_compile_commands* *b:ale_c_parse_compile_commands* Type: |Number| - Default: `0` + Default: `1` If set to `1`, ALE will parse `compile_commands.json` files to automatically determine flags for C or C++ compilers. ALE will first search for the @@ -45,19 +45,23 @@ g:ale_c_parse_compile_commands *g:ale_c_parse_compile_commands* `compile_commands.json` files in the directories for |g:ale_c_build_dir_names|. - If |g:ale_c_parse_makefile| or |b:ale_c_parse_makefile| is set to `1`, the - output of `make -n` will be preferred over `compile_commands.json` files. - g:ale_c_parse_makefile *g:ale_c_parse_makefile* *b:ale_c_parse_makefile* Type: |Number| - Default: `0` + Default: `1` If set to `1`, ALE will run `make -n` to automatically determine flags to set for C or C++ compilers. This can make it easier to determine the correct build flags to use for different files. + You might want to disable this option if `make -n` takes too long to run for + projects you work on. + + If |g:ale_c_parse_compile_commands| or |b:ale_c_parse_compile_commands| is + set to `1`, flags taken from `compile_commands.json` will be preferred over + `make -n` output. + =============================================================================== astyle *ale-c-astyle* -- cgit v1.2.3 From 9e1f511003142db5a1ba05815dc8d40f753c080b Mon Sep 17 00:00:00 2001 From: w0rp Date: Sun, 9 Aug 2020 20:08:42 +0100 Subject: #3276 - Disable make -n by default again --- doc/ale-c.txt | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) (limited to 'doc') diff --git a/doc/ale-c.txt b/doc/ale-c.txt index 53c141b3..fc0d941a 100644 --- a/doc/ale-c.txt +++ b/doc/ale-c.txt @@ -49,12 +49,18 @@ g:ale_c_parse_compile_commands *g:ale_c_parse_compile_commands* g:ale_c_parse_makefile *g:ale_c_parse_makefile* *b:ale_c_parse_makefile* Type: |Number| - Default: `1` + Default: `0` If set to `1`, ALE will run `make -n` to automatically determine flags to set for C or C++ compilers. This can make it easier to determine the correct build flags to use for different files. + WARNING: Running `make -n` automatically can execute arbitrary code, even + though it's supposed to be a dry run, so enable this option with care. You + might prefer to use the buffer-local version of the option instead with + |g:ale_pattern_options|, or you own code for checking which project you're + in. + You might want to disable this option if `make -n` takes too long to run for projects you work on. -- cgit v1.2.3 From d5912b53ddd30102c6e199468998fb6d72a197f3 Mon Sep 17 00:00:00 2001 From: Nihad Abbasov Date: Wed, 12 Aug 2020 16:04:54 +0300 Subject: Restore old behavior of ALEFix command for Rubocop (#3237) * Restore old behavior of ALEFix command for Rubocop Since RuboCop 0.60 ALEFix command stopped to fix all found offenses. This change restores the previous behavior by allowing rubocop to fix all detected offenses. * Fix tests * Allow to configure auto-correct option for Rubocop --- doc/ale-ruby.txt | 8 ++++++++ 1 file changed, 8 insertions(+) (limited to 'doc') diff --git a/doc/ale-ruby.txt b/doc/ale-ruby.txt index a27a20b2..142bb6b8 100644 --- a/doc/ale-ruby.txt +++ b/doc/ale-ruby.txt @@ -114,6 +114,14 @@ g:ale_ruby_rubocop_options *g:ale_ruby_rubocop_options* This variable can be changed to modify flags given to rubocop. +g:ale_ruby_rubocop_auto_correct_all *g:ale_ruby_rubocop_options* + *b:ale_ruby_rubocop_options* + Type: Number + Default: `0` + + This variable can be changed to make rubocop to correct all offenses (unsafe). + + =============================================================================== ruby *ale-ruby-ruby* -- cgit v1.2.3 From 979062235a23d2f2bbe176c64e649e9182826d2d Mon Sep 17 00:00:00 2001 From: w0rp Date: Thu, 13 Aug 2020 13:44:22 +0100 Subject: Fix #3286 - Fix duplicate tags --- doc/ale-ruby.txt | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) (limited to 'doc') diff --git a/doc/ale-ruby.txt b/doc/ale-ruby.txt index 142bb6b8..8815404a 100644 --- a/doc/ale-ruby.txt +++ b/doc/ale-ruby.txt @@ -114,8 +114,8 @@ g:ale_ruby_rubocop_options *g:ale_ruby_rubocop_options* This variable can be changed to modify flags given to rubocop. -g:ale_ruby_rubocop_auto_correct_all *g:ale_ruby_rubocop_options* - *b:ale_ruby_rubocop_options* +g:ale_ruby_rubocop_auto_correct_all *g:ale_ruby_rubocop_auto_correct_all* + *b:ale_ruby_rubocop_auto_correct_all* Type: Number Default: `0` @@ -180,8 +180,8 @@ g:ale_ruby_sorbet_options *g:ale_ruby_sorbet_options* =============================================================================== standardrb *ale-ruby-standardrb* -g:ale_ruby_standardrb_executable *g:ale_ruby_standardrb_executable* - *b:ale_ruby_standardrb_executable* +g:ale_ruby_standardrb_executable *g:ale_ruby_standardrb_executable* + *b:ale_ruby_standardrb_executable* Type: String Default: `'standardrb'` -- cgit v1.2.3 From 506a8532d07fd7e15e9a6cc37d490f7b7088aef5 Mon Sep 17 00:00:00 2001 From: Ben Boeckel Date: Sun, 10 May 2020 08:21:02 -0400 Subject: rust/cargo: add support for a custom target directory This can avoid having to wait for ALE or ALE being blocked on other cargo actions within the same crate. --- doc/ale-rust.txt | 12 ++++++++++++ 1 file changed, 12 insertions(+) (limited to 'doc') diff --git a/doc/ale-rust.txt b/doc/ale-rust.txt index 46d4714b..2c0222b7 100644 --- a/doc/ale-rust.txt +++ b/doc/ale-rust.txt @@ -174,6 +174,18 @@ g:ale_rust_cargo_clippy_options only `cargo clippy` supports (e.g. `--deny`). +g:ale_rust_cargo_target_dir + *g:ale_rust_cargo_target_dir* + *b:ale_rust_cargo_target_dir* + + Type: |String| + Default: `''` + + Use a custom target directory when running the commands for ALE. This can + help to avoid "waiting for file lock on build directory" messages when + running `cargo` commands manually while ALE is performing its checks. + + =============================================================================== rls *ale-rust-rls* -- cgit v1.2.3