From: Po Lu via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: yantar92@posteo.net, 70386-done@debbugs.gnu.org
Subject: bug#70386: 30.0.50; (recenter 0 t) does not put point on top of the window
Date: Thu, 23 May 2024 21:52:25 +0800 [thread overview]
Message-ID: <878r00d49y.fsf@yahoo.com> (raw)
In-Reply-To: <86ed9s4q0t.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 23 May 2024 16:27:30 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
>> Cc: 70386@debbugs.gnu.org
>> Date: Sun, 19 May 2024 18:29:03 +0300
>> From: Eli Zaretskii <eliz@gnu.org>
>>
>> > From: Ihor Radchenko <yantar92@posteo.net>
>> > Cc: luangruo@yahoo.com, 70386@debbugs.gnu.org
>> > Date: Sun, 19 May 2024 13:49:02 +0000
>> >
>> > If I convert my recipe to a defun, there is no problem.
>> >
>> > I am still seeing weirdness on my side though with Emacs entering a
>> > state when calling M-: (recenter -1 t) does nothing even when the buffer
>> > should be scrolled (point not near the top of buffer). But I am unable
>> > to get a reliable reproducer. Feel free to close this bug report.
>>
>> If Po Lu thinks this issue is resolved, we can indeed close it.
>
> Ping!
Yes, I agree that this is very much resolved. Closing.
prev parent reply other threads:[~2024-05-23 13:52 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-14 16:33 bug#70386: 30.0.50; (recenter 0 t) does not put point on top of the window Ihor Radchenko
2024-04-14 19:00 ` Eli Zaretskii
2024-04-14 19:36 ` Ihor Radchenko
2024-04-15 16:11 ` Eli Zaretskii
2024-04-15 17:13 ` Ihor Radchenko
2024-04-15 18:29 ` Eli Zaretskii
[not found] ` <87cyqq5usj.fsf@localhost>
2024-04-15 19:14 ` Eli Zaretskii
2024-04-27 8:29 ` Eli Zaretskii
2024-04-27 10:56 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-04-27 11:51 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-04-29 18:31 ` Ihor Radchenko
2024-05-09 7:37 ` Eli Zaretskii
2024-05-09 7:54 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-11 17:48 ` Ihor Radchenko
2024-05-11 17:56 ` Eli Zaretskii
2024-05-11 18:00 ` Ihor Radchenko
2024-05-11 18:26 ` Eli Zaretskii
2024-05-11 18:42 ` Ihor Radchenko
2024-05-11 18:53 ` Eli Zaretskii
2024-05-11 19:09 ` Ihor Radchenko
2024-05-12 6:00 ` Eli Zaretskii
2024-05-12 6:17 ` Ihor Radchenko
2024-05-12 6:39 ` Eli Zaretskii
2024-05-12 6:58 ` Ihor Radchenko
2024-05-12 7:02 ` Eli Zaretskii
2024-05-12 7:17 ` Ihor Radchenko
2024-05-12 9:17 ` Eli Zaretskii
2024-05-12 9:23 ` Ihor Radchenko
2024-05-12 10:15 ` Eli Zaretskii
2024-05-12 7:19 ` Ihor Radchenko
2024-05-12 9:19 ` Eli Zaretskii
2024-05-19 13:49 ` Ihor Radchenko
2024-05-19 15:29 ` Eli Zaretskii
2024-05-23 13:27 ` Eli Zaretskii
2024-05-23 13:52 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
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=878r00d49y.fsf@yahoo.com \
--to=bug-gnu-emacs@gnu.org \
--cc=70386-done@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=luangruo@yahoo.com \
--cc=yantar92@posteo.net \
/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).