From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Simon Leinen <simon.leinen@switch.ch>, 67526@debbugs.gnu.org
Subject: bug#67526: 30.0.50; Regression: gnus-group-prev-group fails to move to first group
Date: Wed, 29 Nov 2023 07:16:03 -0800 [thread overview]
Message-ID: <87il5koaj0.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <83h6l47l9j.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 29 Nov 2023 15:16:08 +0200")
On 11/29/23 15:16 PM, Eli Zaretskii wrote:
>> From: Simon Leinen <simon.leinen@switch.ch>
>> Date: Wed, 29 Nov 2023 11:16:20 +0100
>>
>> In the current development version of Emacs (Git master branch),
>> gnus-group-prev-group (bound to the "P" key) in Gnus's group buffer
>> works as before, except when it is on the second newgroup line. In this
>> case, the cursor stays put on the second line and refuses to move up to
>> the first. The same is true for gnus-group-prev-unread-group (bound to
>> "p"), even when the first group has unread messages.
>>
>> I suspect the issue lies in gnus-group-search-forward, which was
>> recently simplified by Eric Abrahamsen in commit
>> 7304cc8a9ca8a7d19baaa24f0a72c7ad9a6a9716
>
> Adding Eric to the discussion.
I'm not able to reproduce this, with or without topic-mode. Is there
anything special about the level of the first or the second group, and
`gnus-level-subscribed'? I can't see anything else that might influence
behavior here...
next prev parent reply other threads:[~2023-11-29 15:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-29 10:16 bug#67526: 30.0.50; Regression: gnus-group-prev-group fails to move to first group Simon Leinen
2023-11-29 13:16 ` Eli Zaretskii
2023-11-29 15:16 ` Eric Abrahamsen [this message]
2023-11-29 15:50 ` Simon Leinen
2023-11-30 9:06 ` Simon Leinen
2023-12-03 14:55 ` Eric Abrahamsen
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=87il5koaj0.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.net \
--cc=67526@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=simon.leinen@switch.ch \
/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.