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 - Easier means of launching Windows Terminal #1479

Closed
JaimeStill opened this issue Jun 23, 2019 · 8 comments
Closed

Feature Request - Easier means of launching Windows Terminal #1479

JaimeStill opened this issue Jun 23, 2019 · 8 comments
Labels
Area-Settings Issues related to settings and customizability, for console or terminal Issue-Docs It's a documentation issue that really should be on MicrosoftDocs/Console-Docs Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. Product-Terminal The new Windows Terminal. Resolution-Won't-Fix We're just really obstinate about this. There's probably a good reason.

Comments

@JaimeStill
Copy link

Summary of the new feature/enhancement

Most of the time, when I open a command prompt, I either run cmd from the navbar of the directory I want to open in Windows Explorer, or I run cmd from the Run utility (Win + R).

It would be great if one of the solutions outlined below would allow better integration of Windows Terminal, making it a more viable shell for use in Windows.

Proposed technical implementation details (optional)

Default Shell
In Windows 10, you have the option of setting application defaults. A Shell category could be added and linked to Windows Terminal. This way, any time you launch PowerShell, Command Prompt, or any other CLI, it will launch in Windows Terminal. I know OS-wide settings are outside of the scope of this project, but I think it is a good conversation to have regarding people who want to use this tool by default at the operating system level.

terminal-settings

Alternative Solution
Provide a way to launch Windows Terminal in the same way you can use cmd to launch Command Prompt (as specified above).

@JaimeStill JaimeStill added the Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. label Jun 23, 2019
@ghost ghost added Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Needs-Tag-Fix Doesn't match tag requirements labels Jun 23, 2019
@Shorotshishir
Copy link

instead of cmd, type wt

I either run cmd from the navbar of the directory I want to open in Windows Explorer, or I run cmd from the Run utility (Win + R).

@JaimeStill
Copy link
Author

@Shorotshishir thanks, I didn't find any mention of this on my initial tinkering. This is definitely helpful! However, it does not work for resolving the current directory when launching from the navigation bar in Explorer.

@Shorotshishir
Copy link

@JaimeStill use "startingDirectory" : "%CD%". your issue will be resolved.
image

@ducaale
Copy link

ducaale commented Jun 23, 2019

@Shorotshishir is it possible to use %__CD__% only when launching from the navigation bar in Explorer and use %PROFILE% when launching from start menu?

@JaimeStill
Copy link
Author

@ducaale @Shorotshishir having the ability to differentiate the two scenarios would definitely be ideal.

@Dinjoralo
Copy link

Dinjoralo commented Jun 24, 2019

I'm guessing this will come later when the Terminal is closer to being out of preview, but a way to just have this popup whenever CMD/Powershell/WSL would open would be nice.

@yodurr yodurr added Area-Settings Issues related to settings and customizability, for console or terminal Issue-Docs It's a documentation issue that really should be on MicrosoftDocs/Console-Docs Product-Terminal The new Windows Terminal. labels Jun 25, 2019
@ghost ghost removed the Needs-Tag-Fix Doesn't match tag requirements label Jun 25, 2019
@DHowett-MSFT
Copy link
Contributor

Right now, wt is the "easier" way to launch wt. If you're using a dev build, it's wtd. This'll be better served by #492.

@DHowett-MSFT DHowett-MSFT added Resolution-Won't-Fix We're just really obstinate about this. There's probably a good reason. and removed Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting labels Jun 27, 2019
@ledhed-jgh
Copy link

While this is actually the opposite of "Launching" Windows Terminal, it would be great if you could close the current tab (Powershell or CMD) with CTRL+D. This is very common on Linux shells like Bash.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area-Settings Issues related to settings and customizability, for console or terminal Issue-Docs It's a documentation issue that really should be on MicrosoftDocs/Console-Docs Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. Product-Terminal The new Windows Terminal. Resolution-Won't-Fix We're just really obstinate about this. There's probably a good reason.
Projects
None yet
Development

No branches or pull requests

7 participants