view BUGS @ 858:2c12fe2da451

[xemacs-hg @ 2002-05-31 09:38:45 by michaels] 2002-05-28 Martin Köbele <mkoebele@mkoebele.de>, Jens Müller <jmueller@informatik.uni-tuebingen.de> * lrecord.h (lrecord_type): Add lrecord_type_weak_box to lrecord_type enumeration. * alloc.c (garbage_collect_1): Call prune_weak_boxes(). * lisp.h (struct weak_box): * data.c: (prune_weak_boxes): (mark_weak_box): (print_weak_box): (weak_box_equal): (weak_box_hash): (make_weak_box): (Fmake_weak_box): (Fweak_box_ref): (Fweak_boxp): (syms_of_data): (vars_of_data): Add implementation of weak boxes.
author michaels
date Fri, 31 May 2002 09:38:49 +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/