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

Some possible improvements to the accessibility buffer #175133

Closed
jvesouza opened this issue Feb 22, 2023 · 1 comment
Closed

Some possible improvements to the accessibility buffer #175133

jvesouza opened this issue Feb 22, 2023 · 1 comment
Labels
*duplicate Issue identified as a duplicate of another issue(s)

Comments

@jvesouza
Copy link

Type: Feature Request

CC: @meganrogge @isidorn
At least in my environment, whenever I access the terminal's accessibility buffer, the focus is always moved to the beginning of it. This causes us to lose some time to find the begin of the response of the last command executed, especially if the response is long.
Would it be possible to update the accessibility buffer without changing the focus? The focus position would remain the same since the last access.

When executing a long-running command in the terminal, there seems to be no easy way to find out its status, since the accessibility buffer is only updated at the end of the command.
If, for example, the command being executed asks me for some intervention and if for some reason I have not heard this request, there would be no easy way to repeat it.

VS Code version: Code - Insiders 1.76.0-insider (7b6b686, 2023-02-22T05:27:34.124Z)
OS version: Linux x64 6.1.12-200.fc37.x86_64
Modes:
Sandboxed: Yes
Remote OS version: Linux x64 4.14.146-93.123.amzn1.x86_64

@meganrogge
Copy link
Contributor

Thank you for the issue. We're tracking those here:

/duplicate #175011 and #172582

@vscodenpa vscodenpa added the *duplicate Issue identified as a duplicate of another issue(s) label Feb 22, 2023
@github-actions github-actions bot locked and limited conversation to collaborators Apr 8, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
*duplicate Issue identified as a duplicate of another issue(s)
Projects
None yet
Development

No branches or pull requests

3 participants