-
Notifications
You must be signed in to change notification settings - Fork 8.4k
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
Bring "Open in Windows Terminal" for Right Click on Drive Letter #6654
Comments
I'm not sure if this is caused by the same thing as #6414 or not. |
I'm glad your tracking that issue as well (#6414). I was about report that. |
No no, this is the exact same thing. /dup #6414 |
Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report! |
That should teach me to read. It probably isn't the same. |
I'm now using version 1.6.10571.0 of Windows Terminal. There still is no right click on the drive letter to "Open in Windows Terminal". I can, however, right click on a white area in any folder and "Open in Windows Terminal" is available. After reading this thread, I'm confused on whether this is a duplicate of another issue. When I searched around, I came right back to this one. |
Yep, there has to be a way. With a shift right click there is an "Open PowerShell window here" and on a regular right click there is an "Open with Code" item. |
This is being tracked internally with MSFT:32135340 (I think?) |
(It cannot be done with packaged COM today. Yeah.) |
|
Okay, so if we target the sv2 sdk, this might just work today, but we really really need to confirm on Windows 10 manually. |
What is sv2 sdk? does support Type="Drive" now? please tell me,thank you. |
@nhchmg |
Description of the new feature/enhancement
Bring "Open in Windows Terminal" for right click on drive letter. In Windows Terminal 1.1.1671.0 I am able to do this on a folder but it does not work on a drive letter.
The text was updated successfully, but these errors were encountered: