On Sat, Sep 5, 2015 at 2:49 PM, Florian Balmer <florian.bal...@gmail.com> wrote:
> I'd be happy if these small adaptations could be made. However I'm not > sure if there's a policy to require branch colors to fit the #xxxxxx > format, so that values like #feb (and also 'gold') are invalid in the > first place, and whether hash_color() may always return colors that > bg_to_fg() is able to handle without over/underflows, so that using > custom branch colors outside the "moderate hash_color() range" is > generally not advised. > If i'm not mistaken, Fossil accepts any color string which a user agent can deal with. It does handle '#xxxxxx' in placed, but i don't _think_ it strictly requires that format. e.g. 'red' should be acceptable, with the caveat that functions which derive other colors from hex codes won't work with such strings. -- ----- stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal "Freedom is sloppy. But since tyranny's the only guaranteed byproduct of those who insist on a perfect world, freedom will have to do." -- Bigby Wolf
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
