From: Drew Adams <drew.adams@oracle.com>
To: "Jan Djärv" <jan.h.d@swipnet.se>,
"Stefan Monnier" <monnier@iro.umontreal.ca>
Cc: 16196@debbugs.gnu.org
Subject: bug#16196: 24.3.50; Disable ding when scrolling
Date: Fri, 3 Jan 2014 16:03:13 -0800 (PST) [thread overview]
Message-ID: <39e5261b-85e6-41de-9f3e-bc92c5b5ed07@default> (raw)
In-Reply-To: <3E2B9204-7431-4CC0-952F-C37BB2FFD2D9@swipnet.se>
> Ding implies an error
No, it does not. Read its doc.
And read about particular uses of it, in the Elisp manual. Each
explicit mention of a use makes clear that it is NOT about signaling
an error.
Node `Key Lookup':
"it rings the bell (by calling `ding') but does not signal an error."
^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Node `Functions for Key Lookup':
"It calls `ding', but does not cause an error."
^^^^^^^^^^^^^^^^^^^^^^^^^^^
Node `Beeping' tells you clearly what `ding' *is* for:
"to attract the user's attention."
It also makes clear that one does not want to overuse it: attracting
the user's attention too much defeats the purpose and can be annoying.
> I rather have a silent lack of feedback than a lot of beeping.
Bind `ring-bell-function' wherever you like to whatever you like,
including to `ignore'.
next prev parent reply other threads:[~2014-01-04 0:03 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-20 6:08 bug#16196: 24.3.50; Disable ding when scrolling Jan Djärv
2013-12-20 8:56 ` Eli Zaretskii
2013-12-20 10:26 ` Jan Djärv
2013-12-20 10:32 ` Jan Djärv
2013-12-20 10:48 ` Eli Zaretskii
2013-12-20 17:52 ` Jan Djärv
2013-12-20 18:10 ` Eli Zaretskii
2013-12-20 18:48 ` Jan Djärv
2013-12-20 20:35 ` Eli Zaretskii
2013-12-23 2:46 ` Stefan Monnier
2013-12-23 10:44 ` Jan Djärv
2014-01-03 22:57 ` Stefan Monnier
2014-01-03 23:46 ` Jan Djärv
2014-01-04 0:03 ` Drew Adams [this message]
2014-01-04 5:07 ` Stefan Monnier
2014-01-04 9:40 ` Jan Djärv
2014-01-04 13:43 ` martin rudalics
2014-01-04 20:40 ` Stefan Monnier
2014-01-04 7:25 ` Eli Zaretskii
2014-01-04 9:36 ` Jan Djärv
2013-12-20 10:43 ` Eli Zaretskii
2019-08-09 7:55 ` Stefan Kangas
2019-08-09 8:57 ` Basil L. Contovounesios
2019-08-10 18:07 ` Stefan Kangas
2019-08-11 14:28 ` Basil L. Contovounesios
2019-08-12 0:52 ` Stefan Kangas
2019-09-30 13:26 ` Stefan Kangas
2019-09-30 13:55 ` Eli Zaretskii
2019-09-30 14:03 ` Robert Pluim
2019-09-30 14:11 ` Robert Pluim
2019-09-30 14:19 ` Stefan Kangas
2019-09-30 21:51 ` Stefan Kangas
2019-10-04 16:11 ` Stefan Kangas
2019-08-09 9:00 ` martin rudalics
2019-08-10 18:23 ` Stefan Kangas
2019-08-11 8:17 ` martin rudalics
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=39e5261b-85e6-41de-9f3e-bc92c5b5ed07@default \
--to=drew.adams@oracle.com \
--cc=16196@debbugs.gnu.org \
--cc=jan.h.d@swipnet.se \
--cc=monnier@iro.umontreal.ca \
/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).