Bash's “set -o vi” vs readline's own options?
Clash Royale CLAN TAG#URR8PPP
up vote
1
down vote
favorite
I know there is, for readline,
set editing-mode vi
You can put the above option in ~/.inputrc, editing-mode is documented by Readline as
editing-mode(emacs) Controls whether readline begins with a set of key bindings similar toemacsorvi.editing-modecan be set to eitheremacsorvi.
There is also, for Bash,
set -o vi
According to the Bash documents
viUse a vi-style line editing interface. This also affects the editing interface used for read -e.
Does Bash's -o vi do anything other than set the appropriate Readline mode? And, if you've already got editing-mode set in your ~/.inputrc does this do anything differently?
bash inputrc vi-mode
asked Dec 4 at 4:28
Evan Carroll
5,02494178
add a comment |
up vote
1
down vote
favorite
I know there is, for readline,
set editing-mode vi
You can put the above option in ~/.inputrc, editing-mode is documented by Readline as
editing-mode(emacs) Controls whether readline begins with a set of key bindings similar toemacsorvi.editing-modecan be set to eitheremacsorvi.
There is also, for Bash,
set -o vi
According to the Bash documents
viUse a vi-style line editing interface. This also affects the editing interface used for read -e.
Does Bash's -o vi do anything other than set the appropriate Readline mode? And, if you've already got editing-mode set in your ~/.inputrc does this do anything differently?
bash inputrc vi-mode
asked Dec 4 at 4:28
Evan Carroll
5,02494178
add a comment |
up vote
1
down vote
favorite
up vote
1
down vote
favorite
I know there is, for readline,
set editing-mode vi
You can put the above option in ~/.inputrc, editing-mode is documented by Readline as
editing-mode(emacs) Controls whether readline begins with a set of key bindings similar toemacsorvi.editing-modecan be set to eitheremacsorvi.
There is also, for Bash,
set -o vi
According to the Bash documents
viUse a vi-style line editing interface. This also affects the editing interface used for read -e.
Does Bash's -o vi do anything other than set the appropriate Readline mode? And, if you've already got editing-mode set in your ~/.inputrc does this do anything differently?
bash inputrc vi-mode
asked Dec 4 at 4:28
Evan Carroll
5,02494178
I know there is, for readline,
set editing-mode vi
You can put the above option in ~/.inputrc, editing-mode is documented by Readline as
editing-mode(emacs) Controls whether readline begins with a set of key bindings similar toemacsorvi.editing-modecan be set to eitheremacsorvi.
There is also, for Bash,
set -o vi
According to the Bash documents
viUse a vi-style line editing interface. This also affects the editing interface used for read -e.
Does Bash's -o vi do anything other than set the appropriate Readline mode? And, if you've already got editing-mode set in your ~/.inputrc does this do anything differently?
bash inputrc vi-mode
bash inputrc vi-mode
asked Dec 4 at 4:28
Evan Carroll
5,02494178
asked Dec 4 at 4:28
Evan Carroll
5,02494178
asked Dec 4 at 4:28
Evan Carroll
5,02494178
asked Dec 4 at 4:28
Evan Carroll
5,02494178
asked Dec 4 at 4:28
Evan Carroll
5,02494178
5,02494178
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
up vote
4
down vote
The two are identical.
Doing set -o vi in an interactive bash shell calls the set builtin. The C code for the set builtin calls rl_variable_bind("editing-mode", option_name) (where option_name will be vi) which is the Readline library function that sets the command line editing mode.
Setting the command line editing mode on the command line with set -o would override the corresponding setting configured in ~/.inputrc.
answered Dec 4 at 6:56
Kusalananda
119k16225367
add a comment |
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "106"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f485818%2fbashs-set-o-vi-vs-readlines-own-options%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
4
down vote
The two are identical.
Doing set -o vi in an interactive bash shell calls the set builtin. The C code for the set builtin calls rl_variable_bind("editing-mode", option_name) (where option_name will be vi) which is the Readline library function that sets the command line editing mode.
Setting the command line editing mode on the command line with set -o would override the corresponding setting configured in ~/.inputrc.
answered Dec 4 at 6:56
Kusalananda
119k16225367
add a comment |
up vote
4
down vote
The two are identical.
Doing set -o vi in an interactive bash shell calls the set builtin. The C code for the set builtin calls rl_variable_bind("editing-mode", option_name) (where option_name will be vi) which is the Readline library function that sets the command line editing mode.
Setting the command line editing mode on the command line with set -o would override the corresponding setting configured in ~/.inputrc.
answered Dec 4 at 6:56
Kusalananda
119k16225367
add a comment |
up vote
4
down vote
up vote
4
down vote
The two are identical.
Doing set -o vi in an interactive bash shell calls the set builtin. The C code for the set builtin calls rl_variable_bind("editing-mode", option_name) (where option_name will be vi) which is the Readline library function that sets the command line editing mode.
Setting the command line editing mode on the command line with set -o would override the corresponding setting configured in ~/.inputrc.
answered Dec 4 at 6:56
Kusalananda
119k16225367
The two are identical.
Doing set -o vi in an interactive bash shell calls the set builtin. The C code for the set builtin calls rl_variable_bind("editing-mode", option_name) (where option_name will be vi) which is the Readline library function that sets the command line editing mode.
Setting the command line editing mode on the command line with set -o would override the corresponding setting configured in ~/.inputrc.
answered Dec 4 at 6:56
Kusalananda
119k16225367
edited Dec 4 at 23:28
answered Dec 4 at 6:56
Kusalananda
119k16225367
answered Dec 4 at 6:56
Kusalananda
119k16225367
answered Dec 4 at 6:56
Kusalananda
119k16225367
119k16225367
add a comment |
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f485818%2fbashs-set-o-vi-vs-readlines-own-options%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown