Printing in "pine" using "enscript" and --pretty-print.

Printing in "pine" using "enscript" and --pretty-print.

Post by Thomas R. Stevens » Thu, 20 Aug 1998 04:00:00



-----BEGIN PGP SIGNED MESSAGE-----

I've recently installed "enscript" version 1.6.0. Everything seems to
work great except when I try printing from within "pine" using
enscript's "--pretty-print=mail" option. Here is the "enscript"
command I am having "pine" execute:

enscript --verbose --printer=mezz --pretty-print=mail

When I try printing a piece of email, I get the following error
messages:

AFM: scanning path...
AFM: reading font map "/usr/local/share/enscript/font.map"
processing file ""...
states: couldn't open input file `': No such file or directory
[ 0 pages * 1 copy ] sent to mezz

I get no output (except the printer tailer page) from the above
command. If I leave off the "--pretty-print=mail" option, "pine"
prints the email without any problems, but I lose the highlighting
that the "--pretty-print=mail" option provides.

I get the same results as above (the "--pretty-print" option causes
"enscript" to fail) any time standard input is NOT a file (piped input
to "enscript"). If I copy the email message to a file first, for
example, /tmp/email, and then execute:

enscript --verbose --printer=mezz --pretty-print=mail /tmp/email

The email messages prints (including highlights). But when piped input
is used:

cat /tmp/email | enscript --verbose --printer=mezz --pretty-print=mail

It fails with the same error messages I get when printing from within
"pine" (see error messages above).

How do I get "enscript" to work correctly when standard input is not a
file (piped input to "enscript") AND I use the "--pretty-print"
option?

How (if this is a different answer then above) do I get "enscript" to
work correctly when used within "pine" AND I use the "--pretty-print"
option?


- --

____  __   __  http://tom.cc.wayne.edu ftp://tom.cc.wayne.edu
 /   /_/  /_   VMail: (313) 577-4742   Fax: (313) 577-5626
/.  /\.  __/.  PGP Key: http://bs.mit.edu:8001/pks-toplev.html

"A common mistake that people make when trying
 to design something completely foolproof was    Douglas Adams
 to underestimate the ingenuity of complete      Mostly Harmless
 fools."

-----BEGIN PGP SIGNATURE-----
Version: 2.6.2
Comment: Processed by Mailcrypt 3.4, an Emacs/PGP interface

iQEVAwUBNdtQ3JMdMCa1cOy9AQEE3Af/Th/V8WLoJ1xTkUKUMLWwSY9PmOvASyW3
AofpiFVitDfepAwoGmNl3j6RyIdV7DDoZ7rdpVlUj/FuOG1bTEhp15LdblOb0BSk
1WY/SVTMREGt3uwAJCysweLkuYTYGAOOKH2bLte8CuAGuAtEOh6BXNODOoPntSQt
pL7OUp1/elhhFuL1BbH3qdojFo4ydfmC13mkFFqZbc+T518ZDgFkLNF+/nosL9c9
kamVEZ3nJy+ClurpBgU7OpqC4Ui3ETZUC5FMi/oDANwN/ehuop+Jf1vt7y4LcJrX
FCaQddFSmFEwJ9vUuCW3DhbjVjviB36N5vPpcMXV7fL3QC8NxVr2Ww==
=q3SK
-----END PGP SIGNATURE-----

 
 
 

Printing in "pine" using "enscript" and --pretty-print.

Post by Orjan Johans » Sat, 22 Aug 1998 04:00:00


[Posted and mailed]



Quote:

>I've recently installed "enscript" version 1.6.0. Everything seems to
>work great except when I try printing from within "pine" using
>enscript's "--pretty-print=mail" option. Here is the "enscript"
>command I am having "pine" execute:

>enscript --verbose --printer=mezz --pretty-print=mail
[snip]
>I get the same results as above (the "--pretty-print" option causes
>"enscript" to fail) any time standard input is NOT a file (piped input
>to "enscript").

It seems that pine has no option for using a filename when printing,
but you might try piping to the following (untested) shell script:

#!/bin/sh
cat >/tmp/enscript.$$
enscript --verbose --printer=mezz --pretty-print=mail /tmp/enscript.$$
rm /tmp/enscript.$$

Greetings,
?rjan.

--
A pro-spam bill has passed the US Senate, and is now in the House of
Representatives.  See <http://www.cauce.org> and
<http://www.ybecker.net/>.

 
 
 

Printing in "pine" using "enscript" and --pretty-print.

Post by Jeffrey Goldber » Mon, 24 Aug 1998 04:00:00





> >I've recently installed "enscript" version 1.6.0. Everything seems to
> >work great except when I try printing from within "pine" using
> >enscript's "--pretty-print=mail" option. Here is the "enscript"
> >command I am having "pine" execute:

> >enscript --verbose --printer=mezz --pretty-print=mail

[And some stuff snipped which seems to indicate that enscript is not
reading from stdin with those options]

Hmm.  For me it works just fine.  I just installed

  GNU enscript 1.6.1

and it is reading from stdin with the same options (different printer) as
in the example originally reported.  I have it working from pine as well.

-j

--
Jeffrey Goldberg                +44 (0)1234 750 111 x 2826
 Cranfield Computer Centre      FAX         751 814

Relativism is the triumph of authority over truth, convention over justice.