readline expansion: 'cp $v/' -> 'cp \$v/' (no expansion) - why?

2012-07-05 Thread Jason Vas Dias
my #1 bash gripe is that newer versions do not expand command lines containing '$' in emacs readline editing mode. I used to be able to do: $ export SRC=../somedir $ less ${SRC}/ ( meaning press horizontal tab key ) and emacs mode readline would expand, displaying the contents of ../somedir . Now

Re: readline expansion: 'cp $v/' -> 'cp \$v/' (no expansion) - why?

2012-07-05 Thread Eric Blake
On 07/05/2012 04:58 AM, Jason Vas Dias wrote: > Now it changes the input string into > 'less \$SRC/' and prevents tab expansion > as would be done without use of any variables. > Would anyone know how to restore the old behavior > with bash 4.2.2 + readline 6.2 (linux ubuntu 12.04) ? Yep - upgrad

Re: readline expansion: 'cp $v/' -> 'cp \$v/' (no expansion) - why?

2012-07-05 Thread Jason Vas Dias
hi Eric - thanks for your response, but bash-4.2.29(2), just built from latest patches from gnu on x86_64 ubuntu, does NOT "restore the old behavior" , but now refuses to tab-expand at all - 'cat $SRC/' on the command line still produces no output. Is there some option I need to give to enable it

Re: readline expansion: 'cp $v/' -> 'cp \$v/' (no expansion) - why?

2012-07-05 Thread Chet Ramey
On 7/5/12 7:59 AM, Jason Vas Dias wrote: > hi Eric - thanks for your response, but bash-4.2.29(2), just built from > latest patches from gnu on x86_64 ubuntu, does NOT > "restore the old behavior" , but now refuses to tab-expand at > all - 'cat $SRC/' on the command line still produces no > output

Re: Doc of "set -e" should mention non-locality

2012-07-05 Thread Dan Douglas
On Wednesday, July 04, 2012 05:37:25 PM Rainer Blome wrote: > Original-Nachricht > > Datum: Fri, 29 Jun 2012 18:03:13 -0500 > > Von: Dan Douglas > > An: bug-bash@gnu.org > > CC: Rainer Blome > > Remember that my main suggestion is to clearly document the intended > behavior (se

Re: Doc of "set -e" should mention non-locality

2012-07-05 Thread Chet Ramey
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 7/5/12 11:55 AM, Dan Douglas wrote: >> Remember that my main suggestion is to clearly document the intended >> behavior (see the subject). This could mean to add a generic >> paragraph to the documentation of "set" that describes the scope >> and e