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.
-
@ppatel @Tamasg I'll give it a look later. I'm no vim expert myself but can probably at least find a cheatsheet to figure out the basics.
One thing I do know is that it has the insert and command mode, which I believe is conveyed through the status bar. That bit, you MAY not want to silence as it's a bit of a thing to figure out otherwise
Maybe that was already taken care of, will check and report back later -
@ppatel @Tamasg I'll give it a look later. I'm no vim expert myself but can probably at least find a cheatsheet to figure out the basics.
One thing I do know is that it has the insert and command mode, which I believe is conveyed through the status bar. That bit, you MAY not want to silence as it's a bit of a thing to figure out otherwise Maybe that was already taken care of, will check and report back later -
@FreakyFwoof I fixe it. Apparently there was a regression. I'd managed to fix it at one point and then somehow reverted it. Download the latest. Let me know if you have more trouble.
https://github.com/PratikP1/Terminal-Access-for-NVDA/releases/tag/v1.0.45
-
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. Inspired by TDSR and Speakup, there's quite a bit of functionality here. I welcome contributions. Issues and PRs welcome. Lots of testing needed.
Open issues on the Github repo at: https://github.com/PratikP1/Terminal-Access-for-NVDA
Get it here: https://github.com/PratikP1/Terminal-Access-for-NVDA/releases/latest
@ppatel Can you please explain why this seems to duplicate a lot of NVDA's settings in the add-on itself? This is something we very badly need in general, I think, NVDA's terminal support is so shit it can't even use ed properly, but NVDA already has 4 levels of punctuation, indentation reporting, character code announcements, word/character nav, etc. What does this do different?
-
@ppatel Can you please explain why this seems to duplicate a lot of NVDA's settings in the add-on itself? This is something we very badly need in general, I think, NVDA's terminal support is so shit it can't even use ed properly, but NVDA already has 4 levels of punctuation, indentation reporting, character code announcements, word/character nav, etc. What does this do different?
@TheQuinbox @ppatel My thoughts exactly. There are some interesting features (on paper at least - haven't tested this properly yet) but there is certainly a lot of overlap.
-
@TheQuinbox @ppatel My thoughts exactly. There are some interesting features (on paper at least - haven't tested this properly yet) but there is certainly a lot of overlap.
@tuukkao @TheQuinbox I considered all of that. When I started thinking about the features I wanted to implement, the one that made me pause was apps/terminal profiles. I knew that I could apply NVDA's profiles to different windows. But, I wasn't sure that profiles could go down to terminal app levels. For that, I needed to duplicate these settings. If it proves to be not necessary, I'll remove the extraneous stuff. A lot will depend on feedback.
-
@TheQuinbox @ppatel My thoughts exactly. There are some interesting features (on paper at least - haven't tested this properly yet) but there is certainly a lot of overlap.
@tuukkao @TheQuinbox If the community really tells me that they don't want something, I'll be happy to remove it.
-
@FreakyFwoof It's a combo of manual coding and Claude/Codex. I'm not confident enough in my Python writing skills that I can avoid LLMs
-
@TheQuinbox @ppatel My thoughts exactly. There are some interesting features (on paper at least - haven't tested this properly yet) but there is certainly a lot of overlap.
@tuukkao @TheQuinbox I've tried a couple of tricks to avoid some of the NVDA's performance issues. Whether they work long-term needs to be seen. Where I hope this thing should shine is things like bookmarks, windowing, highlight tracking, etc.
-
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. Inspired by TDSR and Speakup, there's quite a bit of functionality here. I welcome contributions. Issues and PRs welcome. Lots of testing needed.
Open issues on the Github repo at: https://github.com/PratikP1/Terminal-Access-for-NVDA
Get it here: https://github.com/PratikP1/Terminal-Access-for-NVDA/releases/latest
I've bumped up the version number for Terminal Access to v1.0.45 with a fix for global keys issue. If you haven't updated it or got to the v1.0.43 release, you can update it here. I've also submited the add-on to the NVDA store. Hopefully, new updates will show up there once approved.
-
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. Inspired by TDSR and Speakup, there's quite a bit of functionality here. I welcome contributions. Issues and PRs welcome. Lots of testing needed.
Open issues on the Github repo at: https://github.com/PratikP1/Terminal-Access-for-NVDA
Get it here: https://github.com/PratikP1/Terminal-Access-for-NVDA/releases/latest
@ppatel Wait I'm confused. Looking at this readme, are a bunch of these features redundant? The review cursor already can move by line, word and character and output the character at the cursor, with char info I can even output Unicode name. Why do you define separate gestures for that which are likely to clash with everything else? What makes this different from NVDA"s normal terminal support? Better selection and automatic profiling? How doe sit know what app you're running?
-
@ppatel Wait I'm confused. Looking at this readme, are a bunch of these features redundant? The review cursor already can move by line, word and character and output the character at the cursor, with char info I can even output Unicode name. Why do you define separate gestures for that which are likely to clash with everything else? What makes this different from NVDA"s normal terminal support? Better selection and automatic profiling? How doe sit know what app you're running?
@x0 The features are duplicated because of profiles. NVDA doesn't do bookmarks or quite a few other things. I've also tried to get better performance out of this than NVDA. I try to detect running apps inside the terminal and assign profiles based on that.
-
@x0 The features are duplicated because of profiles. NVDA doesn't do bookmarks or quite a few other things. I've also tried to get better performance out of this than NVDA. I try to detect running apps inside the terminal and assign profiles based on that.
-
@x0 The features are duplicated because of profiles. NVDA doesn't do bookmarks or quite a few other things. I've also tried to get better performance out of this than NVDA. I try to detect running apps inside the terminal and assign profiles based on that.
@ppatel Yeah, bookmarks, the cursor reading, better selection sound useful, but I kinda need it to suport my existing gestures for reading, these conflict with my add-ons and I simply don't have enough space left to assign them.
-
@ppatel Yeah, bookmarks, the cursor reading, better selection sound useful, but I kinda need it to suport my existing gestures for reading, these conflict with my add-ons and I simply don't have enough space left to assign them.
@x0 The commands should not conflict as they're bound to supported terminals.
-
@x0 The commands should not conflict as they're bound to supported terminals.
@ppatel And what's with the new keystrokes for tabs and such? Doesn't wt already provide those? Basically I'm just confused as to how much of the README was written by AI and accidentally absorbed features into it that the add-on doesn't even need to get involved for.
-
@kaveinthran @x0 Not yet. Claude code is on my list. I need to find the optimum profile for it.
-
@ppatel And what's with the new keystrokes for tabs and such? Doesn't wt already provide those? Basically I'm just confused as to how much of the README was written by AI and accidentally absorbed features into it that the add-on doesn't even need to get involved for.
@x0 WT isn't the only terminal supported. Not all terminals have the same structure. That functionality will help in other terminals.
-
@x0 The features are duplicated because of profiles. NVDA doesn't do bookmarks or quite a few other things. I've also tried to get better performance out of this than NVDA. I try to detect running apps inside the terminal and assign profiles based on that.
-
@kaveinthran @x0 Not yet. Claude code is on my list. I need to find the optimum profile for it.
