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 711458 - Meld File Filters does not seem to work
Meld File Filters does not seem to work
Status: RESOLVED DUPLICATE of bug 684400
Product: meld
Classification: Other
Component: general
1.8.x
Other Linux
: Normal normal
: ---
Assigned To: meld-maint
meld-maint
Depends on:
Blocks:
 
 
Reported: 2013-11-05 07:52 UTC by Igal
Modified: 2013-11-09 22:02 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
show's status bar while meld is scanning the .meteor folder (35.45 KB, image/png)
2013-11-05 07:53 UTC, Igal
Details
screenshot, ignore .meteor filter (54.23 KB, image/png)
2013-11-05 07:55 UTC, Igal
Details

Description Igal 2013-11-05 07:52:14 UTC
Meld does not seem to take into account a custom "File Filters" rule to ignore a folder.

I defined a new rule to ignore a .meteor folder. Nevertheless, when meld loads it hangs for a few seconds scanning the .meteor folder. I presume that's the case because it shows "Scanning .meteor/local/build/..." at the status bar. 

There are hundreds of files under .meteor. Waiting until meld scans all of them vs my ten relevant project files is quite frustrating. 

Is this a bug? If not, can someone tell what am I missing?
Thanks!

---
some details:

$ lsb_release -a
...
Description:	Ubuntu 13.10

$ dpkg -l meld | grep ii
ii  meld                                  1.8.1-1
Comment 1 Igal 2013-11-05 07:53:26 UTC
Created attachment 258984 [details]
show's status bar while meld is scanning the .meteor folder
Comment 2 Igal 2013-11-05 07:55:12 UTC
Created attachment 258986 [details]
screenshot, ignore .meteor filter
Comment 3 Kai Willadsen 2013-11-07 19:48:36 UTC
The behaviour you're seeing is the intended behaviour... mostly. Filters are intentionally not applied to version control comparisons; they're for folder comparisons only. The idea is that a version control comparison should always show you exactly what the VC sees.

Having said that, we should limit scanning of folders that the VC ignores, and don't do that currently (see bug 684400).

Does that sound like it would reasonably solve your problem?
Comment 4 Igal 2013-11-07 21:50:41 UTC
yes, a fix for bug 684400 will solve my problem. Thanks!
Comment 5 Kai Willadsen 2013-11-09 22:02:54 UTC
Cheers.

*** This bug has been marked as a duplicate of bug 684400 ***