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

Previous Next

Full log

Message #742 received at 1305 <at> debbugs.gnu.org (full text, mbox):

From: Stefan Monnier <monnier <at> iro.umontreal.ca>
To: Lars Ingebrigtsen <larsi <at> gnus.org>
Cc: Alan Third <alan <at> idiocy.org>, 1305 <at> debbugs.gnu.org,
 Michael Welsh Duggan <mwd <at> md5i.com>, Stefan Kangas <stefan <at> marxist.se>,
 jasonspiro4 <at> gmail.com, Gregory Heytings <gregory <at> heytings.org>,
 Dmitry Gutov <dgutov <at> yandex.ru>
Subject: Re: bug#1305: All code that currently beeps should use visual bell
 instead
Date: Sun, 25 Apr 2021 17:03:54 -0400

>>> I would be in favour of fixing this by adding one or more new variables
>>> with reasonable semantics.  For example, why not have a variable called
>>> `alarm-bell' with these valid values:
>>>
>>>     - a function    call this function
>>>     - `visual'      Use a visual bell
>>>     - t             Ring the bell
>>>     - nil           Do nothing
>>
>> Agreed, except I suggest to use slightly different names: `visual` becomes
>> `ring-bell-visual`, `t` becomes `ring-bell-beep`, `nil` becomes `ignore` and
>> `alarm-bell` becomes `ring-bell-function`.
>
> So just use function names instead of symbols?  I think, in general,
> it's nice to have things like nil/t in variables like this -- it's
> easier for users to deal with.
>
> Anyway, I agree that cleaning up this area by introducing a new variable
> and obsoleting the slightly confusing current state of affairs would be
> nice.  

My point was that we can clean up without any new variable ;-)


        Stefan

Previous Next

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