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

wt shortcut not opening in the requested context from Address bar when Starting directory option is customized #11800

Closed
egvijayanand opened this issue Nov 22, 2021 · 3 comments
Labels
Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.

Comments

@egvijayanand
Copy link

Windows Terminal version

1.11.2921.0

Windows build number

10.0.22000.348

Other Software

No response

Steps to reproduce

  • Customize the Starting directory for the Command Prompt tab in Windows Terminal Settings
  • Open any folder (apart from Starting directory) in the File Explorer and type wt in the address bar to launch the Terminal
  • Fails to persist the launch context and instead opens with the Starting directory

Expected Behavior

During the launch, the Terminal should retain the launch context for specific scenarios like Address bar launch and Context menu launch

Actual Behavior

Always opens with the Starting directory customization, this is fine for direct launch whereas when launched from the address bar or from the context menu of a folder, then it is expected to retain the launch context.

@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 Nov 22, 2021
@zadjii-msft
Copy link
Member

This question's been answered a huge number of times before. Please search before filing new issues.

/dup #878

Specifically, there are more details as to "why" here: #878 (comment)

@ghost
Copy link

ghost commented Nov 22, 2021

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!

@ghost ghost closed this as completed Nov 22, 2021
@ghost ghost added Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing. and removed 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 Nov 22, 2021
@egvijayanand
Copy link
Author

Hope the original issue #878 gets an official resolution at the earliest.

For time being, found a workaround by creating a batch file in the profile folder (so that it is available whenever I log in) with the below command in it to invoke the Windows Terminal with the right starting directory.

Name the batch file, like wtd.bat, as per your convenience as that will become the command to execute on the address bar, wtd in this case.

wt.exe --startingDirectory "%cd%"

This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
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

2 participants