-
Notifications
You must be signed in to change notification settings - Fork 98
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
--enable-filters not behaving as expected #306
Comments
Defining the class in a Python file like below doesn't work either. @register_filter
class AllFilter(Filter):
message = 'Running on all messages (allegedly)'
tags_blacklist = "new" |
Hey @xaltsc ,
This can be done, by using a notmuch query (https://www.mankier.com/7/notmuch-search-terms#Date_and_Time_Search), # Select only the last year mails
$ afew --tag date:2Y..1Y
I suppose that's because it should be defined in the config file. Please copy you config, that we can check it, try to call you filter without -R or -T but only notmuch query, |
Old bug, but probably same root cause as I just encountered: selecting filters with |
And sure enough this is ussue #40 which I even commented on back then ... Oh well. I guess I don't need |
Hey,
Perhaps I misunderstood the documentation, but I've got this piece in my config, which should be minimal enough, and with the aim of using it not on new messages, but only on old messages.
However, when running
afew -d --tag --all -vv -e 'AllFilter' -R 100000000000000 -T 1000000000000000000000000
, the output I get is this below, meaning thatAllFilter.0
has not been taken into account.Note, however, that
AllFilter.0
is run when dropping the-e
option.The text was updated successfully, but these errors were encountered: