Re: [Bug-readline] Confused about the behaviour of bind-tty-special-chars

[Richard Michael]

On Tue, Sep 13, 2011 at 3:01 PM, Chet Ramey <address@hidden> wrote:
> On 9/12/11 4:36 PM, Richard Michael wrote:
>
>>> For kicks, I installed bash-4.2.10 and readline-6.2 on my Mac OS X 10.6.8
>>> system, and ran bash.  I didn't test extensively, but the basic emacs
>>> mode movement commands worked fine (C-a, C-e, C-f, C-b, M-f, M-b, etc.).
>>
>> Ok, thank you for investigating, confirmation appreciated.  How did
>> you install?  I'd like to try the same method.
>
> Pretty much standard: port fetch, port build, port install.
>
>> Here, bash readline bindings appear to be 'vi-insert', but I am not
>> doing this in
>> ~/.inputrc.  I am investigating my local configuration (conf files,
>> macports, etc.) ; most of which I did not produce myself.
>>
>> $ bind -V | grep keymap
>> keymap is set to `vi-insert'
>
> You're probably executing a `set -o vi' somewhere in your startup files.
> You can fix it temporarily by running `set -o emacs' while you search
> for that command.

Yes, found ; quite embarrassing.  Thank you for the hint.  In my focus
on "bind", I'd forgotten "set".

Although now disabled, it seems best to "set editing-mode .." via
~/.inputrc to keep readline configuration in one place.


Thank you for your patience, I did learn quite a bit!


Regards,
Richard