GNU bug report logs - #57937
29.0.50; Improve doc of (interactive current-prefix-arg ...)

Previous Next

Package: emacs;

Reported by: Stefan Kangas <stefankangas <at> gmail.com>

Date: Mon, 19 Sep 2022 16:13:03 UTC

Severity: wishlist

Found in version 29.0.50

Done: Stefan Kangas <stefankangas <at> gmail.com>

Bug is archived. No further changes may be made.

Full log


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

From: Eli Zaretskii <eliz <at> gnu.org>
To: Stefan Kangas <stefankangas <at> gmail.com>
Cc: 57937 <at> debbugs.gnu.org
Subject: Re: bug#57937: 29.0.50; Improve doc of (interactive
 current-prefix-arg ...)
Date: Tue, 20 Sep 2022 05:27:28 +0300
> From: Stefan Kangas <stefankangas <at> gmail.com>
> Date: Mon, 19 Sep 2022 15:35:12 -0400
> Cc: 57937 <at> debbugs.gnu.org
> 
> Eli Zaretskii <eliz <at> gnu.org> writes:
> 
> > There is already such a pointer there:
> >
> >    There are three possibilities for the argument ARG-DESCRIPTOR:
> >
> >    • It may be omitted or ‘nil’; ...
> >    • It may be a string; ...
> 
> I was thinking of this item:
> 
>    • It may be a Lisp expression that is not a string; ...
> 
> Here, I'd like to see an example like:
> 
>           (interactive current-prefix-arg)
> 
> and a brief pointer to `(elisp) Prefix Command Arguments'.

That comes _after_ the above-mention place, which already points to
that node, so what would be the point and the importance of repeating
the reference?  Using current-prefix-arg in a Lisp expression is not
different from using any other Lisp variable.




This bug report was last modified 2 years and 301 days ago.

Previous Next


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