On 07.01.2010 20:08, Steve Borho wrote:
> Mercurial looks in the directory of it's executable for Mercurial.ini.
> In your source install case, this is probably C:\Python26. So it
> never picks up the installed merge-tools config.
>
> Running 'hg showconfig' and 'hg.exe showconfig' is usually helpful.
I didn't run hg, I ran 'hgtk log'.
Entering 'hg serve' in a cmd.exe terminal here and checking with Process
Explorer
shows that the hg.exe process executes the image 'C:\Program
Files\TortoiseHg\hg.exe'
In C:\Python26 there is no hg.exe, hg.bat or anything like that.
In C:\Python26\Scripts I see a 'hg.bat' file and a file 'hg', but that path
('C:\Python26\Scripts') isn't in the PATH environment variable here.
Experimenting with 'hg showconfig' and entering distinctive test settings
in 'C:\Program Files\TortoiseHg\Mercurial.ini' here proves that it
picks up 'C:\Program Files\TortoiseHg\Mercurial.ini'.
(Process Explorer is a very nice tool BTW, it can even show the environment
of any running process)
------------------------------------------------------------------------------
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev
_______________________________________________
Tortoisehg-discuss mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/tortoisehg-discuss
