-
Notifications
You must be signed in to change notification settings - Fork 29.3k
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
Creating a terminal and sending text to it should not show it #11384
Comments
Pushing for August since no one has yet programmed against the API and changes after that won't be possible |
This is actually a non-trivial change and is related to #11275. A |
Are you suggesting this should create in background by default? Seems to me that the majority of use cases would want it in the foreground? |
For the sake of being consistent with other API ( |
Alternatively we release-note this behaviour for August - the API is correct but wrongly implemented. That would mean consumers for 1.5 have to be prepared for a behavioural change with 1.6 |
@jrieken while calling |
Set the PR to August, moving this to September for the real fix. |
This was done via #11839 and subsequent fixes with one caveat; if the terminal panel is not initialized, the output will not be retained. So the process will run fine, just output will not be kept until |
@Tyriar We still have the doc comments about changes in 1.6 in vscode.d.ts |
Done, I just removed it and didn't elaborate on it not showing the terminal as that's consistent with |
Creating a new terminal immediately shows it which
createOutputChannel
orcreateStatusBarItem
The text was updated successfully, but these errors were encountered: