Notes:

LSP:

• LSP is new (orignated in early 2016 by Microsoft)
• List of LSP Servers and assessment of how well they are maintained:
  • https://langserver.org/
• Spec: https://microsoft.github.io/language-server-protocol/
• LSP is a JSON-RPC protocol

PowerShell Editor Services:

• The only listed LSP server for PowerShell is the one maintained by Microsoft
• Powers the PowerShell Extension for VSCode
• You can connect to it using Named Pipes or Stdio
• Documentation:
  • Index:
    • https://github.com/PowerShell/PowerShellEditorServices/blob/main/docs/index.md
  • User Guide:
    • https://github.com/PowerShell/PowerShellEditorServices/blob/main/docs/guide/introduction.md
  • API Reference (.NET API??):
    • https://github.com/PowerShell/PowerShellEditorServices/blob/main/docs/api/index.md
    • NuGet package:
      • https://www.nuget.org/packages/Microsoft.PowerShell.EditorServices/
    • I believe this just controls the services aspect. Maybe I can start it and manage it in .NET?
    • FuGet.org page:
      
      • https://www.fuget.org/packages/Microsoft.PowerShell.EditorServices/0.6.2.389
  • "The Host Process" - what is this? Got it! This is the doc on how to use STDIO
    • https://github.com/PowerShell/PowerShellEditorServices/blob/main/docs/guide/using_the_host_process.md
    • states that the only way to interact is with stdio despite the README which says that named pipes are supported??
    • goes over LSP in detail
    • PowerShell Extension Terminal uses this method
  • Named Pipes API (which there is no document for this, guess I gotta learn how to use named pipes lmao)
    • Visual Studio Code, Vim, and IntelliJ use this method - Vim uses this?? Isn't Vim old????