Ethan Glasser-Camp wrote:
> I think I see. So the backslash isn't counting as an escape character
> here, and so passes through without being removed, but does inhibit
> history expansion anyhow?
Yes. This is where the basic incompatibility of csh-derived features
and Posix shows.
Chet
--
``Th
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Chet Ramey wrote:
> Not true, in general. Posix specifies the characters the backslash
> can escape in double-quoted strings. You happened to choose three of
> the five.
>
> http://www.opengroup.org/onlinepubs/009695399/utilities/xcu_chap02.html#tag
Ethan Glasser-Camp wrote:
> Hi,
>
> I'm not a shell script pro and I don't know much about POSIX, but I
> have found this puzzling behavior in bash, and although it is
> documented I don't really understand why bash behaves this way. I was
> hoping someone could tell me.
>
> [EMAIL PROTECTED]:~$
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
I'm not a shell script pro and I don't know much about POSIX, but I
have found this puzzling behavior in bash, and although it is
documented I don't really understand why bash behaves this way. I was
hoping someone could tell me.
[EMAIL PROTECTED
