Mercurial > hg > xemacs-beta

view BUGS @ 1201:c2569faae8ed

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
[xemacs-hg @ 2003-01-12 10:45:53 by michaels] 2002-12-16 Ben Wing <ben@xemacs.org> * lwlib-Xlw.c (xlw_update_one_widget): * lwlib-Xm.c (xm_update_one_widget): * lwlib-Xm.c (xm_update_one_value): * lwlib.c: * lwlib.c (merge_scrollbar_values): * xlwmenu.c: * xlwmenu.c (display_menu): * xlwmenu.c (XlwMenuInitialize): * xlwmenu.c (XlwMenuSetValues): * xlwradio.c: * xlwradio.c (RadioClassPartInit): * xlwradio.c (RadioSet): * xlwradio.c (RadioUnset): class -> class_, new -> new_.
author michaels
date Sun, 12 Jan 2003 10:45:53 +0000
parents 9f59509498e1
children
line wrap: on
line source

If you think you may have found a bug in XEmacs, please
read the Bugs section of the XEmacs 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 XEmacs manual.

(2) With Info.  Start XEmacs, do C-h i to enter Info,
then m XEmacs 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 XEmacs distribution.)

(3) By hand.  Do
    cat info/xemacs* | more "+/^File: xemacs.info,  Node: Bugs,"


Part II of the XEmacs FAQ, available in a manner similar to the above,
or via the world wide web, contains extensive information on how to
track down and report bugs.

	http://www.xemacs.org/faq/