-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to coubeatczech on 1/31/2009 7:24 AM:
> c...@notas:~$ variable=
> c...@notas:~$ if [ -n $variable ]; then echo true; fi
> true
This is equivalent to 'if [ -n ]; then echo true; fi'; in other words,
because there is only one argument ("-n"),
> Bash versions other than `release' are built with extensive extra arena
> and allocation checking enabled in the bash malloc.
Thanks for pointing this out.
Here are the new results:
Bash 4.0, with bash malloc:
* eval `dircolors`: 0.138s
* source /etc/bash_completion: 0.735s
Bash 4.0, withou
c...@notas:~$ echo $variable
c...@notas:~$ variable=hello
c...@notas:~$ if [ -n $variable ]; then echo true; fi
true
c...@notas:~$ if [ -z $variable ]; then echo true; fi
c...@notas:~$ variable=
c...@notas:~$ if [ -n $variable ]; then echo true; fi
true
c...@notas:~$ if [ -z $variable ]; then ech
Nicolas wrote:
> Hello,
>
> I ran some benchmarks of Bash 4.0-rc1. It is quite impressive! Here are the
> results.
Thanks.
> Bash 4.0, with bash malloc:
> * eval `dircolors`: 0.385s
> * source /etc/bash_completion: 41.651s (around 93% of the time is spent in
> function find_entry of lib/malloc
Hello,
I ran some benchmarks of Bash 4.0-rc1. It is quite impressive! Here are the
results.
My computer is a Pentium M (running at 600 MHz for the test), running Linux
2.6.26 with libc6 version 2.7 and Debian bash-completion version 20080705.
The figures are averages over 100 tests.
Bash 3.2, wit
davide.chiar...@gmail.com wrote:
> hi all,
>
> I'm having a strange problem with my bash setup. I'm using bash 3.2.0
> on ubuntu.
> Basically, I can't type a slash ('/') any way I try.
> If I hit the slash key - nothing. Numeric keypad - nothing. I remapped
> the keyboard to assign that character