use the PowerShellEditorServices language server

[jmwatte]

Hello,
I don't know if this is the right place to ask... but
can vim-lisp be configured to use the language server that is provided with the PowerShellEditorServices?
I have collected some information ...
If you look at the powershellscript on the following link you see that they start up a service.

from
https://github.com/PowerShell/PowerShellEditorServices/blob/master/module/Start-EditorServices.ps1

This script contains startup logic for the PowerShell Editor Services
module when launched by an editor. It handles the following tasks:

• Verifying the existence of dependencies like PowerShellGet
• Verifying that the expected version of the PowerShellEditorServices module is installed
• Installing the PowerShellEditorServices module if confirmed by the user
• Finding unused TCP port numbers for the language and debug services to use
• Starting the language and debug services from the PowerShellEditorServices module

and in
https://poshtools.com/2017/11/22/the-future-of-languages-in-visual-studio/

you can see some code that hooks it up to visual code.

extract...

PowerShell Editor Services works by starting up a TCP server within PowerShell and then communicates
back and forth to the editor of the port. The port that it’s listening on is written out to the session file that you > define on the command line. This file contains a bunch other info and is formatted as JSON. After starting
the editor services, I then can parse the JSON file and open a TCP client to the editor services running in
PowerShell.

So the question is : Is it possible to do this in vim-lsp and how?
Or is it not possible?
If I could do it myself, I would.
greetings

[prabirshrestha]

You should be able to start any language server that supports stdin/stdout protocol. You can refer to some examples at https://github.com/prabirshrestha/vim-lsp/wiki/Servers.

[prabirshrestha]

@jmwatte any updates on this?

[prabirshrestha]

Seems like PowerShell server needs to support stdin/stdout protocol first which they are already working on and is in PR. Closing this issue for cleanup.