On Friday, February 23, 2018 at 9:04:23 AM UTC+1, H. Niemann wrote:
>
> Hello Stefan!
>
>
>
> This could be implemented by reserving a return code for “finished without
> error, go to next” and one for “finished without error, go to previous”
>
> and the calling application could react by star
Hello Stefan!
This could be implemented by reserving a return code for “finished without
error, go to next” and one for “finished without error, go to previous”
and the calling application could react by starting a new TMerge instance for
the previous / next file. Then there would be no need for
TMerge does not have the means to fetch files from a working copy,
especially not from a repository.
To make this work, we'd have to fetch and save all the possible files to a
temp location and then pass the full list to TMerge. Now imagine a commit
dialog with 200 changed files...
So no, that
Could you consider adding an option to TortoiseMerge to allow to go to
next/previous file?
Usage:
* commit changes and review them fast => you simply click svn commit, see all
changes, click the first file and select compare with base and now you want to
do this with all changed files, therefor
