66 Again, run "hg kwdemo" to control the results of your config changes. |
66 Again, run "hg kwdemo" to control the results of your config changes. |
67 |
67 |
68 Before changing/disabling active keywords, run "hg kwshrink" to avoid |
68 Before changing/disabling active keywords, run "hg kwshrink" to avoid |
69 the risk of inadvertedly storing expanded keywords in the change history. |
69 the risk of inadvertedly storing expanded keywords in the change history. |
70 |
70 |
|
71 To force expansion after enabling it, or a configuration change, run |
|
72 "hg kwexpand". |
|
73 |
71 Expansions spanning more than one line and incremental expansions, |
74 Expansions spanning more than one line and incremental expansions, |
72 like CVS' $Log$, are not supported. A keyword template map |
75 like CVS' $Log$, are not supported. A keyword template map |
73 "Log = {desc}" expands to the first line of the changeset description. |
76 "Log = {desc}" expands to the first line of the changeset description. |
74 |
77 |
75 Caveat: "hg import" fails if the patch context contains an active |
78 Caveat: "hg import" fails if the patch context contains an active |
76 keyword. In that case run "hg kwshrink", reimport, and then |
79 keyword. In that case run "hg kwshrink", and then reimport. |
77 "hg kwexpand". |
|
78 Or, better, use bundle/unbundle to share changes. |
80 Or, better, use bundle/unbundle to share changes. |
79 ''' |
81 ''' |
80 |
82 |
81 from mercurial import commands, cmdutil, context, fancyopts |
83 from mercurial import commands, cmdutil, context, fancyopts |
82 from mercurial import filelog, localrepo, templater, util, hg |
84 from mercurial import filelog, localrepo, templater, util, hg |