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: Completion in org mode: why pcomplete?
Date: Tue, 21 Dec 2021 09:26:55 -0800	[thread overview]
Message-ID: <874k717tsw.fsf@ericabrahamsen.net> (raw)
In-Reply-To: 878rwee3if.fsf@ucl.ac.uk

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

> On Monday, 20 Dec 2021 at 20:11, Eric Abrahamsen wrote:
>> [...]
>> What I'd like to know is if I can ditch pcomplete altogether, bind C-M-i
>> to `completion-at-point', and just put my completion functions in
>> `completion-at-point-functions' directly.
>
> Hi Eric,
>
> I look forward to seeing what you find.

I switched the key-binding of C-M-i to call `completion-at-point'
directly, and the Org-specific completion still worked just fine, so
that's something!

I notice that `ispell-complete-word' has a FIXME about
`completion-at-point-functions', so I assume it doesn't currently work
with capf. But it's nice to know that someone (Stefan Monnier,
naturally) wishes it would (or he did back in 2012, when he added that
comment).

> In the meantime, you might wish to have a look at hippie-expand which
> does something similar to what you want in terms of accessing a number
> of sources for generating the completions.

I do know about hippie expand, but it seems like a repeat of the same
problem: another mini-framework that can draw completions from multiple
sources. It feels like capf is going to be that framework in the future,
so I'd like to try hard to stick to that, if possible.

Eric




      reply	other threads:[~2021-12-21 17:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-21  4:11 Completion in org mode: why pcomplete? Eric Abrahamsen
2021-12-21  9:00 ` Eric S Fraga
2021-12-21 17:26   ` Eric Abrahamsen [this message]

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=874k717tsw.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).