unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Alexander Adolf <alexander.adolf@condition-alpha.com>
To: emacs-devel@gnu.org
Subject: Re: Thoughts on Refactoring In-Buffer Completion In message.el
Date: Sat, 13 Aug 2022 15:11:41 +0200	[thread overview]
Message-ID: <95b238bfd6be9d9b27a8d4c6631e7cdd@condition-alpha.com> (raw)

Hello,

it's been a while since the last update on this subject. I have chatted
with Thomas, the maintainer of EUDC, and he stated a preference for
having the two new EUDC back-ends (one for ecomplete, and one for
mailabbrev) in a separate patch series.

I will thus separate these two things out into a separate proposal, and
will update the "message completion refactoring proposal" accordingly.

Above and beyond that, I still need to do the following things for the
present "message completion refactoring proposal":

- figure out, and implement how to add completion category metadata to
  completion tables;

- write a NEWS entry;

- update the texi manual for message.


Cheers,

  --alexander



             reply	other threads:[~2022-08-13 13:11 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-13 13:11 Alexander Adolf [this message]
2022-08-17  1:54 ` Thoughts on Refactoring In-Buffer Completion In message.el Stefan Monnier
  -- strict thread matches above, loose matches on Subject: below --
2022-06-23 15:26 Alexander Adolf
2022-06-25  4:35 ` Thomas Fitzsimmons
2022-06-27 15:48   ` Alexander Adolf
2022-06-25  8:22 ` Stefan Monnier
2022-06-27 16:37   ` Alexander Adolf
2022-06-28 15:49     ` Stefan Monnier
2022-07-19 21:41       ` Alexander Adolf
2022-07-19 22:13         ` Stefan Monnier
2022-07-20 20:59           ` Alexander Adolf
2022-07-20 23:59             ` Stefan Monnier
2022-07-22 13:20               ` Alexander Adolf
2022-07-22 13:58                 ` Alexander Adolf
2022-07-27 21:16               ` Alexander Adolf
2022-08-17  2:45                 ` 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

  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=95b238bfd6be9d9b27a8d4c6631e7cdd@condition-alpha.com \
    --to=alexander.adolf@condition-alpha.com \
    --cc=emacs-devel@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.
Code repositories for project(s) associated with this public inbox

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

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