Replace \0 by \g<0> in python sub

> The back reference \g<0> substitutes in the entire substring
> matched by the RE.
> http://docs.python.org/2/library/re.html#re.sub

The documentation does not mention \0 as an alias to it.
Although \1 to \9 works.

I guess this alias (\0 <=> \g<0>) existed in old python version,
but it is not the case any more.

In python 2.7 and 3.3:
> import re; re.compile(r'123').sub(r'@\0@',"ab123cd")
'ab@\x00@cd' # KO
> import re; re.compile(r'123').sub(r'@\g<0>@',"ab123cd")
'ab@123@cd' # OK
Merge pull request #78: Bug fix for accelerated highlighting using Python
Support for synchronous + asynchronous tags file updates (huge refactoring)

See also pull request #49 for my previous and failed attempt:
  https://github.com/xolox/vim-easytags/pull/49
FIX: Ensure full absolute tagsfile filespec in async mode.

On Windows, tagfiles() can return a filespec that is absolute to the current drive (i.e. \foo\bar\tags). In async mode, the forked Vim process may have another current drive, so it should be ensured that the filespec is a full one, including the drive letter: D:\foo\bar\tags.
FIX: Avoid error about empty Dictionary key.

I had a degenerate tags file that had *two* tabs separating the tag from the filespec column; parsing that yields an empty filespec, which caused E713. There used to be an explicit check for that; with your recent refactorings, one instance of that check was lost. Here it is again!
Silence asynchronous tags file updates by default

This change is related to pull request #82 however that pull request
wasn't merged here (and won't be merged at all) because it was based on
the old/dead `async-cleanup' feature branch (see pull request #49 on
GitHub) instead of the new `async-take-two' feature branch (see pull
request #84 on GitHub). This change set implements the equivalent on the
new feature branch.

In addition to Ingo's comments in pull request #82, the asynchronous
message frequently disturbs me while typing a Vim command, which is kind
of annoying. If everything goes well and we can get the async mode to be
stable enough to become the default mode then the status messages will
only be interesting when debugging a problem anyway.
Disable automatic tags file updates during :vimgrep

This change is related to pull request #83 however that pull request
wasn't merged here (and won't be merged at all) because it was based on
the old/dead `async-cleanup' feature branch (see pull request #49 on
GitHub) instead of the new `async-take-two' feature branch (see pull
request #84 on GitHub). This change set implements the equivalent on the
new feature branch (without introducing another option).
Disable automatic tags file updates during session loading
Don't use :redraw in :HighlightTags during session loading
Merge pull request #86: Ensure full absolute tagsfile filespec in async mode
Merge pull request #87: Avoid error about empty Dictionary key
Bug fix for invalid tags filtering (cache.exists() was broken, now fixed)
Actually enable the automatic commands introduced in 6c7a66349ec :-)
Bug fix for Vim based syntax highlighting of tags
Refactor atomic file updates into a feature of vim-misc
Automatically create missing directories when writing tags files
Bug fix for typo introduced in 6c7a66349ec
Merge pull request #84: Asynchronous tags file updates! \o/

This is part 1/2 of speeding up the vim-easytags plug-in. Refer to the
pull request for details: https://github.com/xolox/vim-easytags/pull/84
In part 2/2 I want to speed up the dynamic syntax highlighting.
Potentially related open issues on GitHub (probably missed a few):

 - https://github.com/xolox/vim-easytags/issues/32
 - https://github.com/xolox/vim-easytags/issues/41
 - https://github.com/xolox/vim-easytags/issues/68
Credit Ingo for his work, thank other contributors as well
Support for keyword based syntax highlighting (much faster)

See the following issues on GitHub:
 - https://github.com/xolox/vim-easytags/issues/68
 - https://github.com/xolox/vim-easytags/pull/80

Please note that right now this 'feature' is not integrated with
the "accelerated Python syntax highlighting" feature, because I'm
considering ripping that out and replacing it with a *fast* Vim
script implementation (if I can build one :-).