all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Karl Fogel <kfogel@red-bean.com>
To: Stefan Monnier <monnier@IRO.UMontreal.CA>
Cc: emacs-devel@gnu.org
Subject: Re: Extending the ecomplete.el data store.
Date: Mon, 05 Feb 2018 01:17:49 -0600	[thread overview]
Message-ID: <87a7wn7vmq.fsf@red-bean.com> (raw)
In-Reply-To: <jwvk1vskwf0.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Sun, 04 Feb 2018 21:34:14 -0500")

Stefan Monnier <monnier@IRO.UMontreal.CA> writes:
>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).

Yup.  That's one reason why I think it's worth moving to this more extensible format.  Such things could be added later, and the format could handle them.  (Maybe we should add a top level symbol in each record stating what flavor of record it is -- e.g., for the current proposal, that symbol would be 'email-addr' or something.)

>> 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.

Remember, mailaprop isn't updating the datastore during the Emacs session -- when Emacs exits, mailaprop isn't writing anything out to disk.  Instead, the database is regenerated whole each time, from the entire email corpus.  When I do that regeneration, the last step is to push the new database up to the version control repository.

If mailaprop were like ecomplete, updating the database from activity during the Emacs session (which I think would be a good feature to add some day), then it would indeed have the same conflict problem you experienced.

Best regards,
-Karl




  reply	other threads:[~2018-02-05  7:17 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-04  6:16 Extending the ecomplete.el data store Karl Fogel
2018-02-04 22:33 ` Stefan Monnier
2018-02-04 23:54   ` Karl Fogel
2018-02-05  2:34     ` Stefan Monnier
2018-02-05  7:17       ` Karl Fogel [this message]
2018-02-05 18:30         ` Stefan Monnier
2018-02-06 20:19           ` Karl Fogel
2018-02-06 20:39             ` Stefan Monnier
2018-02-05  9:41   ` Lars Ingebrigtsen
2018-02-06 21:01     ` Modifying a shared file (was: Extending the ecomplete.el data store) Stefan Monnier
2018-02-06 22:33       ` Modifying a shared file Clément Pit-Claudel
2018-02-05  9:40 ` Extending the ecomplete.el data store Lars Ingebrigtsen
2018-02-06 20:17   ` Karl Fogel
2018-04-10 20:47     ` Lars Ingebrigtsen
2018-02-06 21:12   ` Stefan Monnier
2018-02-06 23:04     ` Karl Fogel
2018-02-06 23:21       ` Stefan Monnier
2018-02-08 17:21         ` Karl Fogel
2018-04-10 21:00     ` Lars Ingebrigtsen
2018-04-10 21:08       ` Stefan Monnier

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87a7wn7vmq.fsf@red-bean.com \
    --to=kfogel@red-bean.com \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@IRO.UMontreal.CA \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.