Re: inconsistent treatment of backslash-bang

Paul Jarc wrote: > Lawrence D'Oliveiro <[EMAIL PROTECTED]> 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. > > H

Re: inconsistent treatment of backslash-bang

Chet Ramey wrote: > I already explained that bash follows csh as closely as possible > in its history expansion implementation. Well, it doesn't: [EMAIL PROTECTED]:~> /bin/tcsh hypatia /home/ldo> echo hi there!0 0: Event not found. hypatia /home/ldo> echo "hi there!0" 0: Event not found. hypatia

Re: command line vi style editing - is that possible?

ggolub wrote: Hi folks. I am new to bash. I was using korn for long time. One of the feature I really miss is command line vi editing. Here is an example: osql -E -S.

Re: inconsistent treatment of backslash-bang

Lawrence D'Oliveiro wrote: Chet Ramey wrote: Here's the deal. Only single quotes and backslashes quote the history expansion character. Double quotes don't matter ... Then why do they cause a difference in behaviour? Are you being deliberately obtuse? The rest of the message explained th

Re: "[EMAIL PROTECTED]" strings in the web archive

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Bob Proulx on 7/18/2008 10:35 AM: | | Since Nabble generates very annoying behaviors when used to send | messages[1] let me suggest using Gmane instead. | | http://thread.gmane.org/gmane.comp.shells.bash.bugs | | http://thread.gmane.o

command line vi style editing - is that possible?

Hi folks. I am new to bash. I was using korn for long time. One of the feature I really miss is command line vi editing. Here is an example: osql -E -S.

Re: "[EMAIL PROTECTED]" strings in the web archive

Eric Blake wrote: > According to Poor Yorick: > | What's up with all the "[EMAIL PROTECTED]" strings in the web archives for > | bug-bash? For example: > | > | http://lists.gnu.org/archive/html/bug-bash/2008-07/msg00063.html > > It is the gnu mailing archive's list way of protecting email address

Re: inconsistent treatment of backslash-bang

Lawrence D'Oliveiro <[EMAIL PROTECTED]> 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?

Re: removing null elements from an array

On Fri, Jul 18, 2008 at 08:52:47AM -0400, Poor Yorick wrote: > Stephane Chazelas wrote: >> >> In zsh, removing the empty elements is just a matter of >> >> var1=($var1) > > Wouldn't this corrupt the elements with spaces, just as in bash? [...] No, zsh doesn't do word splitting (nor filename genera

Re: "[EMAIL PROTECTED]" strings in the web archive

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Poor Yorick on 7/18/2008 6:50 AM: | What's up with all the "[EMAIL PROTECTED]" strings in the web archives for | bug-bash? For example: | | http://lists.gnu.org/archive/html/bug-bash/2008-07/msg00063.html It is the gnu mailing archive's

Re: removing null elements from an array

Stephane Chazelas wrote: In zsh, removing the empty elements is just a matter of var1=($var1) Wouldn't this corrupt the elements with spaces, just as in bash? -- Yorick

"[EMAIL PROTECTED]" strings in the web archive

What's up with all the "[EMAIL PROTECTED]" strings in the web archives for bug-bash? For example: http://lists.gnu.org/archive/html/bug-bash/2008-07/msg00063.html -- Yorick

Re: removing null elements from an array

On Thu, Jul 17, 2008 at 11:12:47PM +, Poor Yorick wrote: > To get rid of null elements in an array, I currently do something like this: > > bash-3.2$ var1=("with spaces" "more spaces" '' "the end") > bash-3.2$ for v in "[EMAIL PROTECTED]"; do if test "$v"; then > var2+=("$v"); fi; do

Re: inconsistent treatment of backslash-bang

On Friday 18 July 2008 07:35, Lawrence D'Oliveiro 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. On my system, I g