From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from localhost (localhost [127.0.0.1]) by olra.theworths.org (Postfix) with ESMTP id B9C59431FD0 for ; Mon, 19 Dec 2011 06:14:02 -0800 (PST) X-Virus-Scanned: Debian amavisd-new at olra.theworths.org X-Spam-Flag: NO X-Spam-Score: 0 X-Spam-Level: X-Spam-Status: No, score=0 tagged_above=-999 required=5 tests=[none] autolearn=disabled Received: from olra.theworths.org ([127.0.0.1]) by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZARqxAPBOeTg for ; Mon, 19 Dec 2011 06:14:02 -0800 (PST) Received: from mail.cryptobitch.de (cryptobitch.de [88.198.7.68]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by olra.theworths.org (Postfix) with ESMTPS id E48E0431FB6 for ; Mon, 19 Dec 2011 06:14:01 -0800 (PST) Received: from mail.jade-hamburg.de (unknown [85.183.11.228]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.cryptobitch.de (Postfix) with ESMTPSA id 04F7950FDE9 for ; Mon, 19 Dec 2011 15:14:00 +0100 (CET) Received: by mail.jade-hamburg.de (Postfix, from userid 401) id 1E735DF2A1; Mon, 19 Dec 2011 15:13:59 +0100 (CET) Received: from thinkbox.jade-hamburg.de (unknown [85.183.11.228]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: teythoon) by mail.jade-hamburg.de (Postfix) with ESMTPSA id 09AEADF29F; Mon, 19 Dec 2011 15:13:54 +0100 (CET) Received: from teythoon by thinkbox.jade-hamburg.de with local (Exim 4.77) (envelope-from ) id 1RcdyR-0003Vn-Ny; Mon, 19 Dec 2011 15:13:51 +0100 Content-Type: multipart/mixed; boundary="===============1456673022248049802==" MIME-Version: 1.0 References: <4ee8d62a.596ee30a.1833.ffffc33e@mx.google.com> To: Patrick Totzke , notmuch@notmuchmail.org In-Reply-To: <4ee8d62a.596ee30a.1833.ffffc33e@mx.google.com> From: Justus Winter <4winter@informatik.uni-hamburg.de> Subject: Re: [afew] announcing afew, an universal tagging solution with some fancy features Date: Mon, 19 Dec 2011 15:13:51 +0100 Message-Id: X-BeenThere: notmuch@notmuchmail.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: "Use and development of the notmuch mail system." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Dec 2011 14:14:02 -0000 --===============1456673022248049802== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable 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 ClassifyingFi= lter, > 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.Backen= dError). 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 ex= pected: > I installed as stated in the README, > trained some of my existing tags and called `afew --update-reference` an= d `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 ta= gged 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 --===============1456673022248049802== Content-Type: application/octet-stream MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename=".signature" bG92ZSB1IGFsb3QgQCxACgo= --===============1456673022248049802==--