Saint skullY the Dazed <skully@netlsd.org> writes:
> Bash can't seem to handle correctly parsing backslash characters that appear
> just before the bang (!) character, when both are enclosed in double quotes.
This is the intended behavior. The man page says:
# Enclosing characters in double quotes preserves the literal value of
# all characters within the quotes, with the exception of $, `, and \.
# 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.
paul