bug in bash v18

[raf]

>Here's a bug I noticed in Bash v18:

>In some cases, if a back tick expression is used to generate a command name
>and the generated text contains a newline, bash will reply--

>: command not found

>It appears to trying to treat the newline as the command rather than the
>text.

this might have something to do with file systems mounted as != binary.
the backticked command produces CRLF and bash doesn't expect it?

try remounting as = binary and see what hapepns.

raf

-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".