all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Dmitry Gutov <dgutov@yandex.ru>
To: Drew Adams <drew.adams@oracle.com>, 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 23:35:58 +0300	[thread overview]
Message-ID: <94371f44-4d03-64f2-ed88-edff3546a399@yandex.ru> (raw)
In-Reply-To: <30cc62fc-abee-4f28-9677-82c610b841c5@default>

On 13.10.2016 23:33, Drew Adams wrote:

>>> 1. It cannot be "THE" thing (or THE entity) at point.  Which one?
>>
>> The one at point.
>
> The symbol? word? file name? URL? ... (yes, ... - there are any
> number of kinds of things, most of which - nay, all of which -
> could be completed.

The code in the hooks decides that. In practice, it's a part of a major 
or a minor mode.

>> My understanding is that it's up to the hooks.
>
> Then them most that the doc can & should say is that SOMETHING

What does that mean?

> (some text) BEFORE point, is susceptible to completion.

AROUND point.





  reply	other threads:[~2016-10-13 20:35 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 [this message]
2016-10-13 21:18           ` Drew Adams
2016-10-13 21:26             ` Dmitry Gutov
2016-10-13 21:29               ` Drew Adams
     [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=94371f44-4d03-64f2-ed88-edff3546a399@yandex.ru \
    --to=dgutov@yandex.ru \
    --cc=24663@debbugs.gnu.org \
    --cc=drew.adams@oracle.com \
    --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.