Open alias "wt" have unexpected behavior.

[hungpham3112]

Windows Terminal version

1.12.220208003-release1.12

Windows build number

10.0.22000.0

Other Software

No response

Steps to reproduce

1. Using scoop to add windows-terminal from extras bucket
2. install python use scoop install python
3. run windows terminal and "wt.exe" in 2 instances.
4. type python in window terminal and see result
5. type python in wt.exe and see result

Expected Behavior

Path in wt.exe same like windows terminal.

Actual Behavior

bandicam 2022-02-21 11-54-25-458.zip

You can see in here, because it took 20 mb

[hello-smile6]

#12535 may be related (Crash due to directory being provided as first parameter)

[hungpham3112]

#12535 may be related (Crash due to directory being provided as first parameter)

I don't know but wt.exe and Window Terminal seems to use the different$env:path

On the left wt.exe, on the right Window terminal. So magic

[zadjii-msft]

Hmm. So, the path is different when launched via the alias or via the actual start menu shortcut. Tha's quite unexpected. They both seem to have the same settings, so it's not like one launched the unpackaged version and the other launched the packaged version.

I suppose I don't totally know how scoop sets up the app execution alias. Presumably, it doesn't actually set up an alias the same way as the Store install would. Hmm. There's another thread floating around here that's a bit similar. Lemme look that up.

[zadjii-msft]

#11777 was the thread I was thinking of. That doesn't mention installing from scoop though, so that might not be the only cause.

[hungpham3112]

#1125 was the thread I was thinking of. I can confirm to you that wt.exe used my old path in 2 month ago, it's not updated. I believe scoop quite clean and not related to this issue. Both wt.exe and Window Terminal share same directory

This morning, I checked wt.exe and it can open python but $env:path still stay the same. Is there any update?

[zadjii-msft]

I'm pretty sure #1125 only applies if you change the environment variables while the Terminal is running. From a cold launch (which it looks like this is), then it should always get a fresh set of variables. And I wouldn't expect different launch mechanisms to have different results. Kinda interesting that the scoop/apps/windows-terminal/current directory isn't on the path...

What happens when you launch wt from the Run Dialog? Do you get the working path, or the broken one?

[hungpham3112]

I'm pretty sure #1125 only applies if you change the environment variables while the Terminal is running. From a cold launch (which it looks like this is), then it should always get a fresh set of variables. And I wouldn't expect different launch mechanisms to have different results. Kinda interesting that the scoop/apps/windows-terminal/current directory isn't on the path...

What happens when you launch wt from the Run Dialog? Do you get the working path, or the broken one?

It said: