puredyne-team team mailing list archive

[Aymeric Mansoux <aymeric@xxxxxxxxxx>]

Public bug reported:

My fault,

I made a dircolor theme to have a pretty term, based on the fact that
Puredyne is set to run with a 256 col enabled $TERM but dircolors points
to ANSI codes that makes little sense if displayed in a less fancy
$TERM, resulting in blinking stuff and other weirdness.

The good approach is to redefine the colors in .XResources, in that case
only the local X display will have the nice colors and it won't break
compatibility when sshing to the box from any other $TERM and OS.

** Affects: puredyne-live
     Importance: Medium
     Assignee: Aymeric Mansoux (aymeric)
         Status: New

** Changed in: puredyne-live
   Importance: Undecided => Medium

** Changed in: puredyne-live
     Assignee: (unassigned) => Aymeric Mansoux (aymeric)

-- 
dircolor theme is no good with 2,16,88 colors terms
https://bugs.launchpad.net/bugs/496296
You received this bug notification because you are a member of puredyne
team, which is the registrant for Puredyne Live.

Status in Puredyne liveCD/DVD/USB/HD: New

Bug description:
My fault,

I made a dircolor theme to have a pretty term, based on the fact that Puredyne is set to run with a 256 col enabled $TERM but dircolors points to ANSI codes that makes little sense if displayed in a less fancy $TERM, resulting in blinking stuff and other weirdness.

The good approach is to redefine the colors in .XResources, in that case only the local X display will have the nice colors and it won't break compatibility when sshing to the box from any other $TERM and OS.