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: Dmitry Gutov <dgutov <at> yandex.ru>
To: Gregory Heytings <gregory <at> heytings.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, Stefan Monnier <monnier <at> iro.umontreal.ca>, Lars Ingebrigtsen <larsi <at> gnus.org>
Subject: bug#1305: All code that currently beeps should use visual bell instead
Date: Sat, 1 May 2021 02:28:49 +0300

On 01.05.2021 02:19, Gregory Heytings wrote:
> Amusingly, it's the only "better default" that isn't described in the 
> README, and against which there's a open issue: 
> https://github.com/technomancy/better-defaults/issues/27 .

Have you read the comments? People complain about macOS behavior, and 
the first proposed "fix" was to make it work close to how it works on 
GNU/Linux (except flashing the mode-line, probably because that is 
easier to implement).

Hence the reply: "that's strange; the behavior you describe is how it 
already works for me".

>> A moving reddish shape should bring enough attention, but of course 
>> different users have different levels of sensitivity (as the 
>> discussion in bug#47574 has shown). Only a practical experiment can tell.
>>
> 
> Moving???  Why do you think this would be better than simply blinking 
> the echo area?

"Blinking" is also movement. I don't have a specific animation in mind.

Previous Next

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