Kyle Wheeler wrote:
I figured that since I'm using MH format anyway, I should be able to
include a path directly to the message file itself ... except that
Mutt doesn't seem to give me a way to pass that information when I
pipe a message to a script.
Of course not - it's a *pipe*. :)
In the example:
cat foo | somecommand
somecommand has no way of ever discovering what or where foo is.
That's a feature, not a flaw.
I understand that. I guess what I should have said was "Mutt doesn't
give me any way to pass a pointer to the message file. All I can do is
pipe the contents of the message."
Thanks!
-pd
--
--------
Peter Davis
Funny stuff - http://www.pfdstudio.com
Ideas Great and Dumb - http://www.ideasgreatanddumb.com
Art/Tech Fusion - http://www.arttechfusion.com
The Tech Curmudgeon - http://www.techcurmudgeon.com
