Re: Review position not following system cursor in terminal applications


Jason White
 

Thanks - I wasn't aware of that option. Restarting NVDA seemed to fix it in
Windows Subsystem for Linux, but not in the msysv2 console.

-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Tyler Spivey
Sent: Friday, August 17, 2018 7:30 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Review position not following system cursor in terminal
applications

Is Caret moves review cursor (NVDA+6) on?
On 8/17/2018 4:23 PM, Jason White via Groups.Io wrote:
The problem isn’t confined to Windows Subsystem for Linux; I noticed
it under msysv2 as well.

 

*From:* nvda@nvda.groups.io <nvda@nvda.groups.io> *On Behalf Of
*Walker, Michael E
*Sent:* Friday, August 17, 2018 4:20 PM
*To:* nvda@nvda.groups.io
*Subject:* Re: [nvda] Review position not following system cursor in
terminal applications

 

Jason,

 

Do you absolutely need the Windows subsystem for Linux to accomplish
your goals? Can you accomplish what you need through PowerShell, the
Cygwin terminal, MSYS, or Git BASH?

 

Best regards,

Mike

 

*From:* nvda@nvda.groups.io <mailto:nvda@nvda.groups.io>
[mailto:nvda@nvda.groups.io] *On Behalf Of *Jason White via Groups.Io
*Sent:* Friday, August 17, 2018 3:16 PM
*To:* nvda@nvda.groups.io <mailto:nvda@nvda.groups.io>
*Subject:* [nvda] Review position not following system cursor in
terminal applications

 

I’ve been trying to use NVDA 2018.2.1 in terminal applications such as
the Windows Subsystem for Linux. The BrailleExtender add-on is loaded,
and highly desirable. It’s configured by default to ensure that the
braille display tracks the review position in terminal applications.

 

Unfortunately, the review position isn’t following the system cursor.
Thus, for example, if I issue a command that generates several lines
on the terminal, and the cursor moves to the  new prompt that
immediately follows this output, the review position isn’t moved forward
with it.

 

All of the NVDA preferences related to navigation seem to be set
correctly as far as I can tell (I haven’t changed them from the
defaults, as it’s a new installation on an up to date Windows 10
version
1803 system).

 

Have I neglected to change a setting, or is there a deeper problem here?
Suggestions about likely causes and solutions would be most welcome.

 

Join nvda@nvda.groups.io to automatically receive all group messages.