Dynamic reading in Windows Terminal

[jeanbrazcosta]

NVDA is not dynamic reading in Windows Terminal after a few lines.

When opening Windows terminal, after having several lines in the terminal, when entering any command that returns some information, NfVDA does not read.

Steps to reproduce:

Open Windows terminal and use git for example or whatever, use several commands after a while NVDA will stop announcing dynamic changes

Actual behavior:

NVDA stops reading

Expected behavior:

Deveria anunciar as informações retornardas após algum comando, exemplo, git checkout branch

System configuration

NVDA installed/portable/running from source:

NVDA installed

NVDA version:

2021.2

Windows version:

21 h 1

Name and version of other software in use when reproducing the issue:

Windows Terminal version: 1.0

Other information about your system:

Other questions

Does the issue still occur after restarting your computer?

Have you tried any other versions of NVDA? If so, please report their behaviors.

If NVDA add-ons are disabled, is your problem still occurring?

Does the issue still occur after you run the COM Registration Fixing Tool in NVDA's tools menu?

[lukaszgo1]

cc @codeofdusk

[codeofdusk]

When NVDA stops reading in Windows Terminal, does Windows Explorer continue to work as intended, or do parts of the interface suddenly become inaccessible (i.e. focus tracking becomes unreliable)?

[Neurrone]

I encounter this on a daily basis, see microsoft/terminal#10911. It doesn't seem to be high on their priority of things to fix though unfortunately.

[jeanbrazcosta]

Yes, when the aniver stops reading the focus still remains reliable. Enviado do meu iPhone

…

Em 20 de nov. de 2021, à(s) 21:53, Bill Dengler ***@***.***> escreveu: When NVDA stops reading in Windows Terminal, does Windows Explorer continue to work as intended, or do parts of the interface suddenly become inaccessible (i.e. focus tracking becomes unreliable)? — You are receiving this because you authored the thread. Reply to this email directly, view it on

[codeofdusk]

Duplicate of microsoft/terminal#10911. Sadly I haven't been able to reproduce this.

[Neurrone]

I'm using Terminal 1.11.2921.0, Windows 10.0.19043.1348.

[Neurrone]

I also forgot to mention that nearly all of my usage of Terminal is either SSH or WSL2. In case this helps with reproducing the problem.

[Adriani90]

The referenced terminal bug has been fixed in January 2023, and the issue is not reproducible anymore with NvDA 2024.4.1. Closing as works for me. If you are still having this issue, pleaes comment and we can reopen.