From: Thierry Volpiatto <thierry.volpiatto@gmail.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org
Subject: Re: lisp-completion-at-point "end" position.
Date: Tue, 02 Aug 2011 22:35:44 +0200 [thread overview]
Message-ID: <877h6vr1pb.fsf@gmail.com> (raw)
In-Reply-To: <jwvaabrd19j.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Tue, 02 Aug 2011 16:11:48 -0400")
Stefan Monnier <monnier@iro.umontreal.ca> 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
next prev parent reply other threads:[~2011-08-02 20:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-19 16:09 lisp-completion-at-point "end" position Thierry Volpiatto
2011-08-02 2:50 ` Stefan Monnier
2011-08-02 4:58 ` Thierry Volpiatto
2011-08-02 18:53 ` Stefan Monnier
2011-08-02 19:14 ` Thierry Volpiatto
2011-08-02 20:11 ` Stefan Monnier
2011-08-02 20:35 ` Thierry Volpiatto [this message]
2011-08-03 1:07 ` Stefan Monnier
2011-08-03 4:35 ` Thierry Volpiatto
2011-08-03 14:21 ` Stefan Monnier
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=877h6vr1pb.fsf@gmail.com \
--to=thierry.volpiatto@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).