On 12/22/10 3:25 PM, go...@google.com wrote:
> Repeat-By:
> I enter the following commands and get the following results. I am
> intending that the whole string be sent to a remote system where any
> wildcard characters would be evaluated. From below, it appears that
> my w
In this context, "list" represents a syntactic element rather than a
literal variable. If you read the section above, titled "Lists",
you'll see:
Lists
A list is a sequence of one or more pipelines separated by one of the
operators ;, &, &&, or ⎪⎪, and optionally terminated by one
go...@google.com writes:
> I enter the following commands and get the following results. I am
> intending that the whole string be sent to a remote system where any
> wildcard characters would be evaluated. From below, it appears that
> my wildcard characters are being eval
Configuration Information [Automatically generated, do not change]:
Machine: i686
OS: linux-gnu
Compiler: gcc
Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='i686'
-DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='i686-pc-linux-gnu'
-DCONF_VENDOR='pc' -DLOCALEDIR='/usr/share/locale' -DPACKAGE='bash
Configuration Information [Automatically generated, do not change]:
Machine: x86_64
OS: linux-gnu
Compiler: gcc
Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='x86_64'
-DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='x86_64-pc-linux-gnu'
-DCONF_VENDOR='pc' -DLOCALEDIR='/usr/share/locale' -DPACKA
Indeed, it is more compact to report
' a' than
\ \ \ \ \ \ \ \ \ \ a
OK OK... see you next bug.
> > Well anyway, it would be 'no skin off of bash's back' if it just
> > reported what it was given.
It's the difference between what bash reads and its translation to an internal
form based on words. The words are then translated to an external form
with quoting added to make the original and ex
