Summary: | in output.py "dark" makes a colour lighter | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Benno Schulenberg <bensberg> |
Component: | Enhancement/Feature Requests | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED FIXED | ||
Severity: | normal | Keywords: | InVCS |
Priority: | High | ||
Version: | 2.1 | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 136244 | ||
Attachments: |
reorder to brightest first, and remove the darkteal
add some colour synonyms proposed color.map.5 man page |
Description
Benno Schulenberg
2006-06-18 14:24:05 UTC
Created attachment 89492 [details, diff]
reorder to brightest first, and remove the darkteal
Created attachment 89493 [details, diff]
add some colour synonyms
Thanks, the teal reordering is in svn r3532. I'm not adding or removing any colors though. The color.map can be used to define any colors that the user wants. There is no need to bloat output.py with more colors. The ones that are there exist only for backward compatibility. Okay. But the user should know which color names can be redefined. Maybe put this info in a color.map man page? And then make emerge.1 and equery.1 (and any others that use the mapping) refer to it? ... Yes, I'm volunteering to write the page. :) (In reply to comment #4) > Okay. But the user should know which color names can be redefined. Redefinition of colors is not really optimal. We really need to replace all of the explicite use of *colors* within the portage code with *meanings* so that the user can use color.map to define the colors that they would like to convey specific meanings. Created attachment 89762 [details] proposed color.map.5 man page > We really need to replace all of the explicite use of *colors* within > the portage code with *meanings* That would be ideal. But until then: here's a first shot at a color.map manpage. I don't think it's a good idea to document behavior that will certainly change in the near future. After we've replaced the hard coded colors with meanings, we can document the meanings that are available to be assigned colors. Also, the hex rgb codes from output.py should be documented, since those 16 colors are the definitive set. The teal reordering from svn r3532 has been released in 2.1.1_pre1-r2. |