🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: comp.lang.postscript
Article #6169

Re: how to read stdin?

#6169
From: Tim Maceachern
Date: Fri, 31 May 1991 16:21
23 lines
1348 bytes
jesper@diku.dk (Jesper L. Lauritsen) writes:

>Can someone tell me how to read standard input so CR LF does not get translated
>to LF?
>Thanks in advance.

>--Jesper

>--------------------
>Jesper L. Lauritsen, systems programmer
>ibtjll@vm.ibt.dk    (BITNET/EARN: IBTJLL AT DKIBT)
>Center for Applied Datalogy, University of Copenhagen

If this is possible, I'd like to hear the method as well.  It would be
a convenience to have this transparent input capability to allow users
to write printer-emulators.  I was unable to proceed on a project that
would simply print dumb-LP type PC documentation because CR/LF for normal
text is indistinquishable from CR alone for underlining.

By the way, this work was on a QMS 800 II

    Tim MacEachern     Software Kinetics Ltd.     Dartmouth, Nova Scotia
                     maceache@corp.nstn.ns.ca   or maceache@fox.nstn.ns.ca
Technical Details
Message-ID: <1991May31.162113.8186@nstn.ns.ca>
Path: arc1-ca.pugleaf.net!utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!nstn.ns.ca!usenet
References: <1991May31.105841.13048@odin.diku.dk>

Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!nstn.ns.ca!usenet
From: maceache@fox.nstn.ns.ca (Tim Maceachern)
Newsgroups: comp.lang.postscript
Subject: Re: how to read stdin?
Message-ID: <1991May31.162113.8186@nstn.ns.ca>
Date: 31 May 91 16:21:13 GMT
References: <1991May31.105841.13048@odin.diku.dk>
Sender: usenet@nstn.ns.ca (NNTP Entity)
Organization: NSTN Network Operations Centre, Nova Scotia, Canada
Lines: 23