From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: help-gnu-emacs@gnu.org
Subject: Re: merging results from completion-at-point-functions
Date: Fri, 29 Apr 2022 08:08:37 -0700 [thread overview]
Message-ID: <878rroylje.fsf@ericabrahamsen.net> (raw)
In-Reply-To: 87zgk4mbjp.fsf@ucl.ac.uk
Eric S Fraga <e.fraga@ucl.ac.uk> writes:
> Hello all,
>
> I currently use '(cape-dabbrev cape-ispell cape-dict) as the list for
> completion-at-point-functions when writing prose.
>
> I keep trying different orderings of these entries as the behaviour
> changes significantly, not surprisingly given the /greedy/ nature of
> completing-at-point, if I understand things correctly. Ideally, I would
> like a merged search for potential completions, such as I believe
> company-mode does if you group backends.
>
> Is it possible to specify a grouping or merge operation? Or is there a
> generalised capf that does this, I guess?
Two possibilities: since you're using cape, use `cape-super-capf' to
merge a bunch of cape capf functions into one.
Other possibility: use `completion-table-merge' in exactly the same way.
This should be the general version of what `cape-super-capf' does.
Please try both and report back! I'm very curious, as well.
Eric
next prev parent reply other threads:[~2022-04-29 15:08 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-29 10:25 merging results from completion-at-point-functions Eric S Fraga
2022-04-29 15:08 ` Eric Abrahamsen [this message]
2022-04-29 17:05 ` Eric S Fraga
2022-04-29 18:26 ` Eric Abrahamsen
2022-04-29 20:52 ` Stefan Monnier via Users list for the GNU Emacs text editor
2022-04-29 22:02 ` Eric Abrahamsen
2022-04-30 23:48 ` Ergus
2022-05-01 2:15 ` Stefan Monnier
2022-05-01 2:58 ` Emanuel Berg
2022-05-01 17:20 ` Stefan Monnier via Users list for the GNU Emacs text editor
2022-05-01 17:33 ` tomas
2022-05-01 19:54 ` Emanuel Berg
2022-05-01 16:29 ` Eric S Fraga
2022-05-01 17:22 ` Stefan Monnier via Users list for the GNU Emacs text editor
2022-05-02 11:47 ` Eric S Fraga
2022-05-01 16:31 ` Eric S Fraga
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=878rroylje.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.net \
--cc=help-gnu-emacs@gnu.org \
/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.
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).