Describe the bug
Inline terminal always uses system shell, which is /bin/sh on Linux, even if VS code is configured to always use e.g. bash. This introduces divergence between how user expects inline terminal to work (e.g. that .bashrc would be sourced) compared to what actually happens.
If inline terminal is disabled then all actions are done in VS code terminal. It would be least confusing if inline terminal setting does not change what shell is being used.
To Reproduce
Steps to reproduce the behavior:
- Select bash as VS code shell
- Reload window to get clean state
- Give zoo code this prompt "please run
sleep 60"
- Run
ps aux | grep sleep to observe how Zoo code launched the command
- See that /bin/sh is always used.
Expected behavior
VS code configured shell should be used.
Screenshots
N/A
Video
N/A
What version of zoo are you running
Latest master as of week ago - before 3.56.0 got released.
Additional context
None.
Describe the bug
Inline terminal always uses system shell, which is /bin/sh on Linux, even if VS code is configured to always use e.g. bash. This introduces divergence between how user expects inline terminal to work (e.g. that .bashrc would be sourced) compared to what actually happens.
If inline terminal is disabled then all actions are done in VS code terminal. It would be least confusing if inline terminal setting does not change what shell is being used.
To Reproduce
Steps to reproduce the behavior:
sleep 60"ps aux | grep sleepto observe how Zoo code launched the commandExpected behavior
VS code configured shell should be used.
Screenshots
N/A
Video
N/A
What version of zoo are you running
Latest master as of week ago - before 3.56.0 got released.
Additional context
None.