Closed BitFis closed 7 months ago
Do you have any thoughts on how this would interact with the existing "runOnSave.shell"
setting, which is used when runIn="backend"
to specify the path to the shell to use?
since runIn can still be overwritten per command, I would have expected following priority. 1. overwriting all configuration with highest priority:
"comman[].runIn":
"runOnSave.runIn":
"runOnSave.shell":
set to runIn="backend"
I believe this is reasonable. I add a new option runOnSave.defaultRunIn
, which's default value is vscode
.
Will be released in coming version 1.7.1
Hello,
I maybe have missed this configuration, but it seems the default behavior of
"runIn"
is"backend"
. I would like to request to overwrite the default behavor via a"runOnSave.shell"
global configuration, allowing the user the change between"terminal"
and"backend"
without the need to overwrite the projectssettings.json
. If there are other options to achieve this I am all ears.Thanks