From: Eli Zaretskii <eliz@gnu.org>
To: Geza Herman <geza.herman@gmail.com>
Cc: 66764@debbugs.gnu.org
Subject: bug#66764: 29.1; Emacs scrolls for "(goto-char (point-max))" instead of jumping
Date: Thu, 26 Oct 2023 21:25:16 +0300 [thread overview]
Message-ID: <83jzr9fdh0.fsf@gnu.org> (raw)
In-Reply-To: <ddf1fc8b-2e31-4b2e-8da6-845031ac4171@gmail.com> (message from Geza Herman on Thu, 26 Oct 2023 19:04:42 +0200)
> Date: Thu, 26 Oct 2023 19:04:42 +0200
> From: Geza Herman <geza.herman@gmail.com>
>
> The bug is, that in certain circumstances, emacs moves the point by
> using some kind of scrolling for "(goto-char (point-max))", instead of
> just jumping.
>
> Repro:
>
> - create a file using the little C program at the end (it produces a
> large text to stdout, you'll need to redirect it to some file)
>
> - open the file with "emacs -Q generated.txt"
>
> - with M-:, execute this:
>
> (progn
> (setq scroll-conservatively 101)
> (font-lock-add-keywords nil '(((lambda (bound)) (1 'error prepend
> t))) t)
> (goto-char (point-max)))
>
> Notice that emacs doesn't jump to the end immediately as usual, but it
> does some kind of very fast scrolling.
I didn't yet try to reproduce this, but just reading the description:
why do you consider this behavior a problem, let alone a bug?
> In my real case, a much smaller file produces this problem. Also, Emacs
> doesn't go to the end of the file, but stops somewhere in the middle (I
> was unable to reproduce this issue with a simple configuration).
This can legitimately happen if the last line has tall characters or
you use line-spacing or something similar. Again, why is it a
problem, as long as EOB is visible after that?
> So to go to the end of the file I have to run "(goto-char
> (point-max))" multiple times. Interestingly, "M->" works fine. But
> if I remove the recenter call at the end of "end-of-buffer", it also
> has this odd behavior.
Which isn't surprising, since with the 'recenter' call removed,
end-of-buffer is just (goto-char (point-max)).
next prev parent reply other threads:[~2023-10-26 18:25 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-26 17:04 bug#66764: 29.1; Emacs scrolls for "(goto-char (point-max))" instead of jumping Geza Herman
2023-10-26 18:25 ` Eli Zaretskii [this message]
2023-10-26 19:12 ` Herman, Géza
2023-10-27 5:46 ` Eli Zaretskii
2023-10-27 6:50 ` Eli Zaretskii
2023-10-27 9:43 ` Herman, Géza
2023-11-04 8:29 ` Eli Zaretskii
2023-11-18 9:01 ` Eli Zaretskii
2023-11-25 11:37 ` Gregory Heytings
2023-12-09 13:33 ` Eli Zaretskii
2023-12-23 8:37 ` Eli Zaretskii
2023-12-28 10:53 ` Gregory Heytings
2024-01-09 20:01 ` Eli Zaretskii
2024-01-11 23:40 ` Gregory Heytings
2024-01-13 19:11 ` Eli Zaretskii
2024-01-14 19:36 ` Eli Zaretskii
2024-01-14 22:06 ` Gregory Heytings
2024-01-15 12:22 ` Eli Zaretskii
2024-01-15 13:30 ` Gregory Heytings
2024-01-13 19:10 ` Eli Zaretskii
2024-01-13 19:13 ` Eli Zaretskii
2023-10-27 9:22 ` Herman, Géza
2023-10-27 10:43 ` Eli Zaretskii
2023-10-28 1:15 ` Geza Herman
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83jzr9fdh0.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=66764@debbugs.gnu.org \
--cc=geza.herman@gmail.com \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.