From: Daniel Pittman <daniel@rimspace.net>
To: ding@gnus.org
Subject: Re: NNIR, IMAP SEARCH, and the infinite pain of search terms.
Date: Mon, 14 Apr 2008 21:54:18 +1000 [thread overview]
Message-ID: <87iqyklkid.fsf@rimspace.net> (raw)
In-Reply-To: <v9iqyln947.fsf@marauder.physik.uni-ulm.de>
Reiner Steib <reinersteib+gmane@imap.cc> writes:
> On Mon, Dec 10 2007, Daniel Pittman wrote:
>
>> Gnus contains, in contrib/, the nnir.el interface to search engines.
>> This is a nice tool and, pleasantly, supports IMAP SEARCH to give me
>> efficient searching of my IMAP mail ... or so I thought.
[...]
> Installed. Thanks for your contribution. Sorry for the delay.
No problem. I still have, on my task list, implementing a generic query
language for nnir, then passing that to the appropriate back-ends, so
/hopefully/ this will not be the last you see of that.
> Could you please suggest an improved variant of my minimal ChangeLog
> entry?
>
> * nnir.el (nnir-run-imap): Add doc string. Use `nnir-imap-make-query'.
> (nnir-imap-make-query, nnir-imap-query-to-imap)
> (nnir-imap-expr-to-imap, nnir-imap-parse-query, nnir-imap-next-expr)
> (nnir-imap-peek-symbol, nnir-imap-next-symbol)
> (nnir-imap-delimited-string, nnir-imap-end-of-input): New
> functions.
Hrm. Well, the purpose of the change is:
* nnir.el (nnir-run-imap): Add doc string. Use `nnir-imap-make-query'.
(nnir-imap-make-query, nnir-imap-query-to-imap)
(nnir-imap-expr-to-imap, nnir-imap-parse-query, nnir-imap-next-expr)
(nnir-imap-peek-symbol, nnir-imap-next-symbol)
(nnir-imap-delimited-string, nnir-imap-end-of-input):
New functions. Implement a query language for IMAP search,
parse that and compose the back-end query from it. This allows
searches with AND, OR and fixed strings, not just a single
substring.
I don't think that meets the GNU coding standards, though, which I
confess have never made much sense to me for changes like this.[1]
For something in news that summary would definitely fit, or something
adapted from my comments above.
Regards,
Daniel
Footnotes:
[1] I can't see how anything meaningful can be recorded in the style
requested, and welcome pointers to a better guide.
prev parent reply other threads:[~2008-04-14 11:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-10 11:37 Daniel Pittman
2007-12-11 10:39 ` Vegard Vesterheim
2008-04-13 14:05 ` Reiner Steib
2008-04-14 11:54 ` Daniel Pittman [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87iqyklkid.fsf@rimspace.net \
--to=daniel@rimspace.net \
--cc=ding@gnus.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.
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 NNTP newsgroup(s).