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

Implement scrolling and selection of output text via the keyboard #5948

Closed
Neurrone opened this issue May 17, 2020 · 2 comments
Closed

Implement scrolling and selection of output text via the keyboard #5948

Neurrone opened this issue May 17, 2020 · 2 comments
Labels
Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.

Comments

@Neurrone
Copy link

Neurrone commented May 17, 2020 •
edited
Loading

Environment

Windows build number: 10.0.19041.264
Windows Terminal version (if applicable): latest 0.11 preview
NVDA: latest master snapshot alpha-20220,1c4519a6

Steps to reproduce

  1. Attempt to use the keyboard to scroll upwards.
  2. Attempt to select text in the output buffer.

Expected behavior

It should be possible to do so

Actual behavior

As far as I know this hasn't been implemented. I was trying to use the hotkeys described here. The legacy terminal does support this but unfortunately not in WSL.
@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, 2020
@Neurrone Neurrone mentioned this issue May 17, 2020
Closed
@DHowett
Copy link
Member

DHowett commented May 18, 2020

I believe this will be covered by /dup #715. Thank you!

@ghost
Copy link

ghost commented May 18, 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 May 18, 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 May 18, 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
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 @Neurrone