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

Allow end-users to select and copy shell output without the mouse #4441

Closed
shaunluttin opened this issue Feb 3, 2020 · 2 comments
Closed
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

@shaunluttin
Copy link

shaunluttin commented Feb 3, 2020

Description of the new feature/enhancement

Problem: Selecting and copying shell output requires the use of the mouse.

Solution: Allow end-users to select and copy shell output without the mouse.

Example: In the ConEmu terminal emulator, pressing Shift+UpArrow initiates block selection and navigation of the shell output.

Here is an example from ConEmu which shows a use case in which the end-user selects and copies a commit hash from the git log output.

conemu-cursor-select

@shaunluttin shaunluttin added the Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. label Feb 3, 2020
@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 3, 2020
@zadjii-msft
Copy link
Member

You'd probably be interested in:

@ghost
Copy link

ghost commented Feb 3, 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 Feb 3, 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 Feb 3, 2020
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

2 participants