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: Tue, 16 Jan 2018 00:02:53 -0600 [thread overview]
Message-ID: <871siq8ho2.fsf@red-bean.com> (raw)
In-Reply-To: <m3a7xehaab.fsf@gnus.org> (Lars Ingebrigtsen's message of "Tue, 16 Jan 2018 02:17:32 +0100")
I wrote:
>Lars Ingebrigtsen <larsi@gnus.org> writes:
>>Looks very nice... but the main difference between this and ecomplete
>>seems to be that ecomplete puts the completions in the echo area and
>>mailaprop uses a tooltip?
>
>Hmm, I can't tell. As of commit 9f22b7d2, ecomplete.el has no function doc >strings nor any usage-informing variable doc strings, and the format of >~/.ecompleterc is not documented. From looking at the elisp file, I wasn't >immediately sure what ecomplete does :-). I grepped around and found this in >doc/misc/message.texi: [...]
Sorry, Lars. I think my tone of voice was a little off there! ecomplete looks great -- I was glad you pointed me to it, and mostly wished that I had found it earlier (say, before I wrote mailaprop, ahem).
I confess I got a little frustrated when I looked at the ecomplete.el source code, and that frustration is what came out in my original reply. The code itself was very clean & readable. But I was hungry to know the format and semantics of ~/.ecompleterc, and to know the exact completion behavior, because because then I would know whether mailaprop should continue on its own, or whether I should focus on using (and maybe extending) ecomplete.
Best regards,
-Karl
next prev parent reply other threads:[~2018-01-16 6:02 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
2018-01-19 11:37 ` Lars Ingebrigtsen
2018-02-04 6:35 ` Karl Fogel
2018-01-16 6:02 ` Karl Fogel [this message]
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=871siq8ho2.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).