unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Stefan Monnier via Users list for the GNU Emacs text editor <help-gnu-emacs@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: merging results from completion-at-point-functions
Date: Sun, 01 May 2022 13:22:49 -0400	[thread overview]
Message-ID: <jwvv8upb24d.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: 87mtg1kygt.fsf@ucl.ac.uk

Eric S Fraga [2022-05-01 17:29:54] wrote:
> On Friday, 29 Apr 2022 at 16:52, Stefan Monnier via Users list for the GNU Emacs text editor wrote:
>>>> (setq-local completion-at-point-functions
>>>>     (list (cape-super-capf #'cape-dabbrev #'cape-dict #'cape-keyword)))
>>
>> Note that this sets up these CAPF functions only for the buffer that's
>> current when the code is executed, so if you put it into your .emacs
>> it's probably going to affect completions in *scratch* only.
>
> Yes, that's clear.  Thank you.
>
> I am setting the variable in the right place to have
> it set for the buffer I am writing in.  But it just doesn't do anything
> when I try to complete.
>
> To check, if I use
>
> (setq-local completion-at-point-functions (list #'cape-dabbrev))
>
> instead of the expression above, that particular capf does get invoked.

What happens if you go to the place where you want completion to take
place and then do:

    M-: (funcall (cape-super-capf #'cape-dabbrev #'cape-dict #'cape-keyword)) RET

[ It's not supposed to have any effect other than returning a value, so
  the question is what value does it return.  ]


        Stefan




  reply	other threads:[~2022-05-01 17:22 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
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 [this message]
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=jwvv8upb24d.fsf-monnier+emacs@gnu.org \
    --to=help-gnu-emacs@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.
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).