[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#16604: 24.3.50; False negatives in lisp-completion-at-point
From: |
Stefan Monnier |
Subject: |
bug#16604: 24.3.50; False negatives in lisp-completion-at-point |
Date: |
Sun, 02 Feb 2014 09:12:14 -0500 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/24.3.50 (gnu/linux) |
> Pity. It's a regression compared to company-elisp, as far as I'm concerned.
You can still use company-elisp in the mean time.
>> I also think it should be configurable (I definitely prefer the
>> current behavior; in my use cases your behavior makes the
>> lisp--local-variables-completion-table pretty much useless because
>> there's almost always some other global variable that starts with
>> a similar prefix).
> True, lisp--local-variables-completion-table is less useful this way, but it
> still plays a part when the binding form hasn't been evaluated yet, and so
> the local variable symbols aren't yet in obarray.
I guess it's true that if you choose among a list of completions (or
if you use completion cycling), the extra elements from obarray aren't
nearly as problematic as if you rely on just "plain completion".
Stefan
- bug#16604: 24.3.50; False negatives in lisp-completion-at-point, Dmitry Gutov, 2014/02/01
- bug#16604: 24.3.50; False negatives in lisp-completion-at-point, Stefan Monnier, 2014/02/01
- bug#16604: 24.3.50; False negatives in lisp-completion-at-point, Dmitry Gutov, 2014/02/01
- bug#16604: 24.3.50; False negatives in lisp-completion-at-point, Dmitry Gutov, 2014/02/04
- bug#16604: 24.3.50; False negatives in lisp-completion-at-point, Stefan Monnier, 2014/02/04
- bug#16604: 24.3.50; False negatives in lisp-completion-at-point, Dmitry Gutov, 2014/02/04
- bug#16604: 24.3.50; False negatives in lisp-completion-at-point, Stefan Monnier, 2014/02/05
- bug#16604: 24.3.50; False negatives in lisp-completion-at-point, Dmitry Gutov, 2014/02/05