Bug 6768 - /bin/echo does not process escape char \n
/bin/echo does not process escape char \n
Status: CLOSED DUPLICATE of bug 6498
Product: Red Hat Linux
Classification: Retired
Component: bash (Show other bugs)
6.1
i386 Linux
high Severity high
: ---
: ---
Assigned To: Cristian Gafton
http://www.resonate.com
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 1999-11-05 18:24 EST by jcassell
Modified: 2008-05-01 11:37 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 1999-11-09 11:27:02 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description jcassell 1999-11-05 18:24:52 EST
/bin/echo and echo no longer interpret the newline escape
character embedded in a string. E.G.

TMP="This is some text"
TMP=${TMP}"\nwith a newline in the middle"

/bin/echo ${TMP}

This code work fine in 6.0 and other flavors of unix:

This is some text
with a newline in the middle

but in RH 6.1 this is the output:

This is some text\nwith a newline in the middle

This bug has cost us a lot of time and money! What are you
guys smoking over there?! (sorry)
Comment 1 jcassell 1999-11-08 15:16:59 EST
BTW, I neglected to mention, the bug-like echo behavior is exhibited
in a Bourne shell script - i.e. #!/bin/sh.
Comment 2 Bill Nottingham 1999-11-09 11:27:59 EST
*** This bug has been marked as a duplicate of 6498 ***

Note You need to log in before you can comment on or make changes to this bug.