[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#11139: 24.0.94; inappropriate `face' property for `apropos*' button
bug#11139: 24.0.94; inappropriate `face' property for `apropos*' button types
Sat, 31 Mar 2012 10:27:00 -0700
Here's the thing: Users can customize faces.
That seems to get forgotten sometimes.
In the case of an Apropos buffer, Emacs defines multiple button types,
and all but one of them use _hard-coded_ faces. And there are
additional places where particular faces are hard-coded in `apropos.el'.
This hard-coding is a no-no.
Why? Because USERS CAN CUSTOMIZE FACES.
A user might well customize some of the faces that you use here in a
hard-coded way. Those customizations might make sense for typical uses
of those faces (e.g. font-locking for code), but the result in this
buffer might be awful.
You, writing apropos.el, cannot foresee all of the possibilities. But
you can foresee that users will want to customize the appearance of
Apropos buffers. And they deserve to be able to do that easily.
Please, please provide a way for users to customize the display of
Apropos itself. Add apropos-specific deffaces or face-valued defcustoms
for each of the faces that the Apropos display uses.
Set their default values to whatever you like, including perhaps
font-lock faces. But please stop hard-coding faces, depriving users of
the ability to control the appearance (without resorting to redefining
the Emacs source code).
A face should almost never be hard-coded, fixing Emacs's appearance in
concrete. Please think of the users and of Emacs's mission to be
customizable by them. It is hard to believe that this kind of thing is
still going on. This is 2012, not 1980.
In GNU Emacs 18.104.22.168 (i386-mingw-nt5.1.2600)
of 2012-03-19 on MARVIN
Windowing system distributor `Microsoft Corp.', version 5.1.2600
`configure --with-gcc (4.6) --no-opt --enable-checking --cflags
- bug#11139: 24.0.94; inappropriate `face' property for `apropos*' button types,
Drew Adams <=