On Tue, 1 Aug 2000, John Summerfield wrote:
That is another good way to clean it up. I'm using includes
allready, I just never thought of it. I think though, in keeping
with your KISS rule, a better way would be to write a script
which generates the file for me, which gets included. My reason
Is that so simple? It might be if you were reading your address-book and
generating recipes from that. If you're doing that, perhaps you could write a
script that does the delivery instead.
I've considered doing it via my address book as well. I am
initially going to code it from a dat file though. I need to
make room for future improvements. ;o)
If you want to become a better basher, do it in bash (but do
take care not to lose all 25 friends before you sort it out).
Otherwise, Perl's a good choice.
Yes, I think I will use bash. I have a backup filter that
captures TONNES of email in case something goes wrong. I got bit
by procmail coding before and enabled some nasty backup
for cleaning this stuff up is that looking in the files is
messy. I just want to plop in a line and go.. The script idea
will automate it for me.
I've decided that altogether two many programs are littering my
home directory with their configuration files. I've created
~/.etc and stuffed a few files in there. It's got a a lot of
procmail files, plus a few from my other efforts.
Yes, that is a good idea. I have a ~/etc dir too, but .etc makes
more sense. I think I'll move it. Thanks for the great tips
Mike A. Harris Linux advocate
Computer Consultant GNU advocate
Capslock Consulting Open Source advocate
... Our continuing mission: To seek out knowledge of C, to explore
strange UNIX commands, and to boldly code where no one has man page 4.
procmail mailing list