From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Dmitry Gutov <dgutov@yandex.ru>
Cc: 18265-done@debbugs.gnu.org
Subject: bug#18265: 24.3.92; lisp-completion-at-point should return nil in comments, unless after `
Date: Fri, 19 Sep 2014 10:49:11 -0400 [thread overview]
Message-ID: <jwvbnqb8y75.fsf-monnier+emacsbugs@gnu.org> (raw)
In-Reply-To: <541BA95C.30400@yandex.ru> (Dmitry Gutov's message of "Fri, 19 Sep 2014 07:56:12 +0400")
>> While it's "counter to the c-a-p-f interface", the need to combine
>> several backends is sufficiently common that we need to support it somehow.
>> I hope a "merge" solution can use a less hackish solution than the
>> current ":exclusive no".
> I'm not convinced with this approach. At least, AFAICS, different users
> prefer to merge different backends together. For instance, some
> https://github.com/iquiw/company-ghc users like to merge its results with
> the plain company-dabbrev-code. Some, I believe, don't.
> If the completion function gets to decide that, it would be harder for users
> to customize.
It might be textually a bit more verbose, but other than that it
shouldn't be harder. I'm thinking of something like
(add-hook 'completion-at-point-functions
(completion-table-merge
ghc-completion-table dabbrev-completion-table)
nil t)
-- Stefan
next prev parent reply other threads:[~2014-09-19 14:49 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
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 [this message]
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=jwvbnqb8y75.fsf-monnier+emacsbugs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=18265-done@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).