Re: [GNU ELPA] New package proposal: aggressive-completion.el

["T.V Raman" <raman@google.com>]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=gb18030, Size: 1653 bytes --]

Tassilo Horn <tsdh@gnu.org> writes:


I use ido and ido-completing-read+ and  just tried this new package, was

But installing it from elpa and enabling it as documented made no
perceptible difference in the minibuffer with commands like find-file, I
waited longer than a second and nothing happened "automatically".
hoping it would work alongside those.


> "Basil L. Contovounesios" <contovob@tcd.ie> writes:
>
> Hi Basil,
>
>>> (defcustom aggressive-completion-no-complete-commands
>>>   '( left-char icomplete-fido-backward-updir minibuffer-complete
>>>      right-char delete-backward-char backward-kill-word
>>>      backward-kill-paragraph backward-kill-sentence backward-kill-sexp
>>>      delete-char kill-word kill-line completion-at-point)
>>>   "Commands after which automatic completion is not performed."
>>>   :type '(repeat command))
>>
>> Customising this gives an error, because there is no such thing as a
>> 'command type (yet).  It should probably be '(repeat function).
>
> Indeed.  I've just fixed that in 1.2.  Also, that variable is now
> `aggressive-completion-auto-complete-commands' because Stefan made me
> aware that a whitelist of commands after which auto-completion kicks in
> is much more compact than a blacklist of commands where it shouldn't
> kick in.
>
> And then I got a (wrong-type-argument number-or-marker-p tab), fixed it,
> and pushed 1.3 some minutes after 1.2.
>
> How hard can it be to get it right on the first try?!? ;-)
>
>> Thanks for the cool package,
>
> You're welcome!
>
> Bye,
> Tassilo
>

-- 

Thanks,

--Raman
7©4 Id: kg:/m/0285kf1  •0Ü8