i'm having a bit of trouble understanding how to integrate mhfixmsg
into my workflow.
i'd like to automatically run mhfixmsg on all mail, and, therefore,
keep a backup of messages that it processes. since i kind of abhor
the ,nnn style of mh backups, i'd like to keep the mhfixmsg backups in
a separate folder. i think i can do this by setting mhfixmsg's
rmmproc to a command that does something like:
cp $* $(mhpath +mhfixbackup new)
is there a better way?
to invoke mhfixmsg, using add-hook would normally seem like the best
bet, except that it makes "refile -link" useless (for messages that
mhfixmsg wants to process), as far as i can tell. there's no way to
disable add-hook for individual commands, right? are hooks a useful
enough feature that making them settable for individual commands
(i.e. "inc: -add-hook my-inc-add-hook") be desireable?
the man page also suggests using something like:
alias inc='inc && mhfixmsg'
but i don't see how this will work -- what if inc incorporates several
messages? mhfixmg by default will only act on 'cur', leaving the
others unprocessed. (i suppose "inc && mhfixmsg unseen" would work, at
the cost of re-checking messages that i've manually added back into
the unseen sequence.)
finally -- it feels like mhfixmsg should always add a new
"X-mhfixmsg-was-here" header when it modifies a message, which would
let me know that there is (or was) another version of the message file
floating around somewhere. was this considered?
paul
=----------------------
paul fox, pgf(_at_)foxharp(_dot_)boston(_dot_)ma(_dot_)us (arlington, ma,
where it's 25.0 degrees)
_______________________________________________
Nmh-workers mailing list
Nmh-workers(_at_)nongnu(_dot_)org
https://lists.nongnu.org/mailman/listinfo/nmh-workers