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
{{ message }}
Repository navigation
Don't switch to Output tab when automatically installing packages #2280
This extension seems to always the Output tab when it finds the packages are not up to date with pubspec.yaml and hence auto-fetches the latest packages. (I assume it's an extension issue and not a general VS Code behavior from this comment: microsoft/vscode#34221 (comment))
In my case this happens always when I am actively doing something in the integrated terminal, but makes it especially jarring as it breaks my flow: E.g. after checking out another Git branch with a different pubspec it switches to the Output tab and I have to manually switch back before continuing in the terminal (for example in this case often creating a new branch).
Proposed Solution
Either
Offer an option to disable the automatic switching
Just show a notification in the usual success case instead
Yep, this is done by the extension and I think it's fair to not force this - we could add each line to the existing notification status and then just switch to the output window if the exit code is non-zero (or if possible, add a button for "Show Output"). Same probably applies for the other commands that run through the same code.
@fbettag please file an issue with more details if you think something isn't working correctly. I've just tested and the output pane was not shown (the code change that closed this issue set it to only show if there is a non-zero exit code).
@fbettag please file an issue with more details if you think something isn't working correctly. I've just tested and the output pane was not shown (the code change that closed this issue set it to only show if there is a non-zero exit code).
which happens every 5 seconds when you're using agentic coding. from an UX perspective this is absolutely terrible to just switch views without the user asking for it. other languages/frameworks can do it too.
@fbettag it's not clear to me why using agentic coding would result in a failed pub get every 5 seconds.
Not switching to the output tab when pub get fails could also be a considered terrible UX because it would be unclear why a package you just added is not working.
I'm happy to look at this, but you need to file a new issue and provide some more details, because there's not enough here for me to understand or fix the problem. Thanks!
Activity
DanTup commentedon Feb 29, 2020
Yep, this is done by the extension and I think it's fair to not force this - we could add each line to the existing notification status and then just switch to the output window if the exit code is non-zero (or if possible, add a button for "Show Output"). Same probably applies for the other commands that run through the same code.
uniquejava commentedon Mar 11, 2020
Hello.
I am mad about this.
I am working on TERMINAL tab (say. entering some git commands)
but this plugin constantly disturbs me.
it's auto switching to the OUTPUT tab(even I hide it )
with the following messages from OUTPUT
I can't find any settings about this. Can I temporarily disable the output.
fbettag commentedon Dec 18, 2025
It's almost 6 years later and this issue is still happening.
DanTup commentedon Dec 18, 2025
@fbettag please file an issue with more details if you think something isn't working correctly. I've just tested and the output pane was not shown (the code change that closed this issue set it to only show if there is a non-zero exit code).
fbettag commentedon Dec 18, 2025
which happens every 5 seconds when you're using agentic coding. from an UX perspective this is absolutely terrible to just switch views without the user asking for it. other languages/frameworks can do it too.
DanTup commentedon Dec 18, 2025
@fbettag it's not clear to me why using agentic coding would result in a failed
pub getevery 5 seconds.Not switching to the output tab when
pub getfails could also be a considered terrible UX because it would be unclear why a package you just added is not working.I'm happy to look at this, but you need to file a new issue and provide some more details, because there's not enough here for me to understand or fix the problem. Thanks!