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

Feature Request: command to restart language service #1150

Closed
ntwilson opened this issue Jun 24, 2019 · 3 comments
Closed

Feature Request: command to restart language service #1150

ntwilson opened this issue Jun 24, 2019 · 3 comments

Comments

@ntwilson
Copy link

Sometimes Ionide fails to detect changes in other projects or files, probably similar to #1143, though I've also witnessed the problem when the changes are to a file within the same project. It seems intermittent to me; at least I haven't discovered a reliable way to reproduce it.

I propose that a command is added to the VS Code command palette to restart the F# language service, so that changes can be manually reloaded conveniently. I've noticed the same issue of the IDE getting out-of-sync with the code files when using other language plugins, and the severity of the issue is drastically reduced when there's a simple way to reload.

The only workaround that I know of is to close VS Code and reopen it. I thought that perhaps the "F#: Clear Cache" command would have the desired effect, but it must do something else. I can't discern any noticeable change to anything when I clear the cache.

Also, thanks for all the hard work. Ionide is amazing!

@matthid
Copy link
Contributor

matthid commented Jun 24, 2019

Any reason why you are not using the Reload Window command?

@ntwilson
Copy link
Author

The biggest reason is that I didn't know about it :). Thanks for the tip! That's a far better solution than what I was doing. Feel free to close this issue.

@moinessim
Copy link

Hello,
I'm searching for a way to manually restart the language server, without having to Reload Window or Restart Extension Host.
So we don't have to wait for all the unrelated extensions to restart.

This would be really helpful for when we get this type of behaviour:

[Error - 12:06:06 PM] Connection to server is erroring. Shutting down server.

I found this in vscode backlog, but it seems a long wait.
Would it be possible to add a command for this?

Thank you!

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

4 participants