Thanks, Larry.
>
> You should be able to shorten the tr and save a pipe ...
>
> tr -d ['\r\n'] < brad.txt > brad2.txt
>
> Larry Hiscock
> Western Computer Services
U.S. BANCORP made the following annotations
-
Electronic Priva
You should be able to shorten the tr and save a pipe ...
tr -d ['\r\n'] < brad.txt > brad2.txt
Larry Hiscock
Western Computer Services
> Thanks for the ideas. dd scared me. Lots of warnings about destroying your
> hard drive. =:O
>
> I figured it out with tr. There might be a way to do it in on
Thanks for the ideas. dd scared me. Lots of warnings about destroying your
hard drive. =:O
I figured it out with tr. There might be a way to do it in one step, but
piping works fine.
tr -d '\r' < brad.txt | tr -d '\n' > brad2.txt
U.S. BANCORP made the following annotations
---
es
together in the format required.
It's whichever you find easiest - or is easier for the next guy to
support
Hth
Colin
-Original Message-
From: Marc A Hilbert
Sent: December 12, 2012 5:59 PM
To: 'U2 Users List'
Subject: Re: [U2] Stripping line breaks from InfoTrieve outpu
easier for the next guy to
support
Hth
Colin
-Original Message-
From: Marc A Hilbert
Sent: December 12, 2012 5:59 PM
To: 'U2 Users List'
Subject: Re: [U2] Stripping line breaks from InfoTrieve output
Brad,
I know nothing about infotrieve, but why can't you use OPENSE
Brad,
I know nothing about infotrieve, but why can't you use OPENSEQ and then a
READBLK loop?
READBLK reads the next N bytes from a file, not caring if there are line
delimiters of other strange characters.
Regards,
Marc
-Mensaje original-
De: u2-users-boun...@listserver.u2ug.org
[mailto:
