unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: Teemu Likonen <tlikonen@iki.fi>
To: Kevin Foley <kevin@kevinjfoley.me>, notmuch@notmuchmail.org
Subject: Re: Searching for an Exact Email Address
Date: Sun, 02 Feb 2020 08:12:50 +0200	[thread overview]
Message-ID: <87pnexbjq5.fsf@iki.fi> (raw)
In-Reply-To: <m2wo960zey.fsf@Kevins-MBP.home.lan>

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

Kevin Foley [2020-02-01T16:29:25-05] wrote:

> I'm getting unexpected results when trying to search for messages
> associated with an email address.

> $ notmuch search to:"example@email.com"

> My understanding is this should be treated as a phrase which means
> that exact phrase will be searched for, is this correct?

Double quotes are special characters in your shell and it interprets
them so that notmuch doesn't get them. There are different ways in shell
to escape special characters:

    to:\"example@email.com\"
    'to:"example@email.com"'

The shell built-in "set" is useful for testing parameters:

    $ set -- to:"example@email.com" to:\"example@email.com\"
    $ printf '%s\n' "$@"
    to:example@email.com
    to:"example@email.com"

-- 
///  OpenPGP key: 4E1055DC84E9DFF613D78557719D69D324539450
//  https://keys.openpgp.org/search?q=tlikonen@iki.fi
/  https://keybase.io/tlikonen  https://github.com/tlikonen

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 694 bytes --]

  parent reply	other threads:[~2020-02-02  6:13 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-01 21:29 Searching for an Exact Email Address Kevin Foley
2020-02-02  0:38 ` David Bremner
2020-02-02  6:12 ` Teemu Likonen [this message]
2020-02-02 12:17   ` David Bremner
2020-02-02 15:05     ` Kevin Foley
2020-02-02 17:00       ` David Bremner

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=87pnexbjq5.fsf@iki.fi \
    --to=tlikonen@iki.fi \
    --cc=kevin@kevinjfoley.me \
    --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).