all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Dmitry Gutov <dgutov@yandex.ru>
To: Stefan Monnier <monnier@iro.umontreal.ca>
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 21:45:52 +0400	[thread overview]
Message-ID: <541C6BD0.6000100@yandex.ru> (raw)
In-Reply-To: <jwvbnqb8y75.fsf-monnier+emacsbugs@gnu.org>

On 09/19/2014 06:49 PM, Stefan Monnier wrote:

>> 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)

The users might find it harder to modify these new c-a-p-f values if 
some packages add them during initialization, but otherwise this 
direction is quite in line with what we already do in Company.

And it's different from the `:merge-with-rest' property which you 
suggested earlier (a good thing, IMO).





  reply	other threads:[~2014-09-19 17:45 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
2014-09-19 17:45               ` Dmitry Gutov [this message]
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=541C6BD0.6000100@yandex.ru \
    --to=dgutov@yandex.ru \
    --cc=18265-done@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.