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.

Sign up for GitHub

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

Jump to bottom

Feature Request: Single-instance mode #2379

Closed
mkielar opened this issue Aug 9, 2019 · 2 comments
Closed

Feature Request: Single-instance mode #2379

mkielar opened this issue Aug 9, 2019 · 2 comments
Labels
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 Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.

Comments

@mkielar
Copy link

mkielar commented Aug 9, 2019

Description of the new feature/enhancement

Implement single-instance mode as an option, so that multiple executions of wt.exe would add new tabs to already running instance of WT, instead of opening new windows.

Proposed technical implementation details (optional)

When I run wt.exe multiple times, I get a new Windows Terminal window every time. I do that quite often when navigating folders in Total Commander. I just type wt and expect the new tab to be opened with the directory I'm currently in in TC. Instead, I'd prefer to have a new tab in existing window.

Similarly, when running a shell (wsl.exe) inside Windows Terminal, if I type wt.exe I'd expect another tab to be opened. Currently nothing happens in this scenario (not even new WT window is opened).

I think, this could be managed with a single setting in profile.json:
"mode": "single-window|multiple-window" or sth similar.
@mkielar mkielar added the Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. label Aug 9, 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 Aug 9, 2019
@j4james
Copy link
Collaborator

j4james commented Aug 9, 2019

This sounds like a duplicate of #2227.

@DHowett-MSFT
Copy link
Contributor

sure is! thanks

@DHowett-MSFT DHowett-MSFT added the Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing. label Aug 9, 2019
@ghost ghost removed the Needs-Tag-Fix Doesn't match tag requirements label Aug 9, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
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 Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@mkielar @j4james @DHowett-MSFT