From: Drew Adams <drew.adams@oracle.com>
To: Eli Zaretskii <eliz@gnu.org>, Al Petrofsky <al@petrofsky.org>,
Stefan Monnier <monnier@iro.umontreal.ca>
Cc: "64138@debbugs.gnu.org" <64138@debbugs.gnu.org>
Subject: bug#64138: 28.2; C-x ) won't accept the universal argument
Date: Sun, 18 Jun 2023 13:05:24 +0000 [thread overview]
Message-ID: <SJ0PR10MB5488BF623050EED3CEA59B04F35EA@SJ0PR10MB5488.namprd10.prod.outlook.com> (raw)
In-Reply-To: <83fs6pp8l1.fsf@gnu.org>
> > (Changing "C-u" to "C-u 4" gives the expected result.)
> > The "P" in the interactive declaration of kmacro-end-macro
> > should be a "p".
>
> These commands always required a numeric prefix argument, and that is
> how they are documented. So just "C-u" is invalid, you should use
> "C-u 4" instead.
I thought it was the case that unless specified
otherwise (i.e., unless C-u has another behavior),
when a numeric prefix arg has some behavior then
a plain C-u should act the same as C-u 4 (etc.).
I thought that when doc says _only_ "with numeric
prefix arg..." or "a numeric prefix arg means..."
that's short for an equivalent statement about
plain C-u (and its multiples), plain M--, etc.
I thought that any departure from this general
rule would be mentioned in the doc, including if
plain C-u were ignored or raised an error or...
Hasn't this been the (unwritten) convention?
(Just asking a question - not arguing.)
In this case, if plain C-u were indeed "invalid"
then I'd expect that to be documented.
next prev parent reply other threads:[~2023-06-18 13:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-17 23:47 bug#64138: 28.2; C-x ) won't accept the universal argument Al Petrofsky
2023-06-18 6:50 ` Eli Zaretskii
2023-06-18 11:00 ` Al Petrofsky
2023-06-18 11:05 ` Eli Zaretskii
2023-06-18 13:05 ` Drew Adams [this message]
2023-06-18 13:36 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-18 14:08 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-21 14:02 ` 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=SJ0PR10MB5488BF623050EED3CEA59B04F35EA@SJ0PR10MB5488.namprd10.prod.outlook.com \
--to=drew.adams@oracle.com \
--cc=64138@debbugs.gnu.org \
--cc=al@petrofsky.org \
--cc=eliz@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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).