From: Carl Worth <cworth@cworth.org>
To: James Vasile <james@hackervisions.org>, notmuch@notmuchmail.org
Cc: Martin F Krafft <madduck@debian.org>
Subject: Re: Initial tagging
Date: Fri, 26 Feb 2010 01:13:52 -0800 [thread overview]
Message-ID: <87bpfcs6jz.fsf@yoom.home.cworth.org> (raw)
In-Reply-To: <87ocjc4rsj.fsf@hackervisions.org>
[-- Attachment #1: Type: text/plain, Size: 1307 bytes --]
> Sometimes I manually override a rule-based tag. If automatic tagging
> operated on old messages, overrides could be superseded. When I add
> automatic tag rules, I first execute them manually and globally from the
> command line.
Right. With my global automatic tags, I don't want to be able to
override them, (and the fact that I *can* by adding/removing tags is a
bug---since, as you point out, the next run of my script will destroy my
changes). That's one of the reasons I want to switch to saved searches
for my own use of automatic tags.
Meanwhile, Martin has talked about having some machine-learning
algorithm apply tags, and have it notice when the user adds/removes
for feedback to improve its learning. So that kind of use case is
something that definitely isn't covered by saved searches.
> > To do my "global" searches quickly, I do a similar subsetting, but it's
> > much simpler. If I'm adding the "notmuch" tag I do "and not
> > tag:notmuch". We've even had the proposal of making "notmuch tag" do
> > that automatically.
>
> That sounds like a good idea. What happened with that proposal?
Like many other proposals, it's simply waiting for someone to implement
it.
> Saved searches is a very good idea. I look forward to it.
Me too! :-)
-Carl
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2010-02-26 9:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-25 21:25 Initial tagging James Vasile
2010-02-26 1:02 ` Carl Worth
2010-02-26 3:09 ` James Vasile
2010-02-26 9:13 ` Carl Worth [this message]
2010-02-26 15:00 ` Jameson Rollins
2010-02-26 15:20 ` martin f krafft
2010-02-26 17:14 ` micah anderson
2010-02-27 3:58 ` James Vasile
2010-02-27 1:33 ` micah anderson
2010-02-27 4:03 ` James Vasile
2010-02-27 11:34 ` 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=87bpfcs6jz.fsf@yoom.home.cworth.org \
--to=cworth@cworth.org \
--cc=james@hackervisions.org \
--cc=madduck@debian.org \
--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).