| Subject: | Re: inconsistent treatment of backslash-bang |
|---|---|
| From: | Lawrence D'Oliveiro <ldo@xxxxxxxxxxxxxxxxxxx> |
| Date: | Fri, 18 Jul 2008 13:39:18 +1200 |
| Newsgroups: | gnu.bash.bug |
Chet Ramey wrote: > Yes, this is where the semantics of history expansion clash with traditional > shell behavior. Only single quotes inhibit history expansion. In that case, situation number 3 is producing the wrong result, since there are no single quotes there, only a backslash. Whichever way you look at it, there's still a bug. Lawrence |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | removing null elements from an array, Poor Yorick |
|---|---|
| Next by Date: | setuid from shellscript isn't permanent, Mr Aras |
| Previous by Thread: | Re: inconsistent treatment of backslash-bang, Chet Ramey |
| Next by Thread: | Re: inconsistent treatment of backslash-bang, Chet Ramey |
| Indexes: | [Date] [Thread] [Top] [All Lists] |