Pádraig Brady wrote:
> Original Message
> Date: Tue, 07 Oct 2008 11:55:51 +0100
> From: Pádraig Brady <[EMAIL PROTECTED]>
> To: Chet Ramey <[EMAIL PROTECTED]>
> CC: [EMAIL PROTECTED]
>
> I was just discussing bit shifting with Tim Hockin using shell
> arithmetic expansion, and he
Antonio Macchi wrote:
> $ a=( $'\x7e' $'\x7f' $'\x80' )
>
> $ hexdump -C <(echo -n [EMAIL PROTECTED] )
> 7e 20 01 7f 20 80 |~ .. .|
> 0006
>
>
> bash puts two characters (\x01 and \x7f) instead of only one \x7f
Yes, it's a bug. Thanks for the repor
[EMAIL PROTECTED] wrote:
> 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-unknown-linux-gnu'
> -DCONF_VENDOR='u
pgb wrote:
> What in my environment, post-script-run is making the second source not
> "see" the command line arguments?
Bash doesn't behave as you observe:
$ cat x1
cat > /tmp/x1 <<\EOF
echo source: arguments: "$@"
EOF
. /tmp/x1 -o foo -x bar quux
echo main arguments: "$@"
. /tmp/x1 -o foo -x
pgb schrieb:
I have a bash script that I run using source because I want to be left in the
environment that the script sets up after running the script. The script
takes a few arguments and sets up an environment for me that includes
library paths, classpaths, JAVA_HOME, appends to the PATH, crea
$ a=( $'\x7e' $'\x7f' $'\x80' )
$ hexdump -C <(echo -n [EMAIL PROTECTED] )
7e 20 01 7f 20 80 |~ .. .|
0006
bash puts two characters (\x01 and \x7f) instead of only one \x7f
but...
$ a[1]=$'\x7f'
$ hexdump -C <(echo -n [EMAIL PROTECTED] )
0
