From: Leo Liu <sdl.web@gmail.com>
To: Dmitry Gutov <dgutov@yandex.ru>
Cc: "18643@debbugs.gnu.org" <18643@debbugs.gnu.org>
Subject: bug#18643: 25.0.50; elisp--expect-function-p
Date: Thu, 16 Oct 2014 11:36:25 +0800 [thread overview]
Message-ID: <m338ao8z46.fsf@gmail.com> (raw)
In-Reply-To: <543F2ED7.5020603@yandex.ru> (Dmitry Gutov's message of "Thu, 16 Oct 2014 06:35:03 +0400")
On 2014-10-16 06:35 +0400, Dmitry Gutov wrote:
> Still, the text written in a way I described may be not Lisp code, but
> it's unlikely to be prose (unless it's a way of displaying a block
> quote?), so this kind of heuristic can be useful anyway.
In the past 1-2 months I happen to write an elisp tool from scratch,
which has the following stats:
component 1:
file1: 2744 lines
file2: 275 lines
component 2:
file1: 3194 lines
with component 2 v0.7.2 released on 08 Oct 2014. The packages are
developed using emacs trunk and happened to have some parts developed
before the change and others after the change. When I told you I tried
to live with it, I did try very hard.
Speaking from experience, the recent change to elisp-completion-at-point
has gotten in the way more than just once. It is painfully difficult to
see how this is an improvement to the default features.
(BTW, I hope to submit the packages for inclusion in emacs sometime
later)
Leo
next prev parent reply other threads:[~2014-10-16 3:36 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 [this message]
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
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=m338ao8z46.fsf@gmail.com \
--to=sdl.web@gmail.com \
--cc=18643@debbugs.gnu.org \
--cc=dgutov@yandex.ru \
/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).