From: Ergus <spacibba@aol.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: help-gnu-emacs@gnu.org
Subject: Re: merging results from completion-at-point-functions
Date: Sun, 1 May 2022 01:48:08 +0200 [thread overview]
Message-ID: <20220430234808.xcirau7rpks5bmuf@Ergus> (raw)
In-Reply-To: <jwvr15fpqaz.fsf-monnier+emacs@gnu.org>
On Fri, Apr 29, 2022 at 04:52:21PM -0400, 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.
>
>> (setq my-merged-table (completion-table-merge #'cap-dabbrev
>> #'cape-dict))
>
>I don't think so: `cape-dabbrev` is a CAPF function, not a completion table.
>
>
> Stefan
>
>
Hi Stefan...
Maybe a bit off-topic... but somehow related:
Is it there a way to show the current capf backend for example in the
mode-line?? Company has such thing, and it may be useful for example, to
know which completion-at-point-functions is working better than
others... Because sometimes different functions generate similar
outputs and it may be useful to know which are the one in use, specially
when exclusive is false in some of them.
Any Idea?
Best,
Ergus.
next prev parent reply other threads:[~2022-04-30 23:48 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 [this message]
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=20220430234808.xcirau7rpks5bmuf@Ergus \
--to=spacibba@aol.com \
--cc=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).