bug-gnulib
[Top][All Lists]
Advanced

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

Re: gnulib-tool bug


From: Eric Blake
Subject: Re: gnulib-tool bug
Date: Fri, 27 Feb 2009 22:47:07 +0000 (UTC)
User-agent: Loom/3.14 (http://gmane.org/)

Bruno Haible <bruno <at> clisp.org> writes:

> 
> > /^/test-freadptr.c/d
> 
> This should be  /^\/test-freadptr.c/d
> 
> This may be a difference between sh or sed versions. What's the result of 
these
> two sets of commands for you?
> 
> $ doubly_escaped_anchor='\\/'
> $ echo 'test-freadseek.sh' | \
>   sed -e 's,/,\\/,g' -e "s,^,/^${doubly_escaped_anchor}," -e 's,$,\$/d,'
> 
> $ triply_escaped_anchor='\\\/'
> $ echo 'test-freadseek.sh' | \
>   sed -e 's,/,\\/,g' -e "s,^,/^${triply_escaped_anchor}," -e 's,$,\$/d,'
> 
> For me, with bash and sed-4.1.5, the result of both is
> /^\/test-freadseek.sh$/d
> 
> And on your side?

Using bash 3.2 and set 4.1.5, and both commands gave

/^\/test-freadseek.sh$/d

although I think that technically the doubly_escaped_anchor version is more 
portable, since POSIX says that \/ is not portable when / is not the delimiter.

Hmm, maybe it could also be related to a bug in cygwin 1.7 pipes.  There was a 
patch submitted today (but which I have not yet tested) which attempts to 
reduce races and the likelihood that pipes could sometimes lose data.

-- 
Eric Blake







reply via email to

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