You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For the PowerShell language server, "PowerShell Editor Services", it runs a powershell script that starts the language server in a powershell instance. (see below init.vim for details) When :LanguageClientStop or :call LanguageClient#exit() get called, that powershell process hangs around leading to stray processes.
LanguageClient-neovim should kill these processes when calling Stop or Exit.
Reproduction
neovim/vim version (nvim --version or vim --version): NVIM v0.2.2
This plugin version (git rev-parse --short HEAD): b96f442
This plugin's binary version (bin/languageclient --version): languageclient 0.1.70 6e901906a6b63e074d043b59fe2d44107d5ad792
Minimal vimrc content. A minimal vimrc is the smallest vimrc that could
reproduce the issue. Refer to an example here. Make sure
your vimrc contains let g:LanguageClient_loggingLevel = 'DEBUG' to have
full log:
According to spec the server should quit itself when receiving exit(), no matter what the mode is (TCP or STDIO). This is at least my understanding. PS server should fix it's own problem correctly handling this exit() notification.
Summary
For the PowerShell language server, "PowerShell Editor Services", it runs a powershell script that starts the language server in a powershell instance. (see below init.vim for details) When
:LanguageClientStop
or:call LanguageClient#exit()
get called, that powershell process hangs around leading to stray processes.LanguageClient-neovim should kill these processes when calling Stop or Exit.
Reproduction
nvim --version
orvim --version
):NVIM v0.2.2
git rev-parse --short HEAD
):b96f442
bin/languageclient --version
):languageclient 0.1.70 6e901906a6b63e074d043b59fe2d44107d5ad792
reproduce the issue. Refer to an example here. Make sure
your vimrc contains
let g:LanguageClient_loggingLevel = 'DEBUG'
to havefull log:
init.vim
I'm testing out the following PR by @yatli for PowerShell Editor Services EditorServiceHost: allow Tcp/NamedPipe/Stdio listeners PowerShell/PowerShellEditorServices#629
This will allow PowerShell Editor Services to listen on stdio to be able to work with
LanguageClient-neovim
@yatli's fork is here: https://github.com/yatli/PowerShellEditorServices
clone that to
~/Desktop
You'll need to run the build step to get it working:
https://github.com/powershell/powershelleditorservices#development
:LanguageClientStop
or do:call LanguageClient#exit()
ps aux | grep pwsh
/tmp/LanguageClient.log
and/tmp/LanguageServer.log
.LanguageClient.log
LanguageServer.log
Expected Behavior
LanguageClient-neovim would close the running instance of powershell (where the language server is running)
Current Behavior
The process is still running:
This is bad because I often close and open neovim all the time and every time that happens a new process is left behind. Too many stray processes.
The text was updated successfully, but these errors were encountered: