mirror of
https://github.com/dense-analysis/ale.git
synced 2025-12-06 12:44:23 +08:00
codespell: fix spelling errors picked out by codespell (#4343)
This commit is contained in:
@@ -173,7 +173,7 @@ g:ale_java_javalsp_config *g:ale_java_javalsp_config*
|
||||
Type: |Dictionary|
|
||||
Default: `{}`
|
||||
|
||||
The javalsp linter automatically detects external depenencies for Maven and
|
||||
The javalsp linter automatically detects external dependencies for Maven and
|
||||
Gradle projects. In case the javalsp fails to detect some of them, you can
|
||||
specify them setting a dictionary to |g:ale_java_javalsp_config| variable.
|
||||
>
|
||||
|
||||
@@ -979,7 +979,7 @@ g:ale_python_pylsp_options *g:ale_python_pylsp_options
|
||||
let g:ale_python_pylsp_executable = 'python3'
|
||||
let g:ale_python_pylsp_options = '-m pylsp'
|
||||
|
||||
An example stragety for installing `pylsp`:
|
||||
An example strategy for installing `pylsp`:
|
||||
`python3 -m pip install --user pylsp`
|
||||
|
||||
|
||||
|
||||
@@ -29,7 +29,7 @@ g:ale_deno_lsp_project_root *g:ale_deno_lsp_project_root*
|
||||
executing the following steps in the given order:
|
||||
|
||||
1. Find an ancestor directory containing a tsconfig.json.
|
||||
2. Find an ancestory directory containing a .git folder.
|
||||
2. Find an ancestor directory containing a .git folder.
|
||||
3. Use the directory of the current buffer (if the buffer was opened from
|
||||
a file).
|
||||
|
||||
|
||||
@@ -134,7 +134,7 @@ g:ale_verilog_yosys_options *g:ale_verilog_yosys_options*
|
||||
Default: `'-Q -T -p ''read_verilog %s'''`
|
||||
|
||||
This variable can be changed to modify the flags/options passed to 'yosys'.
|
||||
By default, Yosys is an interative program. To obtain linting functionality,
|
||||
By default, Yosys is an interactive program. To obtain linting functionality,
|
||||
the `'read_verilog'` command is used.
|
||||
|
||||
|
||||
|
||||
@@ -4558,7 +4558,7 @@ ALEFixPost *ALEFixPost-autocmd*
|
||||
These |User| autocommands are triggered before and after every lint or fix
|
||||
cycle. They can be used to update statuslines, send notifications, etc.
|
||||
The autocmd commands are run with |:silent|, so |:unsilent| is required for
|
||||
echoing messges.
|
||||
echoing messages.
|
||||
|
||||
For example to change the color of the statusline while the linter is
|
||||
running:
|
||||
@@ -4591,7 +4591,7 @@ ALEJobStarted *ALEJobStarted-autocmd*
|
||||
ALELSPStarted *ALELSPStarted-autocmd*
|
||||
*ALELSPStarted*
|
||||
|
||||
This |User| autocommand is trigged immediately after an LSP connection is
|
||||
This |User| autocommand is triggered immediately after an LSP connection is
|
||||
successfully initialized. This provides a way to perform any additional
|
||||
initialization work, such as setting up buffer-level mappings.
|
||||
|
||||
|
||||
Reference in New Issue
Block a user