You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is a VSCode Extension specific issue, and has nothing to do with the language server.
Description
I have a decently large project that takes about ~2 minutes for the language server to parse, and during that time the VSCode extension refuses to give up focus of the "output" panel. I would like to be able to use the integrated terminal during the first couple minutes of opening VSCode, but it seems that on every response from the language server the extension forces the focus back to the output panel instead of simply logging in the background.
Ideally the output from the language server would write in the background and possibly update a message in the status bar with the parsing progress instead of repeatedly taking focus.
var outputConsole = window.createOutputChannel("PHP Language Server");
outputConsole.appendLine(`${message}`);
But from what I can tell, this extension simply console.log(...)'s everything, which is likely the source of the "bug" (admittedly just a frustrating inconvenience) I'm experiencing.
The text was updated successfully, but these errors were encountered:
This is a VSCode Extension specific issue, and has nothing to do with the language server.
Description
I have a decently large project that takes about ~2 minutes for the language server to parse, and during that time the VSCode extension refuses to give up focus of the "output" panel. I would like to be able to use the integrated terminal during the first couple minutes of opening VSCode, but it seems that on every response from the language server the extension forces the focus back to the output panel instead of simply logging in the background.
Ideally the output from the language server would write in the background and possibly update a message in the status bar with the parsing progress instead of repeatedly taking focus.
The Crane project output utility seems to achieve this behaviour like so:
But from what I can tell, this extension simply
console.log(...)
's everything, which is likely the source of the "bug" (admittedly just a frustrating inconvenience) I'm experiencing.The text was updated successfully, but these errors were encountered: