From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Dmitry Gutov <dgutov@yandex.ru>
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 08:33:59 -0400 [thread overview]
Message-ID: <jwvy4uqhr9q.fsf-monnier+emacsbugs@gnu.org> (raw)
In-Reply-To: <53ED7AC0.1050607@yandex.ru> (Dmitry Gutov's message of "Fri, 15 Aug 2014 07:13:04 +0400")
> Sometimes the user makes an explicit request, though. So it's "idle mode vs
> manual mode", not "Company vs complete-symbol".
That's right.
> 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'.
Indeed, but it does say that it's better to return some completion table
than none. We'd want the lisp-completion-at-point to use something like
the ":exclusive no" property (or maybe a new ":merge-with-rest") in
this case.
> 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.
As it currently stands, there's no question that your original request
is right (the one stated in the "Subject:"), so feel free to fix it.
I'm just thinking of how we could also satisfy those who might want to
complete code-like things in comments, without having to resort
to customization.
Stefan
next prev parent reply other threads:[~2014-08-15 12:33 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
2014-08-15 12:33 ` Stefan Monnier [this message]
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
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=jwvy4uqhr9q.fsf-monnier+emacsbugs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=18265@debbugs.gnu.org \
--cc=dgutov@yandex.ru \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).