From: Richard Stallman <rms@gnu.org>
Cc: gnu-emacs-bug@moderators.isc.org
Subject: Re: locate-library INTERACTIVE-CALL argument
Date: Tue, 05 Aug 2003 15:14:51 -0400 [thread overview]
Message-ID: <E19k7Gl-0002UD-Jj@fencepost.gnu.org> (raw)
In-Reply-To: <3F2E855C.5040901@yahoo.com> (message from Kevin Rodgers on Mon, 04 Aug 2003 10:10:04 -0600)
Thanks for pointing that out. But I'm still not happy with the current
implementation. If the command is called interactively (within a
keyboard macro or not), INTERACTIVE-CALL is unconditionally set to t, so
the message will displayed.
That is correct.
Since the intent is to display the message
when the command is called interactively, even when it is called via a
keyboard macro, why not test for those conditions explicitly with
interactive-p and executing-macro respectively?
There is no way to do that and get the same condition.
(or (interactive-p) executing-macro) would be t
when called from Lisp code that was run by a keyboard macro.
Perhaps there ought to be a way to use interactive-p to get
such a result. It could be a good feature.
But there may be a better feature. Ever since 1985 I had the idea
that maybe (interactive...) could be extended with a second argument
saying how to display the value. That would be complimentary with the
existing arg saying how to provide the arguments. That might be the
really clean way to do this job.
next prev parent reply other threads:[~2003-08-05 19:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-31 17:00 locate-library INTERACTIVE-CALL argument Kevin Rodgers
2003-08-02 4:47 ` Richard Stallman
[not found] ` <mailman.11.1059814578.2377.bug-gnu-emacs@gnu.org>
2003-08-04 16:10 ` Kevin Rodgers
2003-08-05 19:14 ` Richard Stallman [this message]
[not found] ` <mailman.112.1060111669.29551.bug-gnu-emacs@gnu.org>
2003-08-05 22:35 ` Kevin Rodgers
2003-08-06 13:04 ` Richard Stallman
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E19k7Gl-0002UD-Jj@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=gnu-emacs-bug@moderators.isc.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.