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

Duplicate the tab with the same path #10105

Closed
Taswen opened this issue May 17, 2021 · 3 comments
Closed

Duplicate the tab with the same path #10105

Taswen opened this issue May 17, 2021 · 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

@Taswen
Copy link

Taswen commented May 17, 2021

Description of the new feature/enhancement

Now CTRL + SHIFT + D can copy the existing tab page (with the same configuration file). New tabs always start with the default path, such as C:/Users/myUserName, even though my working path has been moved to D:/somePath.
For me, opening a new tab is often just to operate around the previous path. If the path is too deep, I have to cd in again.
It's also more annoying for remote operations.

Proposed technical implementation details (optional)

  1. For tab located on the local file system, it should just save the path and reopen in the new tab.
  2. For tab that is connecting to a remote, to save SSH’s account temporarily for automatic login may help.
@Taswen Taswen added the Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. label May 17, 2021
@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 May 17, 2021
@skyline75489
Copy link
Collaborator

For local operations, it's possible. But you need to manually configure the shell for now. See #3158 (comment) for help if you're a PowerShell user.

There are also discussions about the SSH scenarios in #3158 and unfortunately that is not possible at the moment. Nor do I think it will be possible in the future.

@ghost
Copy link

ghost commented May 17, 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 May 17, 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 May 17, 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