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
VSCode extensions have the ability to create a "window" in the "OUTPUT" tab. An extension can then pipe logs into that window and be able to open/show it to the user without the user having to navigate to that output themselves.
Here's a screenshot of what I am referring to:
This is done through vscode.window.createOutputChannel('channel name') and you can then call show, clear and appendLine to the instantiated channel.
It is common to ask your editor to perform a task for you and that task will output logs that you might want to see. The newly added $/progress does a good job of showing these logs, but it can only show one message at a time.
Therefore, I propose that the LSP should have the following:
A way for the server to tell the client to create N windows with IDs/names. Probably in the initialize request through a "WindowProvider"
A way for the server to stream to any windows at any time
A way for the server to tell the client to open a specific window
Thanks
The text was updated successfully, but these errors were encountered:
The feature has not gain any traction in the community. I therefore close the issue. Still a big Thank You to you for taking the time to create this issue! To learn more about how we handle feature requests, please see our documentation.
VSCode extensions have the ability to create a "window" in the "OUTPUT" tab. An extension can then pipe logs into that window and be able to open/show it to the user without the user having to navigate to that output themselves.
Here's a screenshot of what I am referring to:
This is done through
vscode.window.createOutputChannel('channel name')
and you can then callshow
,clear
andappendLine
to the instantiated channel.It is common to ask your editor to perform a task for you and that task will output logs that you might want to see. The newly added
$/progress
does a good job of showing these logs, but it can only show one message at a time.Therefore, I propose that the LSP should have the following:
Thanks
The text was updated successfully, but these errors were encountered: