Comments on: Annoyance, colored diffs in perforce

By: Jason

Jason — Fri, 09 Aug 2013 15:11:44 +0000

Thanks, very handy.

By: Let vim colorize p4 diff | parseInt('010')

Let vim colorize p4 diff | parseInt('010') — Thu, 02 Feb 2012 18:32:01 +0000

[…] to know this today from here. Share this:TwitterFacebookLinkedInLike this:LikeBe the first to like this post. This entry was […]

By: tfi fridays

tfi fridays — Tue, 25 Oct 2011 07:47:12 +0000

I am starting to take my feet on associate packages too, so this text is excellent place to begin! Shared it on Stumbleupon and submitted on Digg

By: Eric

Eric — Wed, 26 May 2010 18:43:12 +0000

Set the P4DIFF ennvironment variable to colordiff… a tool which colorizes diff output. For example:

export P4DIFF=colordiff; p4 diff -dU 5

By: David

David — Fri, 12 Mar 2010 20:15:01 +0000

If you want it even closer to a git diff, use unified mode:
p4 diff -du

By: bartman

bartman — Tue, 02 Feb 2010 02:41:54 +0000

Oh, one more thing.

Since your blog is titled :wq … I imagine you use vim. Why not let vim color your diffs?

p4 diff | vim -R –

I keep this handy shell function around:

v() { $@ | vim -R – ; }

So I can simplify the above as:

v p4 diff

… well, if I actually ever wanted to run p4 directly

By: bartman

bartman — Tue, 02 Feb 2010 02:39:38 +0000

> We recently switched from subversion to perforce (definitely not my choice, I pushed for git).

Hehe… I had the same thing happen to me recently. My solution was to start using git-p4, as I had been using git-svn before. Give it a try, it’s actually pretty good… albeit slower then git-svn.