GNU bug report logs - #24369
Docu of prefix-numeric-value

Previous Next

Package: emacs;

Reported by: Andreas Röhler <andreas.roehler <at> easy-emacs.de>

Date: Mon, 5 Sep 2016 07:47:02 UTC

Severity: wishlist

Tags: notabug

Done: npostavs <at> users.sourceforge.net

Bug is archived. No further changes may be made.

Full log


Message #14 received at 24369 <at> debbugs.gnu.org (full text, mbox):

From: Drew Adams <drew.adams <at> oracle.com>
To: Andreas Röhler <andreas.roehler <at> easy-emacs.de>,
 24369 <at> debbugs.gnu.org
Subject: RE: bug#24369: Docu of prefix-numeric-value
Date: Mon, 5 Sep 2016 10:46:07 -0700 (PDT)
> > 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?




This bug report was last modified 8 years and 7 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.