From: "Stefan Monnier" <monnier+gnu/emacs@RUM.cs.yale.edu>
Cc: emacs-devel@gnu.org, xemacs-design@xemacs.org
Subject: Re: API changes
Date: Sun, 28 Apr 2002 19:45:17 -0400 [thread overview]
Message-ID: <aai1on$lkb$2@main.gmane.org> (raw)
In-Reply-To: 3CCAA9FF.4000905@666.com
> commandp takes a second optional argument, CALL-INTERACTIVELY, which
> indicates whether the given item can be executed by `call-interactively'
> (normally, the return value indicates whether the item can be executed
> by `command-execute'; this includes vectors and strings, which are not
> allowed by `call-interactively').
I always disliked this. I feel like the elisp layer should only
have one of the two (i.e. I think that Fcall_interactively should
not be exported to elisp and should be replaced by
(defalias 'call-interactively 'command-execute)).
> this is a clean way of determining,
> for example, how to execute a callback in a menu spec or the like --
> such callbacks are defined as "if an interactive thing, use
> call-interactively; else, use eval".
For what it's worth, `functionp' seems to work just fine for that purpose
(after all, if it's a non-interactive function, `eval' won't be much more
useful than `call-interactively').
Stefan
next prev parent reply other threads:[~2002-04-28 23:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3CCAA9FF.4000905@666.com>
2002-04-28 0:58 ` API changes Daniel Pittman
2002-04-28 5:48 ` Colin Walters
2002-04-28 23:45 ` Stefan Monnier [this message]
2002-04-29 5:05 ` Richard Stallman
2002-05-04 6:26 ` Colin Walters
[not found] ` <1020493576.5286.5.camel@space-ghost>
2002-05-17 12:30 ` Ben Wing
2002-05-18 18:49 ` Richard Stallman
2002-05-18 19:54 ` Colin Walters
[not found] ` <200205191940.g4JJeij24049@aztec.santafe.edu>
2002-05-19 20:09 ` Colin Walters
2002-05-20 3:07 ` Stephen J. Turnbull
[not found] ` <1019972901.27106.63.camel@space-ghost>
2002-04-29 5:05 ` Richard Stallman
2002-04-29 6:25 ` Colin Walters
2002-04-27 13:39 Ben Wing
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='aai1on$lkb$2@main.gmane.org' \
--to=monnier+gnu/emacs@rum.cs.yale.edu \
--cc=emacs-devel@gnu.org \
--cc=xemacs-design@xemacs.org \
/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).