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

Previous Next

Full log

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

From: Gregory Heytings <gregory <at> heytings.org>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: alan <at> idiocy.org, 1305 <at> debbugs.gnu.org, mwd <at> md5i.com, stefan <at> marxist.se,
 jasonspiro4 <at> gmail.com, monnier <at> iro.umontreal.ca,
 Dmitry Gutov <dgutov <at> yandex.ru>, larsi <at> gnus.org
Subject: Re: bug#1305: All code that currently beeps should use visual bell
 instead
Date: Fri, 30 Apr 2021 06:51:47 +0000

[Message part 1 (text/plain, inline)]

>>> I can't really say whether it's better or worse, with visible-bell t 
>>> on Windows the frame briefly flashes (with the FlashWindow function), 
>>> a bit like a flash in a terminal.  Among the three visible-bell t 
>>> behaviors, it's the best one IMO, in the sense that it's visible and 
>>> not intrusive.
>>
>> Is it possible to replicate on other systems?
>
> Just so we are on the same page: FlashWindow on MS-Windows doesn't 
> necessarily flash the frame.  Or maybe I don't understand what Gregory 
> meant by that.
>

Yes, "flash" is perhaps not the best word here, perhaps "vibrate" is 
better.

And no, I don't think it is possible to replicate that behavior on other 
systems, it's a "window manager" primitive, which AFAIU exists on Windows 
but not on macOS or GNU/Linux.

Previous Next

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