summaryrefslogtreecommitdiff
path: root/t/t5515/fetch.br-config-glob-merge_config-glob
diff options
context:
space:
mode:
authorLibravatar Xavier Maillard <zedek@gnu.org>2007-03-28 18:44:34 +0200
committerLibravatar Junio C Hamano <junkio@cox.net>2007-03-31 23:58:10 -0700
commit3cc5ca3923c4db78d638fb94a3dfb70f103267bf (patch)
treedc24583911f042059515ab336974f2f9ea87b423 /t/t5515/fetch.br-config-glob-merge_config-glob
parentgit-blame.el: separate git-blame-mode to ease maintenance (diff)
downloadtgif-3cc5ca3923c4db78d638fb94a3dfb70f103267bf.tar.xz
git-blame.el: pick a set of random colors for each git-blame turn
I thought it would be cool to have different set of colors for each git-blame-mode. Function `git-blame-new-commit' does this for us picking when possible, a random colors based on the set we build on startup. When it fails, `git-blame-ancient-color' will be used. We also take care not to use the same color more than once (thank you David Kågedal, really). * Prevent (future possible) namespace clash by renaming `color-scale' into `git-blame-color-scale'. Definition has been changed to be more in the "lisp" way (thanks for help to #emacs). Also added a small description of what it does. * Added docstrings at some point and instructed defvar when a variable was candidate to customisation by users. * Added missing defvar to silent byte-compilers (git-blame-file, git-blame-current) * Do not require 'cl at startup * Added more informations on compatibility Signed-off-by: Xavier Maillard <zedek@gnu.org> Acked-by: David Kågedal <davidk@lysator.liu.se> Signed-off-by: Junio C Hamano <junkio@cox.net>
Diffstat (limited to 't/t5515/fetch.br-config-glob-merge_config-glob')
0 files changed, 0 insertions, 0 deletions