From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Leo Liu <sdl.web@gmail.com>
Cc: Dmitry Gutov <dgutov@yandex.ru>, 18643@debbugs.gnu.org
Subject: bug#18643: 25.0.50; elisp--expect-function-p
Date: Thu, 09 Oct 2014 11:27:44 -0400 [thread overview]
Message-ID: <jwv1tqhffaf.fsf-monnier+emacsbugs@gnu.org> (raw)
In-Reply-To: <m3h9zdkjge.fsf@gmail.com> (Leo Liu's message of "Thu, 09 Oct 2014 11:31:13 +0800")
> It is the false negatives that kill its usefulness in the case of elisp.
> For example, (ert-deftest |) and (defun |) no longer have the
> completions I need.
Dmitry, what is it exactly that changed?
I mean, Elisp completion has been context-sensitive "for ever", so the
change is not that it now is, but that it now reacts to the
context differently.
Oh, I think I see: the change is the introduction of
elisp--form-quoted-p such that if elisp--form-quoted-p returns nil
(and we're not expecting a function), we only complete against var names
instead of the previous behavior of expanding against "anything".
I think this is not right: we should have a elisp--expect-exp-p
which returns non-nil in a context where we know the symbol at point
should be a valid expression (i.e. a variable). Not sure how to write
it, tho, but in its absence I think we're better off completing against
"anything" than restricting ourselves to variables.
BTW, to improve on these behaviors, one approach is to take the
macro-expansion code used in elisp--local-variables and use it
"everywhere". I.e. expand elisp--local-variables so it doesn't just
return the list of local vars, but also returns whether we're inside
a quote, or we're expecting a function, or we're expecting an expression.
Stefan
next prev parent reply other threads:[~2014-10-09 15:27 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-06 5:13 bug#18643: 25.0.50; elisp--expect-function-p Leo Liu
2014-10-09 2:50 ` Dmitry Gutov
2014-10-09 3:31 ` Leo Liu
2014-10-09 6:17 ` Dmitry Gutov
2014-10-09 15:27 ` Stefan Monnier [this message]
2014-10-09 23:43 ` Leo Liu
2014-10-10 1:16 ` Stefan Monnier
2014-10-10 4:07 ` Leo Liu
2014-10-10 13:25 ` Stefan Monnier
2014-10-10 20:53 ` Dmitry Gutov
2014-10-11 0:25 ` Leo Liu
2014-10-11 13:48 ` Stefan Monnier
2014-10-11 14:21 ` Leo Liu
2014-10-14 18:32 ` Stefan Monnier
2014-10-16 2:42 ` Dmitry Gutov
2014-10-16 13:10 ` Stefan Monnier
2014-10-11 13:47 ` Stefan Monnier
2014-10-11 16:18 ` Dmitry Gutov
2014-10-14 18:34 ` Stefan Monnier
2014-10-16 2:35 ` Dmitry Gutov
2014-10-16 3:36 ` Leo Liu
2014-10-16 9:59 ` Dmitry Gutov
2014-10-11 0:16 ` Leo Liu
2014-10-10 3:56 ` Dmitry Gutov
2014-10-10 4:33 ` Leo Liu
2014-10-11 16:31 ` Dmitry Gutov
2014-10-10 3:34 ` Dmitry Gutov
2014-10-10 13:20 ` Stefan Monnier
2014-10-11 17:07 ` Dmitry Gutov
2022-04-26 13:44 ` Lars Ingebrigtsen
2022-04-26 15:46 ` Leo Liu
2022-04-27 11:52 ` Lars Ingebrigtsen
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=jwv1tqhffaf.fsf-monnier+emacsbugs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=18643@debbugs.gnu.org \
--cc=dgutov@yandex.ru \
--cc=sdl.web@gmail.com \
/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.