From: Lars Magne Ingebrigtsen <larsi@gnus.org>
To: "Drew Adams" <drew.adams@oracle.com>
Cc: 1010@debbugs.gnu.org
Subject: bug#1010: 23.0.60; call-interactively doc
Date: Thu, 07 Jul 2011 18:57:25 +0200 [thread overview]
Message-ID: <m3zkkqt4ei.fsf@quimbies.gnus.org> (raw)
In-Reply-To: <007801c91b34$cfe46170$0200a8c0@us.oracle.com> (Drew Adams's message of "Sat, 20 Sep 2008 08:23:19 -0700")
"Drew Adams" <drew.adams@oracle.com> writes:
> The doc for `call-interactively', both Elisp manual and doc string,
> could perhaps be improved slightly by changing "reading args" to
> "providing args".
Yes, I think you're right. In case of the "r" spec, for instance,
there's little "reading" going on, but it does provide the point/mark to
the function.
I'm guessing the intention was to say that it would prompt the user for
stuff, if the interactive spec is a prompting one.
I've now made the change.
> It's still good to say, in a separate sentence, that this might entail
> reading, depending on the `interactive' spec for the individual
> arguments. The point is that "calling interactively" does not
> necessarily involve anything interactive (input from the user). It
> just calls the command providing arguments as determined by the
> `interactive' spec, which _might_ require reading user input.
>
> In the Elisp manual, a simple example might illustrate what
> `call-interactively' is typically used for.
I've added an example to the manual.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog http://lars.ingebrigtsen.no/
prev parent reply other threads:[~2011-07-07 16:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-20 15:23 bug#1010: 23.0.60; call-interactively doc Drew Adams
2011-07-07 16:57 ` Lars Magne Ingebrigtsen [this message]
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=m3zkkqt4ei.fsf@quimbies.gnus.org \
--to=larsi@gnus.org \
--cc=1010@debbugs.gnu.org \
--cc=drew.adams@oracle.com \
/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.