From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Leo <sdl.web@gmail.com>
Cc: 12852@debbugs.gnu.org
Subject: bug#12852: 24.2; `exit-function' not supported in completion table's metadata alist
Date: Sun, 11 Nov 2012 11:21:19 -0500 [thread overview]
Message-ID: <jwvd2zknmtr.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <m1mwyonner.fsf@gmail.com> (Leo's message of "Sun, 11 Nov 2012 23:56:44 +0800")
>> Hmm.. I don't really understand what this is trying to do.
>> Can you explain to me what should be the end result?
> I am writing a programmed completion table for python modules which
> should work like file name completion but separated by . instead of /.
> After each completion it should tell me whether the completion is a
> package to help me decide whether to type . and get further completions.
Any reason not actually add the ".", just like file-name completion
actually adds the / ?
> So for example, twisted.inte should complete to twisted.internet with
> minibuffer message [package] to mean that twisted.internet is a package.
Right, so it's like an annotation but only displayed when you select
that particular entry.
>>> Looks like with some change to completion--done we can have this.
>>> What do you think?
>> I have the impression that you're subverting exit-function.
>> I"m not sure yet if it's a neat hack, or if there's a better way to do it,
> Probably.
Not sure which of the two you think is probable. Maybe the "neat hack"
is the more probable one.
Stefan
next prev parent reply other threads:[~2012-11-11 16:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-10 7:28 bug#12852: 24.2; `exit-function' not supported in completion table's metadata alist Leo
2012-11-10 22:33 ` Stefan Monnier
2012-11-11 6:45 ` Leo
2012-11-11 15:41 ` Stefan Monnier
2012-11-11 15:56 ` Leo
2012-11-11 16:21 ` Stefan Monnier [this message]
2012-11-11 16:50 ` Leo
2012-11-23 3:22 ` Leo
2012-11-23 3:58 ` Stefan Monnier
2012-12-02 5:41 ` Leo
2022-02-09 9:10 ` Lars Ingebrigtsen
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=jwvd2zknmtr.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=12852@debbugs.gnu.org \
--cc=sdl.web@gmail.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).