Why does my terminal require pressing the up key twice to move backwards in history?
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}
If I press up or down in terminal, be it xterm, a virtual console or kitty, without any custom bashrc or inputrc, via ssh or locally:
After a return, the next line in my history is shown, but otherwise it takes two presses to show the next item.
This also occures with k and j, mapped via readline to history-search-backwards.
terminal
asked Feb 2 at 8:52
BlueDrink9BlueDrink9
336111
add a comment |
If I press up or down in terminal, be it xterm, a virtual console or kitty, without any custom bashrc or inputrc, via ssh or locally:
After a return, the next line in my history is shown, but otherwise it takes two presses to show the next item.
This also occures with k and j, mapped via readline to history-search-backwards.
terminal
asked Feb 2 at 8:52
BlueDrink9BlueDrink9
336111
add a comment |
If I press up or down in terminal, be it xterm, a virtual console or kitty, without any custom bashrc or inputrc, via ssh or locally:
After a return, the next line in my history is shown, but otherwise it takes two presses to show the next item.
This also occures with k and j, mapped via readline to history-search-backwards.
terminal
asked Feb 2 at 8:52
BlueDrink9BlueDrink9
336111
If I press up or down in terminal, be it xterm, a virtual console or kitty, without any custom bashrc or inputrc, via ssh or locally:
After a return, the next line in my history is shown, but otherwise it takes two presses to show the next item.
This also occures with k and j, mapped via readline to history-search-backwards.
terminal
terminal
asked Feb 2 at 8:52
BlueDrink9BlueDrink9
336111
asked Feb 2 at 8:52
BlueDrink9BlueDrink9
336111
asked Feb 2 at 8:52
BlueDrink9BlueDrink9
336111
asked Feb 2 at 8:52
BlueDrink9BlueDrink9
336111
asked Feb 2 at 8:52
BlueDrink9BlueDrink9
336111
336111
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
Figured it out. The problem was there was no problem. History search was working as expected. It was just searching a history where every item was duplicated. This was some code in my bashrc that had been synced across to the ssh server too.
Moral of the story: check assumptions, check the files you think you're reading
answered Feb 2 at 10:07
BlueDrink9BlueDrink9
336111
add a comment |
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',
autoActivateHeartbeat: false,
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%2f1401268%2fwhy-does-my-terminal-require-pressing-the-up-key-twice-to-move-backwards-in-hist%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
Figured it out. The problem was there was no problem. History search was working as expected. It was just searching a history where every item was duplicated. This was some code in my bashrc that had been synced across to the ssh server too.
Moral of the story: check assumptions, check the files you think you're reading
answered Feb 2 at 10:07
BlueDrink9BlueDrink9
336111
add a comment |
Figured it out. The problem was there was no problem. History search was working as expected. It was just searching a history where every item was duplicated. This was some code in my bashrc that had been synced across to the ssh server too.
Moral of the story: check assumptions, check the files you think you're reading
answered Feb 2 at 10:07
BlueDrink9BlueDrink9
336111
add a comment |
Figured it out. The problem was there was no problem. History search was working as expected. It was just searching a history where every item was duplicated. This was some code in my bashrc that had been synced across to the ssh server too.
Moral of the story: check assumptions, check the files you think you're reading
answered Feb 2 at 10:07
BlueDrink9BlueDrink9
336111
Figured it out. The problem was there was no problem. History search was working as expected. It was just searching a history where every item was duplicated. This was some code in my bashrc that had been synced across to the ssh server too.
Moral of the story: check assumptions, check the files you think you're reading
answered Feb 2 at 10:07
BlueDrink9BlueDrink9
336111
answered Feb 2 at 10:07
BlueDrink9BlueDrink9
336111
answered Feb 2 at 10:07
BlueDrink9BlueDrink9
336111
answered Feb 2 at 10:07
BlueDrink9BlueDrink9
336111
336111
add a comment |
add a comment |
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.
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%2f1401268%2fwhy-does-my-terminal-require-pressing-the-up-key-twice-to-move-backwards-in-hist%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
