On Mon, Jan 20, 2014 at 04:18:33PM +0100, Andreas Herz wrote:
> I have the bug described in
> http://sourceforge.net/p/tmux/tmux-code/ci/master/tree/FAQ
>
> so i created the terminfo screen-it as described in the FAQ.
[...]
> But that destroys LS_COLORS :/
> env | grep LS_COLOR results in LS_COLORS=
> instead of
> LS=COLORS=rs=0:di=01;34:ln=01;.... and so on.
>
> Does anyone have an idea how i can fix both issues the same time :)?
LS_COLORS is typically set by the "dircolors" tool, somewhere in your
shell's startup scripts (or your system-wide startup scripts, depending
on distro).
dircolors can read its settings from a config file, but it doesn't
unless it's told to. One of the settings in the config file is
a whitelist of $TERM types in which it will set LS_COLORS.
So:
- Create a dircolors config file with some sensible name like
~/.dircolorsrc and put the default configuration into it:
dircolors --print-database > ~/.dircolorsrc
- Edit ~/.dircolorsrc and add your new terminal to the whitelist,
along with all the other TERM entries:
TERM screen-it
- Edit your shell startup scripts to add the line (or amend it, if it's
already there):
eval $(dircolors ~/.dircolorsrc)
That should do the trick.
------------------------------------------------------------------------------
CenturyLink Cloud: The Leader in Enterprise Cloud Services.
Learn Why More Businesses Are Choosing CenturyLink Cloud For
Critical Workloads, Development Environments & Everything In Between.
Get a Quote or Start a Free Trial Today.
http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk
_______________________________________________
tmux-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/tmux-users
