bergman(_at_)merctech(_dot_)com said:
I like the concept of folder-specific components very much. In fact,
this could be extended to all sorts of folder-specific settings
(different scan filters for different folders, different sortm flags
per-folder, etc.).
My current implementation is for all files that are searched for
in /etc/nmh and in ~/Mail (or your local equivalents). Stuff that is
only commandline, or configured in the mh-profile would need much
more extensive hacking.
At very least, if the per-folder components files are stored in the
data directories they should be hidden files (which breaks the
existing nmh file naming convention, IMHO).
Nmh mails are all numerical-only files. I have not seen any part of
nmh that treats any non-numerical file as an email. Besides hidden
files (I assume you mean files starting with a dot, not hp-ux 9
h-bit files), there are (by default) files starting with a comma
that are backups of deleted emails. I haven't written any program
that assumes all files are mails, and I can't believe anybody has
written serious code that does.
But, as I mailed earlier, the option of a config subdir tree would
be better than one flat directory. Anybody against that system?
Tob