[BRLTTY] SPEAK_NEXT_WORD and word boundaries in Debian Trixie

[Eric Scheibler]

Dave Mielke <Dave at mielke.cc> schrieb am 07.01.2026,  4:20 -0500:
> While I'm in that code: What do you think about adding Spell Current Line? It mightn't be that useful for a long Linux line bu I suspect it'd be helpful for a short, multi-word line such as one easily finds on an Android screen element.

Can't hurt.

> I'm leaning toward having two versions of (let's call it) a short word. One being what it used to be (letters, digits, underscore) and the other being that plus whatever is in word-characters. The former would, I think, be most useful for code and the other could be useful for text. What do you think?

Most times I would want the old Brltty 6.5 behavior. If I can configure the delimiter so much the better for it. The
current 6.7 behavior might be useful sometimes but after two weeks I still find it more annoying than practical in most
cases. Therefore I see the new behavior as an additional feature and the old one as the default.

But you also could define it the other way around and make the 6.7 behavior default. As long as I can redefine delimiter
and keyboard shortcuts I don't care in the end.

> If we have multiple versions of a short word then how do we switch between them? Any thoughts on bindings for that?

If you don't want a set of extra keyboard shortcuts (big and short word) but a wordchar delimiter setting in brltty.conf
instead, how about:

    wordchar_delimiters = "/-.,;:"
    ignore_wordchar_delimiters = true / false?

And then bind ignore_wordchar_delimiters to the keyboard shortcut of your choice?
Don't know, maybe Capslock + k to turn ignore_wordchar_delimiters on or off, because Tab+k speaks the current word...

Cheers
Eric