unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: James Vasile <james@hackervisions.org>
To: Justus Winter <4winter@informatik.uni-hamburg.de>,
	notmuch@notmuchmail.org
Subject: Re: [afew] announcing afew, an universal tagging solution with some fancy features
Date: Mon, 27 Feb 2012 16:10:35 -0500	[thread overview]
Message-ID: <87pqd0dltg.fsf@wyzanski.jamesvasile.com> (raw)
In-Reply-To: <E1RamIG-0003si-K3@thinkbox.jade-hamburg.de>

I'm tring to figure out how to use afew.  It looks interesting, but
gives me surprising results.

I did `afew --learn spam -- tag:spam` and believe this tells afew that
all the messages matching tag:spam should be classified as spam.  But if
that is right, why would `afew -c spam -- tag:spam` then show me a bunch
of messages that are tagged spam by notmuch but not classified spam by
afew?

How do I train afew when I correct it's mistakes?  Is that what `afew
update` is for?  What does "update the reference category" mean?

Thanks much,
James

      parent reply	other threads:[~2012-02-27 21:21 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
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 [this message]

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=87pqd0dltg.fsf@wyzanski.jamesvasile.com \
    --to=james@hackervisions.org \
    --cc=4winter@informatik.uni-hamburg.de \
    --cc=notmuch@notmuchmail.org \
    /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).