From: Justus Winter <4winter@informatik.uni-hamburg.de>
To: Patrick Totzke <patricktotzke@googlemail.com>, notmuch@notmuchmail.org
Subject: Re: [afew] announcing afew, an universal tagging solution with some fancy features
Date: Mon, 19 Dec 2011 15:13:51 +0100 [thread overview]
Message-ID: <E1RcdyR-0003Vn-Ny@thinkbox.jade-hamburg.de> (raw)
In-Reply-To: <4ee8d62a.596ee30a.1833.ffffc33e@mx.google.com>
[-- Attachment #1: Type: text/plain, Size: 2307 bytes --]
Hey Pazz :)
Quoting Patrick Totzke (2011-12-14 17:59:43)
>Hi Justus,
>
>I have just tried your script and have some questions/remarks about it:
>
>* mkdir -p ~/.config/afew ~/.local/share/afew/categories
> As far as I can see, this is not needed if one doesn't use ClassifyingFilter,
> so its OK not to do this directly from the setup.py somehow.
> But it would be nice if a first run uf `afew --learn` would
> create these (or die gracefully instead of raising the afew.DBACL.BackendError).
Ah yes. Good point...
>* if you renamed the README & co to include the suffix ".md" github would nicely
> render them on the project page.
Will do that.
>* I need some more info on how the config works: first, the order in which the
> sections are defined specifies the filter-pipeline yes?
Yes.
> Secondly, what exactly is a "filter object" in the config?
Well, you can define filter types either in the configuration file or
in pure python code (see afew/filters). To use them, you need to
create instances of these types.
The config file is just another way of defining python classes and
creating objects. See afew/Settings.py for details.
> Specifically, what do these 3 lines do:
> https://github.com/teythoon/afew/blob/master/docs/tag_filters#L39
They create two objects (ShitFilter.0 and ShitFilter.1) of type
ShitFilter (defined in line 32-33). ShitFilter inherits from
SpamFilter and adjusts the message field. ShitFilter.1 also customizes
the message.
>* this is surely a user error: I cannot use afew for initial tagging as expected:
> I installed as stated in the README,
> trained some of my existing tags and called `afew --update-reference` and `afew --update`.
> The test with `afew --classify -- ..` works nicely.
> Now I tagges all my mails with is:new, and called `afew --tag --new`.
> This returns immediately without output and all my messages are still tagged new.
> Also, -vv does not result in any output..
> ideas?
Is your new tag called 'is:new'? Mine is just called 'new'. That could
be a problem since 'new' as tag for new mails is currently hardcoded
at various locations. I thought it was universally accepted, but then
again hardcoding these things is obviously a bad practice...
Cheers,
Justus
[-- Attachment #2: .signature --]
[-- Type: application/octet-stream, Size: 17 bytes --]
love u alot @,@
next prev parent reply other threads:[~2011-12-19 14:14 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-14 10:42 [afew] announcing afew, an universal tagging solution with some fancy features Justus Winter
2011-12-14 11:24 ` [afew] announcing afew, Kazuo Teramoto
2011-12-14 12:10 ` Justus Winter
2011-12-14 13:07 ` [afew] announcing afew, an universal tagging solution with some fancy features Jani Nikula
2011-12-14 16:59 ` Patrick Totzke
2011-12-19 14:13 ` Justus Winter [this message]
2011-12-19 17:57 ` Jameson Graef Rollins
2011-12-19 18:17 ` Patrick Totzke
2011-12-21 8:53 ` Justus Winter
2012-01-20 10:40 ` Patrick Totzke
2012-01-20 11:26 ` Justus Winter
2012-01-20 21:55 ` Kazuo Teramoto
2012-01-21 0:13 ` Justus Winter
2011-12-21 8:38 ` Justus Winter
2012-02-27 21:10 ` James Vasile
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E1RcdyR-0003Vn-Ny@thinkbox.jade-hamburg.de \
--to=4winter@informatik.uni-hamburg.de \
--cc=notmuch@notmuchmail.org \
--cc=patricktotzke@googlemail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://yhetil.org/notmuch.git/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).