[Top][All Lists]

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

Re: [PATCH 1/3] Properly expand @configure_input@ in config.status.

From: Ralf Wildenhues
Subject: Re: [PATCH 1/3] Properly expand @configure_input@ in config.status.
Date: Sun, 6 Jan 2008 11:02:31 +0100
User-agent: Mutt/1.5.13 (2006-08-11)

* Paolo Bonzini wrote on Sun, Jan 06, 2008 at 10:35:49AM CET:
> Paolo Bonzini wrote:
> >
> >>I'm interested in how other seds behave for say
> If one really interprets "a literal character", this would require the \ 
> to be dropped in front of 1, {, etc., but not in front of &, ., etc.
> It seems too complicated...  So if these three invocations of other seds 
> are not coherent it would be good to file an interpretation request. 
> Thanks.

Please note that with current GNU sed behavior, it is not possible to
substitute an &.  Even if it may be more coherent, that's not all that

I tried these:

AIX 4.3.3, Darwin 8.11, FreeBSD 6.2, GNU sed 4.1.5, HP-UX 10.20, 11.23
(IA, PA), IRIX 6.5, NetBSD 4.99.43, OpenBSD 4.0, Solaris 6, 10, Tru64
4.0D, 5.1.

1) echo 'axaaxaaaxa{1,2}' | sed 's{a\{1,2\}{b{g'

a) axaaxaaaxb
b) sed: 1: "s{a\{1,2\}{b{g": RE error: parentheses not balanced
Darwin, FreeBSD, NetBSD, OpenBSD
c) bxbxbbxb{1,2}
AIX, HP-UX, Solaris, Tru64
d) sed: command garbled: s{a\{1,2\}{b{g

2) echo abca.c | sed 's.a\'
a) xyzxyz
Darwin, FreeBSD, GNU, IRIX, NetBSD, OpenBSD
b) abcxyz
Solaris, AIX, HP-UX, Tru64

3) echo 'abca(b)ca\(b\)c' | sed 's1a\(b\)c1A\1C1g'
a) A1Ca(b)ca\(b\)c
b) AbCa(b)ca\(b\)c
AIX, Darwin, FreeBSD, HP-UX, IRIX, NetBSD, OpenBSD, Solaris, Tru64


reply via email to

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