Only initialize kwtemplater in kwfilelog if needed

Use full power of util.matcher for kwfmatches()

Simply dict() keywordmaps configitems

Emergency brake against multiline expansion As expansion always happens ad hoc, is not tracked, multiline or incremental expansion do not seem worth the trouble. If at all, it would make sense with static, hardcoded keywords.

More doc, link to KeywordPlan

No need to read changelog in show(); node mandatory arg for expand()

Just re-bin the node kwarg of the hook, instead of using changelog

Same as for hardcoded branch: omit hooktype test, return w/o explicit value

Omit hook test; return w/o explicit value (==False)

No clumsy setting of node in kwfilelog.add, pass as kwarg

Expansion entirely in kwfilectx.expand()

Implement custom keyword map templates in hgrc More expensive than hardcoded keywords. But, of course, more flexible. ATM templates can only be set in hgrc, and perhaps this is enough.

Indentation cosmetics

Clean keyword arg assignment in kwfilelog.add; rename utc() to utcdate()

Init context.filectx only once per file with class kwfilectx This way context.filectx is not initialized for every keyword match.

Added tag very_cvs for changeset 2e930f842242

Very CVS-like format

Functions instead of variables in kwexpand() Should be slightly faster as filectx is asked only on demand.

Module detection cleaner and more reliable Stolen from mercurial.lsprof

Only extend sys.path if needed

Discard head of modular branch

Discard head of decodefilter branch

Make pretxncommit hook work even if extension not in hgext folder

Cosmetics: var name kwfmatchers, remove some line continuations

Add keyword; comment backwards compatible import

Implement self initializing pretxncommit hook This is more expensive than overriding commit(), but a) uses more "official" interface b) less code c) easier to maintain Get all changes up to cee5fef33cf8 in here as well.

Fix timezone expando in doc

Make changes from last cset 474b415433a1 available to 0.9.3

Unexpanded storage hopefully covered now by adding kwfilelog.add (again!) All filelog methods that act on text/data should be consistent. Principle: read expanded kw's; unexpanded kw's for "internal" workings. kwfilelog.iskwcandidate() to check whether keyword action required. More doc.

Check against keyword config in kwfilelog.cmp; be silent in kwfilelog (0.9.3)