unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: "Jan Djärv" <jan.h.d@swipnet.se>
Cc: 16196@debbugs.gnu.org
Subject: bug#16196: 24.3.50; Disable ding when scrolling
Date: Fri, 20 Dec 2013 10:56:18 +0200	[thread overview]
Message-ID: <83d2krc34d.fsf@gnu.org> (raw)
In-Reply-To: <25C13650-058F-45CC-A961-D789709B1179@swipnet.se>

> From: Jan Djärv <jan.h.d@swipnet.se>
> Date: Fri, 20 Dec 2013 07:08:37 +0100
> 
> I think Emacs should by default not beep at all when scrolling and no movement can be done.

This could be hard to implement.  Most scrolling commands just examine
the text around point, and set the window-start for the next
redisplay, so they don't really know when no movement can be done.
Thus, the exact conditions for bitching "End of buffer" are not at all
what you could imagine, and not easily correlated with the situation
you describe.  For example, the next-line and previous-line commands
signal these errors when they find they are unable to scroll text,
something that might be utterly unrelated to hitting end of buffer.

> It should just ignore it and do nothing, like most applications do.

Well, "do nothing" is something Emacs cannot easily do in this case,
since the part that "does nothing" is redisplay, which has no idea
about the scrolling command that just ran.

>  At the very least there should be an option to turn off scrollrelated beeping.

This should be much easier to implement, although you may be surprised
to see in how many places we throw that particular error.  (Hint: grep
the Lisp sources for "'end-of-file".)

Patches are welcome, as usual.





  reply	other threads:[~2013-12-20  8:56 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 [this message]
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
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=83d2krc34d.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=16196@debbugs.gnu.org \
    --cc=jan.h.d@swipnet.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).