From: Christopher Davis <ckd@loiosh.kei.com>
Subject: Re: nnfolder comments (may apply to other backends too)
Date: 15 Jan 1997 10:26:44 -0500 [thread overview]
Message-ID: <w4wwtfj6x7.fsf@loiosh.kei.com> (raw)
In-Reply-To: larsi@ifi.uio.no's message of 14 Jan 97 23:30:10 GMT
JV> == Jan Vroonhof <vroonhof@math.ethz.ch>
LMI> == Lars Magne Ingebrigtsen <larsi@ifi.uio.no>
JV> nnmail could just as well suck in a file in the procmail directory
JV> with same name as the group. I mean there is no need for a suffix if
JV> you keep a separate directory.
LMI> You may keep other files in the spool directory that aren't related
LMI> to mail thingies at all.
But it should be possible to run without the suffix if you *do* keep a
separate directory. This has kept me from moving to Gnus for mail as yet.
The only files in the spool directory that aren't spools are hidden (dot)
files anyway, which should be ignored.
I do it this way because I have a number of tools that do things like
monitor the size and mtime/atime of files in that directory to give me a
multi-file "biff", and they use the name of the file as the title of the
mailbox. A redundant suffix would just clutter up their output
needlessly, or force me to rewrite all of them to use it--including some
that are just shell aliases with a special set of completions. All the
code is built so that to create a new spool file the only files that I
have to change are .procmailrc and .vm, and if I get better at lisp I'll
fix it so .vm doesn't need changing.
Code like the following, for example:
#!/usr/bin/perl
$spooldir = "$ENV{'HOME'}/Mail/spool";
chdir($spooldir) || die "can't chdir";
foreach (<*>) {
($dev,$ino,$mode,$nlink,$uid,$gid,$rdev,$size,
$atime,$mtime,$ctime,$blksize,$blocks) = stat($_);
next if ($size == 0);
print (($atime < $mtime)?" ** ":" ");
print $_,"\n";
}
next prev parent reply other threads:[~1997-01-15 15:26 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
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 [this message]
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=w4wwtfj6x7.fsf@loiosh.kei.com \
--to=ckd@loiosh.kei.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).