Mercurial > emacs
view BUGS @ 25883:2955c353186a
(toplevel) [USE_MOTIF]: Include some Motif headers.
(struct x_resources) [USE_X_TOOLKIT]: New.
(xm_apply_resources, xm_set_menu_resources_from_menu_face)
[USE_MOTIF]: New.
(xl_apply_resources, xl_set_menu_resources_from_menu_face)
[USE_LUCID]: New.
(x_set_menu_resources_from_menu_face) [USE_X_TOOLKIT]: New.
(Qmenu): New.
(syms_of_xfaces): Initialize Qmenu.
(realize_basic_faces): Realize face `menu'.
(resolve_face_name): New.
(lface_from_face_name): Use it.
(Finternal_set_lisp_face_attribute): Ditto.
(Fpixmap_spec_p): Rewritten. Extend doc string.
author | Gerd Moellmann <gerd@gnu.org> |
---|---|
date | Wed, 06 Oct 1999 23:09:44 +0000 |
parents | 354e0c45cedf |
children | af68d12218d0 |
line wrap: on
line source
If you think you may have found a bug in GNU Emacs, please read the Bugs section of the Emacs manual for advice on (1) how to tell when to report a bug, and (2) how to write a useful bug report and what information it needs to have. There are three ways to read the Bugs section. (1) In a printed copy of the Emacs manual. You can order one from the Free Software Foundation; see the file etc/ORDERS. But if you don't have a copy on hand and you think you have found a bug, you shouldn't wait to get a printed manual; you should read the section right away as described below. (2) With Info. Start Emacs, do C-h i to enter Info, then m Emacs RET to get to the Emacs manual, then m Bugs RET to get to the section on bugs. Or use standalone Info in a like manner. (Standalone Info is part of the Texinfo distribution, not part of the Emacs distribution.) (3) By hand. Do cat info/emacs* | more "+/^File: emacs, Node: Bugs,"