From: martin rudalics <rudalics@gmx.at>
To: Drew Adams <drew.adams@oracle.com>, Eli Zaretskii <eliz@gnu.org>
Cc: 34749@debbugs.gnu.org
Subject: bug#34749: 26.1; `delete-windows-on': (1) doc, (2) bug, (3) bug, (4) candidates
Date: Sat, 09 Mar 2019 09:39:19 +0100 [thread overview]
Message-ID: <5C837BB7.6030600@gmx.at> (raw)
In-Reply-To: <a026905a-b5fa-42f9-a002-992106f656a8@default>
> Are you asking what "\nP" means/does?
Yes.
> If so, the "\n" separates
> arguments and the "P" stands for `current-prefix-arg', i.e., the
> raw prefix argument. This is pretty well documented in (elisp)
> `Using Interactive' and (elisp) `Interactive Codes'.
>
> 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::).
It's clear for you since you probably write such specifications all
the time. I hope it's now clear for me as well after reading that
text a couple of times.
Thanks, martin
next prev parent reply other threads:[~2019-03-09 8:39 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-04 16:25 bug#34749: 26.1; `delete-windows-on': (1) doc, (2) bug, (3) bug, (4) candidates Drew Adams
2019-03-05 10:12 ` martin rudalics
2019-03-08 10:29 ` Eli Zaretskii
2019-03-08 11:02 ` martin rudalics
2019-03-08 13:15 ` Eli Zaretskii
2019-03-08 18:52 ` martin rudalics
2019-03-08 19:45 ` Drew Adams
2019-03-09 8:39 ` martin rudalics [this message]
2019-03-09 16:37 ` Drew Adams
2019-03-08 19:58 ` Eli Zaretskii
2019-03-09 8:39 ` martin rudalics
2019-03-09 10:58 ` Eli Zaretskii
2019-03-09 13:16 ` martin rudalics
2019-03-09 16:33 ` Drew Adams
2019-03-09 16:46 ` Eli Zaretskii
2019-03-10 8:46 ` martin rudalics
2019-03-10 8:48 ` martin rudalics
2019-03-08 10:27 ` Eli Zaretskii
2022-04-26 12:32 ` Lars Ingebrigtsen
[not found] <<b375da42-2b65-4579-902c-85e9fdcaeac7@default>
[not found] ` <<83o96lacf8.fsf@gnu.org>
2019-03-08 16:34 ` Drew Adams
2019-03-08 17:00 ` Eli Zaretskii
[not found] ` <<5C7E4BAB.3050508@gmx.at>
[not found] ` <<83mum5accd.fsf@gnu.org>
[not found] ` <<5C824BAC.4090907@gmx.at>
[not found] ` <<83lg1pa4oa.fsf@gnu.org>
[not found] ` <<5C82B9E1.1080302@gmx.at>
[not found] ` <<83zhq587g6.fsf@gnu.org>
[not found] ` <<5C837BD6.9010200@gmx.at>
[not found] ` <<83ef7g8gbc.fsf@gnu.org>
[not found] ` <<5C83BC9B.5020803@gmx.at>
[not found] ` <<e0b90f9b-2d1f-4877-b83a-aeca5425dbea@default>
[not found] ` <<8336nw807g.fsf@gnu.org>
2019-03-09 17:35 ` Drew Adams
2019-03-09 18:12 ` Eli Zaretskii
[not found] <<<b375da42-2b65-4579-902c-85e9fdcaeac7@default>
[not found] ` <<<83o96lacf8.fsf@gnu.org>
[not found] ` <<6aae54ec-85bf-4447-bec0-7c916caeb2f8@default>
[not found] ` <<83a7i59u85.fsf@gnu.org>
2019-03-08 17:14 ` Drew Adams
2019-03-08 18:58 ` Eli Zaretskii
[not found] ` <<<5C7E4BAB.3050508@gmx.at>
[not found] ` <<<83mum5accd.fsf@gnu.org>
[not found] ` <<<5C824BAC.4090907@gmx.at>
[not found] ` <<<83lg1pa4oa.fsf@gnu.org>
[not found] ` <<<5C82B9E1.1080302@gmx.at>
[not found] ` <<<83zhq587g6.fsf@gnu.org>
[not found] ` <<<5C837BD6.9010200@gmx.at>
[not found] ` <<<83ef7g8gbc.fsf@gnu.org>
[not found] ` <<<5C83BC9B.5020803@gmx.at>
[not found] ` <<<e0b90f9b-2d1f-4877-b83a-aeca5425dbea@default>
[not found] ` <<<8336nw807g.fsf@gnu.org>
[not found] ` <<dd8e2b24-ab4a-4a4c-b9b8-9249f9ec035b@default>
[not found] ` <<83sgvv7w99.fsf@gnu.org>
2019-03-09 22:32 ` Drew Adams
[not found] <<<<b375da42-2b65-4579-902c-85e9fdcaeac7@default>
[not found] ` <<<<83o96lacf8.fsf@gnu.org>
[not found] ` <<<6aae54ec-85bf-4447-bec0-7c916caeb2f8@default>
[not found] ` <<<83a7i59u85.fsf@gnu.org>
[not found] ` <<a1314708-0feb-4092-8b60-37d7282a328f@default>
[not found] ` <<834l8d9orm.fsf@gnu.org>
2019-03-08 19:48 ` Drew Adams
2019-03-08 20:14 ` 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
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=5C837BB7.6030600@gmx.at \
--to=rudalics@gmx.at \
--cc=34749@debbugs.gnu.org \
--cc=drew.adams@oracle.com \
--cc=eliz@gnu.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).