After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 763693 - Jump to next/previous file which really differs
Jump to next/previous file which really differs
Status: RESOLVED OBSOLETE
Product: meld
Classification: Other
Component: dirdiff
unspecified
Other All
: Normal enhancement
: ---
Assigned To: meld-maint
meld-maint
Depends on:
Blocks:
 
 
Reported: 2016-03-15 14:23 UTC by Egor
Modified: 2017-12-13 19:17 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Egor 2016-03-15 14:23:30 UTC 
In Folder Comparison cursor jumps to the next/previous different file when pressing buttons "Go to the next/previous change".

Unfortunately, text filters are not taken into account: cursor stops at files which are different, but not considered to be different according to text filters.
(I have option "Apply text filters during folder comparisons" checked in "Meld Preferences"->"Folder Comparisons").

Could you please add new feature "jump to next/previous file which really differs"?

This action could be bind, for example, with Shift-click on buttons "Go to the next/previous change" for using mouse, and with Shift-Ctrl-D/E for using keyboard.
Comment 1 Kai Willadsen 2016-03-20 20:06:37 UTC 
This seems reasonable to me, except that I'd say that if it makes sense to do at all, it should just be the default and only behaviour... no option.

I think this should be relative straightforward. We just need to change the set of states that dirdiff uses to figure out whether to skip over an entry when it's setting self.next_path and self.prev_path.
Comment 2 GNOME Infrastructure Team 2017-12-13 19:17:21 UTC 
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/meld/issues/105.