[PATCH 0 of 3] keyword: bugfix commands where expansion was not filewise
Jesse Glick
jesse.glick at sun.com
Wed Jan 9 08:35:32 CST 2008
By the way, did you consider using encode/decode hooks instead of a
separate command to expand keywords? This would be more like what CVS
does (for better or for worse). E.g.
[decode]
** = expand:
[encode]
** = unexpand:
where you would want to automatically skip over binary files (those
which contain NUL).
'hg cat' and 'hg di' work on the unexpanded versions, which is probably
what you want; the keywords would just get expanded in the working copy.
An irritation is that Hg does not permit encode/decode hooks to be
composed, so for Windows usage you would to add 'expandwithcrlf' and
'unexpandwithcrlf' variants.
More information about the Mercurial-devel
mailing list