From: David Bremner <david@tethera.net>
To: Tomi Ollila <tomi.ollila@iki.fi>, notmuch@notmuchmail.org
Subject: Re: [Patch v4] lib: regexp matching in 'subject' and 'from'
Date: Sun, 05 Feb 2017 19:28:35 -0400 [thread overview]
Message-ID: <87shns8bfg.fsf@rocinante.cs.unb.ca> (raw)
In-Reply-To: <m2wpd4iebd.fsf@guru.guru-group.fi>
Tomi Ollila <tomi.ollila@iki.fi> writes:
> TOn Sun, Jan 29 2017, Jani Nikula <jani@nikula.org> wrote:
>
>>
>> I'd go with an error. It's easy to loosen the rules later on if we
>> decide that's a good idea. Much harder to accept loose rules now, let
>> users get used to it, and try to tighten the rules if we realize we'd
>> need that for some reason.
>
> I agree -- should we allow trailing slash ('/') without first char also
> being '/' (e.g. subject:blah/)
>
I'd say that should also be an error. it doesn't add anything useful to
subject search. Even for path search, (which is non-trivial to add regex
search for, I think) the trailing / doesn't add anything does it?
d
next prev parent reply other threads:[~2017-02-05 23:28 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-27 13:33 [PATCH] lib: regexp matching in 'subject' and 'from' David Bremner
2016-11-14 21:46 ` [Patch v2] " David Bremner
2017-01-18 20:05 ` Jani Nikula
2017-01-18 21:01 ` David Bremner
2017-01-19 12:16 ` [Patch v3] " David Bremner
2017-01-21 3:27 ` [WIP] " David Bremner
2017-01-21 13:59 ` [Patch v4] " David Bremner
2017-01-25 19:40 ` Tomi Ollila
2017-01-26 2:21 ` David Bremner
2017-01-29 11:23 ` Jani Nikula
2017-02-05 20:16 ` Tomi Ollila
2017-02-05 23:28 ` David Bremner [this message]
2017-02-09 3:11 ` David Bremner
2017-02-09 16:15 ` Tomi Ollila
2017-02-10 8:29 ` Mark Walters
2017-02-11 23:25 ` David Bremner
2017-01-29 11:06 ` Jani Nikula
2017-01-19 14:27 ` [Patch v2] " 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=87shns8bfg.fsf@rocinante.cs.unb.ca \
--to=david@tethera.net \
--cc=notmuch@notmuchmail.org \
--cc=tomi.ollila@iki.fi \
/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).