Mercurial > hg > xemacs-beta

view BUGS @ 1692:6265c9c31f53

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
[xemacs-hg @ 2003-09-18 05:13:54 by youngs] 2003-09-18 Steve Youngs <youngs@xemacs.org> * configure: Re-generate after Martin's configure.in patch. 2003-09-13 Martin Buchholz <martin@xemacs.org> * configure.in (OS_RELEASE): Add support for SunOS 5.10. On current OSes produced by Sun, `uname -r' prints "5.9". It seems likely that on future OSes, `uname -r' will print "5.10". We need to accept multi-digit release numbers. 2003-09-13 Martin Buchholz <martin@xemacs.org> * s/sol2.h: Use OS_RELEASE=os_release_major*100+os_release_minor
author youngs
date Thu, 18 Sep 2003 05:14:00 +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/