From: Jan Vroonhof <vroonhof@math.ethz.ch>
Subject: Re: nnfolder comments (may apply to other backends too)
Date: 10 Jan 1997 17:34:19 +0100 [thread overview]
Message-ID: <byenftebg4.fsf@math.ethz.ch> (raw)
In-Reply-To: Lars Magne Ingebrigtsen's message of 10 Jan 1997 15:58:42 +0100
Lars Magne Ingebrigtsen <larsi@ifi.uio.no> writes:
> > Then what's use of having a suffix?
>
> To let nnmail know which files to suck in. `nnmail-procmail-suffix'
> isn't used by nnfolder for anything, and I don't see any reason why it
> should.
nnmail could just as well suck in a file in the procmail directory
with same name as the group. I mean there is no need for a suffix if
you keep a separate directory.
bal/bla/Mail/spool/group.spool
is tautological.
For me at least the whole purpose of having the extention is that you
CAN ceep the spool and the actual folder together. This is a somewhat moot
moint if you use a directory based backend, but I think it looks tidy
with nnfolder.
>
> > (n-g-a-f is way too aggressive for me anyway but I think it should
> > at least be possible to have all mail groups related stuff in one
> > directory)
>
> Probably not.
I like it that way and works just fine as along as you don't use n-g-a-f
For me it would super if nnfolder-g-a-f would just create a gpoup
blabla for any blabla.spool files it didn't know about and forget
about the other files
Jan
next prev parent reply other threads:[~1997-01-10 16:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-01-08 19:28 Jan Vroonhof
1997-01-09 8:04 ` Andy Eskilsson
1997-01-09 11:10 ` Lars Magne Ingebrigtsen
1997-01-10 13:20 ` Jan Vroonhof
1997-01-10 14:58 ` Lars Magne Ingebrigtsen
1997-01-10 16:34 ` Jan Vroonhof [this message]
1997-01-14 23:30 ` Lars Magne Ingebrigtsen
1997-01-15 9:18 ` Jan Vroonhof
1997-01-16 23:01 ` Lars Magne Ingebrigtsen
1997-01-15 15:26 ` Christopher Davis
1997-01-16 23:02 ` Lars Magne Ingebrigtsen
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=byenftebg4.fsf@math.ethz.ch \
--to=vroonhof@math.ethz.ch \
/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).