[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: inconsistent treatment of backslash-bang
From: |
Lawrence D'Oliveiro |
Subject: |
Re: inconsistent treatment of backslash-bang |
Date: |
Mon, 21 Jul 2008 15:26:12 +1200 |
User-agent: |
Microsoft-Outlook-Express-Macintosh-Edition/5.0.6 |
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?
- Re: inconsistent treatment of backslash-bang, (continued)
- Re: inconsistent treatment of backslash-bang, Lawrence D'Oliveiro, 2008/07/18
- Re: inconsistent treatment of backslash-bang, Lawrence D'Oliveiro, 2008/07/18
- Re: inconsistent treatment of backslash-bang, pk, 2008/07/18
- Re: inconsistent treatment of backslash-bang, Lawrence D'Oliveiro, 2008/07/19
- Re: inconsistent treatment of backslash-bang, Lawrence D'Oliveiro, 2008/07/19
- Re: inconsistent treatment of backslash-bang, Lawrence D'Oliveiro, 2008/07/20
- Re: inconsistent treatment of backslash-bang,
Lawrence D'Oliveiro <=
- Re: inconsistent treatment of backslash-bang, Lawrence D'Oliveiro, 2008/07/22
- Re: inconsistent treatment of backslash-bang, pk, 2008/07/22
- Re: inconsistent treatment of backslash-bang, Lawrence D'Oliveiro, 2008/07/23
- Re: inconsistent treatment of backslash-bang, pk, 2008/07/23
- Re: inconsistent treatment of backslash-bang, Lawrence D'Oliveiro, 2008/07/23