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

Previous Next

Full log

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

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

On 21.04.2021 17:33, Stefan Monnier wrote:
>> I think this is a bit of a mess, indeed.
>>
>> 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`.

And obsoleting the visible-bell variable?

Sounds good.

But if we're going to change the default behavior, it would (probably?) 
be weird to keep a special case in this variable for the old one.

So would 'ring-bell-visual' do what 'visible-bell' currently does, or 
will it implement one of the proposals under discussion?

Previous Next

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