workbench with relative synchronisation path fails when current path is different from repo path
Created originally on Bitbucket by tswaehn (Sven Ginka)
when opening the workbench via win-explorer it seems that relative synchronisation paths will be translated incorrectly. the translation begins in the current directory instead of looking up the repo's default path and applying the relative path to that default repo path.
example:
current path is c:\temp
repo path is ** L:\myRepocontainer\project1**
sync path is ....\mySyncContainer\project1
it seems to sync with c:\mySyncContainer\project1 instead of L:\mySycnContainer\project1
{{{ % hg --repository L:\myRepoContainer\project1 pull --verbose ....\mySyncContainer\project1 repository ....\mySyncContainer\project1 not found [command returned code 255 Tue Mar 22 18:23:50 2011] project1% }}}
however when beeing in the correct path when opening the workbench: L:\myRepoContainer\project1 everything is fine as can be seen here:
{{{ % hg --repository L:\myRepoContainer\project1 pull --verbose ....\mySyncContainer\project1 pulling from ....\mySyncContainer\project1 searching for changes no changes found [command completed successfully Tue Mar 22 18:25:51 2011] project1% }}}
the only difference is the current path when opening the workbench. setting the current-path-variable for the hg command might be an option.
tested with: TortoiseHg version 2.0.2 with Mercurial-1.8.1, Python-2.6.6, PyQt-4.8.2, Qt-4.7.1
best
-tswaehn