[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Cannot use `C-h v' on variable names in Customize, and `custom...' varia

From: Drew Adams
Subject: Cannot use `C-h v' on variable names in Customize, and `custom...' variables are not autoloaded
Date: Tue, 25 Jan 2005 11:35:14 -0800

First bug: `custom-unlispify-tag-names' doesn't seem autoloaded -
completion is not available for it with `set-variable' without loading
customize code.

Second bug: Not-unlispified tag names in Customize do not work with
`variable-at-point'. For example, you cannot use `C-h v' and pick up a
variable name at point.

1. set-variable custom-unlispify-tag-names nil
2. customize-variable fill-column
3. put cursor (point) on the name "fill-column" in the Customize buffer
4. `C-h v' offers no default value for which variable to describe,
   because `variable-at-point' can't pick up the name. Perhaps this is
   due to the highlighting?

Also, this does work in Emacs 20, but the following problem exists
there, which also probably will exist in Emacs 21, after the above bug
is fixed: The name that is picked up by `variable-at-point' includes
the colon (:), so users must delete the colon from the minibuffer. It
would be better not to use an adjacent colon.

As long as there is no other way to get to all of the info provided by
`C-h v' from a customize buffer, it is important to let users easily
use `C-h v' in the buffer, to get to that info (e.g. source

In GNU Emacs (i386-mingw-nt5.1.2600)
 of 2004-07-26 on BERATUNG4
configured using `configure --with-gcc
(3.3) --cflags -I../../jpeg-6b-1/include -I../../libpng-1.2.4-1/include -I..
/../tiff-3.5.7/include -I../../xpm-nox-4.2.0/include -I../../zlib-1.1.4-1/in

reply via email to

[Prev in Thread] Current Thread [Next in Thread]