unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: JD Smith <jdtsmith@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: Recommendation for CAPF setup when you don't know completion string in advance
Date: Tue, 11 May 2021 11:52:49 -0400	[thread overview]
Message-ID: <jwv1radp8z2.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <A1E14C88-94DB-430D-BA0C-B3D815BD4C47@gmail.com> (JD Smith's message of "Tue, 11 May 2021 09:42:21 -0400")

> Looking at `completion-table-with-context’, it seems just to prepend the
> prefix after the completion happens, if a string is returned from
> `complete-with-action'.

Indeed.

> I’m struggling then to understand the point of
> completion-boundaries lookup at all.

That's catering to more complex situations.
E.g. imagine completing

    foo:file/name:bar

where your code split this up into a `foo:` prefix and a `:bar` suffix,
and it uses the `completion-file-name-table` as completion table for the
"middle part".

In order to compute the overall boundaries to use when point is inside
"name", you need to add the length of the prefix to the boundaries
returned by `completion-file-name-table`.

IIUC in your case the completion-table used between prefix and suffix
will always be a "plain list" with no "nested" boundaries so you won't
need to worry about that.


        Stefan




  reply	other threads:[~2021-05-11 15:52 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-03 22:23 Recommendation for CAPF setup when you don't know completion string in advance JD Smith
2021-04-03 23:49 ` Stefan Monnier
2021-04-04  2:52   ` JD Smith
2021-04-04  3:20     ` Stefan Monnier
2021-04-04 15:29       ` JD Smith
2021-05-11  3:33   ` JD Smith
2021-05-11  4:04     ` Stefan Monnier
2021-05-11 13:42       ` JD Smith
2021-05-11 15:52         ` Stefan Monnier [this message]
2021-05-11 14:37       ` Daniel Mendler
2021-05-11 15:57         ` Stefan Monnier
2021-05-11 16:10           ` Daniel Mendler
2021-05-11 16:54             ` 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=jwv1radp8z2.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=emacs-devel@gnu.org \
    --cc=jdtsmith@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 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).