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

[FR] New 'selectAll' shortcut action with default mapping ctrl+shift+a #3723

Closed
iamGavinJ opened this issue Nov 26, 2019 · 4 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

@iamGavinJ
Copy link
Member

Description of the new feature/enhancement

Create a new shortcut action to select all text in the buffer

Proposed technical implementation details (optional)

ctrl+shift+a should select all text

@iamGavinJ iamGavinJ added the Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. label Nov 26, 2019
@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 Nov 26, 2019
@j4james
Copy link
Collaborator

j4james commented Nov 27, 2019

This is probably covered by #1469, which was also suggesting the need for a Select All key binding.

@DHowett-MSFT
Copy link
Contributor

Yep, this is a /dupe of #1469.

@ghost
Copy link

ghost commented Nov 27, 2019

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 Nov 27, 2019
@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 Nov 27, 2019
@iamGavinJ
Copy link
Member Author

@j4james, @DHowett thanks for finding the dupe. I did do a brief search as I really didn't believe I would be the first to raise this but none of my search terms were turning anything up.

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