X-Authentication-Warning: kendall.sfbr.org: jeffw set sender to jeffw AT darwin DOT sfbr DOT org using -f
Date: Thu, 20 Jun 2002 10:19:39 -0500
From: JT Williams <jeffw AT darwin DOT sfbr DOT org>
To: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
Cc: djgpp AT delorie DOT com
Subject: Re: sed and bash : djgpp vs Solaris
Message-ID: <20020620151939.GA8979@kendall.sfbr.org>
Mail-Followup-To: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>, djgpp AT delorie DOT com
References: <20020619152624 DOT GA1328 AT kendall DOT sfbr DOT org> <Pine DOT SUN DOT 3 DOT 91 DOT 1020620075557 DOT 9087B-100000 AT is>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <Pine.SUN.3.91.1020620075557.9087B-100000@is>
User-Agent: Mutt/1.3.27i
Reply-To: djgpp AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk

-: Try the same version of Sed on Solaris.  IIRC, there's no difference 
-: between the DJGPP port and the official sources that could affect how \t 
-: and \n are handled in replacements.  It's either a Bash issue (perhaps 
-: Bash converts \t into a literal TAB), or a Sed version issue.

It's the difference between sed 3.02 and sed 3.02.80 (and thanks for
the alpha.gnu.org pointer).  From the NEWS file for sed 3.02.80:

The s/// command now understands the following escapes
(in both halves):
        \a      an "alert" (BEL)
        \f      a form-feed
        \n      a newline
        \r      a carriage-return
        \t      a horizontal tab
        \v      a vertical tab
        \oNNN   a character with the octal value NNN
        \dNNN   a character with the decimal value NNN
        \xNN    a character with the hexadecimal value NN