Gnus development mailing list
 help / color / mirror / Atom feed
From: "François Pinard" <pinard@iro.umontreal.ca>
Cc: ding@gnus.org
Subject: Re: 1) Trying to use `nnfolder'  2) Remote access
Date: 04 Mar 1999 22:29:36 -0500	[thread overview]
Message-ID: <oqhfs0bom7.fsf@titan.progiciels-bpi.ca> (raw)
In-Reply-To: amu@mit.edu's message of "04 Mar 1999 22:14:01 -0500"

amu@mit.edu (Aaron M. Ucko) écrit:

> François Pinard <pinard@iro.umontreal.ca> writes:

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

> You want nnbabyl.

No, I do not! :-)

I need to delete, edit, or otherwise alter the files.  You know, I do such
things all the time.  I surely agree that Gnus shows articles and messages
very well.  Yet, read-only backends are not very attractive to me, as I
almost invariably have to resort to other means to modify file contents.
I wish Gnus should be more helpful than prohibitive, when the times come
to modify my own files.

Hrvoje told me that `nnfolder' was allowing me to do modifications,
and that is why I feel interested to evaluate if `nnfolder' would be
comfortable for me.

-- 
François Pinard                            mailto:pinard@iro.umontreal.ca
Join the free Translation Project!    http://www.iro.umontreal.ca/~pinard



  reply	other threads:[~1999-03-05  3:29 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 [this message]
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
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=oqhfs0bom7.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).