Please add these dynamic-complete-history / menu-complete bindings to bash/readline

2009-06-30 Thread Jason A. Spiro
Hi, Bash ships with lots of useful completion functions, but if you don't bind them to keys, then less people will use them. -  In bash's emacs keymap, please bind dynamic-complete-history to M-/, since it's sort of like Emacs's dabbrev-expand -- it looks through the entire buffer (well, actually

Re: bash prompt issue - lenny - UTF-8.

2009-06-30 Thread Chris Jones
On Tue, Jun 30, 2009 at 01:34:21PM EDT, Chet Ramey wrote: > Chris Jones wrote: [..] > > Is there anything that happened between 3.2.39 & 3.2.49 that might > > account for this, or would you suspect a problem with my setup? > > I would assume that one of the patches addresses this problem. It's

Re: bash 4.x filters out environmental variables containing a dot in the name

2009-06-30 Thread Chet Ramey
Stephane CHAZELAS wrote: >> Posix also says that "variables" are inherited from the environment. That >> word has a very specific meaning, as was reiterated during the $@ and set -u >> discussion. The same "variables" language is used when Posix talks about >> creating the environment for shell

Re: feature request: more complete set -e

2009-06-30 Thread Chet Ramey
Marc Weber wrote: > Chet: >> To do otherwise would have made expr much less useful. Idioms such as >> >> var=10 >> while var=`expr $var - 1` >> do >> echo $var >> done > > Mmh I'd use the C like for loop for this which is supported by bash as well. > A relatively recent addition to the

Re: feature request: more complete set -e

2009-06-30 Thread Greg Wooledge
On Tue, Jun 30, 2009 at 09:58:45PM +0200, Marc Weber wrote: > How is this done? > > CHK0="test $? == 0" > my_important_task; $CHK0 || exit 1 You'd need single quotes instead of double there. (And == is illegal in Bourne/POSIX shell test commands; only bash tolerates it.) You could also use a fu

Re: feature request: more complete set -e

2009-06-30 Thread Marc Weber
Greg Wooledge: > If you simply handle errors yourself by checking the return > code from commands that actually matter, you won't have to worry about > all these nasty little surprises. How is this done? CHK0="test $? == 0" my_important_task; $CHK0 || exit 1 Chet: > To do otherwise would have m

Re: bash prompt misbehaving - correction.

2009-06-30 Thread Chet Ramey
Chris Jones wrote: > On Tue, Jun 30, 2009 at 08:30:35AM EDT, Chet Ramey wrote: >> Chris Jones wrote: >>> Not sure whether this is a bug in my version of bash, but I copied over >>> my colored PS1 prompts from debian etch - regular user & root - and some >>> convenient keyboard actions are misbehavi

Re: bash prompt misbehaving - correction.

2009-06-30 Thread Chris Jones
On Tue, Jun 30, 2009 at 08:30:35AM EDT, Chet Ramey wrote: > Chris Jones wrote: > > Not sure whether this is a bug in my version of bash, but I copied over > > my colored PS1 prompts from debian etch - regular user & root - and some > > convenient keyboard actions are misbehaving. After retrieving a

Re: "$@" vs. nounset

2009-06-30 Thread Chet Ramey
Yang Zhang wrote: > (IIRC, in bash, variables set to > empty arrays and unset variables are the same). In the shell, a variable is not set until it has been assigned a value. An array variable is not set unless one of its indices has been assigned a value. -- ``The lyf so short, the craft so lon

Re: bash prompt misbehaving - correction.

2009-06-30 Thread Chet Ramey
Chris Jones wrote: > Not sure whether this is a bug in my version of bash, but I copied over > my colored PS1 prompts from debian etch - regular user & root - and some > convenient keyboard actions are misbehaving. After retrieving a command > from the history via a CTRL-R, an ensuing CTRL-A moves

Re: bash prompt misbehaving - correction.

2009-06-30 Thread Chris Jones
On Tue, Jun 30, 2009 at 05:23:27AM EDT, Bernd Eggink wrote: > Chris Jones schrieb: >> ... > > After retrieving a command >> from the history via a CTRL-R, an ensuing CTRL-A moves the cursor to >> somewhere in the middle of the prompt and CTRL-E is short of the >> retrieved command's end by some ten

Re: bash 4.x filters out environmental variables containing a dot in the name

2009-06-30 Thread Stephane CHAZELAS
2009-06-29, 10:03(-04), Chet Ramey: > >> and it's a bug that bash-4 is filtering them. > > Maybe, maybe not. That's open to interpretation. Here's how I see it. > >> not allowing them to be used in >> the shell is fine (echo ${vmlinux.lds}), but removing them from the >> environment and thus no

Re: bash prompt misbehaving - correction.

2009-06-30 Thread Bernd Eggink
Chris Jones schrieb: ... > After retrieving a command from the history via a CTRL-R, an ensuing CTRL-A moves the cursor to somewhere in the middle of the prompt and CTRL-E is short of the retrieved command's end by some ten characters. ... PS1="\[\033[0;41m\][\$(date +%T)]...@\h:\w]\\$\[\033

bash prompt misbehaving - correction.

2009-06-30 Thread Chris Jones
Not sure whether this is a bug in my version of bash, but I copied over my colored PS1 prompts from debian etch - regular user & root - and some convenient keyboard actions are misbehaving. After retrieving a command from the history via a CTRL-R, an ensuing CTRL-A moves the cursor to somewhere in