Refactor to initialize kwtemplater only once during reposetup - when overwriting kwtemplater was initialized (and the same keyword regex compiled) before and with every file read. - therefore remove overwrite from kwtemplater, and make it private method. _ matcher becomes attribute of kwtemplater. - by making kwtemplater a global, avoid adding attribute to ui.

Rename kwtemplater.t to kwtemplater.ct

Test that commit hooks are not run on interrupted commit

Do not run commit hooks if there is no node Eg. when commit is interrupted.

(0.9.2compat) do not bother about debug templates

Do not test debug templates

Make match object function private to kwtemplater.substitute

Do not bother about debug templates Speedup of debug flag toggle dubious at best. {files}, {file_adds} etc. templates do not make sense in file context, but leave decision to user; that's what kwdemo is for.

(0.9.2compat) kwfiles print code similar to commands.status

kwfiles print code similar to commands.status

Rearrange commit hook hack

Commit hook handling entirely into if-condition

(0.9.2compat) update doc strings

Add commit hook test

Postpone commit hooks until keywords are expanded If a commit hook acts on a file with keywords, it now does so on the file with keywords already expanded. Unhook all hooks with "commit" in name during kwdemo.

Avoid dispatch import, revert to simple argument parser

(0.9.2compat) avoid dispatch import, revert to simple argument parser Make nokwcommands a tuple as long as it's private. No need to import fancyopts, as we use own w/o bug. Clean overriding of findcmd. We only need simple argument parsing for command. No expensive dispatch import, also avoids potential clashes with invasive RuleDispatch (setuptools).

Make keyword against current Mercurial available as standalone extension

Branch off backwards compatible version The default branch will contain the version without the overhead for backwards compatibility. This will make a standalone extension available which works with current Mercurial.

Avoid name conflict with dispatch package(s) Thanks to Marcin Kasperski for spotting and analysing this. Message-ID: <87wsswvhbk.fsf@cauchy.softax.local> ff.

Add convert to nokwcommands (fix issue802) Is there a more general way to decide on allowed commands? Unfortunately we don't know what commands are added by extensions.

Check if there candidates before _overwrite Potentially saves calculation of node.

Arrange commands and cmdtable in alphabetical order

Tell user that kwexpand/kwshrink do not run if given files contain changes

Respect Mercurial conventions in kwdemo help

Obtaining cwd redundant in pathto wrapper

Detailed test of kwexpand/kwshrink w/ file arguments

Revert to using status for kw-commands cmdutil.bail_if_changed has to call status stat'ing working dir. This renders the whole walk experiment mute, duh. On the upside kwexpand/kwshrink can be applied to selected clean files, while there are local changes in other files. bail_if_changed compatibility wrapper not needed anymore.

Test if warning about non-existing files is triggered

cwd optional argument of _pathto to simplify _kwfwrite