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

Previous Next

Package: emacs;

Reported by: "Jason Spiro" <jasonspiro4 <at> gmail.com>

Date: Tue, 4 Nov 2008 23:00:03 UTC

Severity: wishlist

Merged with 53196

Found in version 28.0.90

Full log


Message #377 received at 1305 <at> emacsbugs.donarmstrong.com (full text, mbox):

From: Lennart Borgman <lennart.borgman <at> gmail.com>
To: Juri Linkov <juri <at> jurta.org>
Cc: Chong Yidong <cyd <at> stupidchicken.com>,
        Per Starbäck <per <at> starback.se>, emacs-devel <at> gnu.org,
        Giuseppe Scrivano <gscrivano <at> gnu.org>, 1305 <at> debbugs.gnu.org
Subject: Re: Beeping (was: Emacs for new users)
Date: Fri, 27 Nov 2009 00:12:49 +0100
On Thu, Nov 26, 2009 at 11:35 PM, Juri Linkov <juri <at> jurta.org> wrote:
>>
>> The problem is that we have no mechanism for telling Emacs not to ring
>> the bell for certain classes of errors.
>
> I suggest to implement this mechanism by adding a new symbol property,
> e.g. `error-bell' by analogy with properties `error-message' and
> `error-conditions', with possible values t, nil and `visible'.
>
> And to put this property with the value nil on `beginning-of-buffer',
> `end-of-buffer' and `keyboard-quit' - most annoying beeping commands.


Maybe the problem is a bit different. There is currently no dedicated
mechanism in Emacs to go to command level. Instead a lot of functions
throws an error when they want to go to command level.

Could we not implement something like (command-level) akin to (top-level)?



This bug report was last modified 3 years and 153 days ago.

Previous Next


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