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

Open a new tab in the same path but in a different terminal #12514

Closed
0xdw opened this issue Feb 17, 2022 · 3 comments
Closed

Open a new tab in the same path but in a different terminal #12514

0xdw opened this issue Feb 17, 2022 · 3 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

@0xdw
Copy link

0xdw commented Feb 17, 2022

Description of the new feature/enhancement

When opening new tabs. It would be great if it can have an option where we can add the new tab in the same path but in a different terminal application.

For example,
Assume I have opened a folder in the CMD (with a large path) and I want to open that path in WSL. In that case, I would click the new tab and it opens a new window in a different path.

This can really help when we have to open a new tab in a different terminal where the current opened folder path is difficult to type quickly.

Actual Behaviour when opening a new tab

windows-terminal-actual-behaviour

Expected Behaviour when opening a new tab

windows-terminal-expected-behaviour

Proposed technical implementation details (optional)

When we duplicate a tab, is it possible to duplicate it to a different terminal application like below?

Proposed option

@0xdw 0xdw added the Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. label Feb 17, 2022
@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 Feb 17, 2022
@237dmitry
Copy link

237dmitry commented Feb 17, 2022

This available from command line:

wt -w 0 nt --startingDirectory %cd% -p "<Profile name>"     # cmd
wt -w 0 nt --startingDirectory $pwd -p "<Profile name>"     # powershell, dot instead of $pwd works too ( --startingDirectory  . )
wt -w 0 nt --startingDirectory $(pwd) -p "<Profile name>"   # bash

@zadjii-msft
Copy link
Member

Thanks for the suggestion! This is actually already being tracked by another issue on our repo - please refer to #10232 for more discussion.

/dup #10232

@ghost
Copy link

ghost commented Feb 17, 2022

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 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 Feb 17, 2022
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