From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from localhost (localhost [127.0.0.1]) by arlo.cworth.org (Postfix) with ESMTP id 0B4166DE0355 for ; Fri, 2 Jun 2017 02:08:36 -0700 (PDT) X-Virus-Scanned: Debian amavisd-new at cworth.org X-Spam-Flag: NO X-Spam-Score: 0.472 X-Spam-Level: X-Spam-Status: No, score=0.472 tagged_above=-999 required=5 tests=[AWL=-0.161, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_NEUTRAL=0.652, UNPARSEABLE_RELAY=0.001] autolearn=disabled Received: from arlo.cworth.org ([127.0.0.1]) by localhost (arlo.cworth.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UaCtsijIbTwk for ; Fri, 2 Jun 2017 02:08:35 -0700 (PDT) Received: from mail-wm0-f48.google.com (mail-wm0-f48.google.com [74.125.82.48]) by arlo.cworth.org (Postfix) with ESMTPS id D3F826DE0350 for ; Fri, 2 Jun 2017 02:08:34 -0700 (PDT) Received: by mail-wm0-f48.google.com with SMTP id b84so17973690wmh.0 for ; Fri, 02 Jun 2017 02:08:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=dme-org.20150623.gappssmtp.com; s=20150623; h=to:cc:subject:in-reply-to:references:from:date:message-id :mime-version:content-transfer-encoding; bh=HVgTcx6jGDihnNwjHoG8MTTL1iCOzes71faBQ+Jm+Nk=; b=LyNKbmQcsDNodiZfAL8XVF8Vpp7l0RdUV2xgC3RKO+JsyJ6g5SJruWKBap5sOK2bD4 Q1KQLNviSRV9Xoq+4UgIcfb+1LBmSRJa6Do1yJJy4RlQYwlzGqb/vdfsClP9fewUdWm7 hVabRSB4DjNgXExRId1HmgDh6R9O9EY6cQ/FWpvDdQ24kKFWg4mN5Er+p9t3BfYAzZtz GtPPkCQNmjaDqHZJPY9cI7tj/S4xkYJYzPbSycJkgZ6KsNylmCRtI6MR7G497oXpuCNf ceSKGXJ+E+x0fe3R0vAzm2t36Si7omxCVRP73wX5rnHNjJcM3qDAlq7HhC1CkexXxWh5 8CPQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:to:cc:subject:in-reply-to:references:from:date :message-id:mime-version:content-transfer-encoding; bh=HVgTcx6jGDihnNwjHoG8MTTL1iCOzes71faBQ+Jm+Nk=; b=EHAbCCm7Rk6ZcjmW3hfaZUKdGLH90fRVJVm4EM423hW2bboxdtpV8djatoAHYjsyYy cMRr21YDB+zMhbg6tPkM+Qp7SCYzqcSsCFgkHIb7TxVvz76PmmuQnxwaSjgVu/eNWkiV vq+vAcPkb0B/4Ib22xskg6XAO9Rl50mPrKb3NtJ9pzwH+p68IzJ7tGSwhHSurWPdJtS5 Kphbo/ZuwXO2L84flZLmO4lyV/0MZtX4jmhQetVU7VxSIsWyefhcFswAfw/9Cy6R9CmT 9sf0vC6Fzwep4aWTNO2Z7VnVxMdMbeQJmgV/t2bCiMJ9GWyMIBfoWV0909lgT3XkUvCW 6r+w== X-Gm-Message-State: AODbwcCMzcHmxZV9Yp/HUrOcRL19XWsaqveTOuDA6YbjBS3TjCwS4cvx 2XSiCxBbyqbDXSEz X-Received: by 10.80.181.57 with SMTP id y54mr5265020edd.109.1496394513129; Fri, 02 Jun 2017 02:08:33 -0700 (PDT) Received: from disaster-area.hh.sledj.net (disaster-area.hh.sledj.net. [81.149.164.25]) by smtp.gmail.com with ESMTPSA id w11sm14968812eda.63.2017.06.02.02.08.31 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 02 Jun 2017 02:08:31 -0700 (PDT) Received: from localhost (disaster-area.hh.sledj.net [local]) by disaster-area.hh.sledj.net (OpenSMTPD) with ESMTPA id 26b21b19; Fri, 2 Jun 2017 09:08:30 +0000 (UTC) To: Edgar Hipp Cc: notmuch@notmuchmail.org Subject: Re: Show email adress in output of `notmuch search --format json` In-Reply-To: <20170602083503.vjakloikbse24prv@fr-fadpc15.europe.altair.com> References: <20170601065917.tb7enmxklevslevt@fr-fadpc15.europe.altair.com> <20170602083503.vjakloikbse24prv@fr-fadpc15.europe.altair.com> X-HGTTG: heart-of-gold From: David Edmondson Date: Fri, 02 Jun 2017 10:08:30 +0100 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-BeenThere: notmuch@notmuchmail.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Use and development of the notmuch mail system." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Jun 2017 09:08:36 -0000 On Friday, 2017-06-02 at 10:35:03 +0200, Edgar Hipp wrote: > What I'm doing is basically=20 > > notmuch search --format=3Djson '*' | 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=3Dfalse --format=3Djson "*" | other_processing | fzf let you achieve your goal? (The processing would have to change, of course.) In general, I wonder whether =E2=80=9Csearch=E2=80=9D or =E2=80=9Cshow=E2= =80=9D for =E2=80=9C*=E2=80=9D 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=3Djson "*" > /dev/null notmuch search --format=3Djson "*" > /dev/null 108.14s user 35.55s system = 75% cpu 3:10.18 total %=20 (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. =E2=80=9Cshow=E2=80=9D will probably be slower. dme. --=20 You know your green from your red.