From: Dmitry Gutov <dgutov@yandex.ru>
To: Leo Liu <sdl.web@gmail.com>
Cc: 18643@debbugs.gnu.org
Subject: bug#18643: 25.0.50; elisp--expect-function-p
Date: Thu, 09 Oct 2014 10:17:32 +0400 [thread overview]
Message-ID: <5436287C.3080805@yandex.ru> (raw)
In-Reply-To: <m3h9zdkjge.fsf@gmail.com>
On 10/09/2014 07:31 AM, Leo Liu wrote:
> It is the false negatives that kill its usefulness in the case of elisp.
I disagree with the word "kill" here. Somewhat diminish, maybe.
> For example, (ert-deftest |) and (defun |) no longer have the
> completions I need.
These would be trivial to improve.
>> I'm pretty sure writing a new variable definition is a much less
>> frequent operation than referring to a variable in a function, or
>> writing a function call. And code completion is most useful when one is
>> referring to existing variables and functions.
>
> I won't jump to such conclusions so soon. You are guessing users'
> editing habits too much.
In which part? The lower frequency of new definitions is self-evident, I
think.
> What is hard is having a good algorithm to determine completion types
> correctly. Unfortunately what we have has too many false negatives. I'd
> much prefer offering multiple candidates instead of showing no
> completions and with completion-cycling I can get to most completions in
> under a second.
In that case, I guess you'll have to add a user option.
`lisp-completion-at-point-uses-context', or something like that.
> My bug report is not based on anything other than completion-at-point,
Does that mean my suggestions can't be based on anything else?
> the plain/standard emacs completion UI, which is what I use for elisp
> for a long while and I am quite content with it. It can be less optimal
> for other languages. but for elisp it has worked well in the past.
I've been using it for a while as well, and I wouldn't say it was, or
is, perfect.
next prev parent reply other threads:[~2014-10-09 6:17 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 [this message]
2014-10-09 15:27 ` Stefan Monnier
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=5436287C.3080805@yandex.ru \
--to=dgutov@yandex.ru \
--cc=18643@debbugs.gnu.org \
--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.