I’m excited to announce the first public release of Terminal Access for NVDA: an add-on focused on improving the NVDA experience when working in terminal/console applications.
-
@kaveinthran @x0 @joslee As far as I can tell, NVDA's profiles can be programmatically launched by Window/app names. Unless I'm mistaken, NVDA can't detect apps that are running inside terminal windows. This add-on tries to detect those apps. Whether or not it succeeds remains to be seen.
-
@kaveinthran @x0 @joslee As far as I can tell, NVDA's profiles can be programmatically launched by Window/app names. Unless I'm mistaken, NVDA can't detect apps that are running inside terminal windows. This add-on tries to detect those apps. Whether or not it succeeds remains to be seen.
@ppatel @kaveinthran @joslee Hmmm. That'd be interesting. If it actually parses out the command you run like the shell does it could maybe, but you have to be aware of pipes not just basic commands, and anything that relies on, say, $EDITOR is likely to break unless it can identify the application from some static output it emits.
-
@ppatel @kaveinthran @joslee Hmmm. That'd be interesting. If it actually parses out the command you run like the shell does it could maybe, but you have to be aware of pipes not just basic commands, and anything that relies on, say, $EDITOR is likely to break unless it can identify the application from some static output it emits.
@x0 @kaveinthran @joslee It's a work in progress. I'm still working on some of the logic in a local branch. Things like Git probably can't be detected unless I somehow try to use the command history feature.
-
S svenja@mstdn.games shared this topic