Terminal doesn't use custom bash profile when debugging

[KV34]

redirected here from closed issue microsoft/vscode#80434
The bug appeared after one of few last updates.
When integrated terminal starts it uses custom profile (as expected),
but after python script is started it loads profile from ~/.bashrc

In my settings.json I have the following settings:

"terminal.integrated.shellArgs.osx": [
   "--rcfile", "/Volumes/DISK/projs/TechStuff/settings/profile"
],
"terminal.integrated.env.osx": {"HISTFILE":"/dev/null"},
"terminal.integrated.setLocaleVariables": false,

Environment data

Version: 1.38.0
Commit: 3db7e09f3b61f915d03bbfa58e258d6eee843f35
Date: 2019-09-03T21:47:00.464Z
Electron: 4.2.10
Chrome: 69.0.3497.128
Node.js: 10.11.0
V8: 6.9.427.31-electron.0
OS: Darwin x64 17.7.0

Expected behaviour

using custom profile (environment)

Actual behaviour

using standard profile (environment), after starting python script

Steps to reproduce:

1. Assign custom profile to integrated terminal settings.(and restart maybe)
2. Open page(tab) with any python script and open integrated terminal.
   (You can put string like echo 'bashrc loaded' in profile file to see it loads)
3. Check profile - it is cutom.
4. Debug python script (F5 or Debug -> Start Debugging) - it loads bashrc profile instead of custom
5. Check which profile is loaded (can use printenv command if you set different env. variables or check echo print as mentioned above) - standard profile loaded.

[kimadeline]

Hello @KV34 👋 Thank you for reaching out.

Sadly I could not reproduce your issue in the following environment:

• OS: macOS Mojave 10.14.6
• VS Code version: 1.38.0
• Python extension version: 2019.9.34911

Could you please provide some extra info, namely:

• Which version of the Python extension for VS Code you have
• Which shell you are using
• Whether your custom profile is located within your workspace folder or not (and if not, could you try moving it there?)
• Whether it happens no matter which shell you are using (bash, zsh, sh...)
• Whether the custom profile is loaded properly when you open new terminals (+ icon next to the terminal dropdown):
  

Thanks!

[alkalinin]

I use the Windows 10 and I have the same issue. Details of the issue in my environment are reported in the microsoft/vscode#80434.

[KV34]

Hello kimadeline, Thanks for quick reply.
There is no effect when you run from context menu.
Try from main menu: Debug->Start Debugging

[KV34]

my versions:

I'm using bash
when new terminals created it loads properly
I hope this enough. Thanks

[kimadeline]

Thank you for the clarification @KV34, I could reproduce your issue when debugging the script instead of just running it 👍

Note

Something to change in the code of LocalDebugClient.LaunchApplicationToDebug(dbgServer: IDebugServer): Promise<any> or LocalDebugClient.launchExternalTerminal maybe (both in src/client/debugger/debugAdapter/DebugClients/LocalDebugClient.ts)?

[ajodfaj]

I have the same issue on win10.
I find the debug terminal does not load the arguments given in terminal.integrated.shellArgs.windows, while the terminal launched with ctrl+` load them.

For example, my settings.json is given as

{
    ...
    "terminal.integrated.shell.windows": "D:\\Program Files\\Git\\bin\\bash.exe",
    "terminal.integrated.shellArgs.windows": ["-l", "-i"]
    ...
}

When launched with ctrl+`, the terminal is a login shell ("-l" works), and loads the profile.
When debugging, the arguments "-l" and "-i" are missing.

My "hacky" solution is to manually source the profile in ~/.bashrc

source "/d/Program Files/Git/etc/profile"

[Wehrdo]

The bug is more than just the bashrc file. On Windows, I have my default terminal set to WSL bash, but for some projects I want to override it and use the regular Windows terminal. I can't even start the debugger, because it tries to execute python.exe in linux bash, which clearly does not work.

[iutlu]

I appear to be running into the same issue:

"terminal.integrated.shellArgs.linux": [
    "-l"
],

is being ignored by the Python Debug Console (I don't get some custom env vars from my .profile). Regular terminal instances, "Run Python File In Terminal", and tasks of type "shell" are in contrast, OK. Note: I have terminal.integrated.inheritEnv set to false.