3 ms·

Better yet, set it in .inputrc https://www.reddit.com/r/archlinux/s/cYoHW9h9I0 https://www.reddit.com/r/archlinux/s/cYoHW9h9I0

anotherevan 2y ago
Better still, /etc/inputrc The three lines that go in the top of /etc/inputrc on my boxes: set completion-ignore-case on set editing-mode vi set keymap vi-command For completion, I also set the following in the bottom of /etc/bash.bashrc export EDITOR=vi set -o vi
Aperocky 2y ago
TIL
chasil 2y ago
POSIX specifically calls out "set -o vi" for any and all compliant shells. The .inputrc is specific to readline, and will not be honored by libedit (used extensively on MacOS and BSD-centric systems). "vi: Allow shell command line editing using the built-in vi editor. Enabling vi mode shall disable any other command line editing mode provided as an implementation extension. It need not be possible to set vi mode on for certain block-mode terminals." The standard does not specify an emacs option. https://pubs.opengroup.org/onlinepubs/9699919799/utilities/V3_chap02.html https://pubs.opengroup.org/onlinepubs/9699919799/utilities/V...
- gkfasdfasdf 2y ago
  Bash uses readline, so setting it in .inputrc would be sufficient for bash, but it will also get applied to other apps using readline like gdb. Setting an .inputrc also allows you to configure other niceties like colored-completion-prefix and colored-stats [0]. There's certainly no harm in doing both 'set -o vi' in shell rc and 'set editing-mode vi' in .inputrc [0]: https://wiki.archlinux.org/title/Readline#Colorized_completion https://wiki.archlinux.org/title/Readline#Colorized_completi...
  - chasil 2y ago
    Well, the impact of .inputrc is going to hit anything else linked with it. Your Postgres psql client will switch to vi mode, which might not be what you intended. And if a day comes that dash gets linked to libedit on Debian/Ubuntu, only the POSIX standard command will have the desired effect.

anotherevan 2y ago

Better still, /etc/inputrc The three lines that go in the top of /etc/inputrc on my boxes: set completion-ignore-case on set editing-mode vi set keymap vi-command For completion, I also set the following in the bottom of /etc/bash.bashrc export EDITOR=vi set -o vi

Aperocky 2y ago

TIL

chasil 2y ago

POSIX specifically calls out "set -o vi" for any and all compliant shells. The .inputrc is specific to readline, and will not be honored by libedit (used extensively on MacOS and BSD-centric systems). "vi: Allow shell command line editing using the built-in vi editor. Enabling vi mode shall disable any other command line editing mode provided as an implementation extension. It need not be possible to set vi mode on for certain block-mode terminals." The standard does not specify an emacs option. https://pubs.opengroup.org/onlinepubs/9699919799/utilities/V3_chap02.html https://pubs.opengroup.org/onlinepubs/9699919799/utilities/V...

gkfasdfasdf 2y ago
Bash uses readline, so setting it in .inputrc would be sufficient for bash, but it will also get applied to other apps using readline like gdb. Setting an .inputrc also allows you to configure other niceties like colored-completion-prefix and colored-stats [0]. There's certainly no harm in doing both 'set -o vi' in shell rc and 'set editing-mode vi' in .inputrc [0]: https://wiki.archlinux.org/title/Readline#Colorized_completion https://wiki.archlinux.org/title/Readline#Colorized_completi...
- chasil 2y ago
  Well, the impact of .inputrc is going to hit anything else linked with it. Your Postgres psql client will switch to vi mode, which might not be what you intended. And if a day comes that dash gets linked to libedit on Debian/Ubuntu, only the POSIX standard command will have the desired effect.