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