From: Dmitry Gutov <dgutov@yandex.ru>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: 16604@debbugs.gnu.org
Subject: bug#16604: 24.3.50; False negatives in lisp-completion-at-point
Date: Sun, 02 Feb 2014 05:00:09 +0200 [thread overview]
Message-ID: <52EDB4B9.9000901@yandex.ru> (raw)
In-Reply-To: <jwvlhxuutr7.fsf-monnier+emacsbugs@gnu.org>
On 02.02.2014 04:39, Stefan Monnier wrote:
> I think it should wait.
Pity. It's a regression compared to company-elisp, as far as I'm concerned.
> I also think it should be configurable (I
> definitely prefer the current behavior; in my use cases your behavior
> makes the lisp--local-variables-completion-table pretty much useless
> because there's almost always some other global variable that starts
> with a similar prefix).
True, lisp--local-variables-completion-table is less useful this way,
but it still plays a part when the binding form hasn't been evaluated
yet, and so the local variable symbols aren't yet in obarray.
If you were using Company, by the way, you could take advantage of the
ordering of candidates based on their occurrences in the visible part of
the buffer, which will be supported in the next version. Naturally,
local vars will be at the top, as long as they're visible in the window.
next prev parent reply other threads:[~2014-02-02 3:00 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-31 4:46 bug#16604: 24.3.50; False negatives in lisp-completion-at-point Dmitry Gutov
2014-01-31 14:34 ` Stefan Monnier
2014-01-31 14:37 ` Dmitry Gutov
2014-01-31 15:05 ` Thierry Volpiatto
2014-02-02 1:52 ` Dmitry Gutov
2014-02-02 2:39 ` Stefan Monnier
2014-02-02 3:00 ` Dmitry Gutov [this message]
2014-02-02 14:12 ` Stefan Monnier
2014-02-02 18:24 ` Stefan Monnier
2014-02-03 2:03 ` Stefan Monnier
2014-02-03 3:48 ` Stefan Monnier
2014-02-04 5:37 ` Dmitry Gutov
2014-02-04 17:54 ` Stefan Monnier
2014-02-05 4:41 ` Dmitry Gutov
2014-02-05 13:53 ` Stefan Monnier
2014-02-06 1:38 ` Dmitry Gutov
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=52EDB4B9.9000901@yandex.ru \
--to=dgutov@yandex.ru \
--cc=16604@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 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).