I’ve released git-wtf version bf06ab7. The highlight of this release is colorized output. ANSI escape sequences are the future of the web.
Also, the feature / integration branch comparisons is now only displayed when
-r is supplied.
Check out the git-wtf home page for an example of the fancy colorization, or just download it now.
On Tue, Aug 18, 2009 at 9:36 PM, William Morgan <comments@all-thing.net>wrote:
on quoted. settings. I’ve released git-wtf version bf06ab7. The highlight of this release is colorized output. ANSI escape sequences are the future of the web. Also, the feature / integration branch comparisons is now only displayed when
-ris supplied. Check out the “git-wtf home page”: http://git-wt-commit.rubyforge.org/#git-wtf for an example of the fancy colorization, or just “download it now”: http://git-wt-commit.rubyforge.org/git-wtf.Hi William. I hope this isn’t a dumb question, but how should I install this script so that it runs as “git wtf”, instead of having to use “git-wtf” and reference where I’ve placed the file?
How should I install this script so that it runs as “git wtf”, instead of having to use “git-wtf” and reference where I’ve placed the file?
If you place it anywhere in your path, modern gits should automatically pick it up when you run
git wtf.I’ve released git-wtf version bf06ab7. The highlight of this release is colorized output. ANSI escape sequences are the future of the web.
Hi! For me the colors didn’t work, as
'git config color.ui'returnstrueand notyes(git 1.6.3.3 / OSX 10.5) I added a condition: when “true”; trueAnd all is working now.
For me the colors didn’t work, as
'git config color.ui'returnstrueand notyes(git 1.6.3.3 / OSX 10.5) I added a condition: when “true”; trueAnd all is working now.
Thanks, I’ve fixed this in the published version. I think ‘yes’ was a mistake; it’s only checking for ‘true’ now.