Skip to content
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

Feature Request: Ability to call Windows Terminal through Win+X Quick Link Menu #1132

Closed
Aster-the-Med-Stu opened this issue Jun 4, 2019 · 3 comments
Labels
Area-Server Down in the muck of API call servicing, interprocess communication, eventing, etc. Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Product-Terminal The new Windows Terminal. Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.

Comments

@Aster-the-Med-Stu
Copy link

Aster-the-Med-Stu commented Jun 4, 2019

Summary of the new feature/enhancement

Apparently the new Windows Terminal would be some people's default terminal. It is possible that they wish to replace PowerShell/cmd in Quick Link Menu with it. Currently there are 3rd softwares/scripts doing the job, but they couldn't add keyboard shortcut. So please add an option to add it to Quick Link menu in Windows Terminal's settings.

@Aster-the-Med-Stu Aster-the-Med-Stu added the Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. label Jun 4, 2019
@ghost ghost added Needs-Tag-Fix Doesn't match tag requirements Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting labels Jun 4, 2019
@Aster-the-Med-Stu Aster-the-Med-Stu changed the title Feature Request: Ability to call Windows Terminal quickly through Win+X Quick Link Menu Feature Request: Ability to call Windows Terminal through Win+X Quick Link Menu Jun 4, 2019
@hez2010
Copy link

hez2010 commented Jun 4, 2019

Currently you can simply run 'wtd' to start Windows Terminal quickly.

@zadjii-msft
Copy link
Member

This is actually something that'll be fixed by #492, whenever we end up adding support for that. When we do add that feature, then when you open a commandline application, it will launch in your default terminal application, as opposed to conhost. So using Win+X to launch you shell will actually launch the shell attached to Windows Terminal.

@zadjii-msft zadjii-msft added Area-Server Down in the muck of API call servicing, interprocess communication, eventing, etc. Product-Terminal The new Windows Terminal. Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing. labels Jun 4, 2019
@ghost ghost removed the Needs-Tag-Fix Doesn't match tag requirements label Jun 4, 2019
@mottosso
Copy link

Currently you can simply run 'wtd' to start Windows Terminal quickly.

Is this still supposed to work? Neither wt or wtd is available here. I've got the Preview build, released yesterday on Windows Store. In my Windows Terminal application directory, I've got conhost.exe and WindowsTerminal.exe, however this directory wasn't added to my PATH on install, and I'm not sure if it should.

# Install dir
C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_0.2.1715.0_x64__8wekyb3d8bbwe

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area-Server Down in the muck of API call servicing, interprocess communication, eventing, etc. Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Product-Terminal The new Windows Terminal. Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.
Projects
None yet
Development

No branches or pull requests

4 participants