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

Command prompt here? #6550

Closed
nurbles opened this issue Jun 17, 2020 · 2 comments
Closed

Command prompt here? #6550

nurbles opened this issue Jun 17, 2020 · 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

@nurbles
Copy link

nurbles commented Jun 17, 2020

Description of the new feature/enhancement

Is there any way to add some like "New Command Tab Here" to a File Explorer shift+context menu as there are for the old-style cmd and power shells? I apologize if this is already possible, but I don't know how those things work, so I couldn't figure out how to do it with Terminal. However, if I could change the existing one to terminal, I'd never use the CMD shell again. :-)

Proposed technical implementation details (optional)

A new tab with the current directory set to the one currently selected for the shift+context menu that invokes the command. The best possible options would be to be able to open any shell, as the current user or as administrator in the current folder from the file explorer shift+context menu.
@nurbles nurbles added the Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. label Jun 17, 2020
@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 Jun 17, 2020
@DHowett
Copy link
Member

DHowett commented Jun 17, 2020

/dup #1060

@ghost
Copy link

ghost commented Jun 17, 2020

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 Jun 17, 2020
@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 Jun 17, 2020
This issue was closed.
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. 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
2 participants
@DHowett @nurbles