From: "François Pinard" <pinard@iro.umontreal.ca>
Cc: ding@gnus.org
Subject: Re: 1) Trying to use `nnfolder' 2) Remote access
Date: 05 Mar 1999 12:32:50 -0500 [thread overview]
Message-ID: <oq1zj3x2nx.fsf@titan.progiciels-bpi.ca> (raw)
In-Reply-To: Hrvoje Niksic's message of "05 Mar 1999 14:26:36 +0100"
Hrvoje Niksic <hniksic@srce.hr> écrit:
> > Following a suggestion from Horvje, I would like trying `nnfolder' to
> > access a lot of Babyl files from within Gnus (and take advantage of MIME
> > and many other features), but do not find the magic incantations to get
> > it up running from my `.gnus' file.
> Did I really say that? I think I suggested the use of `nnbabyl', but
> then you said that `nnbabyl' was unable to edit files, which I think
> is wrong (but I haven't tried it!) Anyway, I may have suggested
> nnfolder as an *alternative* to nnbabyl files.
Most probably. I found a script, in a directory I made for doing such
tests, which converts many Babyl files to mbox format, exactly those I
wanted to play with `nnfolder'. So maybe I realized and forgotten that
I had to move away from Babyl to use `nnfolder'.
But I never really succeeded in using it. For example, the active file
contained a lot of `nil' groups, Gnus was refusing to open most of the
groups, and other strangeties. This is why I was asking if someone has
some working setup that I might try to mimic to start with, at least to
understand a bit what is normal and what should be reported as a bug.
I understand that all folders should be brought into a common directory,
and I'm ready to create many symbolic links from a common place if this is
required. (There might be in the order of 2000 to 3000 groups if I ever
complete this job.) But how should I get the whole thing into motion?
The manual does not help me much about it. I presume I would know how
everything interrelates if I had fought enough to write a few backends,
but as a mere user, I feel a bit lost about how to proceed.
--
François Pinard mailto:pinard@iro.umontreal.ca
Join the free Translation Project! http://www.iro.umontreal.ca/~pinard
next prev parent reply other threads:[~1999-03-05 17:32 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-03-05 2:57 François Pinard
1999-03-05 3:14 ` Aaron M. Ucko
1999-03-05 3:29 ` François Pinard
1999-03-05 9:27 ` Kai.Grossjohann
1999-03-05 17:41 ` Shane Holder
1999-03-05 17:37 ` Kai.Grossjohann
1999-03-05 9:27 ` Kai.Grossjohann
1999-03-05 17:39 ` François Pinard
1999-03-05 17:54 ` Kai.Grossjohann
1999-03-05 20:17 ` Lars Magne Ingebrigtsen
1999-03-05 13:26 ` Hrvoje Niksic
1999-03-05 17:32 ` François Pinard [this message]
1999-03-05 17:40 ` Kai.Grossjohann
1999-03-07 21:33 ` François Pinard
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=oq1zj3x2nx.fsf@titan.progiciels-bpi.ca \
--to=pinard@iro.umontreal.ca \
--cc=ding@gnus.org \
/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).