-
-
Notifications
You must be signed in to change notification settings - Fork 29
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
Start java process lazy / if necessary #4
Comments
I think the fact that a new LS is opened for every VS Code window is by design, as it's supposed to work in a multi-user, multi-window (other workspaces can have different extension settings), and multi-editor (other editors can connect to the LS, too) environment. So this would be an upstream issue of the LSP specs or VS Code. It should, however, not be necessary to have a server if there's no LaTeX file (or none of the supported file types) currently opened. The
If I remove |
See upstream issue for more info: microsoft/vscode#80268 |
Bug has been confirmed upstream. Seems plaintext is used as a fallback if the language mode cannot be detected. |
Now that I think about it... Most people don't want to check
So we'll just remove the |
Every new vscode window starts a java process, even if the window is empty or the project does not contain any latex files.
Optimal behaviour: Java-Process starts not until a latex file is opened.
The text was updated successfully, but these errors were encountered: