From: Lars Ingebrigtsen <larsi@gnus.org>
To: Karl Fogel <kfogel@red-bean.com>
Cc: Emacs Tangents <emacs-tangents@gnu.org>
Subject: Re: [ANNOUNCE] mailaprop: modern popup-style autofill for email addresses
Date: Tue, 16 Jan 2018 14:37:00 +0100 [thread overview]
Message-ID: <m3k1widiwz.fsf@gnus.org> (raw)
In-Reply-To: <878tcy8kg1.fsf@red-bean.com> (Karl Fogel's message of "Mon, 15 Jan 2018 23:02:54 -0600")
Karl Fogel <kfogel@red-bean.com> writes:
> It seems like ecomplete does something at least similar to what
> mailaprop does. The main questions I have are:
>
> 1) Is there a way to load in existing email history? If I knew the
> format of the .ecompletrc file, maybe I could make mailaprop.py
> generate it. Personally, with a million email messages' worth of
> legacy data, it seems a pity to start collecting addresses from
> scratch now :-).
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.
> 2) Does it prioritize the completion list according to some scoring
> algorithm, so that the most likely candidates are keystrokewise
> closest?
It only prioritises by the number of times the address has been used...
Hm... I think I had meant to also make it prioritise based on recency,
but I apparently didn't. But that can be tweaked, of course.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2018-01-16 13:37 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 [this message]
2018-01-16 19:17 ` Karl Fogel
2018-01-17 10:57 ` Lars Ingebrigtsen
2018-01-18 20:16 ` Karl Fogel
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=m3k1widiwz.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=emacs-tangents@gnu.org \
--cc=kfogel@red-bean.com \
/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).