Chet Ramey wrote: > csh allows backslash to act as an escape character > (that is, it is removed) when it precedes ! in a double-quoted string. > Bash doesn't ...
But if it doesn't, then why does bang not have its history-expansion behaviour? Either it's acting as an escape or it isn't. Which is it supposed to be? > -- and Posix and historical sh behavior agree. Plain and simple. But you also said: > I already explained that bash follows csh as closely as possible > in its history expansion implementation. So which is it? Is bash trying to follow csh behaviour "as closely as possible", or not?
