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

Configure all new tabs for the starting directory when Windows Terminal was opened. #9553

Closed
Dominiquini opened this issue Mar 19, 2021 · 2 comments
Labels
Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.

Comments

@Dominiquini
Copy link

Description of the new feature/enhancement

When I use Windows Explorer, select a folder and click in "Open in Windows Terminal" on the context menu, the default terminal is opened in the correct directory. But if I create a new tab (with the same or different terminal type), their open in the default directory, configured in the json file.
I think would be better to open any new tab using the starting directory that I selected in the Windows Explorer.
I'm not asking to open the new terminal tabs in same directory as existing tab. Only to open new terminal tabs in the directory that I opened Windows Terminal from the context menu.

Proposed technical implementation details (optional)

When I open Windows Terminal with a custom starting directory, all new tabs need to use that definition!

Thanks.

@Dominiquini Dominiquini added the Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. label Mar 19, 2021
@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 Mar 19, 2021
@DHowett
Copy link
Member

DHowett commented Mar 19, 2021

/dup #8933. Thanks for filing!

@ghost
Copy link

ghost commented Mar 19, 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 Mar 19, 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 Mar 19, 2021
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. 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

3 participants
@DHowett @Dominiquini and others