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

Use pathto to display nonexisting files

kwexpand/kwshrink: warn about nonexisting files

_overwrite method for kwrepo.commit, kwexpand, kwshrink File selection (kwexpand/kwshrink) in _kwfwrite method.

Sort files before overwriting

_iskwfile checking method for kwrepo.commit, kwexpand/kwshrink

Walk manifest in kwexpand/kwshrink

For overwriting commands use node and manifest to speed up walk

kwfiles: change option "ignored" to "ignore", add option "untracked" "ignore" like corresponding config value. "untracked" allows quick check if a new file that has not been added yet would be target for expansion. Update help accordingly.

File collections specific to kwexpand/kwshrink vs kwfiles commands

Flag kwfiles if verbose; shorten bailout code

Tighten condition for kwshrink/kwexpand test

Underscore prefixes only for names at top level, or compatibility wrappers

Count keywords in a customized kwfilelog read method

walkopts for kwexpand, kwshrink, kwfiles commands kwfiles optionally shows ignored files or all flagged Use pathto method to print kw filenames if possible. Commands abort with meaningful error _weedcandidates renamed to _weedfiles, and only for commands. For kwrepo.commit we could get modified + added from kwrepo.status(match=ui.kwfmatcher) -- but this would mean to read manifest before commit, and again after for expansion.

kwfiles notifies if there are no files configured for expansion

Bail out earlier in overwrite commands if repo has changes

Make kwfmatcher an ui attribute Thus kw commands do not weed candidates twice.

Unlowercase command help

Test kwfiles working context

Determine kwfiles on workingctx Added but not yet committed files should be shown. Removed but not yet committed files should not be shown.

test: use grep instead of grep -F

Test if debug flag influences expansion

Turn off debug while expanding We don't need templates like file_add etc. as keywords a file specific. Turning off debug avoids accidental expansion of such templates. As a side effect it speeds up expansion when running hg --debug. Functionality of _ctxnode now in new _substitute function.

Map re.escape

List comprehension instead of loop to create ui template dictionary

String format keyword pattern before compilation

Ignore errors when removing temp dir in kwdemo

Reduce verbosity of kwexpand/kwshrink

Make kwfilelog.cmp test reliable

Use revlog.cmp to avoid checking for rename twice

Test kwfiles command

New command "kwfiles" prints files configured for expansion

Always exclude .hgtags only .hgtags is the only tracked file that is written to just by issuing an hg command. This ensures that even a very unlikely tag like "$Id$" is processed properly.

Use Mercurial's getcwd()

Set boolean mandatory arguments directly and comment them

Avoid calling kwfmatcher twice (kwtemplater.overwrite, kwrepo.file) when overwriting _weedcandidates already checks if file is configured for keyword substitution.

Test kwshrink w/ argument while not in top level directory