[quoted lines by Eric Scheibler on 2026/01/02 at 09:18 +0100] >I would like to restore the previous behavior. But I'm not sure which >component is responsible for this change. Which >setting does Brltty use to know, what defines a word boundary? Could you point >me in the right direction please?
Okay, I looked back at the original code. It treated characters typical of an identifier (letters, decimal digits, and an underscore) as a word and would skip over any group of those. For any non-identifier character it'd go one character at a time. We could have a setting to switch between these two ways. If we go that route then we could add even more ways to define what a word is. Another approach would be to have two sets of commands. In other words, a regular press would do it the old way and a long press would do it the new way (i.e. skip all the way to a whitespace boundary). With this approach we could still add a setting to decide which one is the regular press and which one is the lnng press. What do you (and anyone else) think? -- 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: [email protected] | Ottawa, Ontario | Twitter: @Dave_Mielke Phone: +1 613 726 0014 | Canada K2A 1H7 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ http://mielke.cc/xmother.html (Letter from a Feminist ex-Mother) _______________________________________________ This message was sent via the BRLTTY mailing list. To post a message, send an e-mail to: [email protected] For general information, go to: http://brltty.app/mailman/listinfo/brltty
