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
disable 'terminal->integrated : inherit env to avoid vscode altering the login shell and breaking goenv / pyenv and other such tools
connect to a remote ssh host
start a shell
customisations from ~/.bashrc have not been applied.
look at ps fax and observe
144050 pts/0 Ss 0:00 | _ /usr/bin/bash --init-file /home/robertc/.vscode-server/bin/e7e037083ff4455cf320e344325dacb480062c3c/out/vs/workbench/contrib/terminal/browser/media/shellIntegration-bash.sh
inspect that script, which has a buggy implementation of bash init-file handling (buggy in that it runs either .profile or .bashrc, never both - which is not how bash operates
file a bug
Reproduction aside, what I would like is for my shell setup - which is not strange or exotic - to work under vscode.
Symptoms: commands are not found in a terminal within vscode, until I start a nested shell that will cause ~/.bashrc to be sourced.
Extension version: 0.106.5
VS Code version: Code 1.83.0 (e7e037083ff4455cf320e344325dacb480062c3c, 2023-10-03T16:12:16.321Z)
OS version: Windows_NT x64 10.0.22621
Modes:
Remote OS version: Linux x64 6.2.0-1014-azure
Remote OS version: Linux x64 5.13.0-52-generic
System Info
Item
Value
CPUs
AMD Ryzen Threadripper 2990WX 32-Core Processor (64 x 2994)
inspect that script, which has a buggy implementation of bash init-file handling (buggy in that it runs either .profile or .bashrc, never both - which is not how bash operates
AFAIK the script is working correctly here, profile runs on login shell (ie. OS login on Linux), rc runs in an interactive shell (ie. most terminals). You might be having problems with the fact that the remote windows don't run the profile when creating the server? #1671
Type: Bug
disable 'terminal->integrated : inherit env to avoid vscode altering the login shell and breaking goenv / pyenv and other such tools
connect to a remote ssh host
start a shell
customisations from ~/.bashrc have not been applied.
look at
ps fax
and observe144050 pts/0 Ss 0:00 | _ /usr/bin/bash --init-file /home/robertc/.vscode-server/bin/e7e037083ff4455cf320e344325dacb480062c3c/out/vs/workbench/contrib/terminal/browser/media/shellIntegration-bash.sh
inspect that script, which has a buggy implementation of bash init-file handling (buggy in that it runs either .profile or .bashrc, never both - which is not how bash operates
file a bug
Reproduction aside, what I would like is for my shell setup - which is not strange or exotic - to work under vscode.
Symptoms: commands are not found in a terminal within vscode, until I start a nested shell that will cause ~/.bashrc to be sourced.
Extension version: 0.106.5
VS Code version: Code 1.83.0 (e7e037083ff4455cf320e344325dacb480062c3c, 2023-10-03T16:12:16.321Z)
OS version: Windows_NT x64 10.0.22621
Modes:
Remote OS version: Linux x64 6.2.0-1014-azure
Remote OS version: Linux x64 5.13.0-52-generic
System Info
canvas_oop_rasterization: enabled_on
direct_rendering_display_compositor: disabled_off_ok
gpu_compositing: enabled
multiple_raster_threads: enabled_on
opengl: enabled_on
rasterization: enabled
raw_draw: disabled_off_ok
video_decode: enabled
video_encode: enabled
vulkan: disabled_off
webgl: enabled
webgl2: enabled
webgpu: enabled
A/B Experiments
The text was updated successfully, but these errors were encountered: