[8755] in Athena Bugs
rsaix 7.3R: enscript
daemon@ATHENA.MIT.EDU (Calvin Clark)
Fri Dec 13 00:57:19 1991
Date: Fri, 13 Dec 91 00:57:05 -0500
From: Calvin Clark <ckclark@Athena.MIT.EDU>
To: klund@Athena.MIT.EDU
Cc: bugs@Athena.MIT.EDU, cyrus@Athena.MIT.EDU, probe@Athena.MIT.EDU,
Reply-To: ckclark@mit.edu
(In reply to [8442], [8675], and [8754] in bugs.)
Comment: You are undoubtedly using a non-standard $path, since this is
the behavior of /usr/bin/enscript. /usr/athena/bin/enscript, which is
first in $athena_path, does not have this problem. However, I'd say
that this is still a bug, since the description of enscript given in the
Info Browser contains the following example, which claims that you *can*
use the -P option, even when you can't:
The enscript command reads plain text files, converts them
to PostScriptb format, and spools them for printing on a
PostScriptb printer. Fonts, headings, limited formatting
options, and spooling options may be specified.
For example:
enscript -Paleph bubble.txt
The -d option to /usr/bin/enscript takes a queueing spool (i.e., a
printer name) for an argument, if you insist on using the vendor
version. Except for the bad example I've just mentioned, the Info
Browser's description of the vendor's enscript is reasonably accurate.
(As a side note, /usr/athena/bin/enscript on the RS/6000 just provides some
compatability for environment variables and command line arguments and
then execs the vendor version.)
-Calvin
Ezra: I believe at some time I compiled a current version of enscript on
all of the architectures, including the RS/6000, and it seemed to work.
Since it is possible, shouldn't we be running the the same version of
enscript on all of our platforms, for homogeneity reasons alone? Or am
I missing something?
