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.


>> My concern was lisp-completion-at-point, not the completion UI of
>> emacs. (i don't use it).
>
> I understand that.  But completion-at-point-functions does allow point
> to be within the to-be-completed element (rather than only at its end)
> and so a UI that wants to use it needs to take this into account (it
> may for example elect to ignore the `end' and always use point instead).
Yes, i prefer `point' for my lisp completion.

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