| Subject: | Re: inconsistent treatment of backslash-bang |
|---|---|
| From: | Lawrence D'Oliveiro <ldo@xxxxxxxxxxxxxxxxxxx> |
| Date: | Sat, 19 Jul 2008 17:29:37 +1200 |
| Newsgroups: | gnu.bash.bug |
Paul Jarc wrote: > Lawrence D'Oliveiro <ldo@xxxxxxxxxxxxxxxxxxx> wrote: >> pk wrote: >>> This is documented in man bash, and only happens in interactive shells (not >>> scripts). >> >> I just tried putting my six cases into a script, and I get exactly the same >> sort of output as interactively. > > How did you invoke the script? If you do ". ./script", then the > script commands are being run in the interactive shell, so you'll get > the same behavior as if you typed them directly. "./script" will run > those commands in a new, non-interactive shell. I spoke too soon... ldo@theon:hack> cat shriek_try #!/bin/bash echo "hi there!0" echo "hi there\!0" echo hi there\!0 echo "hi there$0" echo "hi there\$0" echo hi there\$0 ldo@theon:hack> ./shriek_try hi there!0 hi there\!0 hi there!0 hi there./shriek_try hi there$0 hi there$0 |
| Previous by Date: | Re: inconsistent treatment of backslash-bang, Lawrence D'Oliveiro |
|---|---|
| Next by Date: | Re: setuid from shellscript isn't permanent, Chet Ramey |
| Previous by Thread: | Re: inconsistent treatment of backslash-bang, Lawrence D'Oliveiro |
| Next by Thread: | Re: inconsistent treatment of backslash-bang, Paul Jarc |
| Indexes: | [Date] [Thread] [Top] [All Lists] |