unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 70579@debbugs.gnu.org, jimjoe@gmx.net
Subject: bug#70579: 30.0.50; gnus: Wrong unread count in the Group buffer
Date: Thu, 09 May 2024 21:00:11 -0700	[thread overview]
Message-ID: <87wmo2qptg.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <864jb78nbd.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 09 May 2024 10:19:18 +0300")

Eli Zaretskii <eliz@gnu.org> writes:

> Ping!  Eric, can we make some progress here?
>
>> Cc: jimjoe@gmx.net
>> From: Eric Abrahamsen <eric@ericabrahamsen.net>
>> Date: Thu, 25 Apr 2024 21:34:45 -0700
>> 
>> James Thomas via "Bug reports for GNU Emacs, the Swiss army knife of
>> text editors" <bug-gnu-emacs@gnu.org> writes:
>> 
>> > - (Preferably starting with an empty drafts folder) Compose a message
>> >   and save it.
>> > - Open the drafts group, press e on the message and then kill the new
>> >   buffer; then (incidentally, if you now do '/ N' then this bug does not
>> >   arise) delete the message (B DEL)
>> > - Press q
>> > - The message count is wrong (but can be corrected with M-g)
>> >
>> > cf. In gnus.general (gnus-summary-goto-article "87y192lr8f.fsf@gmx.net")

I've made some progress here -- the root of the problem seems to be
that, when we hit "e" in the draft summary buffer to resume editing a
draft, Gnus "jumps ahead" in message numbers. Basically what "editing"
actually means is that the old draft is deleted, and a new draft is
started, but the new draft has a article number that's the previous
draft's number + 2, and the "draft" group's active number is also
inflated (for instance (12 . 14) when it should be (12 . 13)). I was
also able to get it to jump three numbers in some cases.

From this point, *any* normal usage will end up correcting the error:
using "C-c C-k" to kill the editing buffer (instead of "C-x k") or as
you noted any of the commands that lead to refreshing the unread count.
But if you don't use any of those commands, you'll see the inflated
active/unread count when you get back to the *Group* buffer (the "B DEL"
isn't necessary for the recipe, and in fact at that stage the message
under point has already been deleted).

That's as far as I've gotten, and I'll keep working on why the article
number starts off inflated. But in the meantime, the solution is "don't
do that".

Eric





  reply	other threads:[~2024-05-10  4:00 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-26  3:32 bug#70579: 30.0.50; gnus: Wrong unread count in the Group buffer James Thomas via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-04-26  4:34 ` Eric Abrahamsen
2024-05-09  7:19   ` Eli Zaretskii
2024-05-10  4:00     ` Eric Abrahamsen [this message]
2024-05-10  4:14       ` Eric Abrahamsen
2024-05-10  6:23         ` Eric Abrahamsen
2024-05-10 11:01         ` James Thomas via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-10 11:58           ` James Thomas via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-10 12:37             ` James Thomas via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-10 15:49           ` 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

  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=87wmo2qptg.fsf@ericabrahamsen.net \
    --to=eric@ericabrahamsen.net \
    --cc=70579@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=jimjoe@gmx.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).