From: Stefan Monnier <monnier@iro.umontreal.ca>
To: "João Távora" <joaotavora@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: scratch/backend-completion c807121fbd 1/2: Add lisp/backend-completion.el
Date: Sat, 03 Dec 2022 09:04:48 -0500 [thread overview]
Message-ID: <jwv8rjo37ub.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <CALDnm51gxk3pk9JSPrs7EDxMCg-k_hpuiT+7hCf2=12C4NPK2w@mail.gmail.com> ("João Távora"'s message of "Sat, 3 Dec 2022 13:21:04 +0000")
> I quite like this and it's working well for both Eglot and that other
> library. I haven't tried it with SLY but I'm sure it will do the job
> nicely.
One thing I was wondering is how useful is the `tryc` method. I suspect
that SLY can provide a real implementation for it but in most other
cases I'd expect that the only option is to use a degenerate `tryc`
method. So I was thinking that maybe the `tryc-function` arg should
be optional.
> One of the most important things though is the naming.
> "Backend completion" is not a good name, there are already a ton
> of "backend" semantics that are entirely Emacs only, and this new
> style is really exclusive for tools _outside_ of Emacs's address
> space.
I agree that "backend" is not great since it's largely a matter of
perspective. I can't remember which other names have been considered
but how 'bout `external`?
Stefan
next prev parent reply other threads:[~2022-12-03 14:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <166938157708.15020.14294469350904271113@vcs2.savannah.gnu.org>
[not found] ` <20221125130621.A3C14C0E4C1@vcs2.savannah.gnu.org>
2022-11-25 15:50 ` scratch/backend-completion c807121fbd 1/2: Add lisp/backend-completion.el Stefan Monnier
2022-11-25 16:28 ` João Távora
2022-11-29 21:18 ` Stefan Monnier
2022-11-29 22:59 ` João Távora
2022-11-29 23:44 ` Stefan Monnier
2022-12-03 13:21 ` João Távora
2022-12-03 14:04 ` Stefan Monnier [this message]
2022-12-03 23:22 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=jwv8rjo37ub.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=emacs-devel@gnu.org \
--cc=joaotavora@gmail.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.