"Muttprint" (pretty-print) for Cygwin?

[Thomas Baker <thomas dot baker at bi dot fhg dot de>]

This thread started on mutt-users but really belongs here.
I have been trying to fill in the gaps of things missing from
a Cygwin/Mutt mail environment versus Linux.  Now that I got
enscript and mailcap working, and procmail almost working,
I want to move on to muttprint, urlview, and mailgrep.

If the goal of Muttprint is to suppress administrative
header lines and print mail nicely, one per page (see
http://muttprint.sourceforge.net/pics/sampe.png), then the
script I started to write based on Olaf's (see below) is a 
start.  But I spoke too soon: enscript expects just one 
mail message at a time, not an entire mbox.

I should think that the basic Muttprint task would be doable
by putting an mbox through a Perl script that did the equivalent
of:

	ignore *        # "ignore all header lines by default"
	unignore        from: subject to cc mail-followup-to date 

then split the into separate messages, piping each one
through enscript.

Has anyone perhaps already done this?

Tom


On Sat, Jun 08, 2002 at 12:14:16PM +0200, Thomas Baker wrote:
> Olaf wrote:
> > $ cat ~/bin/print
> > #!/bin/sh
> > cat > .printout
> > lpr -S <server> -P <printer> .printout
> > 
> > where <server> is a windows print server with lpd enabled.
> 
> This script solved my more basic problem of getting _anything_
> to my printer from the Cygwin command line.  However,
> it does not "pretty print" in the style of Muttprint (see
> http://muttprint.sourceforge.net/pics/sampe.png).  
> 
> However, enscript has recently appeared in the Cygwin distribution,
> so putting Olaf's script together with a suggestion Darren made on 
> this list a few months ago yields:
> 
> $ cat ~/bin/muttprint
> #!/bin/sh
> enscript -Email > .printout
> c:/winnt/system32/lpr -S <server> -P <printer> .printout

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/