From: Ted Zlatanov <tzz@lifelogs.com>
Subject: Re: gnus-registry-split-fancy-with-parent misfeature or minibug?
Date: Tue, 27 May 2003 13:19:06 -0400 [thread overview]
Message-ID: <4nn0h8i9yt.fsf@lockgroove.bwh.harvard.edu> (raw)
In-Reply-To: =?iso-8859-1?q?PI-LINK-6fd67eaf995a062ce0968df611916235982c1b7d_(Kai_Gro=DFjohann's_message_of_"Sun,_25_May_200?= =?iso-8859-1?q?3_20:49:03_+0200")?=
On Sun, 25 May 2003, kai.grossjohann@gmx.net wrote:
> Ted Zlatanov <tzz@lifelogs.com> writes:
>
>> Use the gnus-registry-ignored-groups variable or the
>> registry-ignore group parameter. I have:
>>
>> (setq gnus-registry-ignored-groups '(("nntp" t)
>> ("nnrss" t)))
>>
>> That way, messages in those groups won't be registered.
>> What would be a suitable default, any suggestions?
>
> I'm not so happy with this approach. I read an IMAP server via
> nnimap and a POP server via mail-sources and nnml. So suppose I
> read a message on the IMAP server and move it to nnimap:INBOX.foo,
> then I compose a followup. The followup happens to contain the
> "wrong" email message, and so replies go to the POP mailbox. So
> nnmail-split-fancy will put the reply into nnml:INBOX.foo which
> isn't what I wanted.
> If you say that this is a rather unusual setup, I'd agree. So maybe
> that's not so convincing an argument. (Especially the part about
> the "wrong" email address which leads to parts of the same thread
> coming in via IMAP whereas other parts come in via POP.)
I think fully qualified group names would help you here. Most people,
I assumed, would not get a followup to a message in a backend
different from the one where message is stored. I'll get the FQGN
addition to the gnus-registry.el done as time permits - feel free to
put it in sooner. I'm still thinking of a faster storage format...
> But there is another thing: I gather that originally you intended to
> use the registry for other things, not just
> gnus-registry-split-fancy-with-parent? If this is the case, then
> there might be a good reason for registering nntp articles, as well.
Only one other purpose on my horizon: spam processing. I can see the
problems there - maybe at that point the registry will *remember*
group names in the gnus-registry-ignored-groups alist, but won't offer
them as suggestions for splitting with the parents. I think that's
the sensible way to do it.
Ted
prev parent reply other threads:[~2003-05-27 17:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-24 14:56 Kai Großjohann
[not found] ` <848yswgzqs.fsf@lucy.is.informatik.uni-duis?= =?iso-8859-1?q?burg.de>
2003-05-25 10:49 ` Ted Zlatanov
2003-05-25 18:49 ` Kai Großjohann
[not found] ` <84fzn2amlc.fsf@lucy.is.informatik.uni-duis?= =?iso-8859-1?q?burg.de>
2003-05-27 17:19 ` Ted Zlatanov [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=4nn0h8i9yt.fsf@lockgroove.bwh.harvard.edu \
--to=tzz@lifelogs.com \
/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.
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 NNTP newsgroup(s).