VimPlug/ale
1
0
Fork 0
mirror of https://github.com/dense-analysis/ale.git synced 2026-02-25 19:17:23 +08:00
Code Issues Actions Packages Projects Releases Wiki Activity

Feature: Add support for named-pipe sockets for LSPs (#3509)

Browse Source 
* Add support for using named pipes for lsp 'socket' servers; documentation updated accordingly
* Add tests for connecting to named pipe sockets
This commit is contained in:
Kevin Svetlitski
2021-01-26 14:43:17 -06:00
committed by GitHub
parent 3a1728297a
commit cab4280d02
4 changed files with 103 additions and 12 deletions
Download Patch File Download Diff File Expand all files Collapse all files

11
doc/ale.txt
View File

@@ -228,8 +228,8 @@ A minimal configuration for a language server linter might look so. >
\ 'project_root': '/path/to/root_of_project',
\})
<
For language servers that use a TCP socket connection, you should define the
address to connect to instead. >
For language servers that use a TCP or named pipe socket connection, you
should define the address to connect to instead. >
call ale#linter#Define('filetype_here', {
\ 'name': 'any_name_you_want',
@@ -3852,7 +3852,7 @@ ale#linter#Define(filetype, linter) *ale#linter#Define()*
When this argument is set to `'socket'`, then the
linter will be defined as an LSP linter via a TCP
socket connection. `address` must be set.
or named pipe socket connection. `address` must be set.
ALE will not start a server automatically.
@@ -3877,7 +3877,10 @@ ale#linter#Define(filetype, linter) *ale#linter#Define()*
`address` A |String| representing an address to connect to,
or a |Funcref| accepting a buffer number and
returning the |String|.
returning the |String|. If the value contains a
colon, it is interpreted as referring to a TCP
socket; otherwise it is interpreted as the path of a
named pipe.
The result can be computed with |ale#command#Run()|.