all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: "Andreas Röhler" <andreas.roehler@easy-emacs.de>, 24369@debbugs.gnu.org
Subject: bug#24369: Docu of prefix-numeric-value
Date: Mon, 5 Sep 2016 10:46:07 -0700 (PDT)	[thread overview]
Message-ID: <792cdfef-3836-4483-8ff7-fe7f6377774e@default> (raw)
In-Reply-To: <9cd42ba9-014d-91be-24a4-0077c4e85ac4@easy-emacs.de>

> > What "treatment" are you asking to be explained?
> > Just what do you think is missing?
> 
> Elisp Info 20.2.2 Code Characters for ‘interactive’
> ----------------------------------------
> 
> p  The numeric prefix argument
> 
> Likewise with uppecase P.

Again, what do you think is missing?  `p' is the numeric prefix argument.
`P' is the raw prefix argument.

This is not the Elisp manual node that describes WHAT these things
are.  But there is a link here to the node that does that, node
`Prefix Command Arguments'

http://www.gnu.org/software/emacs/manual/html_node/elisp/Prefix-Command-Arguments.html

And that's the case even in the Emacs 20 version of the manual,
which you cited.

> User will expect the argument received by function being consistent with
> input, i.e. M-x 2 foo... sends 2, M-x 1 foo ... sends 1. From there
> omitting an argument will be expected to send nothing - which isn't the
> case.

Why on Earth would the user expect that, simply from reading that
`interactive' code `p' returns the numeric prefix argument and `P'
returns the raw prefix argument?





  reply	other threads:[~2016-09-05 17:46 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-05  7:52 bug#24369: Docu of prefix-numeric-value Andreas Röhler
2016-09-05 15:57 ` Drew Adams
2016-09-05 17:44   ` Andreas Röhler
2016-09-05 17:46     ` Drew Adams [this message]
2016-09-05 17:57     ` Eli Zaretskii
2016-09-05 18:33       ` Andreas Röhler
2016-09-05 18:57         ` Eli Zaretskii
2016-09-05 21:03           ` Drew Adams
2017-07-17  1:37             ` npostavs

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=792cdfef-3836-4483-8ff7-fe7f6377774e@default \
    --to=drew.adams@oracle.com \
    --cc=24369@debbugs.gnu.org \
    --cc=andreas.roehler@easy-emacs.de \
    /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.