Skip to content

color by type #34

@vanzandtj

Description

@vanzandtj

I suggest assigning colors as follows:
For files, use the same colors as GNU ls by respecting the environment variable LS_COLORS. If that variable is not set, then use the defaults printed by "dircolors -p".
For directories:
For .git, foo.git, .svn, and other configuration management directories: use the same color as for a .tar file.
For .../bin, /Applications, etc: same as an executable, or a .exe file.
For ~/Pictures: same as a .jpg file.
Otherwise, a directory should inherit the color of the contents, with votes weighted by space. I.e., add up the space for all the green files & subdirectories, all the red files & subdirectories, etc. Whichever color accounts for the most space is assigned to the directory.

Coloring by content would make it easier to spot duplicate collections of files, because those directories would be assigned the same color. To make this even easier, one could construct a directory color by averaging over the color of its contents. However, I suggest this be an option rather than the default.

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions