unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "João Távora" <joaotavora@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>, Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel <emacs-devel@gnu.org>
Subject: Re: scratch/backend-completion 9a62da21c2 1/2: Integrate Stefan suggestions but rename it to "external-completion.el"
Date: Wed, 7 Dec 2022 11:09:02 +0000	[thread overview]
Message-ID: <CALDnm507ziXQES6eFqvgWGUFoM9=FZDLE00VGSzeass--A1FDQ@mail.gmail.com> (raw)
In-Reply-To: <jwvmt81wfqd.fsf-monnier+emacs@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 1210 bytes --]

On Tue, Dec 6, 2022 at 12:14 AM Stefan Monnier <monnier@iro.umontreal.ca>
wrote:
>
> > Yup, this rhymes exactly with what I wrote in the docstring in the
latest
> > version.  I understand how it could be used now.
>
> Looks great to me, thanks,

Great!  I've now tidied up the branch and pushed it to
feature/external-completion

Eli, if you haven't been following this discussion closely, this is a
refactor of
functionality already present in Eglot that consolidates the support for
offering completions coming from external tools (like LSP servers, but not
only)
and makes it available to more third party packages.

I think there shouldn't be any adverse effects of pushing this to the
emacs-29
branch, but if you think it's better, I'll push it to master instead.

It shouldn't make much of a difference since the new external-completion.el
file is going to be a GNU ELPA :core package and as such it will be
available
in Emacs 28 anyway via package-install.

Let me know what you think.  The commentary of the new file, the docstring
of external-completion-table and the commit messages should give details.
I'll be happy to fix them further if you have comments.

João

[-- Attachment #2: Type: text/html, Size: 1539 bytes --]

  reply	other threads:[~2022-12-07 11:09 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <167007345844.23701.8454474119701440468@vcs2.savannah.gnu.org>
     [not found] ` <20221203131739.3FCF9C004BE@vcs2.savannah.gnu.org>
2022-12-03 14:10   ` scratch/backend-completion aaaa016056 2/2: Speed it up Stefan Monnier
2022-12-03 23:30     ` João Távora
2022-12-04  0:18       ` Stefan Monnier
2022-12-04 11:11         ` João Távora
     [not found] ` <20221203131739.2A601C004BA@vcs2.savannah.gnu.org>
2022-12-03 14:26   ` scratch/backend-completion 9a62da21c2 1/2: Integrate Stefan suggestions but rename it to "external-completion.el" Stefan Monnier
2022-12-03 23:36     ` João Távora
2022-12-04  0:31       ` Stefan Monnier
2022-12-04 10:02         ` João Távora
2022-12-04 16:54           ` Stefan Monnier
2022-12-04 20:04             ` João Távora
2022-12-06  0:14               ` Stefan Monnier
2022-12-07 11:09                 ` João Távora [this message]
2022-12-07 13:56                   ` Eli Zaretskii
2022-12-07 19:09                     ` João Távora

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='CALDnm507ziXQES6eFqvgWGUFoM9=FZDLE00VGSzeass--A1FDQ@mail.gmail.com' \
    --to=joaotavora@gmail.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    /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).