How do I control when bash auto-completion shows a paged list of completions?
In my previous linux installations the bash auto-completion has always worked without problems. If I wanted to do anything to files, giving a prefix of the filename and pressing tabulator listed all that matched the prefix but it also repeated the prompt below it with my command and prefix, so that I could immediately continue typing.
Now I have updated my system to kubuntu 18.04 and the auto-completion doesn't work as fluently anymore. What is even stranger, the behaviour is unpredictable like it depended on the konsole. If the command is less, it works always correctly (as described above), but if the command is cp or mv, the behaviour varies. Sometimes it works correctly, but often it shows a list of matching files with more (hiding my prompt) and I have to type q to exit more and be able to continue. A small thing, but annoying since it requires extra typing.
I see that .bashrc calls /usr/share/bash-completion/bash_completion
but I haven't done any changes to this.
Question: What causes this unpredictable behaviour? How can I fix it?
command-line bash kubuntu auto-completion konsole
edited Dec 24 '18 at 8:41
Mr Shunz
2,1901922
asked Nov 26 '18 at 17:57
whamalai
1266
add a comment |
In my previous linux installations the bash auto-completion has always worked without problems. If I wanted to do anything to files, giving a prefix of the filename and pressing tabulator listed all that matched the prefix but it also repeated the prompt below it with my command and prefix, so that I could immediately continue typing.
Now I have updated my system to kubuntu 18.04 and the auto-completion doesn't work as fluently anymore. What is even stranger, the behaviour is unpredictable like it depended on the konsole. If the command is less, it works always correctly (as described above), but if the command is cp or mv, the behaviour varies. Sometimes it works correctly, but often it shows a list of matching files with more (hiding my prompt) and I have to type q to exit more and be able to continue. A small thing, but annoying since it requires extra typing.
I see that .bashrc calls /usr/share/bash-completion/bash_completion
but I haven't done any changes to this.
Question: What causes this unpredictable behaviour? How can I fix it?
command-line bash kubuntu auto-completion konsole
edited Dec 24 '18 at 8:41
Mr Shunz
2,1901922
asked Nov 26 '18 at 17:57
whamalai
1266
add a comment |
In my previous linux installations the bash auto-completion has always worked without problems. If I wanted to do anything to files, giving a prefix of the filename and pressing tabulator listed all that matched the prefix but it also repeated the prompt below it with my command and prefix, so that I could immediately continue typing.
Now I have updated my system to kubuntu 18.04 and the auto-completion doesn't work as fluently anymore. What is even stranger, the behaviour is unpredictable like it depended on the konsole. If the command is less, it works always correctly (as described above), but if the command is cp or mv, the behaviour varies. Sometimes it works correctly, but often it shows a list of matching files with more (hiding my prompt) and I have to type q to exit more and be able to continue. A small thing, but annoying since it requires extra typing.
I see that .bashrc calls /usr/share/bash-completion/bash_completion
but I haven't done any changes to this.
Question: What causes this unpredictable behaviour? How can I fix it?
command-line bash kubuntu auto-completion konsole
edited Dec 24 '18 at 8:41
Mr Shunz
2,1901922
asked Nov 26 '18 at 17:57
whamalai
1266
In my previous linux installations the bash auto-completion has always worked without problems. If I wanted to do anything to files, giving a prefix of the filename and pressing tabulator listed all that matched the prefix but it also repeated the prompt below it with my command and prefix, so that I could immediately continue typing.
Now I have updated my system to kubuntu 18.04 and the auto-completion doesn't work as fluently anymore. What is even stranger, the behaviour is unpredictable like it depended on the konsole. If the command is less, it works always correctly (as described above), but if the command is cp or mv, the behaviour varies. Sometimes it works correctly, but often it shows a list of matching files with more (hiding my prompt) and I have to type q to exit more and be able to continue. A small thing, but annoying since it requires extra typing.
I see that .bashrc calls /usr/share/bash-completion/bash_completion
but I haven't done any changes to this.
Question: What causes this unpredictable behaviour? How can I fix it?
command-line bash kubuntu auto-completion konsole
command-line bash kubuntu auto-completion konsole
edited Dec 24 '18 at 8:41
Mr Shunz
2,1901922
asked Nov 26 '18 at 17:57
whamalai
1266
edited Dec 24 '18 at 8:41
Mr Shunz
2,1901922
asked Nov 26 '18 at 17:57
whamalai
1266
edited Dec 24 '18 at 8:41
Mr Shunz
2,1901922
edited Dec 24 '18 at 8:41
Mr Shunz
2,1901922
edited Dec 24 '18 at 8:41
Mr Shunz
2,1901922
2,1901922
asked Nov 26 '18 at 17:57
whamalai
1266
asked Nov 26 '18 at 17:57
whamalai
1266
asked Nov 26 '18 at 17:57
whamalai
1266
1266
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
The reason turned out to be very simple: If the terminal is sufficiently large, auto-completion can show all alternatives above the prompt (on two columns), but if it is too small, it uses more. So, the trick is to use sufficiently large terminals.
For some reason, I had not encountered this in my previous installations, maybe due to larger terminals/smaller font. With less, everything worked well, because there were fewer alternatives and they fitted the terminal.
answered Nov 26 '18 at 18:40
whamalai
1266
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
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%2faskubuntu.com%2fquestions%2f1096251%2fhow-do-i-control-when-bash-auto-completion-shows-a-paged-list-of-completions%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
The reason turned out to be very simple: If the terminal is sufficiently large, auto-completion can show all alternatives above the prompt (on two columns), but if it is too small, it uses more. So, the trick is to use sufficiently large terminals.
For some reason, I had not encountered this in my previous installations, maybe due to larger terminals/smaller font. With less, everything worked well, because there were fewer alternatives and they fitted the terminal.
answered Nov 26 '18 at 18:40
whamalai
1266
add a comment |
The reason turned out to be very simple: If the terminal is sufficiently large, auto-completion can show all alternatives above the prompt (on two columns), but if it is too small, it uses more. So, the trick is to use sufficiently large terminals.
For some reason, I had not encountered this in my previous installations, maybe due to larger terminals/smaller font. With less, everything worked well, because there were fewer alternatives and they fitted the terminal.
answered Nov 26 '18 at 18:40
whamalai
1266
add a comment |
The reason turned out to be very simple: If the terminal is sufficiently large, auto-completion can show all alternatives above the prompt (on two columns), but if it is too small, it uses more. So, the trick is to use sufficiently large terminals.
For some reason, I had not encountered this in my previous installations, maybe due to larger terminals/smaller font. With less, everything worked well, because there were fewer alternatives and they fitted the terminal.
answered Nov 26 '18 at 18:40
whamalai
1266
The reason turned out to be very simple: If the terminal is sufficiently large, auto-completion can show all alternatives above the prompt (on two columns), but if it is too small, it uses more. So, the trick is to use sufficiently large terminals.
For some reason, I had not encountered this in my previous installations, maybe due to larger terminals/smaller font. With less, everything worked well, because there were fewer alternatives and they fitted the terminal.
answered Nov 26 '18 at 18:40
whamalai
1266
answered Nov 26 '18 at 18:40
whamalai
1266
answered Nov 26 '18 at 18:40
whamalai
1266
answered Nov 26 '18 at 18:40
whamalai
1266
1266
add a comment |
add a comment |
Thanks for contributing an answer to Ask Ubuntu!
- 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%2faskubuntu.com%2fquestions%2f1096251%2fhow-do-i-control-when-bash-auto-completion-shows-a-paged-list-of-completions%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
