From: Eli Zaretskii <eliz@gnu.org>
To: gregory@heytings.org
Cc: geza.herman@gmail.com, 66764@debbugs.gnu.org
Subject: bug#66764: 29.1; Emacs scrolls for "(goto-char (point-max))" instead of jumping
Date: Sat, 23 Dec 2023 10:37:10 +0200 [thread overview]
Message-ID: <831qbdfh6x.fsf@gnu.org> (raw)
In-Reply-To: <831qbvxzy7.fsf@gnu.org> (message from Eli Zaretskii on Sat, 09 Dec 2023 15:33:52 +0200)
Ping! Ping! Ping! Ping! Gregory, I'd like to release Emacs 29.2 soon,
and I wonder whether we could/should fix this issue there? Could you
please look into this soon?
> Cc: 66764@debbugs.gnu.org, geza.herman@gmail.com
> Date: Sat, 09 Dec 2023 15:33:52 +0200
> From: Eli Zaretskii <eliz@gnu.org>
>
> > Date: Sat, 25 Nov 2023 11:37:19 +0000
> > From: Gregory Heytings <gregory@heytings.org>
> > cc: geza.herman@gmail.com, 66764@debbugs.gnu.org
> >
> > > Ping! Ping! Gregory, are you there?
> > >
> >
> > Yes; I'll have a look.
>
> Any progress with this?
>
> Thanks.
>
>
>
>
next prev parent reply other threads:[~2023-12-23 8:37 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
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 [this message]
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=831qbdfh6x.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=66764@debbugs.gnu.org \
--cc=geza.herman@gmail.com \
--cc=gregory@heytings.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 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.