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 8H+SJYnRbF9YUwAA0tVLHw (envelope-from ) for ; Thu, 24 Sep 2020 17:04:09 +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 eJSVIYnRbF8JQwAA1q6Kng (envelope-from ) for ; Thu, 24 Sep 2020 17:04:09 +0000 Received: from mail.notmuchmail.org (nmbug.tethera.net [144.217.243.247]) (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 AD18794071A for ; Thu, 24 Sep 2020 17:04:07 +0000 (UTC) Received: from nmbug.tethera.net (localhost [127.0.0.1]) by mail.notmuchmail.org (Postfix) with ESMTP id 93A8529C4D; Thu, 24 Sep 2020 13:03:56 -0400 (EDT) Received: from mx1.riseup.net (mx1.riseup.net [198.252.153.129]) by mail.notmuchmail.org (Postfix) with ESMTPS id 4C4492930F for ; Thu, 24 Sep 2020 13:03:53 -0400 (EDT) Received: from bell.riseup.net (bell-pn.riseup.net [10.0.1.178]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.riseup.net", Issuer "Sectigo RSA Domain Validation Secure Server CA" (not verified)) by mx1.riseup.net (Postfix) with ESMTPS id 4By1bX20J8zFdvH; Thu, 24 Sep 2020 10:03:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=riseup.net; s=squak; t=1600967032; bh=F5gHsPHYvEu9UHg/JiIej72Fkhwdq+MMPIuZ9cAgfmY=; h=From:To:Subject:In-Reply-To:References:Date:From; b=rZJogEx6YysRELhUm3BCYogKRjxg8s1v1SZg7LE9D2rWafzyhpFFNkO5AcVsmPJcT fy9okuEs5dSJYJzs6owElDrW+CfqnYiBJ1G+fXJBeX0xdw7HstiukG02+5zh/UuexE hImubz/cU8Opy32PoMhExEAdWxGF9Bsfgek/CmmU= X-Riseup-User-ID: 636317C822406A794DFF266ABD4A4940734A357CE073AA4AA1A525D886B33B46 Received: from [127.0.0.1] (localhost [127.0.0.1]) by bell.riseup.net (Postfix) with ESMTPSA id 4By1bW11z0zJmgj; Thu, 24 Sep 2020 10:03:50 -0700 (PDT) From: George Kadianakis To: Jameson Graef Rollins , notmuch@notmuchmail.org Subject: Re: emacs: How to tab-complete destination email addresses? In-Reply-To: <87blhw5usy.fsf@caltech.edu> References: <87h7roa3fe.fsf@riseup.net> <87blhw5usy.fsf@caltech.edu> Date: Thu, 24 Sep 2020 20:03:47 +0300 Message-ID: <87pn6b85u4.fsf@riseup.net> MIME-Version: 1.0 Message-ID-Hash: BZLHVGJ45YUZUFDEL5BW2WFPJ75YPZZ6 X-Message-ID-Hash: BZLHVGJ45YUZUFDEL5BW2WFPJ75YPZZ6 X-MailFrom: desnacked@riseup.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=fail (body hash did not verify) header.d=riseup.net header.s=squak header.b=rZJogEx6; dmarc=fail reason="SPF not aligned (relaxed)" header.from=riseup.net (policy=none); spf=pass (aspmx1.migadu.com: domain of notmuch-bounces@notmuchmail.org designates 144.217.243.247 as permitted sender) smtp.mailfrom=notmuch-bounces@notmuchmail.org X-Spam-Score: 1.13 X-TUID: L9LuVWc0MhpI Jameson Graef Rollins writes: > On Wed, Sep 23 2020, George Kadianakis wrote: >> One way forward is to switch from using notmuch-address to using >> something like bbdb and manually curate my database (since bbdb offers >> this capability). >> >> But I think the right way would be to somehow introduce a bunch of >> heuristics in notmuch/emacs so that the right email address is chosen >> for each person. For example, if I tab-complete "Alice", I would like >> notmuch to give me the email address that Alice has used herself most >> frequently the past few times she contacted me. >> >> Perhaps there is something that does what I want already? >> If that's the case, I'd love to be pointed to a good solution! > Thanks for the response Jameson! > I find the convenience of not having to maintain an address book to be a > huge win with the use of notmuch-address, so I'm generally fine to > filter through the offered addresses to find the one that I generally > recognize to be the most viable. That said, an obvious improvement (as > you suggest) would be to order addresses based on most recent+frequent > use, so that the most recently used one shows up first. > 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! :) > The problem I have, though, is that for some reason that I don't > understand the interface can use To: address, or From: addresses, but > not both. This is by far the most annoying thing to me, since in both > scenarios there will end up being missing addresses that I need that I > then have to go search for manually. If the interface could be > configured to return most From: and To: address that would be a big > improvement imho. > 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:. Best of luck!