From: Drew Adams <drew.adams@oracle.com>
To: Dmitry Gutov <dgutov@yandex.ru>, Eli Zaretskii <eliz@gnu.org>
Cc: 24663@debbugs.gnu.org
Subject: bug#24663: 24.5; doc string of `completion-at-point-functions'
Date: Thu, 13 Oct 2016 14:29:11 -0700 (PDT) [thread overview]
Message-ID: <cd2c16e8-f439-49d7-9611-ef2b8ec658f4@default> (raw)
In-Reply-To: <4009a3e5-1fd4-fa68-a48d-48dacb181e96@yandex.ru>
> >> AROUND point.
> >
> > Really? In that case, that's what needs to be said in the doc.
> >
> > Of course, if it is AROUND point then presumably any text in the
> > buffer can be used to determine what's to be completed (and in
> > turn what the possible completions are). It could use only the
> > first two or last six characters of the buffer, ignoring the
> > text immediately surrounding point.
>
> Not really. The region to complete has to include the point.
The entire text in the buffer is AROUND point and includes point.
But maybe you are mentioning another part of the behavior: some
text around point is REPLACED by one of the completion candidates.
If that is part of the behavior then that too should be mentioned
in the doc.
next prev parent reply other threads:[~2016-10-13 21:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <<<2178d9e1-fd5c-4045-9a10-d0c45b0de591@default>
[not found] ` <<<83fuo088wa.fsf@gnu.org>
[not found] ` <<225e9a9e-eaa2-4c6a-96f8-7106a9817491@default>
[not found] ` <<83eg3k815a.fsf@gnu.org>
2016-10-13 20:33 ` bug#24663: 24.5; doc string of `completion-at-point-functions' Drew Adams
2016-10-13 20:35 ` Dmitry Gutov
2016-10-13 21:18 ` Drew Adams
2016-10-13 21:26 ` Dmitry Gutov
2016-10-13 21:29 ` Drew Adams [this message]
[not found] <<2178d9e1-fd5c-4045-9a10-d0c45b0de591@default>
[not found] ` <<83fuo088wa.fsf@gnu.org>
2016-10-13 19:46 ` Drew Adams
2016-10-13 20:06 ` Eli Zaretskii
2016-10-10 21:14 Drew Adams
2016-10-13 17:18 ` Eli Zaretskii
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=cd2c16e8-f439-49d7-9611-ef2b8ec658f4@default \
--to=drew.adams@oracle.com \
--cc=24663@debbugs.gnu.org \
--cc=dgutov@yandex.ru \
--cc=eliz@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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.