Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Date: Tue, 11 Jun 2002 10:09:18 +0200
From: Thomas Baker <thomas DOT baker AT bi DOT fhg DOT de>
To: Cygwin <cygwin AT cygwin DOT com>
Subject: Re: "Muttprint" (pretty-print) for Cygwin?
Message-ID: <20020611100918.B792@mail.gmd.de>
Mail-Followup-To: Thomas Baker <thomas DOT baker AT bi DOT fhg DOT de>,
	Cygwin <cygwin AT cygwin DOT com>
References: <20020607145647 DOT A160 AT LEPIDUS> <20020607133143 DOT GB1408 AT NBOF> <20020608121416 DOT A1332 AT LEPIDUS> <20020611095852 DOT A1600 AT mail DOT gmd DOT de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <20020611095852.A1600@mail.gmd.de>; from thomas.baker@bi.fhg.de on Tue, Jun 11, 2002 at 09:58:52AM +0200

On Tue, Jun 11, 2002 at 09:58:52AM +0200, Thomas Baker wrote:
> 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 

Oh, and perhaps filtering out MIME attachments...

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

Tom

-- 
Dr. Thomas Baker                                Thomas DOT Baker AT bi DOT fhg DOT de
Institutszentrum Schloss Birlinghoven          mobile +49-171-408-5784
Fraunhofer-Gesellschaft                          work +49-30-8109-9027
53754 Sankt Augustin, Germany                     fax +49-2241-14-2619

--
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/