Re: Unable to use file filter to filter directories

[Ben Joldersma <ben joldersma 5to1 com>]

Unfortunately I am unable to use these steps to success.

I was wondering - maybe my configuration settings from 1.2 are conflicting somehow?  I tried removing them, but I found them in several places - .gconf/apps/meld, .gconf/apps/gnome-settings, ~/.gnome2.  i tried removing all of them, but the settings still show up.

I will file a bug unless people think that is worth trying first.

Thanks for the help!

--ben

On Sat, Sep 19, 2009 at 3:06 PM, Kai Willadsen <kai willadsen gmail com> wrote:

2009/9/19 Ben Joldersma <ben joldersma 5to1 com>:

> First off,
> Absolutely *love* meld.  Thanks so much for making such a great tool.  All
> my co-workers are jealous (who don't use linux that is!)
> We've got some third party libraries in our source tree that we rarely
> change.  I'd like to exclude them, because they contain several thousand
> files and it takes a while to do the initial scan.  I tried setting some
> variations of what I think are valid shell globs in the file filters
> section, where directory to exclude is named 'foo':
>
> 'foo'
> 'foo/*'
> 'foo/**/*'
> '/foo/'
> 'path/to/foo/*'
>
> I'm not too sure what else I can try.  I disabled the version control
> exclude pattern, but it didn't seem to include the .svn directories either.
>
> Any thoughts?  Am I missing something?  Is there a bug?
> Thanks again for such an incredibly useful tool - 1.3 is awesome!

So I can make this work for me by defining and enabling the filter
"foo", but I have to restart Meld after creating the new file filter.
The fact that it needs to be restarted is definitely a bug. However,
if it doesn't work for you even after restarting, then there may well
be a second bug hanging around. Feel free to file these in bugzilla.

cheers,
Kai