From: Farley Flud <ff@linux.rocks>
Subject: Re: Enscript
Newsgroups: comp.os.linux.advocacy
References: <vfarm9$21oij$1@dont-email.me> <pan$123ce$b55cb55c$c4582e9e$302f6741@linux.rocks> <vfbe4c$2518h$1@dont-email.me>
Mime-Version: 1.0
Message-Id: <pan$6f8d9$abe457c3$85e0006b$f14e2a5d@linux.rocks>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Lines: 22
Path: ...!weretis.net!feeder9.news.weretis.net!panix!usenet.blueworldhosting.com!diablo1.usenet.blueworldhosting.com!feeder.usenetexpress.com!tr2.iad1.usenetexpress.com!news.usenetexpress.com!not-for-mail
Date: Wed, 23 Oct 2024 19:06:13 +0000
Nntp-Posting-Date: Wed, 23 Oct 2024 19:06:13 +0000
X-Received-Bytes: 1142
X-Complaints-To: abuse@usenetexpress.com
Organization: UsenetExpress - www.usenetexpress.com
Bytes: 1467

On Wed, 23 Oct 2024 14:09:01 -0400, Chris Ahlstrom wrote:

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

That's the same old excuse.

It seems that you haven't gotten fully accustomed to the digital way
of doing things.

There are ways, if only totally ad hoc, of doing the same with text
editors. 

In my opinion, there should NEVER be a need to rise up from ones chair
to peruse a ridiculous print.


-- 
Systemd: solving all the problems that you never knew you had.