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

Previous Next

Full log

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

From: Gregory Heytings <gregory <at> heytings.org>
To: Lars Ingebrigtsen <larsi <at> gnus.org>
Cc: jasonspiro4 <at> gmail.com, 1305 <at> debbugs.gnu.org,
 Stefan Kangas <stefan <at> marxist.se>, monnier <at> iro.umontreal.ca
Subject: Re: bug#1305: All code that currently beeps should use visual bell
 instead
Date: Sun, 18 Apr 2021 15:42:03 +0000

>> Or do we need a complete rethinking of this?  Perhaps there is some 
>> other software that we can steal some good ideas from?  (And if we can 
>> come up with something very good, perhaps we will want to do the same 
>> on GNU/Linux.)
>
> That's a good idea.  What does (for instance) Libreoffice or Excel do to 
> signal a user error or "end of search" and stuff like that?
>

LibreOffice does very little: when the string is not found at all in the 
document it turns red and a "Search key not found" message is displayed at 
the end of the search bar; when you reach the last occurrence a "Reached 
the end of the document" is displayed in the search bar and the search 
wraps silently.  For other errors, LibreOffice does even less, for example 
if you paste and there is nothing to paste, nothing happens, and that's 
all.

For Microsoft Office, I don't know, but from what I remember the error 
handling was similar.

Previous Next

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