From: Leo Liu <sdl.web@gmail.com>
To: Dmitry Gutov <dgutov@yandex.ru>
Cc: 11906@debbugs.gnu.org
Subject: bug#11906: 24.1; completion-at-point failures
Date: Fri, 06 Dec 2013 13:36:52 +0800 [thread overview]
Message-ID: <m1txempmkr.fsf@gmail.com> (raw)
In-Reply-To: <52A1534D.3000902@yandex.ru> (Dmitry Gutov's message of "Fri, 06 Dec 2013 06:32:13 +0200")
On 2013-12-06 12:32 +0800, Dmitry Gutov wrote:
> I don't understand what you mean by "doesn't need a completion table".
> Could you give an example?
See completion-at-point:
(let ((newstart (car-safe (funcall hookfun))))
(and newstart (= newstart start)))
so basically every command following completion-at-point calls HOOKFUN
to check if start matches, in this case it doesn't need the completion
table. Hopefully There will be more places to optimise if studying
minibuffer.el in more details.
Leo
next prev parent reply other threads:[~2013-12-06 5:36 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-11 5:54 bug#11906: 24.1; completion-at-point failures Leo
2012-07-12 14:00 ` Stefan Monnier
2013-05-10 6:38 ` Leo Liu
2013-05-10 20:36 ` Stefan Monnier
2013-05-11 1:50 ` Leo Liu
2013-05-11 3:40 ` Stefan Monnier
2013-05-11 4:47 ` Leo Liu
2013-05-11 14:51 ` Stefan Monnier
2013-05-13 1:28 ` Leo Liu
2013-05-13 15:27 ` Stefan Monnier
2013-05-14 0:56 ` Leo Liu
2013-05-14 2:53 ` Stefan Monnier
2013-05-14 3:30 ` Leo Liu
2013-05-11 20:18 ` Andreas Röhler
2013-05-11 23:11 ` Daimrod
2013-05-13 15:28 ` Stefan Monnier
2013-05-21 23:39 ` Dmitry Gutov
2013-05-22 19:16 ` Stefan Monnier
2013-12-05 3:23 ` Dmitry Gutov
2013-12-05 4:33 ` Stefan Monnier
2013-12-06 1:02 ` Dmitry Gutov
2013-12-06 4:00 ` Leo Liu
2013-12-06 4:32 ` Dmitry Gutov
2013-12-06 5:36 ` Leo Liu [this message]
2013-12-06 13:15 ` Dmitry Gutov
2013-12-06 14:04 ` Leo Liu
2013-12-06 17:35 ` Stefan Monnier
2013-12-07 2:05 ` Leo Liu
2013-12-07 22:45 ` Stefan Monnier
2013-12-06 17:36 ` Stefan Monnier
2013-12-07 2:02 ` Dmitry Gutov
2013-12-07 2:40 ` Leo Liu
2013-12-07 16:13 ` Dmitry Gutov
2013-12-09 2:27 ` Leo Liu
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=m1txempmkr.fsf@gmail.com \
--to=sdl.web@gmail.com \
--cc=11906@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).