unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: Mark Walters <markwalters1009@gmail.com>
To: David Edmondson <dme@dme.org>, Jani Nikula <jani@nikula.org>,
	notmuch@notmuchmail.org
Subject: Re: [PATCH] NEWS: folder:, path:, and database upgrade
Date: Fri, 02 May 2014 15:10:35 +0100	[thread overview]
Message-ID: <87ppjw9spw.fsf@qmul.ac.uk> (raw)
In-Reply-To: <cunwqe5jn7h.fsf@hotblack-desiato.hh.sledj.net>


I don't like the wildcard bit as an important part of the change was the
removal of stemming. Perhaps keep exact in the headline and in the body
say explicitly what the changes are no stemming, no wildcards (except
globbing), etc (maybe case sensitivity is different?)

Best wishes

Mark



On Thu, 01 May 2014, David Edmondson <dme@dme.org> wrote:
> On Sun, Apr 27 2014, Jani Nikula wrote:
>> +The `folder:` search prefix now requires an exact match
>
> I think that it would be clearer to say:
>
>   The `folder:` search prefix no longer supports wildcard matching
>
> (Or something like that.)
> _______________________________________________
> notmuch mailing list
> notmuch@notmuchmail.org
> http://notmuchmail.org/mailman/listinfo/notmuch

  reply	other threads:[~2014-05-02 14:10 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-27 14:46 [PATCH] NEWS: folder:, path:, and database upgrade Jani Nikula
2014-04-27 20:54 ` [PATCH] NEWS: mbox files are no longer supported Jani Nikula
2014-04-27 21:09   ` [PATCH] NEWS: message header parser changes Jani Nikula
2014-04-28  2:03 ` [PATCH] NEWS: folder:, path:, and database upgrade David Bremner
2014-05-01 19:47 ` David Edmondson
2014-05-02 14:10   ` Mark Walters [this message]
2014-05-02 15:01     ` David Edmondson
2014-05-02 16:28       ` [PATCH] NEWS: make it explicit that wildcard matching is no longer supported Jani Nikula
2014-05-02 16:44         ` David Edmondson
2014-05-02 20:38         ` 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=87ppjw9spw.fsf@qmul.ac.uk \
    --to=markwalters1009@gmail.com \
    --cc=dme@dme.org \
    --cc=jani@nikula.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).