[BRLTTY] SPEAK_NEXT_WORD and word boundaries in Debian Trixie

Dave Mielke Dave at mielke.cc
Mon Jan 26 09:13:49 UTC 2026


[quoted lines by Eric Scheibler on 2026/01/26 at 01:22 +0100]

>Right, works. Let's keep it this way.

Would you like ASPK_DEL/REP/INS_CHARS to stay on m,comma,period or do you think they should move up to j,k,l and that the ones currently on j,k,l should move to the lower row?

>one which slows down speech navigation autorepeat so that you can actually hear what's going on.
>
>Yes, that's useful. Maybe slow it down even a little bit more?

Could you please experiment with these values and let me know which ones work best? The rate for navigating by character, word, and line are separate. Right now they're hard-coded. Look in ktb_translate.c for case BRL_CMD_SPEAK_PREV_CHAR. Starting from there you'll find the three values.

While they're hard-coded for now, being as it's an experiment, I'm not one for leaving it like that. What do you think of making all three of them separate choices in the Speech submenu?

>Besides that, I think we are done here. Thank you.

You're very welcome. The word-nav branch is now gone and the code has been merged into master.

-- 
I believe the Bible to be the very Word of God: http://Mielke.cc/bible/
Dave Mielke            | 2213 Fox Crescent | WebHome: http://Mielke.cc/
EMail: Dave at Mielke.cc  | Ottawa, Ontario   | Twitter: @Dave_Mielke
Phone: +1 613 726 0014 | Canada  K2A 1H7   |
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
http://mielke.cc/xmother.html (Letter from a Feminist ex-Mother)


More information about the BRLTTY mailing list