Re: Enscript

Farley Flud wrote this copyrighted missive and expects royalties:

On Wed, 23 Oct 2024 08:54:11 -0400, Chris Ahlstrom wrote:
>

I haven't used enscript for quite awhile. I used it all the time at work to
print code without having to use a text editor to do it. Here's part of a
script to convert a text file to PDF, with line numbers and a narrow font
suitable to printing. Blank lines and some info output removed.
 
#!/bin/bash
FONT="Monospace8"
OPTIONS="q -B -C -G -T3"

>
You must write very short lines.

I generally keep them under 80 characters.  Much easier to read, for
one thing.

The default page for enscript is A4 and that is very near to
Letter size of 8.5" x 11".
>
Most code, if we include the indents, has long lines of far more
than 80 characters that even with a size 8 font will exceed the
bounds of an A4 page.  Enscript will wrap them by default and the
result is sort of ugly.
>
One could specify "landscape" orientation but that may not solve
the problem entirely.
>
The only other possibility would be to specify an A1 page size.
>
My philosophy is just to keep it in text format.

Well, printing text (e.g. from vim) doesn't (as far as I know) allow
for changing the font.

Enscript, and equivalents such as aps, paps, etc., are certainly
very capable programs, but who the fuck actually PRINTS nowadays?

I do, in limited quantities.

Printing is, or should be, dead.  Like facsimile (fax) it is kept
alive by throwback idiots that cannot adapt to change.

:-D

Sometimes it's easier, when going through a big script, to have the print
out to mark up as one makes the script work. Then later apply the fixes to the
file.

--
My analyst told me that I was right out of my head,
But I said, "Dear Doctor, I think that it is you instead.
Because I have got a thing that is unique and new,
To prove it I'll have the last laugh on you.
'Cause instead of one head -- I've got two.
And you know two heads are better than one.