Benjamin Pasero
Benjamin Pasero
@kamikazechaser the key difference is that when you run from a terminal, we do not attempt to resolve any shell environment, we just inherit the one from where you launched...
@kamikazechaser maybe that error in the log is actually a red herring because the result of this call: ``` /bin/bash -i -l -c /usr/share/code/code -p '"26f12dfdbc05" + JSON.stringify(process.env) + "26f12dfdbc05"'...
@kamikazechaser so is `bash` not the terminal you have a profile for? Is it `fish`? I wonder if we detect your default shell wrongly?
And is it set as environment variable `SHELL`?
I think this is obsolete with V2.
This reproduces with a minimal Electron app too: https://github.com/electron/electron/issues/45916
/duplicate https://github.com/microsoft/vscode/issues/3884
I wonder if we should introduce a new state along side running/cancelled/finished to indicate this. Basically a 4th state for input by user needed? And we would use this in...
Besides the UX piece, this needs some kind of new API and adoption for all providers.
fyi @jo-oikawa @mrleemurray our designs need to include this state: a session is in progress but also stuck on user input