I have this same problem. I do software development and when I am doing
testing I don't want items from the test directories showing up. Having
all that noise (a *LOT* of it) makes zeitgeist useless to me. (Some
convoluted global turn recording off and on again system may also work
but would be
I am with Markus here. You might also want to blacklist files which
contain a seven-letter palindrome in the URI, but only when Jupiter
aligns with Mars - that's up to you! ;-)
'*private*' is not a good use case imho. For instance there is a unity-
private/ directory in the Unity sources. What
OK, I don't feel like arguing about this now so I'll forget it (until
someone else requests it).
By the way, there's also another topic which is the big kill switch
(aka firefox private mode); any comments on how we want to implement
this? Two new D-Bus methods in the D-Bus extension (Set/Get) to
From my point of view this bug is Wont't fix as using (event-) templates for
almost everything in zeitgeist is a well discussed design decission, and
1.) we don't support *boo* queries, only boo*
2.) I don't think it makes sense to not use event_templates in blacklists
And if you *really* want
Hey,
2010/7/9 Markus Korn thek...@gmx.de:
1.) we don't support *boo* queries, only boo*
Well, this isn't a querym, Blacklisting is something completely unrelated.
As a side note: Why do you want to block an event just because it has
'private' in its uri?
Why not? It's my choice what I want
5 matches
Mail list logo
