unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "Aaron S. Hawley" <aaron.s.hawley@gmail.com>
To: Drew Adams <drew.adams@oracle.com>
Cc: 13373@debbugs.gnu.org
Subject: bug#13373: 24.3.50; doc string of `execute-extended-command' is incorrect
Date: Mon, 7 Jan 2013 18:08:28 -0500	[thread overview]
Message-ID: <CAFw1JJ7MLB4R5u2zw71CT09R+pZmGnLN19SHG2mJDGXwVLJg-Q@mail.gmail.com> (raw)
In-Reply-To: <C9E18DB5C3BD40FC9FAFED7674FF874A@us.oracle.com>

>> 3. The usage in the Emacs manual is "numeric argument", so for better
>> or worse, it seems consistent.
>
> Where do you see "numeric argument" used in the Elisp manual for the doc of
> `e-e-c'?  That doc is in node `Interactive Call'.  It says no such thing, and
> explicitly refers to the raw prefix argument:

The *Emacs* manual uses the term "numeric argument".  It's the name of
the section:

(info "(emacs) Arguments")

> If the Elisp manual did as you say it does, then it too would wrong.  Two wrongs
> are not to be rewarded just because they are "consistent" with each other.

> The main thing "worth fixing" is the misleading statements about the prefix arg.

Again, the user manual introduces them as "numeric arguments".  It's
not as precise as "prefix argument" for the Lisp hackers in the room,
but for user's purposes it is probably helpful to do it this way -- as
long the section is read in its entirety since the second half has all
the special cases.

Numeric arguments, prefix arguments, universal arguments, the use of a
C-u as a terminator in some cases ("terminator argument?")... the
terrain is fraught with peril.  It's an Emacs world, we just live in
it.

-- 
In general, we reserve the right to have a poor
memory--the computer, however, is supposed to
remember!  Poor computer.  -- Guy Lewis Steele Jr.





  reply	other threads:[~2013-01-07 23:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-07  1:02 bug#13373: 24.3.50; doc string of `execute-extended-command' is incorrect Drew Adams
2013-01-07 21:27 ` Aaron S. Hawley
2013-01-07 22:29   ` Drew Adams
2013-01-07 23:08     ` Aaron S. Hawley [this message]
2013-01-07 23:59       ` Drew Adams
2014-02-08 13:14 ` Lars Ingebrigtsen

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=CAFw1JJ7MLB4R5u2zw71CT09R+pZmGnLN19SHG2mJDGXwVLJg-Q@mail.gmail.com \
    --to=aaron.s.hawley@gmail.com \
    --cc=13373@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 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).