From: Lars Ingebrigtsen <larsi@gnus.org>
To: "Basil L. Contovounesios" <contovob@tcd.ie>
Cc: 41842@debbugs.gnu.org
Subject: bug#41842: 28.0.50; gnus-new-mail-mark is applied to too many groups
Date: Tue, 28 Jul 2020 00:35:56 +0200 [thread overview]
Message-ID: <877duo4mcz.fsf@gnus.org> (raw)
In-Reply-To: <87h7u4wbif.fsf@gnus.org> (Lars Ingebrigtsen's message of "Sun, 19 Jul 2020 03:15:36 +0200")
Lars Ingebrigtsen <larsi@gnus.org> writes:
> But looking at the code used in nnmail.el (i.e.,
> nnmail-check-duplication), it doesn't (at that point) know what the Gnus
> group names are; it just gets data from the backends. (This is when
> nnml splits from, say, pop3 fetching.)
>
> So I don't know how to fix this generally.
Aha!
I traced the call sequence up and up to try to find out just how to get
at what the select method was, and it's not present in the nine layers
of calls down to where nnmail-split-history is set...
But! gnus-command-method is bound! The unique Gnus group name can be
trivially determined based on that. I think.
I'll try hacking that up and see what happens...
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2020-07-27 22:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-13 23:14 bug#41842: 28.0.50; gnus-new-mail-mark is applied to too many groups Basil L. Contovounesios
2020-07-19 1:15 ` Lars Ingebrigtsen
2020-07-22 20:57 ` Eric Abrahamsen
2020-07-23 13:51 ` Lars Ingebrigtsen
2020-07-23 17:00 ` Eric Abrahamsen
2020-07-27 22:35 ` Lars Ingebrigtsen [this message]
2020-07-27 22:47 ` Lars Ingebrigtsen
2020-07-28 10:32 ` Basil L. Contovounesios
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=877duo4mcz.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=41842@debbugs.gnu.org \
--cc=contovob@tcd.ie \
/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).