Moving on with my stream of RFCs, today it's COLORS! We inherit the colors from hgrc, such as color.status.added, but this is not a good idea since users will generally set these with the underlying expectation that they are shown against a black background.
The default colors happen to look ok on both black and white, except for status.deleted which is then hard-coded to a different color in changeset 1d113569d4b6 by Steve. This, however, does no work if it's overridden in the config. I propose we introduce new keywords, thgstatus.* or whatever, and set the default colors as we like them (probably like the defaults for status.* plus the change in the mentioned changeset), and then accept that changes to status.* aren't propagated; this will more often than not be a good thing. Thoughts? /Sune ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-novd2d _______________________________________________ Tortoisehg-develop mailing list Tortoisehg-develop@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/tortoisehg-develop
