unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Chong Yidong <cyd@stupidchicken.com>
To: Giuseppe Scrivano <gscrivano@gnu.org>
Cc: "Per Starbäck" <per@starback.se>,
	1305@emacsbugs.donarmstrong.com, emacs-devel@gnu.org
Subject: bug#1305: Emacs for new users
Date: Mon, 23 Nov 2009 15:49:26 -0500	[thread overview]
Message-ID: <874oolarvt.fsf__14279.6623440974$1259011453$gmane$org@stupidchicken.com> (raw)
In-Reply-To: <87zl6dgjt1.fsf@stupidchicken.com> (Chong Yidong's message of "Mon, 23 Nov 2009 13:47:22 -0500")

Chong Yidong <cyd@stupidchicken.com> writes:

>>> * beeping is often disturbing and unexpected, in particular for
>>> scrolling past the beginning or end of the
>>>   buffer with the scroll wheel. (I agree. That's hardly an error.)
>>
>> yes, I agree with you, beeping is often disturbing.  You can disable it,
>> changing the value of visible-bell to t:

> This is bug#1305.  That discussion never came to a conclusion.

One complication, now that I recall, is that we really do want to signal
an error for beginning-of-buffer and end-of-buffer, so that keyboard
macros will terminate.

The problem is that we have no mechanism for telling Emacs not to ring
the bell for certain classes of errors.

But I'm not sure Emacs should even be in the bell-ringing business,
anyway; it's a barbaric practice, and an echo-area message IMHO
suffices.





       reply	other threads:[~2009-11-23 20:49 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <912155b0911230837i48326730m82e0d54d4004be59@mail.gmail.com>
     [not found] ` <87y6lxdvnl.fsf@mandingo.thematica.it>
     [not found]   ` <87zl6dgjt1.fsf@stupidchicken.com>
2009-11-23 20:49     ` Chong Yidong [this message]
     [not found]     ` <874oolarvt.fsf@stupidchicken.com>
2009-11-26 22:35       ` bug#1305: Beeping (was: Emacs for new users) Juri Linkov
     [not found]       ` <87aay91k9j.fsf_-_@mail.jurta.org>
2009-11-26 23:12         ` Lennart Borgman
     [not found]         ` <e01d8a50911261512u7c75059aub77c87198396cab2@mail.gmail.com>
2009-11-27  4:12           ` bug#1305: Beeping Stefan Monnier
     [not found]           ` <jwveinksj72.fsf-monnier+emacsbugreports@gnu.org>
2009-11-27  6:48             ` Lennart Borgman
     [not found]             ` <e01d8a50911262248i10e60401q1b3c31d748aae310@mail.gmail.com>
2009-11-27 19:25               ` Stefan Monnier
     [not found]               ` <jwvtywfg4bl.fsf-monnier+emacsbugreports@gnu.org>
2009-11-27 20:25                 ` Lennart Borgman

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='874oolarvt.fsf__14279.6623440974$1259011453$gmane$org@stupidchicken.com' \
    --to=cyd@stupidchicken.com \
    --cc=1305@emacsbugs.donarmstrong.com \
    --cc=emacs-devel@gnu.org \
    --cc=gscrivano@gnu.org \
    --cc=per@starback.se \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).