|
cat origNow is the time for all good men to come to the aid of their country.
sed 's:i:\>
i:g' orig > sedd$
cat seddNow
Aaron,
I intentionally added the extra back slash. I read the following line at
the information center:
Each \n (new-line character) inside Text must have an additional \
character before it (\\n).
My interpretation of that is that I needed to add an additional slash to
the replacement string.
Here's the link I was looking at.
http://publib.boulder.ibm.com/infocenter/systems/index.jsp?topic=/com.ib
m.aix.genprogc/doc/genprogc/manip_strings_sed.htm
I honestly don't know the first think about sed, but that was just
something I came across. I figured it was worth a try.
-----Original Message-----
From: midrange-l-bounces+grizzlym=northernwholesale.com@xxxxxxxxxxxx
[mailto:midrange-l-bounces+grizzlym=northernwholesale.com@xxxxxxxxxxxx]
On Behalf Of Aaron Bartell
Sent: Monday, November 19, 2007 4:01 PM
To: 'Midrange Systems Technical Discussion'
Subject: RE: Using sed to replace all instances with a hex value
I believe you have one to many back slashes in there. Try the
following:
sed 's/i/\n/g' /home/grizzly/file1.txt > /home/grizzly/file2.txt
I am guessing it will simply do an 'n' vs. '\n' in the resulting text,
but
thought I would point that out.
Thanks for your response,
Aaron Bartell
http://mowyourlawn.com
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Grizzly Malchow
Sent: Monday, November 19, 2007 3:59 PM
To: Midrange Systems Technical Discussion
Subject: RE: Using sed to replace all instances with a hex value
Aaron,
I had the same results as you did. I am also at V5R3. We installed a
cume back in June that I believe put us up to date in regards to PTF's.
I tried:
sed 's/i/\\n/g' /home/grizzly/file1.txt > /home/grizzly/file2.txt
and the results were as follows:
Th\ns \ns a test to see \nf a new l\nne w\nll be created for each t\nme
the letter \n \ns found.
This replaced i with \n but it doesn't seem to insert a new line.
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Aaron Bartell
Sent: Monday, November 19, 2007 3:09 PM
To: 'Midrange Systems Technical Discussion'
Subject: RE: Using sed to replace all instances with a hex value
I think I may have not relayed my problem well enough. My problem is
that
the new line (i.e. \n) isn't working - or any excaped character for that
matter.
For example, given the following content in /home/aaron/file1.txt:
-----------------------------------------------
This is a test to see if a new line will be created for each time the
letter
i is found.
-----------------------------------------------
Now I run the following sed statement:
sed 's/i/\n/g' /home/aaron/file1.txt > /home/aaron/file2.txt
file2.txt now contains:
-----------------------------------------------
Thns ns a test to see nf a new lnne wnll be created for each tnme the
letter
n ns found.
-----------------------------------------------
Note how it simply replaced all letter 'i' instances with 'n' instead of
creating a new line like it should have. Can somebody else run the same
on
their system to see if I may need to load some PTF's? Note that I
looked
for PTF's at Fix Central, but found none for sed.
I am at V5R3.
Thanks,
Aaron Bartell
http://mowyourlawn.com
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.