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
VS Code's integrated terminal has the terminal.integrated.inheritEnv setting, and the various terminal profile settings allow you to "unset" things from the base environment by "setting" them to null in the terminal profile, but terminal.integrated.inheritEnv doesn't seem to affect programs being debugged by this extension when using the internal console, and the cppdbg launch config type doesn't have the same set-to-null-to-erase mechanism.
Reading the description of the environment property of the cppdbg launch config type, it says it own supports adding to the environment.
Is there any way to "remove" things from the environment? And is there a way to not inherit any environment?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
VS Code's integrated terminal has the
terminal.integrated.inheritEnv
setting, and the various terminal profile settings allow you to "unset" things from the base environment by "setting" them tonull
in the terminal profile, butterminal.integrated.inheritEnv
doesn't seem to affect programs being debugged by this extension when using the internal console, and the cppdbg launch config type doesn't have the same set-to-null-to-erase mechanism.Reading the description of the
environment
property of the cppdbg launch config type, it says it own supports adding to the environment.Is there any way to "remove" things from the environment? And is there a way to not inherit any environment?
Beta Was this translation helpful? Give feedback.
All reactions