How to change bash completion result coloring











up vote
1
down vote

favorite












How to change completion coloring when auto-completing subcommands in bash?enter image description here



For unknown reason, it looks like the completion results are treated by bash as broken symlinks. And it looks really disturbing.



System info:




  • Bash version: 4.4.23(1)-release

  • OS: Manjaro Linux




Edit: I understand that by setting off the colored-stats GNU Readline option in ~/.inputrc the coloring will be turned off altogether:



set colored-stats off


But that would also disable other coloring, such as for directory, when auto-completing.



I think this is weird because the broken-symlink-like coloring happens on my Manjaro Linux box at home, but not my Arch Linux box at work. Both are applied with the same bashrc and inputrc. But I didn't check for other potential difference for now.





Edit again: Pasting my ~/.inputrc for reference:



$include /etc/inputrc
$if mode=emacs
# cycle through possible completions
TAB: menu-complete
# complete until the end of common prefix before cycling through possible completions
set menu-complete-display-prefix on
# show possible completions if more than one completions are possible
set show-all-if-ambiguous on
set show-all-if-unmodified on
# do not duplicate characters after the cursor if they consist partially of possbile completion
set skip-completed-text on
# display colors when doing completion as `ls` does
set colored-stats on
# color tab-completion matched prefix part
set colored-completion-prefix on
# fuck off stty key bindings. (stty -a)
set bind-tty-special-chars off
"C-w": unix-word-rubout
"eh": kill-region
"eH": copy-region-as-kill
"C-x'": "''C-b"
"C-x`": "``C-b"
"C-x"": """C-b"
"C-x{": "{}C-b"
"C-x[": "C-b"
"C-x(": "()C-b"
"C-x0": vi-eWord
"eF": "C-x0C-f"
"eB": vi-bWord
"eD": "e eFeh"
$endif









share|improve this question
























  • I'm trying to understand this as well. My assumption is that something in the way it presents the output is assuming that it's a local file and so is treating it as "missing", but I don't know why yet. It would be good if it just showed them as plain text!
    – IBBoard
    Dec 6 at 20:51















up vote
1
down vote

favorite












How to change completion coloring when auto-completing subcommands in bash?enter image description here



For unknown reason, it looks like the completion results are treated by bash as broken symlinks. And it looks really disturbing.



System info:




  • Bash version: 4.4.23(1)-release

  • OS: Manjaro Linux




Edit: I understand that by setting off the colored-stats GNU Readline option in ~/.inputrc the coloring will be turned off altogether:



set colored-stats off


But that would also disable other coloring, such as for directory, when auto-completing.



I think this is weird because the broken-symlink-like coloring happens on my Manjaro Linux box at home, but not my Arch Linux box at work. Both are applied with the same bashrc and inputrc. But I didn't check for other potential difference for now.





Edit again: Pasting my ~/.inputrc for reference:



$include /etc/inputrc
$if mode=emacs
# cycle through possible completions
TAB: menu-complete
# complete until the end of common prefix before cycling through possible completions
set menu-complete-display-prefix on
# show possible completions if more than one completions are possible
set show-all-if-ambiguous on
set show-all-if-unmodified on
# do not duplicate characters after the cursor if they consist partially of possbile completion
set skip-completed-text on
# display colors when doing completion as `ls` does
set colored-stats on
# color tab-completion matched prefix part
set colored-completion-prefix on
# fuck off stty key bindings. (stty -a)
set bind-tty-special-chars off
"C-w": unix-word-rubout
"eh": kill-region
"eH": copy-region-as-kill
"C-x'": "''C-b"
"C-x`": "``C-b"
"C-x"": """C-b"
"C-x{": "{}C-b"
"C-x[": "C-b"
"C-x(": "()C-b"
"C-x0": vi-eWord
"eF": "C-x0C-f"
"eB": vi-bWord
"eD": "e eFeh"
$endif









share|improve this question
























  • I'm trying to understand this as well. My assumption is that something in the way it presents the output is assuming that it's a local file and so is treating it as "missing", but I don't know why yet. It would be good if it just showed them as plain text!
    – IBBoard
    Dec 6 at 20:51













up vote
1
down vote

favorite









up vote
1
down vote

favorite











How to change completion coloring when auto-completing subcommands in bash?enter image description here



For unknown reason, it looks like the completion results are treated by bash as broken symlinks. And it looks really disturbing.



System info:




  • Bash version: 4.4.23(1)-release

  • OS: Manjaro Linux




Edit: I understand that by setting off the colored-stats GNU Readline option in ~/.inputrc the coloring will be turned off altogether:



set colored-stats off


But that would also disable other coloring, such as for directory, when auto-completing.



I think this is weird because the broken-symlink-like coloring happens on my Manjaro Linux box at home, but not my Arch Linux box at work. Both are applied with the same bashrc and inputrc. But I didn't check for other potential difference for now.





Edit again: Pasting my ~/.inputrc for reference:



$include /etc/inputrc
$if mode=emacs
# cycle through possible completions
TAB: menu-complete
# complete until the end of common prefix before cycling through possible completions
set menu-complete-display-prefix on
# show possible completions if more than one completions are possible
set show-all-if-ambiguous on
set show-all-if-unmodified on
# do not duplicate characters after the cursor if they consist partially of possbile completion
set skip-completed-text on
# display colors when doing completion as `ls` does
set colored-stats on
# color tab-completion matched prefix part
set colored-completion-prefix on
# fuck off stty key bindings. (stty -a)
set bind-tty-special-chars off
"C-w": unix-word-rubout
"eh": kill-region
"eH": copy-region-as-kill
"C-x'": "''C-b"
"C-x`": "``C-b"
"C-x"": """C-b"
"C-x{": "{}C-b"
"C-x[": "C-b"
"C-x(": "()C-b"
"C-x0": vi-eWord
"eF": "C-x0C-f"
"eB": vi-bWord
"eD": "e eFeh"
$endif









share|improve this question















How to change completion coloring when auto-completing subcommands in bash?enter image description here



For unknown reason, it looks like the completion results are treated by bash as broken symlinks. And it looks really disturbing.



System info:




  • Bash version: 4.4.23(1)-release

  • OS: Manjaro Linux




Edit: I understand that by setting off the colored-stats GNU Readline option in ~/.inputrc the coloring will be turned off altogether:



set colored-stats off


But that would also disable other coloring, such as for directory, when auto-completing.



I think this is weird because the broken-symlink-like coloring happens on my Manjaro Linux box at home, but not my Arch Linux box at work. Both are applied with the same bashrc and inputrc. But I didn't check for other potential difference for now.





Edit again: Pasting my ~/.inputrc for reference:



$include /etc/inputrc
$if mode=emacs
# cycle through possible completions
TAB: menu-complete
# complete until the end of common prefix before cycling through possible completions
set menu-complete-display-prefix on
# show possible completions if more than one completions are possible
set show-all-if-ambiguous on
set show-all-if-unmodified on
# do not duplicate characters after the cursor if they consist partially of possbile completion
set skip-completed-text on
# display colors when doing completion as `ls` does
set colored-stats on
# color tab-completion matched prefix part
set colored-completion-prefix on
# fuck off stty key bindings. (stty -a)
set bind-tty-special-chars off
"C-w": unix-word-rubout
"eh": kill-region
"eH": copy-region-as-kill
"C-x'": "''C-b"
"C-x`": "``C-b"
"C-x"": """C-b"
"C-x{": "{}C-b"
"C-x[": "C-b"
"C-x(": "()C-b"
"C-x0": vi-eWord
"eF": "C-x0C-f"
"eB": vi-bWord
"eD": "e eFeh"
$endif






bash autocomplete manjaro






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Dec 7 at 0:32

























asked Nov 13 at 15:55









Naitree

2971211




2971211












  • I'm trying to understand this as well. My assumption is that something in the way it presents the output is assuming that it's a local file and so is treating it as "missing", but I don't know why yet. It would be good if it just showed them as plain text!
    – IBBoard
    Dec 6 at 20:51


















  • I'm trying to understand this as well. My assumption is that something in the way it presents the output is assuming that it's a local file and so is treating it as "missing", but I don't know why yet. It would be good if it just showed them as plain text!
    – IBBoard
    Dec 6 at 20:51
















I'm trying to understand this as well. My assumption is that something in the way it presents the output is assuming that it's a local file and so is treating it as "missing", but I don't know why yet. It would be good if it just showed them as plain text!
– IBBoard
Dec 6 at 20:51




I'm trying to understand this as well. My assumption is that something in the way it presents the output is assuming that it's a local file and so is treating it as "missing", but I don't know why yet. It would be good if it just showed them as plain text!
– IBBoard
Dec 6 at 20:51















active

oldest

votes











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
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f481493%2fhow-to-change-bash-completion-result-coloring%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown






























active

oldest

votes













active

oldest

votes









active

oldest

votes






active

oldest

votes
















draft saved

draft discarded




















































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.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f481493%2fhow-to-change-bash-completion-result-coloring%23new-answer', 'question_page');
}
);

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







Popular posts from this blog

サソリ

広島県道265号伴広島線

Accessing regular linux commands in Huawei's Dopra Linux