TortoiseHg 0.8 and pull error

[Craig McQueen]

Steve Borho wrote:
> On Wed, Jul 8, 2009 at 12:15 AM, Steve Borho<steve at borho.org> wrote:
>   
>> On Tue, Jul 7, 2009 at 11:55 PM, Craig
>> McQueen<mcqueen-c at edsrd1.yzk.co.jp> wrote:
>>     
>>> Steve Borho wrote:
>>>
>>> On Tue, Jul 7, 2009 at 10:04 PM, Steve Borho<steve at borho.org> wrote:
>>>
>>>
>>> On Tue, Jul 7, 2009 at 9:43 PM, Craig McQueen<mcqueen-c at edsrd1.yzk.co.jp>
>>> wrote:
>>>
>>>
>>> Hello folks,
>>>
>>> Sorry if this is a stupid question...
>>>
>>> In TortoiseHg 0.8 on Windows XP, if I select "Synchronise" then click "Pull"
>>> in TortoiseHg, it is telling me:
>>>
>>> (None, GetoptError('option --nofork not recognized', 'nofork'))
>>>
>>>
>>> The only other person who reported this had the fixutf8 extension loaded.
>>>
>>> http://bitbucket.org/tortoisehg/stable/issue/297
>>>
>>> I have no idea how that error ends up in the synchronize output
>>> window.  Was there a valid path entered to pull from?
>>>
>>>
>>> Other random questions:
>>>
>>> Do you happen to have another copy of THG installed?
>>> Was that text in red?
>>> Was the URL http:// or ssh://?
>>> Do the other buttons give the same error?
>>>
>>> Lastly.  Could you try this from a command prompt:
>>>
>>> set THGDEBUG=1
>>> hgtk synch
>>>
>>> And check if there is spew on the console when you press 'Pull'?
>>>
>>> --
>>> Steve Borho
>>>
>>>
>>>
>>> No other copies of THG installed.
>>> Yes text was red.
>>> URL was https:// or local file. The repository I'm working with was pulling
>>> from a USB key with filename p:\Mercurial\reponame.
>>> It also happens when I try "push", "incoming", "outgoing".
>>> It only happens when I start THG from Explorer. If I start it from the
>>> command line with 'hgtk synch' then I just get the message 'sync [command
>>> interrupted]' (in red).
>>> I tried THGDEBUG=1 but saw no extra text.
>>>       
>> Thanks for humouring me.  Now I'm real curious how fixutf8 can cause that.
>>     
>
> Without even looking at, I understand now what is happening.  fixutf8
> is monkeypatching Mercurial's dispatch() function and replacing my
> ['pull', 'url', '--verbose'] arguments with unicode safe version of
> sys.argv[1:]  (['--nofork', 'sync'] when launched from explorer, just
> ['sync'] when launched from the command line).
>
> So it's safe to say fixutf8 as it's currently implemented cannot
> interoperate safely with THG.
>
> --
> Steve Borho
>
>
>   
Hmm, sounds about right. I guess the fixutf8 extension should be 
regarded as a "hack fix" at the moment. So Mercurial support for 
non-ASCII filenames is not really production-quality.

Regards,
Craig McQueen

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://selenic.com/pipermail/mercurial/attachments/20090708/cd41e894/attachment.htm