Hgk and cygwin

[Steve Borho]

On Friday 22 December 2006 1:40 pm, Joe Bruce wrote:
> Unfortunately not. Based on my troubleshooting, it appears that 'tk'
> is incapable of 'exec'ing anything other than real EXEs. It refuses
> to execute any script, whether 'hg', 'hgk', or a simple shell script
> of my own making.
>
> I'd love to have this work -- 'hg view' only works under Linux for
> me. If anyone knows how to make it work, I would love to know how as
> well...

Wonderful timing.  I'm having this same exact problem even outside of 
cygwin.  My commit tool, qct, tries to spawn hg as an eternal process 
and this always fails unless hg.exe is in the path.  hg.cmd, hg.py, 
etc. are all ignored by subprocess.Popen().

Since the problem is common to Tk (wish), python, and the cygwin 
versions of the same, it must be an issue with the underlying O/S.

While we're on the topic of Windows and path issues, I've found that 
running hg.exe in a directory that has hgext/ in it will cause it to 
break, just like the mercurial/ problems mentioned by Lee Cantey.

-- 
Steve Borho (steve at ageia.com)
http://www.borho.org/~steve/steveAgeia.asc
Key fingerprint = 3D9C 67D5 F426 4322 075B  0795 C9B2 C3A0 97D0 C090