Re: lisp-completion-at-point "end" position.

[Thierry Volpiatto]

Stefan Monnier <address@hidden> writes:

>>>>>> (def(something) => doesn't complete def
>>>>>> (def! (something) => complete def
>>>>> A space should not be needed when the subsequent char is an open-paren.
>>>> At another level, not lisp-completion-at-point.
>>> 
>>> No, I mean for lisp-completion-at-point.  I.e. I can't reproduce the
>>> problem you show above.
>> If you eval:
>
>> (let ((data (lisp-completion-at-point))) (cadr data)) 
>
>> with point (!) at: 
>
>> (def!(something)
>
>> and then point (!) at: 
>
>> (def! (something)
>
>> You will get a different value.
>
> No, I get the same value.  I just tried with an "emacs -Q" on the trunk.
Yes, sorry, it works with this example.
It doesn't with:
(def!something

It's why i prefer always the value of point instead of end.

Thanks. 

-- 
A+ Thierry
Get my Gnupg key:
gpg --keyserver pgp.mit.edu --recv-keys 59F29997