[BRLTTY] SPEAK_NEXT_WORD and word boundaries in Debian Trixie

[Eric Scheibler]

Dave Mielke <Dave at mielke.cc> schrieb am 19.01.2026, 14:54 -0500:
> In config.mk, what does the RGX_PACKAGE line say?

RGX_PACKAGE = libpcre2-32

> >I think, 7, 8 and 9 would be more intuitive / better to reach. Orca does this too.
> 
> This has been done.

Confirmed.

> >Anyway I find it more convenient to keep both part and word on the same key and add ShiftLeft instead like this:
> 
> I'm still resisting adding a new key. Maybe you'll find it a lot more comfortable now that 8,9,0 has bee moved to 7,8,9.

Ok, I'm only interested in the laptop key table and for this, ShiftLeft suits me perfectly fine. But if you want to define
some key, which also works for the keypad... don't know.

Problem with 7, 8 and 9 is, that they are so far away from j, k and l although the functions are strongly related.

- full words
- lines
- partial words
- chars

If you want to keep the key binding logic, you would have to assign full words to u, i and o and put lines on 7-9. But
lines are important too: I use the shortcut a lot and don't want to move my fingers that far. In fact I use the line
bindings much more often than the char bindings.

But we don't want to introduce such massive changes (usability!). Therefore your 7-9 solution seems to be a good
compromise. I don't mind these bindings (never used them before -> no collision here). I just add my 4 ShiftLeft
bindings in my personal key table and everyone is happy :-).

> >And we should keep the laptop keytable bindings "shift+arrow_left" and "shift+arrow_right" in mind - currently they
> >still point to the word commands.
> 
> Those have now been converted to move by partial words.

Yes, I think, that should be the default. Thanks.

Regarding your other question about a config param to switch full/part word definition: I don't think this is necessary (just adds complexity).

Cheers
Eric