On Tue, Feb 17, 2009 at 9:44 PM, Gary Ruben
<[email protected]> wrote:
> Hi,
>
> I had some trouble getting the keyword extension working with
> 1.1.2+tortoisehg so I thought I'd post my experience and some
> suggestions of how the Mercurial.ini file might be changed to make this
> a bit easier.
>
> In the [extensions] section of Mercurial.ini the default line is
> hgext.keyword = !
> but there's a comment saying "A leading '!' disables an extension (new
> in 0.9.5)". Since the '!' was trailing I assumed that this meant that
> keyword was enabled, but I was suspicious so I think it would be less
> confusing if the wording in the .ini file was "A trailing '!'..."
>
> I added the following sections to the Mercurial.ini file:
>
> [keyword]
> # expand keywords in all python files in working dir
> **.py =
>
> [keywordmaps]
> Author = {author|user}
> Header = {root}/{file},v {node|short} {date|utcdate} {author|user}
> Source = {root}/{file},v
> Date = {date|utcdate}
> Id = {file|basename},v {node|short} {date|utcdate} {author|user}
> Revision = {node|short}

As it turned out, this {desc} format collides with InnoSoft's string
expand functions, so I had to leave the [keywordmaps] section empty.
I included the URL to the documentation so the user can find examples
easily.

--
Steve

------------------------------------------------------------------------------
Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA
-OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise
-Strategies to boost innovation and cut costs with open source participation
-Receive a $600 discount off the registration fee with the source code: SFAD
http://p.sf.net/sfu/XcvMzF8H
_______________________________________________
Tortoisehg-discuss mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/tortoisehg-discuss

Reply via email to