Re: What exactly does "read -e" do? bind weirdnesses

[Rocky Bernstein]

You are correct, here is no problem in bash-4.0 alpha. My apologies.

An error message when bind is used and line editing is not enabled would
help.

Alas, I suspect many will not try to use bind but still use "read" or
perhaps a set +o emacs and subsequently expecting some of default key
bindings which no longer are in effect. I threw in the bind command just to
try to help me see what was going on.

On Thu, Sep 11, 2008 at 11:36 AM, Chet Ramey <chet.ramey@case.edu> wrote:

> Rocky Bernstein wrote:
> > 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.
>
> Actually, I tested in bash-4.0 and got the right results before I tried
> bash-3.2.  What are you seeing?
>
> > 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.
>
> The thing that would probably have done the most good is an error message:
> (bind: line editing not enabled).
>
> Chet
> --
> ``The lyf so short, the craft so long to lerne.'' - Chaucer
>
> Chet Ramey, ITS, CWRU    chet@case.edu
> http://cnswww.cns.cwru.edu/~chet/ <http://cnswww.cns.cwru.edu/%7Echet/>
>