From: David Bremner <david@tethera.net>
To: "Alexey I. Froloff" <raorn@raorn.name>
Cc: notmuch@notmuchmail.org
Subject: Re: [PATCH] lib: Add a new prefix "list" to the search-terms syntax
Date: Mon, 08 Apr 2013 18:56:26 -0300 [thread overview]
Message-ID: <877gkchek5.fsf@zancas.localnet> (raw)
In-Reply-To: <20130408100336.GA1806@raorn.name>
"Alexey I. Froloff" <raorn@raorn.name> writes:
> On Sat, Apr 06, 2013 at 08:54:59AM -0300, David Bremner wrote:
>> On the other hand, _notmuch_message_gen_terms does return a status. I
>> agree that currently this status is not useful, but that could change in
>> the future. I also agree that the existing code does the same thing in
>> a few places, but I think it's better not to introduce more.
> Well, this is an adaptation of earlier patch, posted in this list
> some time ago.
Sure, no blame attaches. But somebody still needs to fix the patch or
convince us it doesn't need fixing.
> Personally I see no reason in indexing list description.
That's an independent question. I guess there is the question of how
much overhead this introduces into
>> Any objections to the list: syntax? The only issue I see is that at
>> some point we will probably add a generic header search syntax, and this
>> implicitly says list-id is more important/common than other headers.
> Actual list ID differs from List-Id header value. I can't give
> an example of other message header with similar syntax other from
> From/To/Cc, but those headers already specially processed.
OK, that part seems relatively convincing to me.
d
next prev parent reply other threads:[~2013-04-08 21:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-03 13:46 [PATCH] lib: Add a new prefix "list" to the search-terms syntax Alexey I. Froloff
2013-04-06 11:54 ` David Bremner
2013-04-08 10:03 ` Alexey I. Froloff
2013-04-08 21:56 ` David Bremner [this message]
2013-04-09 8:30 ` Alexey I. Froloff
2013-04-09 23:16 ` Alexey I. Froloff
2013-04-30 1:12 ` David Bremner
2013-04-30 9:52 ` Alexey I. Froloff
2013-05-04 0:54 ` David Bremner
2013-10-17 14:17 ` Jani Nikula
2013-12-17 18:03 ` Kirill A. Shutemov
2013-12-17 19:46 ` Kirill A. Shutemov
2014-01-01 12:04 ` Jani Nikula
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=877gkchek5.fsf@zancas.localnet \
--to=david@tethera.net \
--cc=notmuch@notmuchmail.org \
--cc=raorn@raorn.name \
/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).