Re: Is bash's "test" broken in a command substition ?

[cgf at cygnus dot com (Christopher G. Faylor)]

In article <365730B5.83912514.cygnus.gnu-win32@solfin.com>,
Gabriel Galibourg <gabriel@solfin.com> wrote:
>Hi,
>
>Is bash's 'test' broken (in a command substitution!) ? can someone else try this and tell me if they have a
>problem too ... this construct used to work fine in B19, works in ksh (under Solaris) ... quid?
>
>To reproduce:
>1) type this line in a file (call it foo.sh, but any other name will do)
>echo $( test 1 == 1 && /bin/echo yes || echo no $)
>
>2) under bash type:
>. foo.sh (YES! source it!)
>
>3) you should get the following (at least I do):
>bash.exe-2.02$ . foo.sh
>[proc] C:\usr\H-i586-cygwin32\bin\bash.exe 1607 (0) sig_send: wait for sig_complete event failed, sig 20, rc
>-1, error 6
>yes
>bash.exe-2.02$
>
>... ok, it does print 'yes' as expected but the error message is not really necessary!

The "error message" is a cygwin diagnostic.  It's a bug that will be fixed
in B20.2.
-- 
cgf@cygnus.com
http://www.cygnus.com/
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".