Date: Wed, 19 Apr 2023 17:36:25 +0200 From: Hans Petter Selasky <hps@selasky.org> To: Pau Amma <pauamma@gundo.com> Cc: freebsd-accessibility@freebsd.org Subject: Re: FreeBSD-14 and accessibility Message-ID: <77362659-4cb5-a34b-44b3-209b3a4997a1@selasky.org> In-Reply-To: <b3cca3be-aabf-68dc-9f51-d033cbfb4fa1@selasky.org> References: <af27328d-43fc-f116-6a31-f11d42bf3d68@selasky.org> <0f9f2f6e6ce9fe3ec67264f934bbf831@gundo.com> <b3cca3be-aabf-68dc-9f51-d033cbfb4fa1@selasky.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 4/19/23 11:02, Hans Petter Selasky wrote: > On 4/19/23 04:47, Pau Amma wrote: >> On 2023-04-18 13:33, Hans Petter Selasky wrote: >>> Hi, >>> >>> Are the current VT accessibility patches in a state worth committing? >>> >>> I'm thinking of: >>> >>> 1) Updates for kernel >>> https://reviews.freebsd.org/D35754 >>> >>> 2) New vtspeakd daemon >>> https://reviews.freebsd.org/D35776 >> >> As far as I'm concerned, https://reviews.freebsd.org/D35754#857657 is >> the only possible pain point. (Were you able to duplicate it?) >> > > I'll try to reproduce that and find a solution. > Hi, It might be more clever to kill the espeak on reading the bell character, than when writing the bell character. Because that depends on the shell. Let me look into it! --HPS
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?77362659-4cb5-a34b-44b3-209b3a4997a1>