Skip to content
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.

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

question: output location of L refs #13

Closed
mpl opened this issue Jul 27, 2019 · 2 comments
Closed

question: output location of L refs #13

mpl opened this issue Jul 27, 2019 · 2 comments
Labels
question Further information is requested

Comments

@mpl
Copy link

mpl commented Jul 27, 2019

At the moment the output of "L refs" appears in the terminal where I've started acme-lsp. I would expect it to be somewhere in acme, so I can interact with it directly (maybe in /LSP/Diagnostics ?), or maybe even directly sent to the plumber.
Am I missing something, or did I misconfigure something? or is it behaving as expected?

@fhs fhs added the question Further information is requested label Jul 27, 2019
@fhs
Copy link
Collaborator

fhs commented Jul 27, 2019

This is the expected behavior. The communication between L and acme-lsp is uni-directional: L asks acme-lsp (using plumber) to show the references to an identifier at a position in a window but acme-lsp can't send the answer back to L. So, acme-lsp just prints the answer to stdout.

I usually run acme-lsp from within acme, so all its output ends up in the +Errors window. You can also run it outside acme but with the same effect like this:

acme-lsp [args] 2>&1 | 9p write acme/cons

I know this is not ideal (and confusing), but it's the result of doing RPC using plumber. I'm still thinking if we should implement a 9P file server (or some other RPC mechanism) for a bi-direction communication between L and acme-lsp. We may need it to support more advanced LSP features.

@mpl
Copy link
Author

mpl commented Jul 27, 2019

yeah I was wondering if I was supposed to simply run acme-lsp from acme directly.
Makes sense, thanks.

@mpl mpl closed this as completed Jul 27, 2019
fhs added a commit that referenced this issue Jul 27, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants