bzr diff --using myapp.exe -r submit: only prints to stdout

Could someplease who sees this problem please upload a copy of bzrlog?

I have verified that I am able to launch an external GUI diff tool on WindowsXP, using bzr 1.16 installed using bzr-setup-1.16-1.exe. The diff tool I use is BeyondCompare.

I did not try specifying a revisionspec. Is this essential to the report?

In other words, does your GUI diff tool start properly if you are looking at a change between your working tree and the head of the (local) branch from which it is derived?

-M

External diff tools are working fine with bzr. The only time I am currently seeing this issue is when using "-r submit:". I use this revision option nearly every day so I can confirm that this issue is new with the recent upgrade.

Thanks!
Scott

Scott,

I have just run

   bzr diff --using <my GUI tool>

and

   bzr diff --using <my GUI tool> -r submit:

against a working copy with modifications, where bzr version is 1.16 installed from the windows installer and <my GUI tool> happens to be BeyondCompare, but I doubt that matters.

Both commands worked as expected: the GUI launched and showed the diffs.

I don't doubt what you're seeing, but is there any chance that more than one thing changed? And does anything interesting appear in bzrlog when the problem occurs?

Thanks
-M

Option --using on Windows requires full path to the diff application. I'd say probably bzr can't find your diff tool and fall back to internal implementation. I dunno.

I don't see the big problem with WinMerge, but I should note there is small problem. WinMerge is GUI diff tool, nevertheless bzr prints in the console name of changed file prefixed with 3 equal signs, e.g.

=== modified file 'foo.txt'

Perhaps I understand where from it come, but probably it should be possible to disable it.

Thanks for the help. I confirmed that "-r submit:" does work with my other repositories for files that were updated but not added. I totally forgot that all of the files in this particular repository were added and not modified so the "-r submit:" is as expected in this case. I believe that this issue can be closed.

Thanks!
Scott

Thanks for your follow-up, Scott. I think launchpad lets you close your own issues, but since I jumped into this one with both feet, I will try closing it on your behalf. (We'll see if the system permits me.) -M