1

enter image description here

enter image description here

I was using bash's autocompletion by pressing TAB key at the end of a pathname. I was also using ls (alias ls='ls --color=auto' in ~/.bashrc). I had trouble recognizing the filenames in the color. (Is it just me? Let me know if I am color-blind.)

I used to solve the problem in Ubuntu, by following https://unix.stackexchange.com/a/94508/, to edit ~/.dircolor and to run:

$ eval "$(/usr/bin/env dircolors ~/.dircolor)"

But it doesn't make any difference indicated in the above screenshots. What can I do to solve the above problem? (I am in NixOS, but it probably doesn't matter.)

Is the output of the following command normal:

$ dircolors ~/.dircolor
LS_COLORS='';
export LS_COLORS

?

Thanks.

~/.dircolor, which I copied from Ubuntu:

# Configuration file for dircolors, a utility to help you set the
# LS_COLORS environment variable used by GNU ls with the --color option.
# Copyright (C) 1996-2013 Free Software Foundation, Inc.
# Copying and distribution of this file, with or without modification,
# are permitted provided the copyright notice and this notice are preserved.
# The keywords COLOR, OPTIONS, and EIGHTBIT (honored by the
# slackware version of dircolors) are recognized but ignored.
# Below, there should be one TERM entry for each termtype that is colorizable
TERM Eterm
TERM ansi
TERM color-xterm
TERM con132x25
TERM con132x30
TERM con132x43
TERM con132x60
TERM con80x25
TERM con80x28
TERM con80x30
TERM con80x43
TERM con80x50
TERM con80x60
TERM cons25
TERM console
TERM cygwin
TERM dtterm
TERM eterm-color
TERM gnome
TERM gnome-256color
TERM jfbterm
TERM konsole
TERM kterm
TERM linux
TERM linux-c
TERM mach-color
TERM mlterm
TERM putty
TERM rxvt
TERM rxvt-256color
TERM rxvt-cygwin
TERM rxvt-cygwin-native
TERM rxvt-unicode
TERM rxvt-unicode-256color
TERM rxvt-unicode256
TERM screen
TERM screen-256color
TERM screen-256color-bce
TERM screen-bce
TERM screen-w
TERM screen.Eterm
TERM screen.rxvt
TERM screen.linux
TERM st
TERM st-256color
TERM terminator
TERM vt100
TERM xterm
TERM xterm-16color
TERM xterm-256color
TERM xterm-88color
TERM xterm-color
TERM xterm-debian
# Below are the color init strings for the basic file types. A color init
# string consists of one or more of the following numeric codes:
# Attribute codes:
# 00=none 01=bold 04=underscore 05=blink 07=reverse 08=concealed
# Text color codes:
# 30=black 31=red 32=green 33=yellow 34=blue 35=magenta 36=cyan 37=white
# Background color codes:
# 40=black 41=red 42=green 43=yellow 44=blue 45=magenta 46=cyan 47=white
#NORMAL 00 # no color code at all
#FILE 00 # regular file: use no color at all
RESET 0 # reset to "normal" color
DIR 01;34 # directory
LINK 01;36 # symbolic link. (If you set this to 'target' instead of a
 # numerical value, the color is as for the file pointed to.)
MULTIHARDLINK 00 # regular file with more than one link
FIFO 40;33 # pipe
SOCK 01;35 # socket
DOOR 01;35 # door
BLK 40;33;01 # block device driver
CHR 40;33;01 # character device driver
ORPHAN 40;31;01 # symlink to nonexistent file, or non-stat'able file
SETUID 37;41 # file that is setuid (u+s)
SETGID 30;43 # file that is setgid (g+s)
CAPABILITY 30;41 # file with capability
STICKY_OTHER_WRITABLE 30;42 # dir that is sticky and other-writable (+t,o+w)
# OTHER_WRITABLE 34;42 # dir that is other-writable (o+w) and not sticky
OTHER_WRITABLE 34;43 # dir that is other-writable (o+w) and not sticky # my edit. the original uses 42 green bkg, which hides 34 blue text, I choose 43 yellow for contrasting with blue text
STICKY 37;44 # dir with the sticky bit set (+t) and not other-writable
# This is for files with execute permission:
EXEC 01;32
# List any file extensions like '.gz' or '.tar' that you would like ls
# to colorize below. Put the extension, a space, and the color init string.
# (and any comments you want to add after a '#')
# If you use DOS-style suffixes, you may want to uncomment the following:
#.cmd 01;32 # executables (bright green)
#.exe 01;32
#.com 01;32
#.btm 01;32
#.bat 01;32
# Or if you want to colorize scripts even if they do not have the
# executable bit actually set.
#.sh 01;32
#.csh 01;32
 # archives or compressed (bright red)
.tar 01;31
.tgz 01;31
.arj 01;31
.taz 01;31
.lzh 01;31
.lzma 01;31
.tlz 01;31
.txz 01;31
.zip 01;31
.z 01;31
.Z 01;31
.dz 01;31
.gz 01;31
.lz 01;31
.xz 01;31
.bz2 01;31
.bz 01;31
.tbz 01;31
.tbz2 01;31
.tz 01;31
.deb 01;31
.rpm 01;31
.jar 01;31
.war 01;31
.ear 01;31
.sar 01;31
.rar 01;31
.ace 01;31
.zoo 01;31
.cpio 01;31
.7z 01;31
.rz 01;31
# image formats
.jpg 01;35
.jpeg 01;35
.gif 01;35
.bmp 01;35
.pbm 01;35
.pgm 01;35
.ppm 01;35
.tga 01;35
.xbm 01;35
.xpm 01;35
.tif 01;35
.tiff 01;35
.png 01;35
.svg 01;35
.svgz 01;35
.mng 01;35
.pcx 01;35
.mov 01;35
.mpg 01;35
.mpeg 01;35
.m2v 01;35
.mkv 01;35
.webm 01;35
.ogm 01;35
.mp4 01;35
.m4v 01;35
.mp4v 01;35
.vob 01;35
.qt 01;35
.nuv 01;35
.wmv 01;35
.asf 01;35
.rm 01;35
.rmvb 01;35
.flc 01;35
.avi 01;35
.fli 01;35
.flv 01;35
.gl 01;35
.dl 01;35
.xcf 01;35
.xwd 01;35
.yuv 01;35
.cgm 01;35
.emf 01;35
# http://wiki.xiph.org/index.php/MIME_Types_and_File_Extensions
.axv 01;35
.anx 01;35
.ogv 01;35
.ogx 01;35
# audio formats
.aac 00;36
.au 00;36
.flac 00;36
.mid 00;36
.midi 00;36
.mka 00;36
.mp3 00;36
.mpc 00;36
.ogg 00;36
.ra 00;36
.wav 00;36
# http://wiki.xiph.org/index.php/MIME_Types_and_File_Extensions
.axa 00;36
.oga 00;36
.spx 00;36
.xspf 00;36
Tim
  • 101,790

1 Answers1

2

dircolors won’t output anything if the current terminal type (as indicated by the value of the TERM environment variable) isn’t listed in its configuration file.

Since you’re using foot, which supports colours, you need to add a

TERM foot

line to your dircolors configuration file.

Stephen Kitt
  • 434,908
  • do I need to add more lines in discolors configuration file for foot? I saw there are more lines after TERM xterm, TERM st. – Tim Mar 25 '22 at 14:06
  • Take your current configuration file, as listed in your question, and add a TERM foot line to it. That’s all. – Stephen Kitt Mar 25 '22 at 14:16
  • May I ask what the few lines after TERM xterm and TERM st are used for? – Tim Mar 25 '22 at 14:28
  • I meant TERM st TERM st-256color TERM terminator TERM vt100 TERM xterm TERM xterm-16color TERM xterm-256color TERM xterm-88color TERM xterm-color TERM xterm-debian – Tim Mar 25 '22 at 14:32
  • See the introductory comment in the file, # Below, there should be one TERM entry for each termtype that is colorizable: each TERM line specifies a terminal type which supports colours. If dircolors matches the value of the TERM environment variable against one of those entries, it produces output, otherwise it doesn’t. – Stephen Kitt Mar 25 '22 at 14:39
  • So are "TERM xterm TERM xterm-16color TERM xterm-256color TERM xterm-88color TERM xterm-color TERM xterm-debian" different terminal emulators? – Tim Mar 25 '22 at 17:55
  • How do discolor and a terminal emulator work together? Is coloring directly done by a terminal emulator and therefore a configuration of a terminal emulator? If yes, what is the role of discolor? Are the answers long enough and worth a new post? – Tim Mar 26 '22 at 01:58
  • @Tim if you have follow up questions, please post them separately and not as comments. – terdon Mar 26 '22 at 14:28
  • Stephen, your reply solved the problem in the output of ls, but not in the output of autocompletion in bash by TAB – Tim Mar 28 '22 at 23:41
  • Do you have set colored-stats on in your .inputrc? – Stephen Kitt Mar 29 '22 at 04:28
  • @StephenKitt set colored-stats on is in /etc/inputrc. What does that mean and what can I do? I don't have file ~/.inputrc. Still bother by that shell autocompletion displays unintelligible colors over filenames. Also could you help with https://unix.stackexchange.com/questions/696951/how-does-the-command-created-by-dircolors-work? Thanks – Tim Apr 07 '22 at 22:23
  • colored-stats enabled colours in auto-completion; I just wanted to make sure that it’s not disabled in your setup. – Stephen Kitt Apr 08 '22 at 10:30
  • Does its enabling mean that autocompletion will follow the same configurations as the output of ls? (It does not in my case) – Tim Apr 08 '22 at 20:59
  • That’s what it’s supposed to do; I wondered whether it might be disabled in your case. I don’t know why it would behave differently as it does for you... – Stephen Kitt Apr 08 '22 at 21:11