| Subject: | Re: inconsistent treatment of backslash-bang |
|---|---|
| From: | Lawrence D'Oliveiro <ldo@xxxxxxxxxxxxxxxxxxx> |
| Date: | Mon, 21 Jul 2008 15:26:12 +1200 |
| Newsgroups: | gnu.bash.bug |
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? |
| Previous by Date: | Re: inconsistent treatment of backslash-bang, Paul Jarc |
|---|---|
| Next by Date: | Re: setuid from shellscript isn't permanent, Aras Vaichas |
| Previous by Thread: | Re: inconsistent treatment of backslash-bang, Paul Jarc |
| Next by Thread: | Re: inconsistent treatment of backslash-bang, Chet Ramey |
| Indexes: | [Date] [Thread] [Top] [All Lists] |