Differences between revisions 1 and 2
Revision 1 as of 2007-01-17 20:41:39
Size: 1330
Comment: Add keyword expansion page
Revision 2 as of 2007-01-17 20:51:12
Size: 1327
Comment: fix configuration information
Deletions are marked like this. Additions are marked like this.
Line 15: Line 15:
hgext.keyword = path/to/keyword.py
#or, if keyword.py is in the hgext folder:
#hgext.keyword=
hgext.keyword=
#or, if keyword.py is in not the hgext folder:
#keyword=/path/to/keyword.py

Keyword Expansion extension

This extension is not being distributed along with Mercurial.

It's being developed by Christian Ebert and can be downloaded from its [http://www.blacktrash.org/cgi-bin/hgwebdir.cgi/hgkeyword/ keyword expansion repository].

Overview

This extension allows the expansion of RCS/CVS-like and user defined keys in Mercurial repositories.

Configuration

To enable this extension add it to the '[extensions]' stanza in the hgrc file:

[extensions]
hgext.keyword=
#or, if keyword.py is in not the hgext folder:
#keyword=/path/to/keyword.py

Additional configuration is dones in they [keyword] and [keywordmaps] sections in your configuration file:

# filename patterns for expansion are configured in this section
# files matching patterns with value 'ignore' are ignored
[keyword]
**.py =
x* = ignore
...
# in case you prefer your own keyword maps over the cvs-like defaults:
# using {{{key-to-be-expanded = value

lines, where values are taken from the avaliable Mercurial template names.[keywordmaps] HGdate = {date|rfc822date} lastlog = {desc} ## same as {desc|firstline} in this context checked in by = {author} }}}

Usage

The defined keys (or default ones) are automatically expanded, without user interaction.

KeywordExtension (last edited 2024-03-06 12:11:11 by ChristianEbert)