Many thanks for the explanation. I've just updated bashdb CVS to add an edit
style (emacs/vi) and which will give more complete readline handling in
entering debugger commands.
There still is some weirdness in how history retrieval works, but I need to
isolate what's going on there.
And it looks like in bash 4.0 alpha there is a problem regaring this
particular case.
It would be really great to note somewhere in the "bind" and "read" builtin
sections (if not also under "set' and "emacs and 'vi" that there is some
interaction between these settings and how the bind and read builtins work.
If you want me to suggest some text, I'd be happy to.
Thanks again.
On Thu, Sep 11, 2008 at 9:29 AM, Chet Ramey <[EMAIL PROTECTED]> wrote:
> rocky wrote:
> > The most recent bash docs say this about builtin function read with
> > option -e:
> >
> > Readline (@pxref{Command Line Editing}) is used to obtain the line.
> >
> > Consider this little program:
> >
> > PS4='-$LINENO: $? $ '
> > set -x
> > builtin bind '"\C-x\C-r": "bind completion"'
> > builtin bind -P
> > while read -e -p 'huh? ' line ; do
> > echo $line
> > done
>
> Things will work as you expect with bash-3.2 if you enable line editing
> before attempting to run `bind'. `set -o emacs' will do the job.
>
> Chet
>
> --
> ``The lyf so short, the craft so long to lerne.'' - Chaucer
>
> Chet Ramey, ITS, CWRU [EMAIL PROTECTED]
> http://cnswww.cns.cwru.edu/~chet/ <http://cnswww.cns.cwru.edu/%7Echet/>
>
