unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
* Re: scratch/backend-completion 1af23aade6f: More tweaks to external-completion.el after Stefan's comments
       [not found] ` <20221203233625.5BBB0C00B0F@vcs2.savannah.gnu.org>
@ 2022-12-04  4:23   ` Stefan Monnier
  2022-12-04  9:45     ` João Távora
  0 siblings, 1 reply; 2+ messages in thread
From: Stefan Monnier @ 2022-12-04  4:23 UTC (permalink / raw)
  To: emacs-devel; +Cc: João Távora

> +Despite the original authors's best efforts,
> +TRY-COMPLETION-FUNCTION is still a poorly understood
> +implementation detail.  If you understand what it's for, you

FWIW, I'm not really the original author of try-completion.
More specifically, the `try-completion` function itself predates my
involvement with Emacs, and its generalization in
`partial-completion-mode` as well.  I do take responsability for
`completion-try-completion`, admittedly, where I tried to give an
"official" interface to that operation, but I was just trying to
preserve existing semantics.


        Stefan




^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: scratch/backend-completion 1af23aade6f: More tweaks to external-completion.el after Stefan's comments
  2022-12-04  4:23   ` scratch/backend-completion 1af23aade6f: More tweaks to external-completion.el after Stefan's comments Stefan Monnier
@ 2022-12-04  9:45     ` João Távora
  0 siblings, 0 replies; 2+ messages in thread
From: João Távora @ 2022-12-04  9:45 UTC (permalink / raw)
  To: Stefan Monnier; +Cc: emacs-devel

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

On Sun, Dec 4, 2022, 04:23 Stefan Monnier <monnier@iro.umontreal.ca> wrote:

> > +Despite the original authors's best efforts,
> > +TRY-COMPLETION-FUNCTION is still a poorly understood
> > +implementation detail.  If you understand what it's for, you
>
> FWIW, I'm not really the original author of try-completion.
> More specifically, the `try-completion` function itself predates my
> involvement with Emacs, and its generalization in
> `partial-completion-mode` as well.  I do take responsability for
> `completion-try-completion`, admittedly, where I tried to give an
> "official" interface to that operation, but I was just trying to
> preserve existing semantics.



Thanks for the insight. But I meant the original author of this function,
of course. I don't have a gripe with try-completion. I'm sure it's doing
useful stuff. I just don't know what to write in this docstring for it to
teach the caller how to use the argument effectively.  Please help me, it's
the last thing that needs to be done, i think.

And of course I'll squash all this silly history afterwards, this is just a
scratch branch.

>
>

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

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2022-12-04  9:45 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
     [not found] <167011058506.11167.15396713347917244845@vcs2.savannah.gnu.org>
     [not found] ` <20221203233625.5BBB0C00B0F@vcs2.savannah.gnu.org>
2022-12-04  4:23   ` scratch/backend-completion 1af23aade6f: More tweaks to external-completion.el after Stefan's comments Stefan Monnier
2022-12-04  9:45     ` João Távora

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