Specific regular expressions depending on read mode More safeguarding against accidental (un)expansion: Reading filelog: act only on \$(kw1|kw2|..)\$ as keywords are always stored unexpanded. Reading wdir: act only on \$(kw1|kw2|..): [^$\n\r]*? \$ as we only are interested in expanded keywords in this situation. Note: we cannot use ..): [^$\n\r]+? \$ because e.g. the {branch} template might be empty. hg record is a special case as we read from the working directory and need one regex each for modified and added files. Therefore test recording an added file. This way we finally also forbid sequences like $Id: $ being treated as keywords.

     1

$Id$

     2

     3

keyword extension for Mercurial SCM

     4

===================================

     5

     6

CAVEAT: Please use the keyword extension distributed with

     7

Mercurial > 1.0.2!

     8

For Mercurial 0.9.2 to 1.0.2 install the 0.9.2compat branch.

     9

    10

The default and stable branches are meant for development.

    11

    12

install

    13

-------

    14

    15

Run "python setup.py install".

    16

See also "pyton setup.py --help".

    17

Then add the line:

    18

    19

[extensions]

    20

keyword = /path/to/hgkw/keyword.py

    21

    22

to your hgrc, where /path/to/ is somewhere in your $PYTHONPATH.

    23

    24

    25

first steps and online help

    26

---------------------------

    27

    28

$ hg help keyword 

    29

$ hg kwdemo

    30

    31

    32

testing

    33

-------

    34

    35

$ cd tests

    36

$ python run-tests.py --with-hg=/path/to/hg test-keyword