20 The default template mappings (view with "hg kwdemo -d") can be replaced |
20 The default template mappings (view with "hg kwdemo -d") can be replaced |
21 with customized keywords and templates. |
21 with customized keywords and templates. |
22 Again, run "hg kwdemo" to control the results of your config changes. |
22 Again, run "hg kwdemo" to control the results of your config changes. |
23 Before changing/disabling active keywords, run "hg kwshrink" to avoid |
23 Before changing/disabling active keywords, run "hg kwshrink" to avoid |
24 the risk of inadvertedly storing expanded keywords in the change history. |
24 the risk of inadvertedly storing expanded keywords in the change history. |
|
25 To force expansion after enabling it, or a configuration change, run |
|
26 "hg kwexpand". |
25 Expansions spanning more than one line and incremental expansions, |
27 Expansions spanning more than one line and incremental expansions, |
26 like CVS' $Log$, are not supported. A keyword template map |
28 like CVS' $Log$, are not supported. A keyword template map |
27 "Log = {desc}" expands to the first line of the changeset description. |
29 "Log = {desc}" expands to the first line of the changeset description. |
28 Caveat: "hg import" fails if the patch context contains an active |
30 Caveat: "hg import" fails if the patch context contains an active |
29 keyword. In that case run "hg kwshrink", reimport, and then |
31 keyword. In that case run "hg kwshrink", and then reimport. |
30 "hg kwexpand". |
|
31 Or, better, use bundle/unbundle to share changes. |
32 Or, better, use bundle/unbundle to share changes. |
32 kwdemo print [keywordmaps] configuration and an expansion example |
33 kwdemo print [keywordmaps] configuration and an expansion example |
33 kwexpand expand keywords in working directory |
34 kwexpand expand keywords in working directory |
34 kwshrink revert expanded keywords in working directory |
35 kwshrink revert expanded keywords in working directory |
35 % hg kwdemo |
36 % hg kwdemo |