We use it on certain files here. You basically have to change the filetypes that you want to have this behavior (to +k or +ko.) Do a p4 help filetypes for a quick summary.

To answer your next question ;), you have to check out files, then change their types, then check them back in to get this going. If you only want this on certain filetypes, you can set a typemap to default certain extensions to use keyword expansion.

The only problem we have seen (and this is usually true for any keyword expansion in any tool) is that you automatically have an extra line (or two or three or twelve) of diffs. If you use any tools to (attempt to) accurately count lines of code changed etc., these lines always show up.

I honestly can't remember who requested we do this here or why, because a majority of our developers use some sort of integration (with Visual Studio .NET) and most metadata is readily available that way. We don't have any third parties that we send code out to where this sort of data would be useful when Perforce itself is not available.

-Matt

On Tue, 26 Apr 2005 09:23:08 -0700, Zarnes, Todd <Todd_Zarnes at intuit.com> wrote: