Use env option about terminus

[randy3k]

What shell are you using? A better solution is to specify the path in your shell.

[gepd]

I'm using cmd but I need a solution not os dependent. I want to include your package in my plugin Deviot but In some cases I need to modify the env, so I need a solution to be configured by the plugin it self, not by the user. My idea was to use the shell_configs option of your plugin, do you think there is another way to achieve that?

[randy3k]

Is this what you want?

path = new_path + ":" + old_path
window.run_command("terminus_open", {"cmd": "whatever", "env": {"PATH": path }})

However, the PATH variable only makes sense in Unix system.

[gepd]

However, the PATH variable only makes sense in Unix system.

Why would be that?

With your command I got the results I do expected, however what would be the best way to get the cmd used by the os, I mean in windows is cmd.exe in unix system the bash, there is a way to let your plugin decide this and only modify the PATH?

[randy3k]

Ai, actually Windows also uses PATH. But there are 2 issues.

1. Windows uses ; to separate paths instead of :

2. A more important issue is to support WSL. So it means you need to also define WSLENV it seems that the PATH variable is passed automatically.

[gepd]

1. I've been dealing with it using os.pathsep (link) when I've need it
2. you mean by ST?

Cause your last command worked but I only wish to avoid manually "select" the cmd

[randy3k]

os.pathsep is a better solution. I meant from cmd.exe to wsl.exe.

[gepd]

It works with cmd.exe but not with wsl.exe, I've just checked it

[gepd]

I've checked again and it's working with wsl.exe too

After output the wsl paths with echo $PATH I realized that my paths were there, so I guess shouldn't be a problem using the env feature

[randy3k]

Ya, it was also what I have figaured out.