TortoiseHg clone behaviour is anomalous compared to standard Mercurial clone command.
Created originally on Bitbucket by Neutrino_Sunset (Neutrino Sunset)
c:\mydir> hg clone \share\project
(That should be c:\mydir> hg clone share\project) What is with this entry form, why is it rewriting my fracking path?
Anyway, this command clones 'project' into directory 'mydir'. However the same operation performed using TortoiseHg behaves differently and in a manner which is counterintuitive and unhelpful.
Open 'mydir' in Windows Explorer, right click in its file and folder view and selecting TortoiseHg->Clone, enter the source path and click ok. Instead of it pulling a new clone of 'project' into 'mydir' it instead turns 'mydir' into a cloned copy of 'project' named 'mydir'.
In the TortoiseHg->Clone dialog there is no Destination drop down option to have the newly cloned repository live in its own directory with the same name as the source, nor does this facility appear to be available from the 'Options'.
It appears the only way to get the standard Mercurial clone functionality using TortoiseHg is to manually create the target directory first and then call TortoiseHg clone in that directory, or manually edit the target path, which seems pointlessly unnecessary and enough of a pain in the arse that I just use the command line instead and do it in one go.
I can't think of any use case in which the current TortoiseHg behaviour in this regard in anything other than a ball ache, and imo the standard Mercurial behaviour should ideally be the default, or at the very least an easy to select option requiring minimal manual intervention.