From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: Extending the ecomplete.el data store. Date: Sun, 04 Feb 2018 21:34:14 -0500 Message-ID: References: <87fu6hcm9r.fsf@red-bean.com> <87efm071lm.fsf@red-bean.com> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: blaine.gmane.org 1517798013 24314 195.159.176.226 (5 Feb 2018 02:33:33 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Mon, 5 Feb 2018 02:33:33 +0000 (UTC) User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.0.50 (gnu/linux) Cc: emacs-devel@gnu.org To: Karl Fogel Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Feb 05 03:33:28 2018 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1eiWai-0004pi-5L for ged-emacs-devel@m.gmane.org; Mon, 05 Feb 2018 03:33:08 +0100 Original-Received: from localhost ([::1]:41517 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1eiWcj-0004e9-9c for ged-emacs-devel@m.gmane.org; Sun, 04 Feb 2018 21:35:13 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:52838) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1eiWbs-0004cH-5n for emacs-devel@gnu.org; Sun, 04 Feb 2018 21:34:21 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1eiWbp-0003Ef-0f for emacs-devel@gnu.org; Sun, 04 Feb 2018 21:34:20 -0500 Original-Received: from chene.dit.umontreal.ca ([132.204.246.20]:37263) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1eiWbo-0003EQ-Q4 for emacs-devel@gnu.org; Sun, 04 Feb 2018 21:34:16 -0500 Original-Received: from ceviche.home (lechon.iro.umontreal.ca [132.204.27.242]) by chene.dit.umontreal.ca (8.14.7/8.14.1) with ESMTP id w152YE49021393; Sun, 4 Feb 2018 21:34:14 -0500 Original-Received: by ceviche.home (Postfix, from userid 20848) id 6CF9E66372; Sun, 4 Feb 2018 21:34:14 -0500 (EST) In-Reply-To: <87efm071lm.fsf@red-bean.com> (Karl Fogel's message of "Sun, 04 Feb 2018 17:54:13 -0600") X-NAI-Spam-Flag: NO X-NAI-Spam-Threshold: 5 X-NAI-Spam-Score: 0 X-NAI-Spam-Rules: 2 Rules triggered EDT_SA_DN_PASS=0, RV6214=0 X-NAI-Spam-Version: 2.3.0.9418 : core <6214> : inlines <6361> : streams <1778057> : uri <2586816> X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 132.204.246.20 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:222534 Archived-At: > Mailaprop tries to figure out the "best" variant of a given address, and > assign that variant a higher score than any of the other variants, so that > the "best" one shows up higher in the completion list than any of > those others. OK, I see. It's kind of a pain having to keep all that info just for that little tweak, but I guess it can indeed be significant. And, I guess, in various corner cases, explicit user input to select the right variant might be needed. This said, there can be various other info that could determine which alternative to use. E.g. you might like to use nicknames when sending to a group of close friends, but more official names when sending to some of the same person but as part of a work email. So maybe we should keep more info than you currently have (i.e. keep a list of other email addresses that appeared in the same message). > That's probably related only to how ecomplete generates its database; > I don't think it affects the format of the database. No, indeed, it's not related to the format. More a question of process synchronization. >>[ And along vaguely related lines, I'd really like if the ecompleterc >> database could be somehow shared between my different machines. >> E.g. by arranging for git-merge to "do-the-right-thing" on it, or by >> storing (a copy of) it in IMAP. ] > > I haven't thought much about that, because I solve that problem out-of-band > right now: my mailaprop database is under version control and gets > automatically sync'd across all the machines I work on (and the same would > be true of .ecompleterc if I were using that). I agree it would be a good > thing if Emacs solved that automagically, as long as it were truly reliable. I tried doing the same with ecompleterc but that results in too may conflicts that are annoying to resolve by hand. Based on your description of the format you use, I'm surprised you're not suffering from conflicts as well. Stefan