From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Kangas <stefankangas@gmail.com>
Cc: 57937@debbugs.gnu.org
Subject: bug#57937: 29.0.50; Improve doc of (interactive current-prefix-arg ...)
Date: Mon, 19 Sep 2022 19:33:57 +0300 [thread overview]
Message-ID: <83h713xr0q.fsf@gnu.org> (raw)
In-Reply-To: <CADwFkmmCwLWGqH8-QmVwCDMHZevH+tTdyC9+1YFAbG=AwU3t-g@mail.gmail.com> (message from Stefan Kangas on Mon, 19 Sep 2022 12:12:52 -0400)
> From: Stefan Kangas <stefankangas@gmail.com>
> Date: Mon, 19 Sep 2022 12:12:52 -0400
>
> Severity: wishlist
>
> I think the explanation in (info "(elisp) Using Interactive") could
> include a pointer to `current-prefix-arg', which AFAICT is only
> documented much later in (info "(elisp) Prefix Command Arguments").
There is already such a pointer there:
There are three possibilities for the argument ARG-DESCRIPTOR:
• It may be omitted or ‘nil’; then the command is called with no
arguments. This leads quickly to an error if the command requires
one or more arguments.
• It may be a string; its contents are a sequence of elements
separated by newlines, one for each argument(1). Each element
consists of a code character (*note Interactive Codes::) optionally
followed by a prompt (which some code characters use and some
ignore). Here is an example:
(interactive "P\nbFrobnicate buffer: ")
The code letter ‘P’ sets the command’s first argument to the raw
command prefix (*note Prefix Command Arguments::).
next prev parent reply other threads:[~2022-09-19 16:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-19 16:12 bug#57937: 29.0.50; Improve doc of (interactive current-prefix-arg ...) Stefan Kangas
2022-09-19 16:33 ` Eli Zaretskii [this message]
2022-09-19 19:35 ` Stefan Kangas
2022-09-20 2:27 ` Eli Zaretskii
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=83h713xr0q.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=57937@debbugs.gnu.org \
--cc=stefankangas@gmail.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.