I am currently trying to write a new extension to meet the needs of my
workplace, and am having a hard time getting it to work right with
TortoiseHg.
I am implementing hooks (pre-commit, update, post-status) using the
appropriate code [ui.setconfig(...)] in uisetup/extstup/reposetup.
Everything works fine from the command-line, and it *almost* works from
within TortoiseHg. Of course, the post-status hook is meaningless in
TortiseHg. But the update hook fires off and does exactly what it is
supposed to. It is the pre-commit hook that I am having problems with.
The code for the pre-commit hook works perfectly from command-line, but
doesn't even seem to be accessed when committing from TortoiseHg. I even
tried substituting the [extensions.wrapcommand(...)] method instead of using
the hook to no avail. I can not figure out how to intercept the commit
event from within TortoiseHg. The output log looks like it
is simply calling "hg commit ..." but there must be more to it than that or
it should work the same as it does from the command-line.
How to I trigger code in my extension to run at the beginning of a commit
that was initiated from TortoiseHg?
Here is my configuration information:
OS: Windows XP SP3
TortoiseHg ver. 2.0.0
Hg ver. 1.8.3 (from TortoiseHg package)
Pythom ver. 2.6.6 (from TortoiseHg package)
Thanks for the help,
Nathan Durnan
------------------------------------------------------------------------------
What Every C/C++ and Fortran developer Should Know!
Read this article and learn how Intel has extended the reach of its
next-generation tools to help Windows* and Linux* C/C++ and Fortran
developers boost performance applications - including clusters.
http://p.sf.net/sfu/intel-dev2devmay
_______________________________________________
Tortoisehg-discuss mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/tortoisehg-discuss
