Sami Kerola <kerolasa@xxxxxx> writes:
> Or add the needed to ncurses. Isn't that better than adding a new
> library?
That would work, but only for utilities that use ncurses. OTOH, it
would be good if ncurses understood and provided information from the
general color configuration to programs that use it.
Bruce Dubbs <bruce.dubbs@xxxxxxxxx> writes:
> Why not use the LS_COLORS environment variable used by coreutils' dircolors?
> Does util-linux need to create something different?
Using an environment variable is the standard Unix way of configuring
the user-oriented behavior of programs. But the "definition" of
LS_COLORS seems to be very specific to "ls".
The /etc/terminal-colors.d system seems a bit oversized (all those
files!), but it seems unlikely that anything simpler would work for a
large set of utilities, each of which the user may want to customize.
The main deficiency of terminal-colors.d is that it's system-wide. But
I see this in a blog:
$HOME/.config/terminal-colors.d overrides the global setting
so that is taken care of.
You also want to define an environment variable to override *that*,
e.g., files in $UTIL_LINUX_TERMINAL_COLORS override the ones in
$HOME/.config/terminal-colors.d -- that allows you to set up custom
environments for particular trees of processes by creating a suitable
colors directory and setting UTIL_LINUX_TERMINAL_COLORS.
Dale
--
To unsubscribe from this list: send the line "unsubscribe util-linux" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
