1module Graphics.Vty.Attributes.Color where
5-- | Abstract data type representing a color.
7-- Currently the foreground and background color are specified as points
10-- * 16 color palette. Where the first 8 colors are equal to the 8
11-- colors of the ISO 6429 (ANSI) 8 color palette and the second 8
12-- colors are bright/vivid versions of the first 8 colors.
14-- * 240 color palette. This palette is a regular sampling of the full
15-- RGB colorspace for the first 224 colors. The remaining 16 colors is
16-- a greyscale palette.
18-- The 8 ISO 6429 (ANSI) colors are as follows:
36-- The mapping from points in the 240 color palette to colors actually
37-- displayable by the terminal depends on the number of colors the
38-- terminal claims to support. Which is usually determined by the
39-- terminfo "colors" property. If this property is not being accurately
40-- reported then the color reproduction will be incorrect.
42-- If the terminal reports <= 16 colors then the 240 color palette
43-- points are only mapped to the 8 color pallete. I'm not sure of
44-- the RGB points for the "bright" colors which is why they are not
45-- addressable via the 240 color palette.
47-- If the terminal reports > 16 colors then the 240 color palette
48-- points are mapped to the nearest points in a ("color count" - 16)
49-- subsampling of the 240 color palette.
51-- All of this assumes the terminals are behaving similarly to xterm and
52-- rxvt when handling colors. And that the individual colors have not
53-- been remapped by the user. There may be a way to verify this through
54-- terminfo but I don't know it.
56-- Seriously, terminal color support is INSANE.
57data Color = ISOColor !Word8 | Color240 !Word8
58 deriving ( Eq, Show, Read )
keysesc to close
- j k
- move down, up
- enter
- open
- esc
- back, or up a level
- 1 2 3 4
- readme, files, commits, refs
- /
- filter
- y
- copy the clone command
- c
- compare the chosen commit with another (or shift-click both)
- ?
- show or hide this list