bug#11176: 24.0.94; Why the prefix arg behavior for `customize-apropos'?

[Drew Adams]

Why do we provide a way for users to "customize" non-option variables?
What is the point of showing those in a Customize buffer?
 
And the State menu offers these actions for such an uncustomizable
variable (and offers more if you edit the comment):
 
1. Show saved Lisp expression.
2. Add comment.
 
#1 makes no sense - there is no saved Lisp expression, and there is no
non-Lisp value display possible for such a variable.
 
#2 makes no sense, unless I'm missing something.  You are actually able
to add a comment, but you of course cannot save the edit.  You can undo
the edit.  But you cannot remove the comment, even if it is empty.  If
the comment is not empty, then you can "set" the variable for the
current session.

All of that seems meaningless to me, but maybe I'm missing something.
 
Also, AFAICT, the use of a prefix arg with `customize-apropos' is
explained nowhere in the manual(s).  A user trying to figure out what it
is for is in for some wondering...

In GNU Emacs 24.0.94.1 (i386-mingw-nt5.1.2600)
 of 2012-03-19 on MARVIN
Windowing system distributor `Microsoft Corp.', version 5.1.2600
Configured using:
 `configure --with-gcc (4.6) --no-opt --enable-checking --cflags
 -ID:/devel/emacs/libs/libXpm-3.5.8/include
 -ID:/devel/emacs/libs/libXpm-3.5.8/src
 -ID:/devel/emacs/libs/libpng-dev_1.4.3-1/include
 -ID:/devel/emacs/libs/zlib-dev_1.2.5-2/include
 -ID:/devel/emacs/libs/giflib-4.1.4-1/include
 -ID:/devel/emacs/libs/jpeg-6b-4/include
 -ID:/devel/emacs/libs/tiff-3.8.2-1/include
 -ID:/devel/emacs/libs/gnutls-3.0.9/include'