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: Sat, 11 Oct 2014 20:31:33 +0400 [thread overview]
Message-ID: <54395B65.2060704@yandex.ru> (raw)
In-Reply-To: <m3r3ygpmre.fsf@gmail.com>
On 10/10/2014 08:33 AM, Leo Liu wrote:
> Sorry, I am merely reporting this as a usability bug and I don't intend
> to get too deep into it (too little time :().
I'm not asking you to code, just to read the available info. Otherwise
you're assuming others have the time to repeat the discussions.
> I failed so I spoke up but not to blame any change.
Why not? vc-annotate is a standard tool.
> 1. Leave room for other usage habits;
Sure. But unfortunately, supporting a set of different usage habits
means the result may be suboptimal for some of them.
On 10/11/2014 04:25 AM, Leo Liu wrote:
> This gives me a sense that you are thinking about a situation when
> someone uses company and has the completions displayed immediately.
Yes, that's my point of reference. But on the other hand, you could say
that it just emphasises the existing problem: Lisp code outside of
quotes usually constitutes the minority of the text in docstrings (and
moreso in comments). The rest of the text would be better served by a
different completion function (maybe dictionary-based, like Ispell). And
if `lisp-completion-at-point' offers completions there, no other
completion function can do so.
> In standard default emacs behaviour, I had never getting anything
> without me asking for it, be it in comments or strings or code. They
> only appear when I ask.
Maybe someone else would prefer to see actual words as completions, when
they are writing prose?
next prev parent reply other threads:[~2014-10-11 16:31 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
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 [this message]
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=54395B65.2060704@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.