sendMessage: E906 about lsp HOT 7 CLOSED

Thanks for following up on this. Hopefully the typescript language server will handle this exception properly without exiting.

from lsp.

We could check the status of the channel before sending the message. But the job exit callback (exit_cb)
is supposed to be called when the LSP server exits. This function sets the LSP server job handle to v:none
and updates the LSP server running status to false. So further messages to this LSP server should not
be sent.

Did the LSP server exit because of an exception or error?

from lsp.

yes, checked,
exit_cb was called, the code is 1.
and that time, ch is 'buffered'.

from lsp.

Committed 4c57eb5 to check for the status of the channel before sending the message to the LSP server.

from lsp.

yea, that ch_status chk can avoid err raised.
// however not sure why ts lsp server cannot startup (exit '1'), or started, but failed later.
// so far just found ts lsp server is failed, maybe there was something special......................

from lsp.

i did a rough debug, looks that was a lsp server code flaw: typescript-language-server/typescript-language-server#191
// at least from the version at npm, looks... FYI.

from lsp.

for reference: above issue in ts lsp server had been fixed.
however another similar issue on perl lsp server still no clue.
// richterger/Perl-LanguageServer#81

from lsp.