We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Testing #182970
In my extension's activate function, I have:
activate
vscode.window.createTerminal({ name: `Ext Terminal tranisent #${NEXT_TERM_ID++}`, isTransient: true } as any); vscode.window.createTerminal({ name: `Ext Terminal tranisent #${NEXT_TERM_ID++}`, isTransient: true, shellPath: 'fish' } as any); const collection = context.environmentVariableCollection; collection.replace('FOO', 'REPLACED', { applyAtShellIntegration: true }); collection.append('APPENDING', 'appending', { applyAtShellIntegration: true }) collection.prepend('PREPENDING', 'prepending', { applyAtShellIntegration: true });
When the extension activates, I log the env in each terminal. In the first, zsh, the mutations are applied right next to each-other in order
env
zsh
In the second, fish, I see that they're applied in a different order and the appending / prepending happens twice. I'm not sure if this is expected.
fish
The text was updated successfully, but these errors were encountered:
This is probably expected because different shells do different things on startup. To be sure, set apply at process creation to false
Sorry, something went wrong.
does not occur when I set process creation to false
Will bring up in API sync #179476 (comment)
Tyriar
No branches or pull requests
Testing #182970
In my extension's
activate
function, I have:When the extension activates, I log the
env
in each terminal. In the first,zsh
, the mutations are applied right next to each-other in orderIn the second,
fish
, I see that they're applied in a different order and the appending / prepending happens twice. I'm not sure if this is expected.The text was updated successfully, but these errors were encountered: