From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp0 ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms11 with LMTPS id AL9BHdHbbF/RfgAA0tVLHw (envelope-from ) for ; Thu, 24 Sep 2020 17:48:01 +0000 Received: from aspmx1.migadu.com ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp0 with LMTPS id OCFWGdHbbF/JYAAA1q6Kng (envelope-from ) for ; Thu, 24 Sep 2020 17:48:01 +0000 Received: from mail.notmuchmail.org (nmbug.tethera.net [IPv6:2607:5300:201:3100::1657]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (2048 bits)) (No client certificate requested) by aspmx1.migadu.com (Postfix) with ESMTPS id 16BEA9402B3 for ; Thu, 24 Sep 2020 17:47:59 +0000 (UTC) Received: from nmbug.tethera.net (localhost [127.0.0.1]) by mail.notmuchmail.org (Postfix) with ESMTP id 74CEB29C4D; Thu, 24 Sep 2020 13:47:52 -0400 (EDT) Received: from fethera.tethera.net (fethera.tethera.net [IPv6:2607:5300:60:c5::1]) by mail.notmuchmail.org (Postfix) with ESMTP id 7501A2931D for ; Thu, 24 Sep 2020 13:47:50 -0400 (EDT) Received: by fethera.tethera.net (Postfix, from userid 1001) id 580FE5FE30; Thu, 24 Sep 2020 13:47:48 -0400 (EDT) Received: (nullmailer pid 1102309 invoked by uid 1000); Thu, 24 Sep 2020 17:47:46 -0000 From: David Bremner To: George Kadianakis , Jameson Graef Rollins , notmuch@notmuchmail.org Subject: Re: emacs: How to tab-complete destination email addresses? In-Reply-To: <87pn6b85u4.fsf@riseup.net> References: <87h7roa3fe.fsf@riseup.net> <87blhw5usy.fsf@caltech.edu> <87pn6b85u4.fsf@riseup.net> Date: Thu, 24 Sep 2020 14:47:46 -0300 Message-ID: <87y2kz3w3h.fsf@tethera.net> MIME-Version: 1.0 Message-ID-Hash: RDLJPVYFSIALZCXLHAAPL33QJYNU4PTT X-Message-ID-Hash: RDLJPVYFSIALZCXLHAAPL33QJYNU4PTT X-MailFrom: david@tethera.net X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-notmuch.notmuchmail.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; suspicious-header X-Mailman-Version: 3.2.1 Precedence: list List-Id: "Use and development of the notmuch mail system." List-Help: List-Post: List-Subscribe: List-Unsubscribe: Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Scanner: scn0 Authentication-Results: aspmx1.migadu.com; dkim=none; dmarc=none; spf=pass (aspmx1.migadu.com: domain of notmuch-bounces@notmuchmail.org designates 2607:5300:201:3100::1657 as permitted sender) smtp.mailfrom=notmuch-bounces@notmuchmail.org X-Spam-Score: 0.03 X-TUID: gy5q7G/MbJUc George Kadianakis writes: > > So I guess this ordering should happen internally in notmuch-address, > right? Perhaps as a new type of "--sort" option like "--most-frequent" > or "--best-fit". > > If this is the right way to do it, perhaps I'll take a stab at it over > the next days. If it's not the right way to do it, please let me know so > that I don't do useless things! :) > there was some discussion about upstreaming some of the features of notmuch-addrlookup-c into notmuch-address [1]. I'm not sure what happened there, but maybe this helps. > > Hmm, I've never used this interface but if you are talking about the > "--output" switch I see that they can be combined. So like you can do: > > $ notmuch address --output sender --output recipients jameson > > to combine both To: and From:. Maybe the elisp 'internal' front-end needs to be updated to (optionally) do what Jamie asks. [1]: https://github.com/aperezdc/notmuch-addrlookup-c/issues/23