From: Lars Ingebrigtsen <larsi@gnus.org>
To: Stefan Monnier <monnier@IRO.UMontreal.CA>
Cc: emacs-devel@gnu.org
Subject: Re: Limit what M-x TAB lists?
Date: Thu, 26 Dec 2013 16:24:23 +0100 [thread overview]
Message-ID: <87wqirhbyw.fsf@building.gnus.org> (raw)
In-Reply-To: <jwvob43wtxz.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Thu, 26 Dec 2013 09:58:25 -0500")
Stefan Monnier <monnier@IRO.UMontreal.CA> writes:
>> 2) New form like (command-interactive 'vc-mode "p")
>
> More generally, move the "sanity checks" performed at the beginning of
> some commands to a special place so they can be run without actually
> calling the function. IOW add a "callable" predicate alongside the
> interactive-spec that M-x could then use to filter out
> inapplicable commands.
Hm, yes, that would be nice. Then multi-mode commands like
`quit-window' could have a complex predicate that does the right thing,
while very mode-specific commands like `gnus-summary-catchup-to-here'
could have a simple (mode-only) predicate.
If these predicates become very complex, then `M-x fooTAB' would become
exceedingly slow, though...
> Of course, this will require many changes in many packages before it
> becomes really useful.
Yes, but modes could be converted gradually, and things would get better
and better as time passes...
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog http://lars.ingebrigtsen.no/
next prev parent reply other threads:[~2013-12-26 15:24 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-26 14:18 Limit what M-x TAB lists? Lars Ingebrigtsen
2013-12-26 14:58 ` Stefan Monnier
2013-12-26 15:24 ` Lars Ingebrigtsen [this message]
2013-12-26 16:03 ` Óscar Fuentes
2013-12-26 16:09 ` Lars Ingebrigtsen
2013-12-26 17:50 ` Stefan Monnier
2013-12-26 18:03 ` Lars Ingebrigtsen
2013-12-27 1:41 ` Lars Ingebrigtsen
2014-01-03 18:00 ` Ted Zlatanov
2014-01-06 15:47 ` Davis Herring
2014-01-18 17:43 ` Lars Ingebrigtsen
2013-12-26 17:50 ` Tom
2014-01-11 21:07 ` Nix
2014-01-11 23:38 ` Drew Adams
2013-12-27 7:29 ` Stephen J. Turnbull
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=87wqirhbyw.fsf@building.gnus.org \
--to=larsi@gnus.org \
--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).