Skip to content

vscode.env.onDidChangeShell not firing in the webworker extension host #249823

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.

Sign up for GitHub

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

Jump to bottom
Open
jeanp413 opened this issue May 26, 2025 · 1 comment · May be fixed by #249824
Open

vscode.env.onDidChangeShell not firing in the webworker extension host #249823

jeanp413 opened this issue May 26, 2025 · 1 comment · May be fixed by #249824
Assignees
@meganrogge

Comments

@jeanp413
Copy link
Contributor

jeanp413 commented May 26, 2025 •
edited
Loading

Does this issue occur when all extensions are disabled?: Yes/No

  • VS Code Version: stable and from sources
  • OS Version:

The vscode.env.onDidChangeShell event is never fired in the webworker extension host and vscode.env.shell is always empty
@jeanp413 jeanp413 linked a pull request May 26, 2025 that will close this issue
Open
jeanp413 added a commit to jeanp413/vscode that referenced this issue May 26, 2025
@jeanp413
Fixes microsoft#249823
41b75a6
@jeanp413
Copy link
Contributor Author

jeanp413 commented May 26, 2025 •
edited
Loading

PR fixing it #249824

@Yoyokrazy Yoyokrazy assigned meganrogge and unassigned Yoyokrazy May 28, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@meganrogge meganrogge

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Fix vscode.env.onDidChangeShell not firing in the webworker extension host jeanp413/vscode
3 participants
@Yoyokrazy @jeanp413 @meganrogge