unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: Jameson Graef Rollins <jrollins@finestructure.net>
To: Michal Vyskocil <mvyskocil@suse.cz>, notmuch@notmuchmail.org
Subject: Re: funcmail.py: generate notmuch-tags based on headers
Date: Fri, 29 Mar 2013 12:43:41 -0700	[thread overview]
Message-ID: <87r4iyq9ea.fsf@servo.finestructure.net> (raw)
In-Reply-To: <20130322115623.GA18329@linux-xtv2.site>

[-- Attachment #1: Type: text/plain, Size: 1080 bytes --]

On Fri, Mar 22 2013, Michal Vyskocil <mvyskocil@suse.cz> wrote:
> because it seems that notmuch does not index all headers, I've written a
> simple, but quite usable tool, which goes through a maildir and generate
> an output for notmuch-tag --batch according a simple rules. I've
> borrowed the syntax from notmuch-tag --batch format, so it should be
> very easy for any notmuch user to configure.
>
> You can query the content of a paricular header
> # tags will be applied when string is in header
> +notmuch -inbox -- 'notmuch.notmuchmail.org' in 'List-Id'

Hi, Michal.  You might consider using a format that might be actually
adopted by notmuch down the line.  This is sure to set off a protracted
bike-shedding debate, but let me get the ball rolling.

Imagine down the line we are able to index arbitrary user-specified
headers.  Maybe we could adopt a new search prefix of the form:

  x:<header>:<value>

e.g.

  x:list-id:notmuch.notmuchmail.org

I think this would work with the Xapian term prefixing, but I'll let the
Xapian experts comment.

Bike shed away!

jamie.

[-- Attachment #2: Type: application/pgp-signature, Size: 835 bytes --]

      parent reply	other threads:[~2013-03-29 19:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-22 11:56 funcmail.py: generate notmuch-tags based on headers Michal Vyskocil
2013-03-22 12:14 ` Patrick Totzke
2013-03-22 13:33   ` Michal Vyskocil
2013-03-29 19:43 ` Jameson Graef Rollins [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=87r4iyq9ea.fsf@servo.finestructure.net \
    --to=jrollins@finestructure.net \
    --cc=mvyskocil@suse.cz \
    --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).