unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "João Távora" <joaotavora@gmail.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel <emacs-devel@gnu.org>
Subject: Re: scratch/backend-completion 1af23aade6f: More tweaks to external-completion.el after Stefan's comments
Date: Sun, 4 Dec 2022 09:45:45 +0000	[thread overview]
Message-ID: <CALDnm51OL8rL+=O3-7YoNN8FE9U88xotzuvbsftidGso9ECWHg@mail.gmail.com> (raw)
In-Reply-To: <jwv359vzto2.fsf-monnier+emacs@gnu.org>

[-- 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 --]

      reply	other threads:[~2022-12-04  9:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [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 [this message]

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='CALDnm51OL8rL+=O3-7YoNN8FE9U88xotzuvbsftidGso9ECWHg@mail.gmail.com' \
    --to=joaotavora@gmail.com \
    --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).