Replies: 1 comment
-
First, WinMerge does not apply plugins automatically by default, so you need to select the Plugins → Automatic Unpacking menu item as shown below to apply the plugin automatically. Recent versions of WinMerge allow you to create plugin aliases and simple plugins, so try creating one as follows.
Any aliases you create can be deleted in the Plugins window. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I know WinMerge has binary diff support BUT I'm looking to diff some encrypted files. As an initial test, I thought I'd try and use xxd from vim (or any other hex dump tool) to do a test hex diff without generating temporary disk files.
Auto plugin config doesn't work. The plugin is never run, even when setting a wild card to match the file extension
Manually applying the plugin needs to be run for each side/pane. By default, it seems to retain the binary view rather than operating as a filter as it autoselects the diff not the entire file :-( If you manually select all the content then manually apply (PLugins, Scripts, Apply Filter Command the output will be replaced BUT then there is no diff :-(.
Also when manually running, the "Plugin Settings" button generates an error pop-up, "Unknown name". This part feels like a bug.
I'm not sure if the other behaviors are a bug or user problem. The documentation at https://manual.winmerge.org/en/Plugins.html (and the help file) don't have any examples.
My test is to generate 2 small binary files with the extension
.biny
so as to not trigger the hex diff viewer that's built in.Generated via:
Beta Was this translation helpful? Give feedback.
All reactions