summaryrefslogtreecommitdiff
path: root/doc/ale-powershell.txt
diff options
context:
space:
mode:
authorKevin Locke <kevin@kevinlocke.name>2020-02-16 14:03:41 -0700
committerKevin Locke <kevin@kevinlocke.name>2020-02-16 14:03:41 -0700
commit8c0b0f085f21d96216a337aa4fae027a3e391c99 (patch)
tree4ae0ee039ea259aacf8e6c5fdf333ca74a199417 /doc/ale-powershell.txt
parentd6d2a0c77010db6a75a8942e2af9606971738c23 (diff)
downloadale-8c0b0f085f21d96216a337aa4fae027a3e391c99.zip
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 <kevin@kevinlocke.name>
Diffstat (limited to 'doc/ale-powershell.txt')
-rw-r--r--doc/ale-powershell.txt7
1 files changed, 0 insertions, 7 deletions
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*