On Tue, Sep 6, 2011 at 10:23 PM, Chet Ramey <[email protected]> wrote: > On 9/4/11 4:00 AM, Richard Michael wrote: > >> Thank you very much for quick reply and clear explanation. Is there a >> list of these defaults (or, which source file contains them)? I offer >> to contribute them to the manual. (Did I miss it?) > > The default emacs-mode key bindings appear in the manual with the > description of the function to which they're bound. For example: > > beginning-of-line (C-a) > Move to the start of the current line. > end-of-line (C-e) > Move to the end of the line. > forward-char (C-f) > Move forward a character. > backward-char (C-b) > Move back a character. > > The default vi-mode commands are the traditional bindings as defined by, > e.g., Posix: > > http://pubs.opengroup.org/onlinepubs/9699919799/utilities/sh.html#tag_20_117_13_03 > >> Regarding default bindings, the manual indicates many "defaults", ex. >> \C-a beginning-of-line. These do not work out-of-the-box on my >> readline, I've had to add them to an inputrc. How should I understand >> "default" in the documentation: "configured by the inputrc which ships >> with the readline library and may therefore be broken by a vendor on >> your system", or, "hard coded in readline" (such as above, \C-u >> unix-line-discard and \e[H beginning-of-line, etc.)? > > They appear in readline's source (emacs_keymap.c, vi_keymap.c).
Thank you. > 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. 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' This is clearly no longer "bug" related. Is this too specific an issue for the mailing list? Thank you, Richard _______________________________________________ Bug-readline mailing list [email protected] https://lists.gnu.org/mailman/listinfo/bug-readline
