From: Dmitry Gutov <dgutov@yandex.ru>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: 18265@debbugs.gnu.org
Subject: bug#18265: 24.3.92; lisp-completion-at-point should return nil in comments, unless after `
Date: Fri, 15 Aug 2014 07:13:04 +0400 [thread overview]
Message-ID: <53ED7AC0.1050607@yandex.ru> (raw)
In-Reply-To: <jwvppg2v4k4.fsf-monnier+emacsbugs@gnu.org>
On 08/15/2014 07:04 AM, Stefan Monnier wrote:
> Good point. Makes me wonder how to extend completion-at-point-functions
> such that a function like lisp-completion-at-point could behave
> differently for something like Company (which calls it without the user
> making an explicit completion request) than for an explicit M-TAB.
Sometimes the user makes an explicit request, though. So it's "idle mode
vs manual mode", not "Company vs complete-symbol".
Still, the fact that user called `M-x company-complete' inside a comment
doesn't tell me that they actually want to see completions from
`company-capf' and not some other backend like `company-dabbrev'.
Likewise, user pressing C-M-i inside a comment might prefer not to talk
`lisp-completion-at-point', but some other completion function that goes
after it that's more suited for completion in comments.
If we really want to use `lisp-completion-at-point' in comments in more
cases, I'd try to detect whether we're probably in a code sample (by the
extra indentation, maybe), and otherwise return nil.
next prev parent reply other threads:[~2014-08-15 3:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-14 12:11 bug#18265: 24.3.92; lisp-completion-at-point should return nil in comments, unless after ` Dmitry
2014-08-15 3:04 ` Stefan Monnier
2014-08-15 3:13 ` Dmitry Gutov [this message]
2014-08-15 12:33 ` Stefan Monnier
2014-08-16 1:02 ` Dmitry Gutov
2014-08-16 18:00 ` Stefan Monnier
2014-09-19 3:56 ` Dmitry Gutov
2014-09-19 14:49 ` Stefan Monnier
2014-09-19 17:45 ` Dmitry Gutov
2014-09-20 1:55 ` Stefan Monnier
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=53ED7AC0.1050607@yandex.ru \
--to=dgutov@yandex.ru \
--cc=18265@debbugs.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.
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.