From: David Edmondson <dme@dme.org>
To: Edgar Hipp <contact@javascript-ninja.fr>
Cc: notmuch@notmuchmail.org
Subject: Re: Show email adress in output of `notmuch search --format json`
Date: Fri, 02 Jun 2017 10:08:30 +0100 [thread overview]
Message-ID: <m24lvyiwoh.fsf@dme.org> (raw)
In-Reply-To: <20170602083503.vjakloikbse24prv@fr-fadpc15.europe.altair.com>
On Friday, 2017-06-02 at 10:35:03 +0200, Edgar Hipp wrote:
> What I'm doing is basically
>
> notmuch search --format=json '*' | processing_program | fzf
>
> Which makes it possible to search trough messages interactively : fzf is
> a fuzzy finder(see the gif on the page https://github.com/junegunn/fzf)
>
> What I would expect is to have the same format as show but for multiple
> messages, (in my case for search).
>
> That's why I would find it interesting to be able to customize the
> fields shown in search.
Understood. There is no general ability to customise the fields today.
Would:
notmuch show --body=false --format=json "*" | other_processing | fzf
let you achieve your goal? (The processing would have to change, of
course.)
In general, I wonder whether “search” or “show” for “*” will give you
the performance you want if fzf waits for all of the input before
allowing the user to start matching.
For example, with 0.5 million messages in a database:
% time notmuch search --format=json "*" > /dev/null
notmuch search --format=json "*" > /dev/null 108.14s user 35.55s system 75% cpu 3:10.18 total
%
(Not a particularly fast machine, but all of the relevant stuff is on
SSD.)
If I had to wait 108 seconds to start matching it would be
unusable. “show” will probably be slower.
dme.
--
You know your green from your red.
next prev parent reply other threads:[~2017-06-02 9:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-01 6:59 Show email adress in output of `notmuch search --format json` Edgar Hipp
2017-06-01 9:41 ` David Edmondson
2017-06-02 8:35 ` Edgar Hipp
2017-06-02 9:08 ` David Edmondson [this message]
2017-06-02 9:28 ` Edgar Hipp
2017-06-02 9:30 ` Edgar Hipp
2017-06-02 10:11 ` David Edmondson
-- strict thread matches above, loose matches on Subject: below --
2017-06-02 10:40 Edgar Hipp
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=m24lvyiwoh.fsf@dme.org \
--to=dme@dme.org \
--cc=contact@javascript-ninja.fr \
--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).