Skip to content

Instantly share code, notes, and snippets.

@cskeeters
Last active January 19, 2017 00:59
Show Gist options
  • Save cskeeters/aacd10c075d3c7092a5e4e36db34e62d to your computer and use it in GitHub Desktop.
Save cskeeters/aacd10c075d3c7092a5e4e36db34e62d to your computer and use it in GitHub Desktop.
dircolors compatible with 16 color base-vim (Started with RHEL6 /etc/DIR_COLORS)
# Configuration file for the color ls utility
# Synchronized with coreutils 8.5 dircolors
# This file goes in the /etc directory, and must be world readable.
# You can copy this file to .dir_colors in your $HOME directory to override
# the system defaults.
# COLOR needs one of these arguments: 'tty' colorizes output to ttys, but not
# pipes. 'all' adds color characters to all output. 'none' shuts colorization
# off.
COLOR tty
# Extra command line options for ls go here.
# Basically these ones are:
# -F = show '/' for dirs, '*' for executables, etc.
# -T 0 = don't trust tab spacing when formatting ls output.
OPTIONS -F -T 0
# 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-unicode256
TERM screen
TERM screen-256color
TERM screen-256color-bce
TERM screen-bce
TERM screen-w
TERM screen.linux
TERM vt100
TERM xterm
TERM xterm-16color
TERM xterm-256color
TERM xterm-88color
TERM xterm-color
TERM xterm-debian
# EIGHTBIT, followed by '1' for on, '0' for off. (8-bit output)
EIGHTBIT 1
# 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 # normal file, use no color at all
RESET 0 # reset to "normal" color
DIR 00;34 # directory
LINK 00;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 00;35 # socket
DOOR 00;35 # door
BLK 40;33;01 # block device driver
CHR 40;33;01 # character device driver
ORPHAN 40;31 # symlink to nonexistent file, or non-stat'able file
MISSING 00;05;37;41 # ... and the files they point to
SETUID 37;41 # file that is setuid (u+s)
SETGID 33 # 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
STICKY 37;44 # dir with the sticky bit set (+t) and not other-writable
# This is for files with execute permission:
EXEC 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 '#')
# executables (bright green)
# Source Code Magenta
.java 35
.c++ 35
.h 35
.py 35
.sh 35
.csh 35
.zsh 35
.xml 35
# archives or compressed (bright red)
.tar 37
.tgz 37
.arj 37
.taz 37
.lzh 37
.lzma 37
.tlz 37
.txz 37
.zip 37
.z 37
.Z 37
.dz 37
.gz 37
.lz 37
.xz 37
.bz2 37
.tbz 37
.tbz2 37
.bz 37
.tz 37
.deb 37
.rpm 37
.jar 37
.rar 37
.ace 37
.zoo 37
.cpio 37
.7z 37
.rz 37
# Media (cyan)
.jpg 36
.jpeg 36
.gif 36
.bmp 36
.pbm 36
.pgm 36
.ppm 36
.tga 36
.xbm 36
.xpm 36
.tif 36
.tiff 36
.png 36
.svg 36
.mng 36
.pcx 36
.mov 36
.mpg 36
.mpeg 36
.mkv 36
.mp3 36
.wmv 36
.avi 36
.flv 36
.xcf 36
.aac 36
.mp3 36
.ogg 36
.wav 36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment