Bob Proulx wrote:
> Mr Aras wrote:
>
>> $ ./setuid_test_script.sh
>> mode of `/nfsroot/bin/busybox' changed to 4755 (rwsr-xr-x)
>> -rwsr-xr-x 1 root root 515956 2008-07-18 11:46 /nfsroot/bin/busybox
>>
>> $ ls /nfsroot/bin/busybox
>> -rwxr-xr-x 1 root root 515956 2008-07-18 11:45 /nfsroot/bin/bu
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
Lawrence D'Oliveiro <[EMAIL PROTECTED]> wrote:
> It's not going to break any executable scripts, since it has already
> been pointed out to me that history expansion doesn't happen in
> scripts.
History expansion doesn't happen in scripts *by default*, but it can
be enabled explicitly.
paul
Paul Jarc wrote:
> Lawrence D'Oliveiro <[EMAIL PROTECTED]> wrote:
>>
>> Chet Ramey wrote:
>>
>>> I already explained that bash follows csh as closely as possible
>>> in its history expansion implementation.
>>
>> Well, it doesn't:
>
> Sure it does ...
I have shown that it doesn't.
> Where they
Lawrence D'Oliveiro <[EMAIL PROTECTED]> wrote:
> Chet Ramey wrote:
>> I already explained that bash follows csh as closely as possible
>> in its history expansion implementation.
>
> Well, it doesn't:
Sure it does: in your examples, bash tries history expansion in
exactly the same cases as tcsh.
