unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "Jan Djärv" <jan.h.d@swipnet.se>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 16196@debbugs.gnu.org
Subject: bug#16196: 24.3.50; Disable ding when scrolling
Date: Fri, 20 Dec 2013 19:48:57 +0100	[thread overview]
Message-ID: <FEB00DC8-49FE-4150-AA89-7F0F309E02AA@swipnet.se> (raw)
In-Reply-To: <831u17bdfy.fsf@gnu.org>

Hello.

20 dec 2013 kl. 19:10 skrev Eli Zaretskii <eliz@gnu.org>:

>> From: Jan Djärv <jan.h.d@swipnet.se>
>> Date: Fri, 20 Dec 2013 18:52:27 +0100
>> Cc: 16196@debbugs.gnu.org
>> 
>> 11 hits, 6 in simple.el.  17/10 if we include beginning-of-buffer.  About half is kill-related and does not involve scrolling.  Does not sound many to me.
> 
> There are a couple in C as well.  But the main problem would be to
> understand which ones belong to what use cases.
> 
>> But I would settle for no beep for WHEEL events.  I'd prefer no beep at all though.
> 
> What, never?  Not even if you hit the beginning or end by moving
> cursor or by C-v/M-v?

Yes never.  I always though the beeping to be a bit out of this world:

"Where do you want to be?"
"At the end of the buffer."
"You are at the end of the buffer."
"Fine!"
"Not at all, it is an error to be where you want to be."
"??"


>  That'd be a serious change of behavior, so it
> should be discussed and/or users polled before we do that, I think.

Best make it an option then.  Does not require polling.

	Jan D.







  reply	other threads:[~2013-12-20 18:48 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 [this message]
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
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=FEB00DC8-49FE-4150-AA89-7F0F309E02AA@swipnet.se \
    --to=jan.h.d@swipnet.se \
    --cc=16196@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    /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).