Skip to content

Do not activate for task terminal - #964

Closed
Anthony Kim (anthonykim1) wants to merge 1 commit into
mainfrom
anthonykim1/XactivateTask
Closed

Anthony Kim (anthonykim1) wants to merge 1 commit into
mainfrom
anthonykim1/XactivateTask

Conversation

@anthonykim1

@anthonykim1 Anthony Kim (anthonykim1) commented Nov 6, 2025 •

Copy link
Copy Markdown
Contributor

Resolves: microsoft/vscode#275667

We'd probably want to switch over to more reliable long term approach like microsoft/vscode#234440 in the future though. /cc Megan Rogge (@meganrogge) I think we can either add the api to tell if terminal is task terminal, or just straight up block extension from contributing commands to task terminal.

I don't know how aggressive the later would be, maybe some extension actually wants to contribute to task terminal via input?

@anthonykim1 Anthony Kim (anthonykim1) added this to the October 2025 milestone Nov 6, 2025
@anthonykim1 Anthony Kim (anthonykim1) added bug Issue identified by VS Code Team member as probable bug important Issue identified as high-priority labels Nov 6, 2025
@anthonykim1
Anthony Kim (anthonykim1) marked this pull request as ready for review November 6, 2025 09:03
@Tyriar

Copy link
Copy Markdown
Contributor

Let's do the fix in core: microsoft/vscode#275782

@Tyriar

Copy link
Copy Markdown
Contributor

Also ideally the python extension(s) wouldn't attempt to activate these, there's a long standing problem with the processId API though so I worry about this fix introducing hard to diagnose bugs: microsoft/vscode#91905

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Issue identified by VS Code Team member as probable bug important Issue identified as high-priority

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Attempts to activate Python environment in task terminal

2 participants