Re: more than one prefix argument

[Andreas Röhler]

Am 26.07.2011 22:10, schrieb Daniel Colascione:
> On 7/26/11 12:59 PM, Andreas Röhler wrote:
> > Hi,
> >
> > what about allowing more than one prefix argument
> > by making interactive codes "p" and "P" sending
> > truly separated.
>
> We already have more than one kind of prefix argument: see
> universal-coding-system-argument for an example.  You can already define as many
> kinds of "prefix argument" as you'd like: just define a global flag and a
> command to set that flag, and have post-command-hook clear the flag unless (eq
> this-command 'my-prefix-setting-function).

Hi,

yes I can, thanks for the hints, which will be helpful.

Let may say however that things like

21.12 Prefix Command Argument

tells it, might be easier, more clear implemented IMHO, it reads:


   Here are the possible values of a raw prefix argument:

   * `nil', meaning there is no prefix argument.  Its numeric value is
     1, but numerous commands make a distinction between `nil' and the
     integer 1.

   * An integer, which stands for itself.

   * A list of one element, which is an integer.  This form of prefix
     argument results from one or a succession of `C-u''s with no
     digits.  The numeric value is the integer in the list, but some
     commands make a distinction between such a list and an integer
     alone.

;;;;;;;;;;

well, it's great:

numerous commands make a distinction between `nil' and the
     integer 1.

;;;;;;;;;

Indeed: (prefix-numeric-value nil) -->1
But does this make sense in a lisp-environement?

Booleans treat nil and 1 different:

(when 1 (message "%s" "1"))-->1
(when nil (message "%s" "1"))-->nil

Cheers,

Andreas