GNU bug report logs - #1305
All code that currently beeps should use visual bell instead

Previous Next

Full log

View this message in rfc822 format

From: Gregory Heytings <gregory <at> heytings.org>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: 1305 <at> debbugs.gnu.org, mwd <at> md5i.com, stefan <at> marxist.se, jasonspiro4 <at> gmail.com, monnier <at> iro.umontreal.ca, larsi <at> gnus.org
Subject: bug#1305: All code that currently beeps should use visual bell instead
Date: Sun, 18 Apr 2021 18:02:11 +0000

[Message part 1 (text/plain, inline)]

>>> I think, perhaps, introducing a new visible bell (across all 
>>> significant system), that's considerably less intrusive than the ones 
>>> we have today on GNU/Linux and Macos, might be an option.  And then 
>>> defaulting to using that.
>>>
>>> Gregory suggested blinking the cursor in a different colour -- 
>>> perhaps?
>>
>> I attach a POC of what I have in mind.
>
> If this is being proposed as the default setting, then we should have a 
> different default for TTY frames, because AFAIR cursor color cannot be 
> changed there, right?
>

Indeed.

>>   (sit-for 0.5)
>
> I think half a second is too long, a bell should be much shorter, like 
> 0.1 sec or something.
>

Hmmm... 0.5 seconds is the duration of typical audible bells.  And with a 
sit-for, it's at most 0.5 seconds, when the user presses a key the bell 
signal disappears.  That being said, I agree with you that 0.5 seconds is 
perhaps a bit too long, so I changed it to 0.25 seconds.

I attach the updated POC, which works on non-graphical displays.

[visible-bell.el (text/plain, attachment)]

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.