From: Ted Zlatanov <tzz@lifelogs.com>
Subject: Re: regular and adaptive scoring with nnimap
Date: Tue, 04 Feb 2003 14:50:58 -0500 [thread overview]
Message-ID: <4n1y2nkeot.fsf@lockgroove.bwh.harvard.edu> (raw)
In-Reply-To: <ilu4r7k83j5.fsf@latte.josefsson.org> (Simon Josefsson's message of "Tue, 04 Feb 2003 16:32:46 +0100")
On Tue, 04 Feb 2003, jas@extundo.com wrote:
> Ted Zlatanov <tzz@lifelogs.com> writes:
>
>> I wrote some pieces of code, specifically file creation and listing
>> of groups on a nnimap server. I'm very slowly working my way
>> through the file operations - stuff like make-directory is trivial
>> when dealing with files, but pretty complex with nnimap.
>> Fortunately I can just ignore most file functionality.
>>
>> groups will be mapped to directories files will be mapped to
>> articles (filename == article number) the current nnimap server
>> will always be used (good idea? bad idea?)
>
> As Kai said, using imap.el directly might be better. nnimap.el is a
> hack but I like to believe that imap.el isn't as bad. I think
> nnimap still alters some Gnus internal variables when you enter a
> group, for instance.
I was hoping to find those variables, but I see that it's a losing
game to play catch-up with the rest of Gnus as new group-level
variables are introduced. There's no save-all-variables-in-scope, is
there? :)
> OTOH using nnimap might make it easy to generalize the code for any
> Gnus backend, which could be interesting.
I thought about that, but I'm not sure I'm up to doing all that work -
I'm pretty sure it requires modifications to Gnus in order to allow a
temporary switch to another group without repercussions to the current
group.
>> Filenames will have to be numeric. Retrieving an article by
>> subject is significantly harder.
>
> imap.el's `imap-search' is rather powerful;
>
> (imap-search "HEADER Message-Id \"mydirectory/myfile.txt\"")
>
> should return all UID's for articles with that Subject.
OK, I'll use that and allow for both numeric and by-subject
addressing. Thanks!
Ted
next prev parent reply other threads:[~2003-02-04 19:50 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-25 16:39 Ted Zlatanov
2003-01-25 21:39 ` Kai Großjohann
2003-01-26 0:16 ` Simon Josefsson
2003-01-26 0:43 ` Ted Zlatanov
2003-01-26 1:13 ` Simon Josefsson
2003-01-26 14:36 ` Kai Großjohann
2003-01-27 18:37 ` Ted Zlatanov
2003-01-27 20:26 ` Kai Großjohann
2003-02-03 20:53 ` Ted Zlatanov
2003-02-04 6:48 ` Kai Großjohann
2003-02-04 19:54 ` Ted Zlatanov
2003-02-04 20:08 ` Kai Großjohann
2003-02-04 9:16 ` Andreas Fuchs
2003-02-04 19:45 ` Ted Zlatanov
2003-02-04 20:10 ` Kai Großjohann
2003-02-04 20:32 ` Ted Zlatanov
2003-02-04 15:32 ` Simon Josefsson
2003-02-04 19:50 ` Ted Zlatanov [this message]
2003-02-04 22:03 ` Ted Zlatanov
2003-02-05 5:52 ` Simon Josefsson
2003-02-05 20:35 ` Ted Zlatanov
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=4n1y2nkeot.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).