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

Previous Next

Full log

Message #571 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: Michael Welsh Duggan <mwd <at> md5i.com>,
 Gregory Heytings <gregory <at> heytings.org>, 1305 <at> debbugs.gnu.org,
 Stefan Kangas <stefan <at> marxist.se>, jasonspiro4 <at> gmail.com
Subject: Re: bug#1305: All code that currently beeps should use visual bell
 instead
Date: Sun, 18 Apr 2021 14:34:33 -0400

>> FWIW, I don't see what's "intrusive" about the "blink top and bottom lines of
>> the selected frame" which I currently see in GNU/Linux.
> In this Emacs, it blinks the two topmost lines.  Which may be a bug?

My crystal ball tells me it's a hidpi bug, indeed: it probably doubles
something where it shouldn't, so at the top, it turns into 1 line into
2 and at the bottom, the line ends up being twice too far (and probably
twice too think as well, but we don't get to see it anyway).

>> It may not be slick but it does the job and I don't find it intrusive.
>> Of course, I'm biased (I've used it for too many years), but it's
>> clearly less intrusive than the non-visual bell.
> It's more intrusive than what many people are using -- which is neither
> an audible nor a visible bell, but just the echo area saying "Quit" when
> you hit `C-g' (etc).

But those people won't be affected by a change in the default.
The only people which would see a "more intrusive" bell is those who
keep the default settings but whose environment ends up muting the
audible bell.  I don't know how common this is.


        Stefan

Previous Next

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