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: Sat, 03 Apr 2021 19:49:41 -0400 [thread overview]
Message-ID: <jwvh7knvss3.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <E6BC3D85-0FE1-4510-A698-0829D5755FF1@gmail.com> (JD Smith's message of "Sat, 3 Apr 2021 18:23:28 -0400")
> So it’s a quandary: I won’t yet know `beg’ and `end’ until _after_
> interacting with iPython. Is there any way to “revise” ‘beg’ and ‘end’ in
> a collection function returned from a CAPF?
Indeed, that's a problem.
You might be able to get away with the following:
Make your CAPF function return a beg..end that covers "the whole line"
and which returns a completion table in the form of a function.
That function will then defer to the iPython code for the grunt of its
work and will return the "real" boundaries via the
`completion-boundaries` method. This will probably require some caching
in the completion table so we don't call iPython too many times for
a single completion (like once for `completion-boundaries`, once for
`try-completion`, once for `all-completions`, etc...).
The completion is written under the assumption that
`completion-boundaries` is cheaper to perform than `all-completions`,
so there's a risk it won't work very well, but my intuition tells me it
should work "well enough".
Stefan
next prev parent reply other threads:[~2021-04-03 23:49 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 [this message]
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
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=jwvh7knvss3.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).