Open LuminousPath opened 3 years ago
Instead of cmd, you might want to use shell_cmd
. My guess is that cmd
prevents the environmental variable interpolation. See https://forum.sublimetext.com/t/shell-cmd-stopped-working/48792
I don't think the shell_cmd
key is available? I get this error in the console when I try and open a new terminal with shell_cmd
instead of cmd
:
Unable to open <Sublime_Text_Install_Loc>/Data/Packages/Terminus/Terminus.sublime-settings
Traceback (most recent call last):
File "<Sublime_Text_Install_Loc>\Data\Installed Packages\Terminus.sublime-package\terminus/core.py", line 98, in <lambda>
File "<Sublime_Text_Install_Loc>\Data\Installed Packages\Terminus.sublime-package\terminus/core.py", line 149, in run_async
KeyError: 'cmd'
Popping open the error line:
I feel like this line might need a guard against only shell_cmd
existing in config
Oh, you are right. We don't respect shell_cmd in config, only as a parameter passed by the build system.
Added a PR that fixes it by assigning cmd
and shell_cmd
the values from config
before the rest of the checks occur
When I try and start up a powershell session via Terminus, I try and pass in a custom powershell profile like I normally do when using windows terminal. However, the command line variables don't seem to be expanding. So the following error code occurs:
the current settings I'm using are:
I saw in #88 that someone had fixed it by explicitly setting their environment variables, but that didn't seem to do anything.
Is there a particular way that Terminus calls
cmd.exe
? I would think it uses the same mechanism that sublime uses in its build system...