Wincent Colaiuta <win@xxxxxxxxxxx> writes:
>>> Any feedback or suggestions before I get in too deep?
>>
>> I personally find your "prposal" picture too loud to my eye.
>
> Yes, mine too. I wouldn't actually use those colors in practice.
> (Doubly so because the "removed" color looks like the "whitespace
> error" color.)
I did not mean that your choice of colors is loud. Not at all. What I
meant was the use of color _everywhere_ makes it too loud, and also the
use of _larger number of_ colors makes it too loud.. In other words, you
are painting the output more than what the current output does, and that
made me find it too loud, no matter what the choice of colors are.
You might have misunderstood my illustration, but what I meant to suggest
was to leave most of the characters on both - and + lines in monochrome
(or whatever the "normal" is), and paint _only_ the words that are
different. The outcome would become _less_ colorful than the current
"whole -/+ lines are painted" output, but "only different words are
coloured; the words that are unmodified are left uncoloured, without
distracting the eyes." Much less louder than even the current one, yet
giving more information.
As -/+ has a marker value, I think colouring them may be Ok, too. That
would make something like this:
| {
|<red>-</red> <gray>local subcommands="add rm show prune<gray> <red>update</red>"
|<green>+</green> local subcommands="add <green>rename</green> rm show prune"
| if ...
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
