Gnus development mailing list
 help / color / mirror / Atom feed
From: Ted Zlatanov <tzz@lifelogs.com>
Subject: Re: regular and adaptive scoring with nnimap
Date: Mon, 03 Feb 2003 15:53:49 -0500	[thread overview]
Message-ID: <4nof5txezm.fsf@lockgroove.bwh.harvard.edu> (raw)
In-Reply-To: <84wukqtk3c.fsf@lucy.is.informatik.uni-duisburg.de> (kai.grossjohann@uni-duisburg.de's message of "Mon, 27 Jan 2003 21:26:47 +0100")

On Mon, 27 Jan 2003, kai.grossjohann@uni-duisburg.de wrote:
> Ted Zlatanov <tzz@lifelogs.com> writes:
> 
>> If I knew anything about filename handlers, I'd love to write this.
>> How hard are they to use?  This needs to be integrated with
>> nnimap.el pretty tightly, so it should be an interesting module.
> 
> When I wrote Tramp, I just looked at the magic filenames node in the
> elisp reference and at the documentation of each function referenced
> there.  From time to time, I also looked at Ange-FTP to see how it
> does things.  (That's how I discovered that (0 0) appears to be the
> way to express a don't-know value for the mtime, ctime and atime
> values returned from file-attributes.)
> 
> It seems intimidating at first, but turns out to be not that
> difficult.

Well, I'm basically trying to figure things out at this point...

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?)

Filenames will have to be numeric.  Retrieving an article by subject
is significantly harder.

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.

Ted



  reply	other threads:[~2003-02-03 20:53 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 [this message]
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
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=4nof5txezm.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).