From: Karl Fogel <kfogel@red-bean.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: Emacs Tangents <emacs-tangents@gnu.org>
Subject: Re: [ANNOUNCE] mailaprop: modern popup-style autofill for email addresses
Date: Thu, 18 Jan 2018 14:16:30 -0600 [thread overview]
Message-ID: <87r2qm6hy9.fsf@red-bean.com> (raw)
In-Reply-To: <m36080da75.fsf@gnus.org> (Lars Ingebrigtsen's message of "Wed, 17 Jan 2018 11:57:34 +0100")
Lars Ingebrigtsen <larsi@gnus.org> writes:
>Karl Fogel <kfogel@red-bean.com> writes:
>> Lars Ingebrigtsen <larsi@gnus.org> writes:
>>>The format is like this:
>>>
>>>((mail
>>> ("larsi@gnus.org" 38154 1516109510 "Lars Ingebrigtsen <larsi@gnus.org>")
>>> ("kfogel@red-bean.com" 10 1516065455 "Karl Fogel <kfogel@red-bean.com>")
>>> ...
>>> ))
>>>
>>>Which is email address/times used/last time used/full name.
>>
>> Thanks. How does it handle cases where the same email address appears
>> with different full names? Is there a separate top-level entry for
>> each of those (i.e., the same car is repeated)?
>
>The first elem is the key, so the full name appears only once per key.
>That is, it'll be updated.
Thanks, Lars.
Mailaprop stores a superset of the information ecomplete stores. Namely, mailaprop tracks the sent-to count separately from the received-from count, and mailaprop tracks each real-name form of a given email address separately. I'd like to discuss the possibility of having ecomplete store that information too, so that mailaprop and ecomplete can work from the same data.
Should I start that thread on Emacs Devel? I think so, but wanted to get your opinion first.
Best regards,
-Karl
next prev parent reply other threads:[~2018-01-18 20:16 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-15 18:52 [ANNOUNCE] mailaprop: modern popup-style autofill for email addresses Karl Fogel
2018-01-15 19:48 ` John Wiegley
2018-01-15 23:31 ` Karl Fogel
2018-01-16 0:54 ` joakim
2018-01-16 4:49 ` Karl Fogel
2018-01-16 1:17 ` Lars Ingebrigtsen
2018-01-16 5:02 ` Karl Fogel
2018-01-16 13:37 ` Lars Ingebrigtsen
2018-01-16 19:17 ` Karl Fogel
2018-01-17 10:57 ` Lars Ingebrigtsen
2018-01-18 20:16 ` Karl Fogel [this message]
2018-01-19 11:37 ` Lars Ingebrigtsen
2018-02-04 6:35 ` Karl Fogel
2018-01-16 6:02 ` Karl Fogel
2018-01-16 13:38 ` Lars Ingebrigtsen
2018-01-16 13:54 ` Lars Ingebrigtsen
2018-01-16 14:23 ` Lars Ingebrigtsen
2018-01-16 19:22 ` Karl Fogel
2018-01-17 10:58 ` Lars Ingebrigtsen
2018-01-16 17:17 ` Eli Zaretskii
2018-01-17 10:53 ` Lars Ingebrigtsen
2018-01-17 15:24 ` Eli Zaretskii
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87r2qm6hy9.fsf@red-bean.com \
--to=kfogel@red-bean.com \
--cc=emacs-tangents@gnu.org \
--cc=larsi@gnus.org \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).