-
Notifications
You must be signed in to change notification settings - Fork 8.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open alias "wt" have unexpected behavior. #12545
Comments
This comment was marked as off-topic.
This comment was marked as off-topic.
I don't know but On the left |
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 |
#11777 was the thread I was thinking of. That doesn't mention installing from scoop though, so that might not be the only cause. |
#1125 was the thread I was thinking of. I can confirm to you that This morning, I checked |
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 What happens when you launch |
|
and |
This might have been fixed by #14999 |
Hey we pretty aggressively changed how env vars are loaded in 1.18. Could you check if this is fixed in Terminal Preview/? |
This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment. |
I will take a look and response as soon as I can. |
This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment. |
5 similar comments
This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment. |
This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment. |
This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment. |
This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment. |
This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment. |
I tested, version 1.18 fixed PATH in |
Windows Terminal version
1.12.220208003-release1.12
Windows build number
10.0.22000.0
Other Software
No response
Steps to reproduce
scoop
to addwindows-terminal
fromextras
bucketwindows terminal
and "wt.exe" in 2 instances.window terminal
and see resultwt.exe
and see resultExpected Behavior
Path in
wt.exe
same likewindows terminal
.Actual Behavior
bandicam 2022-02-21 11-54-25-458.zip
You can see in here, because it took 20 mb
The text was updated successfully, but these errors were encountered: