Re: mapfile callback

2009-07-19 Thread Chris F.A. Johnson
On Mon, 20 Jul 2009, Pierre Gaston wrote: On Mon, Jul 20, 2009 at 5:46 AM, Chris F.A. Johnson wrote: On Sun, 19 Jul 2009, Chet Ramey wrote: Chris F.A. Johnson wrote: mapfile callback code is executed in a subshell. It's not. It's executed in the same context as an `eval' or a trap

Re: mapfile callback

2009-07-19 Thread Pierre Gaston
On Mon, Jul 20, 2009 at 5:46 AM, Chris F.A. Johnson wrote: > On Sun, 19 Jul 2009, Chet Ramey wrote: > > Chris F.A. Johnson wrote: >> >>> >>> mapfile callback code is executed in a subshell. >>> >> >> It's not. It's executed in the same context as an `eval' or a trap >> command. >> > > So it

Re: Prompt length calculation fails when UTF-8 is used within \[ \]

2009-07-19 Thread Chet Ramey
Lasse Kärkkäinen wrote: > Steps to reproduce: (using UTF-8 locales) > > $ export PS1="\[\e]2;test Ä and Ö here\a\]prompt>" > prompt>abcdefgh# Enter some alphabets and press Home > ^ Cursor goes here, instead of >^ here where it should go. > > Add more UTF-8 letters as non-printab

Re: mapfile callback

2009-07-19 Thread Chris F.A. Johnson
On Sun, 19 Jul 2009, Chet Ramey wrote: Chris F.A. Johnson wrote: mapfile callback code is executed in a subshell. It's not. It's executed in the same context as an `eval' or a trap command. So it is. Great! I wonder what I was doing wrong before. -- Chris F.A. Johnson

Re: Setting READLINE_POINT isn't always applied (4.0.24)

2009-07-19 Thread Chet Ramey
Henning Bekel wrote: > Hello, > If I try to change READLINE_LINE and READLINE_POINT from a > function bound via bind -x, then setting READLINE_POINT is not > applied every second time I invoke the function. Instead, the > cursor is placed at the end of the line. > > Simple test case: > > test_

Re: mapfile callback

2009-07-19 Thread Chet Ramey
Chris F.A. Johnson wrote: > >mapfile callback code is executed in a subshell. It's not. It's executed in the same context as an `eval' or a trap command. Chet -- ``The lyf so short, the craft so long to lerne.'' - Chaucer Chet Ramey, ITS, CWRUc...@case.eduhttp://cnswww.cns.cwru.e

Re: printf -v doesn't allow array assignment

2009-07-19 Thread Chet Ramey
Chris F.A. Johnson wrote: > > $ printf -v q[2] "%s" "$RANDOM" > bash: printf: `q[2]': not a valid identifier > > > I know I can work around it with a temporary variable, but it > would be nice if it could be done in a single step. That could be a useful extension. It will probably find

Re: bash 4: source does not search current dir

2009-07-19 Thread Chet Ramey
Denys Vlasenko wrote: > Hi, > > I assume . command does not search current directory anymore > in bash 4 for a reason. Perhaps it is specified by relevant > standard, although I did not find it. > > This incompatible change affects me a lot. I imagine > I am not alone with this. This happens onl

Re: echo "-e" produces no outputs

2009-07-19 Thread Chet Ramey
Stephane CHAZELAS wrote: > 2009-07-17, 13:09(-06), Eric Blake: >> According to Huang Tao on 7/17/2009 9:46 AM: >>> I'm not sure whether it is a bug >>> how can i echo the text string "-e" barely ( or "-n", "-E") >>> i tried >>> $echo "-e" >>> $echo '-e' >>> and some other inputs, all of which produ

Re: 3-lines long segfault

2009-07-19 Thread Chet Ramey
Marc Herbert wrote: > The following script crashes bash versions 2.05, 3.2.25, 4.0.16,... > > > trap "echo USR1caught" USR1 > read -t 1 > foo=$( kill -USR1 $$ ) > echo 'Yeah! no Segmentation fault!' Thanks for the report. Fixed in the next version. Chet -- ``The lyf so short, the craft so lon