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: Stefan Monnier <monnier <at> iro.umontreal.ca>
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, Dmitry Gutov <dgutov <at> yandex.ru>, Lars Ingebrigtsen <larsi <at> gnus.org>
Subject: bug#1305: All code that currently beeps should use visual bell instead
Date: Wed, 21 Apr 2021 16:14:24 +0000

>> But I do have similar reservations about flashing red so prominently 
>> (given that the pressing C-g does not usually indicate an error of any 
>> sort).
>
> Why not flashing the mode line with something like:
>

I don't understand why flashing the mode-line is among the possible 
options.  Calling the attention of the user to the mode-line is not TRT, 
it's neither where the error happened (usually at point or around point) 
nor where the error that happened is explained (in the echo area).  It's 
like flashing the fringes, there's no point in doing that when an error 
happens.

Yes, there's an option in Doom to do this.  But AFAIU Doom does that 
because it can't do better, namely, because there is no way to access the 
last error symbol in Emacs and do something with it.  This (making the 
last error symbol and data accessible from Elisp) is included in my 
proposed patch.

Previous Next

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