bug-gnu-utils
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: sed newline bug (sed 3.2)


From: Stepan Kasal
Subject: Re: sed newline bug (sed 3.2)
Date: Mon, 25 Oct 2004 14:34:16 +0200
User-agent: Mutt/1.4.1i

Hello,

On Mon, Oct 25, 2004 at 01:57:16PM +0200, galeran wrote:
> Sed version 3.2 does recognize the \n sequence in the s/// command's
> regexp part, but doesn't recognize neither \n or \<newline> sequence in

I recall that the \newline escape sequence was supported in a GNU sed 3.x.

Try to create file
--------
# cmd.sed
s/x/\
/
--------
and then do
        sed -f cmd.sed

But the real fix is to upgrade to sed 4.x

If yyou cannot upgrade and the above doesn't work, you can use the
hold space in sed (commands g, h, etc.) or perhaps you could jump
into (GNU) awk.

Good luck,
        Stepan Kasal




reply via email to

[Prev in Thread] Current Thread [Next in Thread]