* ?? call-interactively doesn't always make KEYS available to `interactive' form.
@ 2009-04-06 14:27 Alan Mackenzie
2009-04-06 16:07 ` Stefan Monnier
0 siblings, 1 reply; 2+ messages in thread
From: Alan Mackenzie @ 2009-04-06 14:27 UTC (permalink / raw)
To: emacs-devel
Hi, Emacs!
In
(call-interactively FUNCTION &optional RECORD-FLAG KEYS)
, KEYS is a list of key/mouse events to be used in place of
(this-command-keys) (or something similar).
If FUNCTION contains `(interactive "string")', KEYS gets used properly.
If it has `(interactive (lisp-form))', though, the lisp-form can't access
KEYS.
Surely, this is a bug?
[Context: I'm documenting lisp equivalents for code letters in
interactive "string"s.]
--
Alan Mackenzie (Nuremberg, Germany).
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: ?? call-interactively doesn't always make KEYS available to `interactive' form.
2009-04-06 14:27 ?? call-interactively doesn't always make KEYS available to `interactive' form Alan Mackenzie
@ 2009-04-06 16:07 ` Stefan Monnier
0 siblings, 0 replies; 2+ messages in thread
From: Stefan Monnier @ 2009-04-06 16:07 UTC (permalink / raw)
To: Alan Mackenzie; +Cc: emacs-devel
> If FUNCTION contains `(interactive "string")', KEYS gets used
> properly. If it has `(interactive (lisp-form))', though, the
> lisp-form can't access KEYS.
> Surely, this is a bug?
Yup, that's a bug.
Stefan
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2009-04-06 16:07 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2009-04-06 14:27 ?? call-interactively doesn't always make KEYS available to `interactive' form Alan Mackenzie
2009-04-06 16:07 ` Stefan Monnier
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).