seebi / dircolors-solarized Goto Github PK

How the dircolors color scheme looks on my terminal

Take look at /dev/sd* and /tmp/tmux/* - the color mix looks ugly.

I found out that these colors are not correct. For example, in this screenshot, colors are different from the ones I have.

I did not find my mistakes in whether I installed the color theme correctly, and so I guess there is a bug in the color scheme; I also tried different terminals - the result is the same.

My setup:

• GNOME Terminal 3.24.1 (also tried rxvt-unicode 9.22)
• TERM=screen-16color (also tried rxvt-* and *-255color)
• dircolors.ansi-dark (also tried ansi-light)

I made a mistake? Or/and is this a known problem?

Sockets get colored using SOCK 35;44, which translates to magenta on blue.

Given that the intention here is to have a blue background, I'd say to use 37;44 as with CHR here, too.

It might be better to use 01;37;44 (bright white) here even.

BLK 33;44 is also problematic (33=yellow).

Setup

1. Prepare iterm2 palette as instructed by https://github.com/altercation/solarized/tree/master/iterm2-colors-solarized
2. Download .dircolors from https://github.com/seebi/dircolors-solarized/blob/master/dircolors.256dark

How to reproduce

1. Open iterm2 on mac.
2. ssh
3. Apply dircolors, and invoke ls to see the output.
   

Other info

• After launching tmux, the color becomes correct:
  
• Using uxterm (configured using https://github.com/solarized/xresources) on the server directly (without ssh) gives me the correct color both outside and inside tmux.

ENV

Server (linux) OS: Ubuntu 14.03
Mac: 10.9.5
iterm2: 2.1.4
Shell: zsh

Hello, I got 2 questions please.

• Does that work without any terminal emulator but directly in console text mode ?
  I'm using my debian in text mode with no Xorg installed.
• Is it only for Ls command or other commands works ?
  If not, any other way to gor Solarized working in basic console on a linux in text mode.

Thanks anyway

Expect pretty color theme, but recieve white screen. Don't like.

± % ls -alF ~/.dircolors                                                                                                                                                                                    !10071
lrwxrwxrwx 1 muammar muammar 58 Mar  3 12:38 /home/muammar/.dircolors -> /home/muammar/github/dircolors-solarized/dircolors.256dark

muammar@nuc ~ 
  % dircolors -b .dircolors                                                                                                                                                                                 !10074
LS_COLORS='no=00;38;5;244:rs=0:di=00;38;5;33:ln=00;38;5;37:mh=00:pi=48;5;230;38;5;136;01:so=48;5;230;38;5;136;01:do=48;5;230;38;5;136;01:bd=48;5;230;38;5;244;01:cd=48;5;230;38;5;244;01:or=48;5;235;38;5;160:su=48;5;160;38;5;230:sg=48;5;136;38;5;230:ca=30;41:tw=48;5;64;38;5;230:ow=48;5;235;38;5;33:st=48;5;33;38;5;230:ex=00;38;5;64:*.tar=00;38;5;61:*.tgz=00;38;5;61:*.arj=00;38;5;61:*.taz=00;38;5;61:*.lzh=00;38;5;61:*.lzma=00;38;5;61:*.tlz=00;38;5;61:*.txz=00;38;5;61:*.zip=00;38;5;61:*.z=00;38;5;61:*.Z=00;38;5;61:*.dz=00;38;5;61:*.gz=00;38;5;61:*.lz=00;38;5;61:*.xz=00;38;5;61:*.bz2=00;38;5;61:*.bz=00;38;5;61:*.tbz=00;38;5;61:*.tbz2=00;38;5;61:*.tz=00;38;5;61:*.deb=00;38;5;61:*.rpm=00;38;5;61:*.jar=00;38;5;61:*.rar=00;38;5;61:*.ace=00;38;5;61:*.zoo=00;38;5;61:*.cpio=00;38;5;61:*.7z=00;38;5;61:*.rz=00;38;5;61:*.apk=00;38;5;61:*.gem=00;38;5;61:*.jpg=00;38;5;136:*.JPG=00;38;5;136:*.jpeg=00;38;5;136:*.gif=00;38;5;136:*.bmp=00;38;5;136:*.pbm=00;38;5;136:*.pgm=00;38;5;136:*.ppm=00;38;5;136:*.tga=00;38;5;136:*.xbm=00;38;5;136:*.xpm=00;38;5;136:*.tif=00;38;5;136:*.tiff=00;38;5;136:*.png=00;38;5;136:*.PNG=00;38;5;136:*.svg=00;38;5;136:*.svgz=00;38;5;136:*.mng=00;38;5;136:*.pcx=00;38;5;136:*.dl=00;38;5;136:*.xcf=00;38;5;136:*.xwd=00;38;5;136:*.yuv=00;38;5;136:*.cgm=00;38;5;136:*.emf=00;38;5;136:*.eps=00;38;5;136:*.CR2=00;38;5;136:*.ico=00;38;5;136:*.tex=00;38;5;245:*.rdf=00;38;5;245:*.owl=00;38;5;245:*.n3=00;38;5;245:*.ttl=00;38;5;245:*.nt=00;38;5;245:*.torrent=00;38;5;245:*.xml=00;38;5;245:*Makefile=00;38;5;245:*Rakefile=00;38;5;245:*Dockerfile=00;38;5;245:*build.xml=00;38;5;245:*rc=00;38;5;245:*1=00;38;5;245:*.nfo=00;38;5;245:*README=00;38;5;245:*README.txt=00;38;5;245:*readme.txt=00;38;5;245:*.md=00;38;5;245:*README.markdown=00;38;5;245:*.ini=00;38;5;245:*.yml=00;38;5;245:*.cfg=00;38;5;245:*.conf=00;38;5;245:*.h=00;38;5;245:*.hpp=00;38;5;245:*.c=00;38;5;245:*.cpp=00;38;5;245:*.cxx=00;38;5;245:*.cc=00;38;5;245:*.objc=00;38;5;245:*.sqlite=00;38;5;245:*.go=00;38;5;245:*.sql=00;38;5;245:*.csv=00;38;5;245:*.log=00;38;5;240:*.bak=00;38;5;240:*.aux=00;38;5;240:*.lof=00;38;5;240:*.lol=00;38;5;240:*.lot=00;38;5;240:*.out=00;38;5;240:*.toc=00;38;5;240:*.bbl=00;38;5;240:*.blg=00;38;5;240:*~=00;38;5;240:*#=00;38;5;240:*.part=00;38;5;240:*.incomplete=00;38;5;240:*.swp=00;38;5;240:*.tmp=00;38;5;240:*.temp=00;38;5;240:*.o=00;38;5;240:*.pyc=00;38;5;240:*.class=00;38;5;240:*.cache=00;38;5;240:*.aac=00;38;5;166:*.au=00;38;5;166:*.flac=00;38;5;166:*.mid=00;38;5;166:*.midi=00;38;5;166:*.mka=00;38;5;166:*.mp3=00;38;5;166:*.mpc=00;38;5;166:*.ogg=00;38;5;166:*.opus=00;38;5;166:*.ra=00;38;5;166:*.wav=00;38;5;166:*.m4a=00;38;5;166:*.axa=00;38;5;166:*.oga=00;38;5;166:*.spx=00;38;5;166:*.xspf=00;38;5;166:*.mov=00;38;5;166:*.MOV=00;38;5;166:*.mpg=00;38;5;166:*.mpeg=00;38;5;166:*.m2v=00;38;5;166:*.mkv=00;38;5;166:*.ogm=00;38;5;166:*.mp4=00;38;5;166:*.m4v=00;38;5;166:*.mp4v=00;38;5;166:*.vob=00;38;5;166:*.qt=00;38;5;166:*.nuv=00;38;5;166:*.wmv=00;38;5;166:*.asf=00;38;5;166:*.rm=00;38;5;166:*.rmvb=00;38;5;166:*.flc=00;38;5;166:*.avi=00;38;5;166:*.fli=00;38;5;166:*.flv=00;38;5;166:*.gl=00;38;5;166:*.m2ts=00;38;5;166:*.divx=00;38;5;166:*.webm=00;38;5;166:*.axv=00;38;5;166:*.anx=00;38;5;166:*.ogv=00;38;5;166:*.ogx=00;38;5;166:';
export LS_COLORS

However,

muammar@nuc ~ 
  % echo $LS_COLORS                                                                                                                                                                                         !10075

What could be the problem here?. Thanks :).

muammar@nuc ~ 
  % dircolors --version                                                                                                                                                                                     !10076
dircolors (GNU coreutils) 8.26
Copyright (C) 2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>.
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

Written by H. Peter Anvin.

I have added "eval $(dircolors ~/.dircolors)" to my .zshrc, but the LS_COLORS environment variable is still empty when I log in and the colors don't change. But if I run the exact same eval command outside of my .zshrc (in the shell), the colors apply and everything works fine. Why is this?

Hi seebi,

Thank you for the great work on dircolors-solarized. I really want to use your script at work but my employer requires that dircolors-solarized has an explicit open-source license on Github page. So far I see that dircolors.256dark has a license (even though not GPL / MIT). Can you add license to the whole repo or to the other dircolors.ansi-* files? Thank you for your work.

The Solarized color themes are distributed as database files for GNU dircolors, which is the application that sets up colors for GNU ls. To use any of the database files, run this:

eval dircolors /path/to/dircolorsdb
To activate the theme for all future shell sessions, copy or link that file to ~/.dir_colors, and include the above command in your ~/.profile (for bash) or ~/.zshrc (for zsh).

If you do add "eval dircolors /path/to/dircolorsdb", xrdb will return "xrdb: colon missing on line 1, ignoring line". Not an error, but some may stumble over it.
"eval: dircolors /path/to/dircolorsdb" should be written there.

I am unable to read directories names which have drwxrwsrwx permissions with green background ,Can someone suggest some alternative .
i am using solarized dark theme in terminal.

I wasn't quite sure where to post this, so figured an issue off of your repository might be the most likely to be found by others. :) I took a bit of time today and roughly mirrored the base colors that your solarized theme for dircolors gives in OSX's LSCOLORS environment variable:

export LSCOLORS=gxfxbEaEBxxEhEhBaDaCaD

It's not nearly as comprehensive (you can't do file-type matching, for example), but it should be close, for those who don't want to replace ls with the GNU version.

.cxx and .cc are present, but not .cpp. Much appreciated -- thanks!

Probably worth an issue:

~$ dircolors -b .dircolors 
LS_COLORS='';
export LS_COLORS

edit: I downloaded the bright ansi color file and renamed it into .dircolor.

Canon Raw files (haven't checked other RAW formats) are also image formats.

Good morning,

just a quick mini thing: The link "Understanding Solarized Colors in Terminals" within then TOC is broken. Instead of https://github.com/seebi/dircolors-solarized#understanding-solarized-colors-in-terminals it links to https://github.com/seebi/dircolors-solarized#understanding.

Screenshot
I'm using the 256dark theme, which is loaded by eval `dircolors ~/.dircolors` in .zshrc.

As you see, the background color of the current path is different, even though both versions get their color settings the same way. Is there a fix for this? It should be as in VSC.

Kind regards
Patrick

Not sure if this is something that would be interesting, but .java, .c, .cpp, .php, .pl, .py etc are all "special" files in that they are all source code files. Similarily, compiled files might be marked as irrelevant (.o, .class)?

I want to customize the theme,like robbyrussell etc.

dircolors gives no output.

EDIT: Just made an important discovery. The weird color is for any folder on an NTFS drive, and any file on an NTFS drive is orange. My Dropbox folder happens to be linked from an NTFS storage drive. So, what customization in .dir_colors is for NTFS folders/files? Thanks!

Hi,

I seem to be having a funky issue with colors of folders within Dropbox.

Setup: Ubuntu 12.04.1; Gnome3; xterm16-color (setup properly with Solarized and etc.); this file set as my .dir_colors and evaled in .bashrc

Within my Dropbox folder in the terminal all folders have a bright yellow background with the normal background color of green for the font. I'm assuming it's because it's registering not as a folder, since the dropbox daemon marks it with synced/not-synced.

I'm fine with having it colored, but the color it currently is, is simply obnoxious, and I don't know enough about the color codes (and folder status) to fix this.

Thanks!

As of 5044ba7 you have your test suite stored in a bzip2 compressed file. This is not ideal for a few reasons:

1. git already compresses plain text using delta compression and zlib. The disk space and bandwidth conserved with bzip2 will be minimal.
2. Incremental changes to the test suite cannot be reviewed in the git log without checking out the old branches and doing a diff - a laborious process.
3. git stores binary files completely in the revision tree since delta compression is not possible. That means that each revision to the compressed file gets stored anew with the commit, which in turn bloats the source tree -- completely defeating the purpose of saving disk space.

Further reading:

1. https://stackoverflow.com/questions/11254733/can-git-differentially-store-gzip-files
2. https://stackoverflow.com/questions/3329041/best-practice-to-store-jar-files-in-vcs-svn-git

You might want to add "TERM rxvt-unicode-256color" as one of the valid terminals to support unicode color rxvt on Arch Linux =)

@seebi
Would that be possible?

I mean if I'm using this as my terminal's theme, how would I use it as Vim's theme?

I suppose somebody would have to make a theme for Vim. Is that in the plans? Is it done yet?

As I understand it, this is a theme of it's own, using the colors that Solarized uses correct? So it's got the same colors, used differently?

Thanks for your attention. :)

I found https://github.com/altercation/solarized/ and couldn't find this repository so maybe by putting this in the solarized repository will make people more easier to find the dircolors.

I've tried eval (dircolors ~/.dir_colors), replacing backsticks with parentheses but it didn't help. Fish outputs error.

I've also tried to manually set and export LS_COLORS environment variable, but also without results.

The string is incredibly long.

Please help with fish shell, the standard command for exporting variable is set -x, and there's no equal (=) character when setting the value (set var value is enough) unlike var=value;export $var of zsh and bash.

I don't understand the merge from issue #44. It would seem that the change was just to get rid of the bold font hierarchy that is still described in the README. I believe the user who submitted the change was simply having an issue whereby a particular terminal was not displaying bold fonts properly and simply giving them a dark background, but on Xfce4-term (e.g.) the commit simply gets rid of having bold fonts for certain files.

Submitting this as a new issue because I'm not sure which version is preferred by others, but anyway there's at least an inconsistency in the README vs the current state of the repo.

I found ,v in color file:

➜  dircolors-solarized git:(master) git grep -w ',v'
dircolors.ansi-dark:#*,v 01;36
dircolors.ansi-dark:*,v 01;33
dircolors.ansi-light:*,v 01;36
dircolors.ansi-light:#*,v 01;33
dircolors.ansi-universal:*,v 01;36
dircolors.ansi-universal:#*,v 01;33

Is this meant to match *.v ? Or it has its own meaning?

.swp files are created by vim when you have a file open in the editor, and should be colored as temporary/unimportant.

I'm changing between dark and light solarized theme in my terminal emulator (termite) and I wanted to change dircolors as well, but I've noticed that dircolors.ansi-light and dircolors.ansi-universal cause 0777 folders to be drawn in a bad color combination (blue on yellow). See these screenshots demonstrating the weird colors of universal and light, and the good colors of dark:

http://imgur.com/gallery/U0Kvz

Is that a fault on my end, or just an unfortunate color combination nobody has noticed before? After all 0777 folders are rare, and maybe few users use the light themes.

Please advise if you need more information about my setup. I can dump values of $LS_COLORS etc. if you need them.

The fact that it looks nice with the ansi-dark theme leads me to believe I have my terminal emulator colors configured correctly, and the right boldfont settings.

I like the feature of LS_COLORS [1] to highlight dangling symlinks with a red background.

Please consider adding this (speaking of dircolors.256dark).

LS_COLORS uses ORPHAN 48;5;196;38;5;232;1

1: https://github.com/trapd00r/LS_COLORS

dircolors.256dark is not in sync with the dircolors.ansi* (has less file-types).
Just wondering if it's intentional?

PS - I use the ansi-light colors though.

Would be good to have special colors for download/downloading files:
*.torrent - Torrent files
*.part - Chromium/Google Chrome unfinished downloads
*.incomplete - wget and other download tools

Why there's no 256light version, since we have 256dark?

There is an inconsistency (at least) in the color of directories in the 256 color and ANSI schemes. 256 color use a blue color (as is usual) for directories, whereas the ANSI scheme uses Solarized cyan. I think this should be made consistent and I would prefer to have blue directories in the ANSI scheme (DIR 34 instead of DIR 36), as that is what I am used to from other color schemes.

My tmux session uses the screen-256color-bce-s terminal type. You may want to add it to the dircolors files for others who use this terminal type.