From: Karl Fogel <kfogel@red-bean.com>
To: Emacs Tangents <emacs-tangents@gnu.org>
Subject: Re: [ANNOUNCE] mailaprop: modern popup-style autofill for email addresses
Date: Mon, 15 Jan 2018 17:31:25 -0600 [thread overview]
Message-ID: <87vag28zsi.fsf@red-bean.com> (raw)
In-Reply-To: <m2efmqj42f.fsf@newartisans.com> (John Wiegley's message of "Mon, 15 Jan 2018 11:48:56 -0800")
"John Wiegley" <johnw@gnu.org> writes:
>KF> Hi. I wrote a new package, 'mailaprop', that provides popup-style autofill
>KF> for email addresses in recipient headers of message composition buffers.
>
>If you want a nice source of candidates, I wrote this unpublished package:
>
>https://github.com/jwiegley/dot-emacs/blob/master/lisp/gnus-harvest/gnus-harvest.el
>
>It watches who you write to, and who you read e-mail from (if you hook it into
>Gnus), and stores them all in an SQLite database with timestamps. It then lets
>you query for a candidate list. I use it via message-x.
Thanks, John. That looks handy.
To be useable by mailaprop, it would need to remember the datestamp of the message the address was harvested from (or at least remember the date of the most recent message that address was harvested from), and keep separate counts for how often the address had been sent to and how often it had been received from.
This is because the order in which addresses are offered in autofill matters. The most likely candidate should be at the top, the next-most-likely underneath it, and so on. Right now, the inputs to the likelihood-calculating algorithm are the last-seen date, the total sent-to count, and total received-from count. I could make things fancier later, but for now those are the inputs.
Would those pieces of information be useful for message-x and other integratees of gnus-harvest too? Obviously, that information would be pretty easy to harvest. If mailaprop and message-x could share inputs, that'd be nice.
By the way, mailaprop's current solution to the problem of gathering input data is a standalone Python script. It crawls all your mbox files (other formats to be supported in the future, I hope) and builds the autofill database from that. I've just added a paragraph to the README.md explaining that it could take input from other sources too, and linking to this discussion.
Best regards,
-Karl
next prev parent reply other threads:[~2018-01-15 23:31 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 [this message]
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
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=87vag28zsi.fsf@red-bean.com \
--to=kfogel@red-bean.com \
--cc=emacs-tangents@gnu.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).