To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Child items
...
Show closed items
Linked items
0
Link issues together to show that they're related.
Learn more.
Activity
Sort or filter
Newest first
Oldest first
Show all activity
Show comments only
Show history only
Chris Lambchanged title from suport external diff tools such as meld and kdiff3 --diftool to Please support external diff tools such as meld and kdiff3 --diftool
changed title from suport external diff tools such as meld and kdiff3 --diftool to Please support external diff tools such as meld and kdiff3 --diftool
Hi @adrelanos-guest, thanks for your request. I'm a little lost how diffoscope might plug into these tools though as, as you know, diffoscope supports nested diffs whilst meld and similar operate on a single "flat" level.
Yes, probably can't mix multiple/all files into one diff viewer process.
Similar to how git interacts great with graphical diff viewers. For each
file that needs diffing, open a new process. The process would be
blocking and therefore diffoscope would wait until that process terminated.
Ah, interesting idea indeed. Just to understand a bit more, what would you have diffoscope do in the case of detecting changes in the metadata of an archive? For example:
That is a good question. Didn't consider this. --difftool maybe cannot
be a full replacement for the current replacement. Just an additional
convince feature. You could just run "meld /home/lamby/Downloads/a.apk
/home/lamby/Downloads/b.apk" as "simple" implementation and call it a
day. Leave it to that diff viewer. Realistically that diff viewer
wouldn't show anything interesting. But it would hint the diffoscope to
also run without --difftool to see something more helpful.
The part that I was diffing when I wrote this feature request was
unrelated to metadata.
And/or additionally echoing this out to stdout as you are currently doing.