From: Stefan Monnier <monnier@iro.umontreal.ca>
To: eric@siege-engine.com
Cc: Chong Yidong <cyd@stupidchicken.com>, emacs-devel@gnu.org
Subject: Re: Completions in Semantic
Date: Mon, 19 Oct 2009 16:06:26 -0400 [thread overview]
Message-ID: <jwvoco3qhk8.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <1255980824.6961.1075.camel@projectile.siege-engine.com> (Eric M. Ludlam's message of "Mon, 19 Oct 2009 15:33:44 -0400")
>> You mean like lisp-complete-symbol but modal?
> Yes, that's what I meant, but in light of your simplified description, I
> suppose it doesn't matter much. If there was a single function like
> 'completing-read' that took arguments to control what proposed text
> after the cursor was, I suppose it wouldn't matter what happened
> underneath. I used overlays and overlay keymaps.
> You could try semantic-complete-analyze-inline on something that needs
> completing to see the effect I was going for. It should work for Lisp
> or C code.
> I would expect designing such a thing would be challenging since the
> rules for what is before the cursor is a bit vague and language
> specific, so it might belong in a tool like Semantic.
We have `symbol-complete' although I'm not very happy about its API.
But something along thses lines would be good. When I rewrite the
minibuffer completion code I tried to make it possible to use it in
non-minibuffer contexts, so for example lisp-complete-symbol nowadays
uses minibuffer-complete internally.
I also intend to consolidate the comint completion this way, tho it's
more difficult because its current UI is slightly different. Part of
the difficulty is how to determine when the "completion is done" so as
to know when to pop-down the *Completions* buffer (if any). Maybe the
best option is to pop-down *Completions* eagerly ("all the time").
Stefan
next prev parent reply other threads:[~2009-10-19 20:06 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-18 23:00 Completions in Semantic Chong Yidong
2009-10-18 23:55 ` Miles Bader
2009-10-19 3:50 ` Eric M. Ludlam
2009-10-19 13:48 ` Stefan Monnier
2009-10-19 16:26 ` Eric M. Ludlam
2009-10-19 18:29 ` Stefan Monnier
2009-10-19 19:33 ` Eric M. Ludlam
2009-10-19 20:06 ` Stefan Monnier [this message]
2009-10-19 22:17 ` Eric M. Ludlam
2009-10-20 0:07 ` Lennart Borgman
2009-10-30 21:17 ` Toby Cubitt
2009-10-30 21:37 ` Lennart Borgman
2009-10-20 0:14 ` Stefan Monnier
2009-10-20 20:20 ` Eric M. Ludlam
2009-10-21 10:58 ` Lluis
2009-10-21 12:35 ` Eric M. Ludlam
2009-10-21 13:28 ` Lluis
2009-10-21 17:35 ` Eric M. Ludlam
2009-10-22 20:12 ` Stefan Monnier
2009-10-27 21:21 ` Lluis
2009-10-28 0:56 ` Stefan Monnier
2009-10-28 2:25 ` Eric M. Ludlam
2009-10-28 3:23 ` Stefan Monnier
2009-10-29 14:38 ` Lluis
2009-10-31 20:18 ` Stefan Monnier
2009-11-01 16:01 ` Lluís
2009-11-02 6:12 ` Stefan Monnier
2009-11-02 12:13 ` Eric M. Ludlam
2009-10-22 20:00 ` Stefan Monnier
2009-10-19 23:52 ` Eric M. Ludlam
2009-10-21 14:07 ` Chong Yidong
2009-10-21 16:10 ` Eric M. Ludlam
2009-10-23 1:01 ` Chong Yidong
2009-10-23 1:28 ` Eric M. Ludlam
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=jwvoco3qhk8.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=cyd@stupidchicken.com \
--cc=emacs-devel@gnu.org \
--cc=eric@siege-engine.com \
/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).