On 6/24/11 1:18 PM, Rui Santos wrote:
> Try this script:
> #!/bin/bash
>
> declare -ax array
> array[$(( $( echo -n 1001 ) - 1001 ))]=1
>
> this will issue an error: line 6: 1001: command not found
>
> If however the script is turned into:
> #!/bin/bash
>
> declare -ax array
> array[$(( `echo
On Fri, Jun 24, 2011 at 06:18:08PM +0100, Rui Santos wrote:
> Try this script:
> #!/bin/bash
>
> declare -ax array
> array[$(( $( echo -n 1001 ) - 1001 ))]=1
>
> this will issue an error: line 6: 1001: command not found
imadev:~$ unset array
imadev:~$ array[$(( $( echo -n 1001 ) - 1001 ))]=1
ima
Hi all,
This is my first post to this mailing list. If I'm doing anything that
is not right, please do let me know.
While upgrading my company's Linux distribution, I also upgrade Bash to
version 4.2-10, and found a glitch, that I consider a BUG. However I
might be doing something wrong. He
http://mywiki.wooledge.org/BashFAQ/105 -- Why doesn't set -e (set -o
errexit) do what I expected?
On 06/24/2011 03:51 AM, Harald Dunkel wrote:
> Hi folks,
>
> A colleague pointed me to this problem: If I run
>
> ( set -e; ( false; echo x ) )
>
> in bash 4.1.5, then there is no screen output, as
> expected. If I change this to
>
> ( set -e; ( false; echo x ) || echo y )
>
> then
Hi folks,
A colleague pointed me to this problem: If I run
( set -e; ( false; echo x ) )
in bash 4.1.5, then there is no screen output, as
expected. If I change this to
( set -e; ( false; echo x ) || echo y )
then I get "x" instead of "y". How comes?
Any helpful comment would
On 6/16/11 3:55 PM, Bradley M. Kuhn wrote:
> Actually, this relates to a thing I'd been looking into recently. My
> bash history is 11MB now, and on some machines I have a noticeable load
> time as it reads the history. I'd thought about adding support for
> incremental read to bash history/read
On Thu, Jun 23, 2011 at 10:49:20AM -0400, Chet Ramey wrote:
> On 5/30/11 2:05 PM, Raphaël Droz wrote:
> > It seems like if gnu.bash@googlegroups.com eat the first occurrence
> > of this email (not in the mailman archives)... second attempt:
> >
> > === Rationale:
> > Let's say you want to comp
