unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: Jameson Graef Rollins <jrollins@finestructure.net>
To: Mark Walters <markwalters1009@gmail.com>,
	David Bremner <david@tethera.net>, Carl Worth <cworth@cworth.org>,
	Michal Vyskocil <mvyskocil@suse.cz>,
	notmuch@notmuchmail.org
Subject: Re: Search using email headers does not work
Date: Wed, 13 Feb 2013 13:09:22 -0800	[thread overview]
Message-ID: <874nhfncot.fsf@servo.finestructure.net> (raw)
In-Reply-To: <87ip5wlkbb.fsf@qmul.ac.uk>

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

On Tue, Feb 12 2013, Mark Walters <markwalters1009@gmail.com> wrote:
> I think I mentioned this on irc sometime ago: would indexing all the
> headers as a separate free text entry (under headers: for example)
> satisfy most of this. So then you could search for things like
> headers:"List-Id: blah" or similar.
>
> It is not as nice as individually indexed headers, but it does mean that
> all notmuch instances would be the same and the same commands would
> work, the library interface would be consistent etc.

I like this idea.  Simple to implement, and covers all needs
automatically.

jamie.

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

  reply	other threads:[~2013-02-13 21:09 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-11 14:52 Search using email headers does not work Michal Vyskocil
2013-02-12 11:50 ` David Bremner
2013-02-12 17:03   ` Jameson Graef Rollins
2013-02-12 17:32     ` Michal Vyskocil
2013-02-12 19:57       ` Carl Worth
2013-02-12 20:05         ` David Bremner
2013-02-13  7:55           ` Mark Walters
2013-02-13 21:09             ` Jameson Graef Rollins [this message]
2013-02-13 21:20               ` Alexey Feldgendler
2013-02-15  8:27           ` Tomi Ollila

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=874nhfncot.fsf@servo.finestructure.net \
    --to=jrollins@finestructure.net \
    --cc=cworth@cworth.org \
    --cc=david@tethera.net \
    --cc=markwalters1009@gmail.com \
    --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).