From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: 70579@debbugs.gnu.org
Subject: bug#70579: 30.0.50; gnus: Wrong unread count in the Group buffer
Date: Fri, 10 May 2024 08:49:19 -0700 [thread overview]
Message-ID: <877cg1r7k0.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <87ttjo7q98.fsf@outlook.com>
James Thomas via "Bug reports for GNU Emacs, the Swiss army knife of
text editors" <bug-gnu-emacs@gnu.org> writes:
[...]
> Of course. I was only hoping that this would shed some light on the
> other unread-count problems.... IMO this is low-severity.
That was my hope too, bummer that it's its own bug. But still worth fixing.
[...]
>> I don't see why that should mean that you need a whole new buffer for
>> editing the message
>
> I can see a possible use case: you might want two versions of a draft
> message, one being a 'root' (or 'base') version.
>
>> , and the fact that there are now two "copies" of the
>> message buffer causes further problems with the inflating article
>> numbers (why I could sometimes see three or even four "jumps").
>>
>> The patch removes the check for modification
>
> If my guess above is correct, this should be avoided.
Hmm, I guess so, though I wonder how many people are making use of the
ability to have two copies, vs how many are confused by it. But
I suppose it ain't broke, so I shouldn't fix it. I do think I'll update
the code to use `find-buffer-visiting', though.
>> Anyway, please let me know if you can check the patch.
[...]
>>> There's also a small hiccup with its working: 'B DEL' in the recipe
>>> above does not work (i.e. it's not deleted - is it related to it already
>>> being marked with 'G' at that point?), unless I 'q', re-enter and retry.
>>
>> This issue remains.
>
> I'm mistaken about this too. I missed your explanation:
>
> Eric Abrahamsen wrote:
>
>> (the "B DEL" isn't necessary for the recipe, and in fact at that stage
>> the message under point has already been deleted).
The UX is fairly confusing, but it makes more sense if you remember that
"edit" is actually just "delete-and-create". And if you use "C-c C-k" as
intended :)
Okay, there may be more bugs here, but I'll put this much in and close
the report; please open a new report if you find more.
Thanks,
Eric
prev parent reply other threads:[~2024-05-10 15:49 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
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 [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=877cg1r7k0.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.net \
--cc=70579@debbugs.gnu.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.