my test seems to indicate that the backslash escape character is being
processed twice.

below producea <\\MCBELL4\BossTemp\NewAccount\LHCTEST2ERROR.csv>
QSH CMD('sed -e
"s?&1?<\\\\\\\\MCBELL4\\\\BossTemp\\\\NewAccount\\\\LHCTEST2ERROR.csv>?g"
/home/palhc/sed.txt > /home/palhc/sed.txt.sedout')

ugly.....


"hockchai Lim" <lim.hock-chai@xxxxxxxxxxxxxxx> wrote in message
news:mailman.35115.1300803844.2702.midrange-l@xxxxxxxxxxxx...
it almost looks like the backslash escape character is being processed
twice (once by qsh and once by sed).

All I know at the moment is that I fed it this
:\\MCBELL4\BossTemp\NewAccount\LHCTEST2ERROR.csv and it splited out this:
<MCBELL4BossTempNewAccountLHCTEST2ERROR.csv>.

"Dennis Lovelady" <iseries@xxxxxxxxxxxx> wrote in message
news:mailman.35068.1300747685.2702.midrange-l@xxxxxxxxxxxx...
You should be able to get the effect you want my changing quotes (") to
apostrophes (').

It's the shell, not sed, that's processing the escapes.






This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2026 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.