Hi,
I've found a problem with dvc-diff-jump-to-change and
dvc-diff-diff-or-list when invoked from a bzr-status buffer.
The problem is that 'bzr status' produces output like this:
conflicts:
Text conflict in src/foo.c
When jump-to-change is invoked, it looks for a file named "Text
conflict in src/foo.c", which of course doesn't exist. A similar
problem applies to diff-or-list. It also doesn't know what to do with
pending merge lines, but that's not important to me right now.
I thought 'bzr status --short' might produce cleaner output, but it
doesn't really help with this problem:
C Text conflict in src/ed/lsm_derivs.f90
I took a look at the source of dvc-diff-jump-to-change. Looks like
this is going to require backend-specific code for bzr. If nobody has
time to deal with this I'm willing to give it a try, but somebody will
have to give me suggestions about where to put the bzr-specific
parsing, and how the dispatch will work. I'm not familiar with how
ewoc works, if that's going to be important.
Regards,
Dan
_______________________________________________
Dvc-dev mailing list
[email protected]
https://mail.gna.org/listinfo/dvc-dev
