.inputrc bindings sporadically not working
up vote
0
down vote
favorite
I have the following entries in my ~/.inputrc file:
"e[A": history-search-backward
"e[B": history-search-forward
Normally, this works fine. For example, if I type 'ss' then press up or down, I can scroll through all commands in my history that start with 'ss' (such as ssh logins).
However, sometimes I log into my server and these bindings do not work. When I type 'ss' and press up, it instead scrolls through my bash history normally, instead of matching based on the letters I typed.
I tried all the methods described here to try and reload the .inputrc file to re-enable these bindings, but it does not work. Logging out and logging back in does not work. Starting a new bash shell in a new terminal window, or from within the current session, does not work. Pressing 'Control-x', 'Control-r' does not work. The .inputrc bindings refuse to work again, until some random time in the future when in a new session (or maybe the current session?) they decide to start working again. This has been going on for years and I've just lived with it, but it would be nice to figure out what is causing it to stop working, and how to get it to start working again.
The systems I use include:
Mac computers running macOS 10.10 - 10.12, running iTerm2
RHEL 7 servers (logged in from the Mac)
Centos 6 servers (logged in from the Mac)
bash readline inputrc
asked Dec 5 at 16:48
user5359531
1214
add a comment |
up vote
0
down vote
favorite
I have the following entries in my ~/.inputrc file:
"e[A": history-search-backward
"e[B": history-search-forward
Normally, this works fine. For example, if I type 'ss' then press up or down, I can scroll through all commands in my history that start with 'ss' (such as ssh logins).
However, sometimes I log into my server and these bindings do not work. When I type 'ss' and press up, it instead scrolls through my bash history normally, instead of matching based on the letters I typed.
I tried all the methods described here to try and reload the .inputrc file to re-enable these bindings, but it does not work. Logging out and logging back in does not work. Starting a new bash shell in a new terminal window, or from within the current session, does not work. Pressing 'Control-x', 'Control-r' does not work. The .inputrc bindings refuse to work again, until some random time in the future when in a new session (or maybe the current session?) they decide to start working again. This has been going on for years and I've just lived with it, but it would be nice to figure out what is causing it to stop working, and how to get it to start working again.
The systems I use include:
Mac computers running macOS 10.10 - 10.12, running iTerm2
RHEL 7 servers (logged in from the Mac)
Centos 6 servers (logged in from the Mac)
bash readline inputrc
asked Dec 5 at 16:48
user5359531
1214
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I have the following entries in my ~/.inputrc file:
"e[A": history-search-backward
"e[B": history-search-forward
Normally, this works fine. For example, if I type 'ss' then press up or down, I can scroll through all commands in my history that start with 'ss' (such as ssh logins).
However, sometimes I log into my server and these bindings do not work. When I type 'ss' and press up, it instead scrolls through my bash history normally, instead of matching based on the letters I typed.
I tried all the methods described here to try and reload the .inputrc file to re-enable these bindings, but it does not work. Logging out and logging back in does not work. Starting a new bash shell in a new terminal window, or from within the current session, does not work. Pressing 'Control-x', 'Control-r' does not work. The .inputrc bindings refuse to work again, until some random time in the future when in a new session (or maybe the current session?) they decide to start working again. This has been going on for years and I've just lived with it, but it would be nice to figure out what is causing it to stop working, and how to get it to start working again.
The systems I use include:
Mac computers running macOS 10.10 - 10.12, running iTerm2
RHEL 7 servers (logged in from the Mac)
Centos 6 servers (logged in from the Mac)
bash readline inputrc
asked Dec 5 at 16:48
user5359531
1214
I have the following entries in my ~/.inputrc file:
"e[A": history-search-backward
"e[B": history-search-forward
Normally, this works fine. For example, if I type 'ss' then press up or down, I can scroll through all commands in my history that start with 'ss' (such as ssh logins).
However, sometimes I log into my server and these bindings do not work. When I type 'ss' and press up, it instead scrolls through my bash history normally, instead of matching based on the letters I typed.
I tried all the methods described here to try and reload the .inputrc file to re-enable these bindings, but it does not work. Logging out and logging back in does not work. Starting a new bash shell in a new terminal window, or from within the current session, does not work. Pressing 'Control-x', 'Control-r' does not work. The .inputrc bindings refuse to work again, until some random time in the future when in a new session (or maybe the current session?) they decide to start working again. This has been going on for years and I've just lived with it, but it would be nice to figure out what is causing it to stop working, and how to get it to start working again.
The systems I use include:
Mac computers running macOS 10.10 - 10.12, running iTerm2
RHEL 7 servers (logged in from the Mac)
Centos 6 servers (logged in from the Mac)
bash readline inputrc
bash readline inputrc
asked Dec 5 at 16:48
user5359531
1214
asked Dec 5 at 16:48
user5359531
1214
asked Dec 5 at 16:48
user5359531
1214
asked Dec 5 at 16:48
user5359531
1214
asked Dec 5 at 16:48
user5359531
1214
1214
add a comment |
add a comment |
active
oldest
votes
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
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: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
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%2fsuperuser.com%2fquestions%2f1381065%2finputrc-bindings-sporadically-not-working%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Super User!
- 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%2fsuperuser.com%2fquestions%2f1381065%2finputrc-bindings-sporadically-not-working%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
