|
From: | Dmitry Gutov |
Subject: | bug#11906: 24.1; completion-at-point failures |
Date: | Fri, 06 Dec 2013 15:15:09 +0200 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.1.1 |
On 06.12.2013 07:36, Leo Liu wrote:
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.
But that function is fast! Compared to doing the actual completion, the time it takes to `(funcall hookfun)' should be negligible:
ELISP> (js2-time (setq ocap (with-current-buffer "*Inferior Octave*" (octave-completion-at-point))))
0.0ELISP> (js2-time (with-current-buffer "*Inferior Octave*" (funcall (nth 2 ocap) "a" nil t)))
0.0055
[Prev in Thread] | Current Thread | [Next in Thread] |