From: Eli Zaretskii <eliz@gnu.org>
To: Drew Adams <drew.adams@oracle.com>
Cc: 24663@debbugs.gnu.org
Subject: bug#24663: 24.5; doc string of `completion-at-point-functions'
Date: Thu, 13 Oct 2016 23:06:09 +0300 [thread overview]
Message-ID: <83eg3k815a.fsf@gnu.org> (raw)
In-Reply-To: <225e9a9e-eaa2-4c6a-96f8-7106a9817491@default> (message from Drew Adams on Thu, 13 Oct 2016 12:46:19 -0700 (PDT))
> Date: Thu, 13 Oct 2016 12:46:19 -0700 (PDT)
> From: Drew Adams <drew.adams@oracle.com>
> Cc: 24663-done@debbugs.gnu.org
>
> > I changed that to say "the entity at point" because the rest of the
> > doc string refers to that.
>
> 1. It cannot be "THE" thing (or THE entity) at point. Which one?
The one at point.
> You can get different kinds of thing at point. You must provide
> the desired THING type, for "thing at point" to mean anything.
My understanding is that it's up to the hooks.
> 2. I don't see how/why saying "entity" changes anything, here.
> "THE" entity? What is that?
Then I guess I will say that I don't want to fix that part.
> 3. It is not text AT point that is completed. It is text BEFORE
> point that is completed. AT can only refer to characters after
> point, not before.
The doc string doesn't say "text", it says "entity". IOW, it doesn't
talk about characters.
next prev parent reply other threads:[~2016-10-13 20:06 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>
2016-10-13 19:46 ` bug#24663: 24.5; doc string of `completion-at-point-functions' Drew Adams
2016-10-13 20:06 ` Eli Zaretskii [this message]
[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 ` 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
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=83eg3k815a.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=24663@debbugs.gnu.org \
--cc=drew.adams@oracle.com \
/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.