From: Alan Mackenzie <acm@muc.de>
To: Miles Bader <miles@gnu.org>
Cc: Stefan Monnier <monnier@iro.umontreal.ca>, emacs-devel@gnu.org
Subject: Re: Interactive hat.
Date: Wed, 25 Mar 2009 10:53:16 +0000 [thread overview]
Message-ID: <20090325105316.GB1487@muc.de> (raw)
In-Reply-To: <buohc1hx5ca.fsf@dhlpc061.dev.necel.com>
Hi, Miles!
On Wed, Mar 25, 2009 at 07:30:13PM +0900, Miles Bader wrote:
> Alan Mackenzie <acm@muc.de> writes:
> > How is an external library writer going to use the interactive "^"?
> > Assuming that the library should also work under XEmacs and Emacs 22,
> > just using the "^" won't work; an interactive string with "^" throws an
> > error in Emacs 22.
> Isn't that a pretty basic problem with _any_ extension to interactive?
> Do you think `interactive' should never be extended?
Yes, and yes. Or, rather, yes and yes except in the most exceptional of
circumstances, such as adding a new parameter type.
> In this case, I think the right solution would be to simply add another,
> possibly clunkier method for commands to indicate they want to enable
> shift-selection behavior.
Agreed.
> E.g.: have the command loop also look for a `handle-shift-select'
> property on command-name's plist, and treat that as it would "^" in the
> interactive string. Then external library authors who are worried about
> backwards compability could use (put COMMAND 'handle-shift-select t)
> instead of putting ^ in COMMAND's interactive string.
Agreed, except I wouldn't put it in the command loop - I'd put it in a
hook (pre-command-hook), for the same reason font-locking is in a hook
rather than directly in the command loop. M-x shift-select would
install/remove this function onto/from the hook.
Now the question arises, if we've got the property
`handle-shift-select', doesn't the "^" in the interactive string become
redundant?
> [Yeah, that only works for commands which are defined functions, but I
> think that's an acceptable limitation for a feature like this which
> should be used only rarely.]
Yes, a lambda expression can't use this. That's the only use of "^" I
can see which absolutely requires "^". But let's be honest, how often
do hackers write movement commands as anonymous lambdas?
> -Miles
> --
> "1971 pickup truck; will trade for gnus"
Hey, you can get gnus for nothing. :-)
--
Alan Mackenzie (Nuremberg, Germany).
next prev parent reply other threads:[~2009-03-25 10:53 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20090323223703.GA5650@muc.de>
[not found] ` <jwvfxh392k9.fsf-monnier+emacsbugreports@gnu.org>
[not found] ` <20090324135210.GA4657@muc.de>
[not found] ` <jwvzlfacrk0.fsf-monnier+emacsbugreports@gnu.org>
2009-03-25 10:16 ` Interactive hat. [Was: CUA-like stuff spuriously enables transient-mark-mode] Alan Mackenzie
2009-03-25 10:30 ` Interactive hat Miles Bader
2009-03-25 10:53 ` Alan Mackenzie [this message]
2009-03-25 11:03 ` Lennart Borgman
2009-03-25 14:24 ` Alan Mackenzie
2009-03-26 11:29 ` Alan Mackenzie
2009-03-25 14:59 ` Miles Bader
2009-03-26 11:51 ` Alan Mackenzie
2009-03-26 12:14 ` David Kastrup
2009-03-26 12:51 ` Alan Mackenzie
2009-03-26 13:48 ` Stefan Monnier
2009-03-26 14:33 ` Alan Mackenzie
2009-03-26 16:30 ` Stefan Monnier
2009-03-26 16:45 ` Alan Mackenzie
2009-03-26 18:57 ` Stefan Monnier
2009-03-29 0:44 ` Kim F. Storm
2009-03-29 1:40 ` Miles Bader
2009-03-29 2:02 ` Lennart Borgman
2009-03-26 14:47 ` Stephen J. Turnbull
2009-03-26 15:23 ` Miles Bader
2009-03-26 17:43 ` Stephen J. Turnbull
2009-03-25 16:18 ` Stefan Monnier
2009-03-25 11:26 ` Interactive hat. [Was: CUA-like stuff spuriously enables transient-mark-mode] Juanma Barranquero
2009-03-25 13:20 ` Interactive hat Chong Yidong
2009-03-25 14:19 ` Interactive hat. [Was: CUA-like stuff spuriously enables transient-mark-mode] Alan Mackenzie
2009-03-25 16:41 ` Juanma Barranquero
2009-03-26 12:44 ` Alan Mackenzie
2009-03-26 13:50 ` Interactive hat Stefan Monnier
2009-03-26 15:27 ` Alan Mackenzie
2009-03-26 17:09 ` Stefan Monnier
2009-03-26 19:06 ` Alan Mackenzie
2009-03-26 21:18 ` Stefan Monnier
2009-03-26 22:32 ` Johan Bockgård
2009-03-26 23:34 ` Alan Mackenzie
2009-03-26 23:32 ` Alan Mackenzie
2009-03-27 2:50 ` Stefan Monnier
2009-03-27 11:15 ` Alan Mackenzie
2009-04-13 19:32 ` Interactive hat. (Patch) Alan Mackenzie
2009-04-13 20:47 ` Eli Zaretskii
2009-04-14 20:15 ` Alan Mackenzie
2009-04-14 20:47 ` Eli Zaretskii
[not found] ` <20090423205030.GA2723@muc.de>
2009-04-24 13:38 ` Interactive hat. (Patch V2) Eli Zaretskii
2009-04-27 11:46 ` Alan Mackenzie
2009-04-27 18:39 ` Eli Zaretskii
2009-04-28 22:33 ` Alan Mackenzie
2009-04-29 7:22 ` Eli Zaretskii
2009-04-29 11:36 ` Alan Mackenzie
2009-04-29 13:13 ` Eli Zaretskii
2009-05-07 19:14 ` Stefan Monnier
2009-04-28 0:14 ` Karl Berry
2009-04-28 1:12 ` Miles Bader
2009-04-28 7:55 ` Eli Zaretskii
2009-04-28 21:44 ` Alan Mackenzie
2009-04-28 21:39 ` Alan Mackenzie
2009-04-13 22:50 ` Interactive hat. (Patch) Miles Bader
2009-04-14 20:22 ` Alan Mackenzie
2009-04-14 20:49 ` Eli Zaretskii
2009-04-15 8:29 ` Stephen J. Turnbull
2009-03-27 0:20 Interactive hat naesten
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=20090325105316.GB1487@muc.de \
--to=acm@muc.de \
--cc=emacs-devel@gnu.org \
--cc=miles@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).