From: "Adam Sjøgren" <asjo@koldfront.dk>
To: info-gnus-english@gnu.org
Subject: Re: nnir notmuch search on specific groups?
Date: Sun, 21 Oct 2018 19:50:47 +0200 [thread overview]
Message-ID: <87a7n79ojs.fsf@tullinup.koldfront.dk> (raw)
In-Reply-To: <87bm7ni6sy.fsf@ericabrahamsen.net>
Eric writes:
> I vaguely remember that I couldn't even make it work properly on the
> command line, couldn't figure out why "folder" and "path" returned the
> results they did.
path:{folder} works for me, using notmuch on the command line.
My email is in nnml format in various folders in ~/Mail/{folder}, and my
.notmuch-config has:
[database]
path=/home/asjo/Mail
Searching for "Adam" gives me a lot of results:
asjo@tullinup:~$ time notmuch search Adam | wc -l
32911
real 0m6.574s
user 0m5.016s
sys 0m1.577s
If I limit the search using path:, I get less, so it looks like it
works:
asjo@tullinup:~$ time notmuch search "Adam path:cron" | wc -l
507
real 0m0.148s
user 0m0.128s
sys 0m0.024s
My notmuch index has ~119K entries:
$ time notmuch count
119018
> But `nnir-run-notmuch' filters its results same as all the other search
> routines, so I'm not sure why we can't do the filtering on group name,
> after the fact. It has this:
>
> ;; maybe limit results to matching groups.
> (when (or (not groupspec)
> (string-match groupspec dirnam))
> (nnir-add-result dirnam artno "" prefix server artlist)))))
>
> That should be usable for filtering, right?
Yeah! I guess it could matter when the results are excluded,
performance-wise, but in practise, I would guess it would be "fast
enough"™ to do it post hoc.
> I have the feeling that I've gone over all this before, then forgotten
> what the conclusion was...
I know that feeling all too well... :-)
Best regards,
Adam
--
"Since it is completely undocumented, your faith that Adam Sjøgren
it will stick around until they invent v4 is asjo@koldfront.dk
charmingly quaint."
_______________________________________________
info-gnus-english mailing list
info-gnus-english@gnu.org
https://lists.gnu.org/mailman/listinfo/info-gnus-english
next prev parent reply other threads:[~2018-10-21 17:50 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-20 21:56 Andreas Goesele
2018-10-21 3:48 ` Eric Abrahamsen
2018-10-21 10:35 ` Adam Sjøgren
2018-10-21 16:49 ` Eric Abrahamsen
2018-10-21 17:50 ` Adam Sjøgren [this message]
2018-10-21 18:58 ` Eric Abrahamsen
[not found] ` <mailman.2552.1540148988.1284.info-gnus-english@gnu.org>
2018-10-21 19:41 ` Andreas Goesele
2018-10-21 20:08 ` Eric Abrahamsen
2018-10-21 20:24 ` Eric Abrahamsen
[not found] ` <mailman.2556.1540152550.1284.info-gnus-english@gnu.org>
2018-10-21 21:17 ` Andreas Goesele
2018-10-23 3:01 ` Eric Abrahamsen
[not found] ` <mailman.2606.1540263818.1284.info-gnus-english@gnu.org>
2018-10-23 20:37 ` Andreas Goesele
2018-10-24 0:47 ` Eric Abrahamsen
[not found] ` <mailman.2644.1540342724.1284.info-gnus-english@gnu.org>
2018-10-24 16:46 ` Andreas Goesele
[not found] ` <mailman.2547.1540140585.1284.info-gnus-english@gnu.org>
2018-10-21 18:49 ` Andreas Goesele
[not found] ` <mailman.2538.1540118168.1284.info-gnus-english@gnu.org>
2018-10-21 16:41 ` Andreas Goesele
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=87a7n79ojs.fsf@tullinup.koldfront.dk \
--to=asjo@koldfront.dk \
--cc=info-gnus-english@gnu.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).