Skip to content

Stdout/stdin (pipe) protocol support #634

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
nanoant opened this issue Mar 16, 2018 · 5 comments
Closed

Stdout/stdin (pipe) protocol support #634

nanoant opened this issue Mar 16, 2018 · 5 comments

Comments

@nanoant
Copy link

nanoant commented Mar 16, 2018 •
edited
Loading

It seems that PowerShellEditorServices support only TCP protocol and cannot be ran as simply pipe (stdin/stdout) Language Service Server.

It there any change (plan) to add stdin/stdout support, this will enable integration with more Editors/IDEs such as Sublime Text LSP and VIM-LSP.

prabirshrestha/vim-lsp#104
https://github.com/tomv564/LSP
@TylerLeonhardt
Copy link
Member

Sooner then you think :)

#629

@TylerLeonhardt
Copy link
Member

If you hop in the PowerShellEditorServices gitter, there's some conversation on how to get that PR working with NeoVim 😀

@nanoant
Copy link
Author

nanoant commented Mar 16, 2018

@tylerl0706 wow, thanks a lot :) Actually I am trying to make it working with Sublime Text 3 LSP plugin. I'll let you know if I get it running.

@TylerLeonhardt
Copy link
Member

Feel free to bug us on Gitter, here, or the #vscode-contributors channel on the PowerShell slack! :)

I'm all for getting new editors on board!

@TylerLeonhardt
Copy link
Member

Oh hey we did this 🎉 thanks to @yatli 😄

added in #629

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@nanoant @TylerLeonhardt