unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
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 11:26:13 -0700	[thread overview]
Message-ID: <87y1znyce2.fsf@ericabrahamsen.net> (raw)
In-Reply-To: 87r15flt0w.fsf@ucl.ac.uk

Eric S Fraga <e.fraga@ucl.ac.uk> writes:

> Hi Eric,
>
> thank you for the quick response.
>
> On Friday, 29 Apr 2022 at 08:08, Eric Abrahamsen wrote:
>> Two possibilities: since you're using cape, use `cape-super-capf' to
>> merge a bunch of cape capf functions into one.
>
> First of all, apologies: this is in the cape documentation which I
> forgot to look at again.  Nevertheless, this doesn't work at all.  If I
> do
>
> (setq-local completion-at-point-functions
>     (list (cape-super-capf #'cape-dabbrev #'cape-dict #'cape-keyword)))
>
> when visiting an appropriate file, as the web page
> (https://github.com/minad/cape) suggests, nothing happens when invoking
> completion-at-point.

Sounds like some kind of bug, then. I'd check the github issues (several
of the closed issues are about super capes) and maybe open a new one.

>> Other possibility: use `completion-table-merge' in exactly the same way.
>
> This one I cannot figure out how to use.  My elisp-fu is obviously not
> up to scratch. :-(

No worries! It's supposed to work the same way:

(setq my-merged-table (completion-table-merge #'cap-dabbrev
#'cape-dict))

(setq-local completion-at-point-functions (list #'my-merged-table))

That appears to be working for me (at least, it raises a "lookup-words"
error from `cape-dict', so at least it's *trying* to work).

Eric





  reply	other threads:[~2022-04-29 18:26 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
2022-04-29 17:05   ` Eric S Fraga
2022-04-29 18:26     ` Eric Abrahamsen [this message]
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=87y1znyce2.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).