Re: `history -r` can not read from /dev/stdin ?

2012-08-17 Thread Techlive Zheng
2012/8/17 郑文辉(Techlive Zheng) : > 2012/8/17 Chet Ramey : >> On 8/16/12 10:11 PM, 郑文辉(Techlive Zheng) wrote: >>> 2012/8/17 Chet Ramey : On 8/16/12 9:17 AM, 郑文辉(Techlive Zheng) wrote: > I was trying to reload the bash history file which changed by another > bash session with the followin

Re: `history -r` can not read from /dev/stdin ?

2012-08-17 Thread Techlive Zheng
2012/8/17 郑文辉(Techlive Zheng) : > 2012/8/17 郑文辉(Techlive Zheng) : >> 2012/8/17 Chet Ramey : >>> On 8/16/12 10:11 PM, 郑文辉(Techlive Zheng) wrote: 2012/8/17 Chet Ramey : > On 8/16/12 9:17 AM, 郑文辉(Techlive Zheng) wrote: >> I was trying to reload the bash history file which changed by anoth

Bash 4.1 doesn't behave as I think it should: arrays and the environment

2012-08-17 Thread John Summerfield
GNU bash, version 4.1.2(1)-release (x86_64-redhat-linux-gnu) Copyright (C) 2009 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later This is free software; you are free to change and redistribute it. There is NO WARRANTY, to the extent per

Re: Bash 4.1 doesn't behave as I think it should: arrays and the environment

2012-08-17 Thread Greg Wooledge
On Fri, Aug 17, 2012 at 03:19:56PM +0800, John Summerfield wrote: > In two cases I wish to pass an array in the environment, like so: > 14:28 john@Boomer$ STUFF[1]=one STUFFX=stuffx env | grep ^ST > STUFFX=stuffx > STUFF[1]=one You are creating an environment variable called "STUFF[1]". This is a

`bash --debugger` in interactive mode

2012-08-17 Thread Techlive Zheng
I happened to have `shopt -s extdebug` in my .bashrc recently. After a new bash session started, I got the following output. bash debugger, bashdb, release 4.2-0.8 Copyright 2002, 2003, 2004, 2006, 2007, 2008, 2009, 2010, 2011 Rocky Bernstein This is free software, covered by the GNU