view BUGS @ 975:151d438d2d55

[xemacs-hg @ 2002-08-28 05:36:20 by youngs] 2002-08-16 Steve Youngs <youngs@xemacs.org> * version.sh (xemacs_extra_name): New var to identify XEmacs version > release < next release. ie, release+cvs. * configure.in: Test for xemacs_extra_name. * configure: Re-generate. 2002-08-16 Steve Youngs <youngs@xemacs.org> * build-report.el (build-report-installation-version-regexp): Update to cater for 'xemacs-extra-name'. (build-report-version-file-regexp): Ditto. (build-report): Ditto. (build-report-installation-data): Ditto. (build-report-version-file-data): Ditto. * version.el (emacs-version): Test for 'xemacs-extra-name'. 2002-08-16 Steve Youngs <youngs@xemacs.org> * config.h.in (XEMACS_EXTRA_NAME): New. * emacs.c (vars_of_emacs): Use it.
author youngs
date Wed, 28 Aug 2002 05:36:34 +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/