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

Nimsuggest replying with garbage value through socket every second invocation - then the channel breaks #18001

Open
ghost opened this issue May 12, 2021 · 1 comment

Comments

@ghost
Copy link

ghost commented May 12, 2021

Hello!

I made a nim extension for my code editor 2 years ago and I had a lot of problem with trying to work around nimsuggest's output. Now only the first invocation succeeds(testing this with def $file:$L:$C over and over) and for the second invocation I just get empty lines then the socket channel just breaks. Is this expected behavior? And is there any way to make nimsuggest use a standardized response format like json or xml?

~$ nimsuggest -v
Nim Compiler Version 1.4.4 [Linux: amd64]
Compiled at 2021-02-23
Copyright (c) 2006-2020 by Andreas Rumpf

git hash: 2ff517462bf8609b30e6134c96658aa7912b628a
active boot switches: -d:release -d:danger --gc:markAndSweep
@alaviss
Copy link
Collaborator

alaviss commented May 19, 2021

This is not documented properly but nimsuggest process one query per socket.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant