Re: inconsistent treatment of backslash-bang

[Chet Ramey]

> That still leaves the issue of the discrepancy between the way bash actually
> behaves, and the way it's documented to behave.

Really.

This is from the man page, in the QUOTING section:

Enclosing characters in double quotes preserves the  literal  value  of
all  characters  within the quotes, with the exception of $, `, \, and,
when history expansion is enabled, !.  The characters $  and  `  retain
their  special meaning within double quotes.  The backslash retains its
special meaning only when followed by one of the following  characters:
$,  `,  ", \, or <newline>.  A double quote may be quoted within double
quotes by preceding it with a backslash.  If enabled, history expansion
will  be  performed  unless an !  appearing in double quotes is escaped
using a backslash.  The backslash preceding the !  is not removed.

Essentially the same text appears in the info document.

Chet

-- 
``The lyf so short, the craft so long to lerne.'' - Chaucer

Chet Ramey, ITS, CWRU    chet@case.edu    http://tiswww.tis.case.edu/~chet/