Gnus development mailing list
 help / color / mirror / Atom feed
From: Ted Zlatanov <tzz@lifelogs.com>
Subject: Re: regular and adaptive scoring with nnimap
Date: Tue, 04 Feb 2003 14:45:48 -0500	[thread overview]
Message-ID: <4nptq7kexf.fsf@lockgroove.bwh.harvard.edu> (raw)
In-Reply-To: <87d6m8h09r.fsf@eris.void.at> (Andreas Fuchs's message of "Tue, 4 Feb 2003 09:16:26 +0000 (UTC)")

On Tue, 4 Feb 2003, asf@void.at wrote:
> On 2003-02-03, Ted Zlatanov <tzz@lifelogs.com> wrote:
>> Filenames will have to be numeric.  Retrieving an article by
>> subject is significantly harder.
> 
> Why not just use http://www.isi.edu/in-notes/rfc2192.txt URLs?

Chiefly, it was my ignorance of that RFC that caused me to overlook it
:) Now that I look at it, it's rather difficult to reconcile it with
Gnus.  The URL has a lot of information built-in that in Gnus is
associated with the server name.  So I should ignore that part of the
RFC and just do

imap://minbari.org/storage?SUBJECT%20filename

passing the filename as a subject string search, and

imap://minbari.org/storage?UID=20

for direct access to articles.

Something like this is probably good enough, and I'd rather let
imap.el worry about the best authenticator.  Does that sound OK?

Supporting the full syntax is way too much work for something that
Gnus already does internally.  If anyone wants to work on supporting
the full URL scheme and create an ephemeral server on the fly to
retrieve a message, they're welcome :)

>> I'm currently trying to figure out how to enter the storage nnimap
>> group to store or retrieve an article without affecting variables
>> like gnus-newsgroup-name.
> 
> These are lexically bound. It should be possible to (let
> ((gnus-newsgroup-name "name")) <do things>) and have them
> automatically restored after <do things>.

Sorry, I should have been clearer.  I understand about local scope, I
just don't know which variables to save before entering another group
temporarily.  But I think this won't be a problem if I use imap.el
instead of nnimap.el.

Ted



  reply	other threads:[~2003-02-04 19:45 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 [this message]
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
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=4nptq7kexf.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).