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 21:14:21 +0200 [thread overview]
Message-ID: <87fwljr5gy.fsf@gmail.com> (raw)
In-Reply-To: <jwvd3gnfy1f.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Tue, 02 Aug 2011 14:53:44 -0400")
Stefan Monnier <monnier@iro.umontreal.ca> writes:
>> (let ((completion-styles 'emacs22))
>> (lisp-completion-at-point))
>
> completion-styles does not influence the set of completions and the
> completion field (which is what lisp-completion-at-point returns).
> Instead it influences how the completion UI acts on that information.
>
> I.e. the value of completion-styles is only used when completion is
> actually performed (e.g. by completion-in-region).
I understood that.
>>>> Is there a good reason for that?
>>> I'll let you judge whether it's good or not. But it's the same behavior
>>> as in the minibuffer.
>> It's inconvenient to have to type a space just to have completion.
>> e.g:
>> (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.
My concern was lisp-completion-at-point, not the completion UI of
emacs. (i don't use it).
Thanks for infos.
--
A+ Thierry
Get my Gnupg key:
gpg --keyserver pgp.mit.edu --recv-keys 59F29997
next prev parent reply other threads:[~2011-08-02 19:14 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 [this message]
2011-08-02 20:11 ` Stefan Monnier
2011-08-02 20:35 ` Thierry Volpiatto
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87fwljr5gy.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.