From: kai.grossjohann@uni-duisburg.de (Kai Großjohann)
Subject: Re: nnima-split-with-parent
Date: Sat, 07 Dec 2002 21:25:02 +0100 [thread overview]
Message-ID: <84of7xpof5.fsf@lucy.cs.uni-dortmund.de> (raw)
In-Reply-To: <m3hedpg07k.fsf@heechee.beld.net>
Ted Zlatanov <tzz@lifelogs.com> writes:
> On Sat, 07 Dec 2002, kai.grossjohann@uni-duisburg.de wrote:
>> But this doesn't deal with the unqualified group names that are
>> currently in the file.
>
> We convert them to the nnmail-cache-primary-backend:groupname fully
> qualified format. Wouldn't that make sense?
Usually, an unqualified group name is assumed to come from the
primary backend (ie, gnus-select-method). So it's not sufficient to
_just_ call the functions I gave.
Of course, for new lines there isn't really a problem.
But how do you distinguish a new line from an old one? Oh, you
_always_ add a prefix, even for the primary backend. Yes, that would
work.
--
~/.signature is: umop ap!sdn (Frank Nobis)
next prev parent reply other threads:[~2002-12-07 20:25 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-06 20:24 nnima-split-with-parent Ted Zlatanov
[not found] ` <m2k7imroo1.fsf@tnuctip.rychter.com>
2002-12-07 13:54 ` nnimap-split-with-parent Ted Zlatanov
2002-12-07 15:01 ` nnima-split-with-parent Kai Großjohann
2002-12-07 15:14 ` nnima-split-with-parent Ted Zlatanov
2002-12-07 15:28 ` nnima-split-with-parent Kai Großjohann
2002-12-07 18:20 ` nnima-split-with-parent Ted Zlatanov
2002-12-07 20:25 ` Kai Großjohann [this message]
2002-12-09 15:54 ` nnima-split-with-parent Ted Zlatanov
2002-12-09 16:21 ` nnima-split-with-parent Kai Großjohann
[not found] ` <m27kelycce.fsf@tnuctip.rychter.com>
2002-12-07 20:23 ` nnima-split-with-parent Kai Großjohann
2002-12-07 14:59 ` nnima-split-with-parent Kai Großjohann
2002-12-07 18:20 ` nnima-split-with-parent Ted Zlatanov
2002-12-07 20:22 ` nnima-split-with-parent Kai Großjohann
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=84of7xpof5.fsf@lucy.cs.uni-dortmund.de \
--to=kai.grossjohann@uni-duisburg.de \
/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).