Mercurial > hg > xemacs-beta

view BUGS @ 831:5d09ddada9ae

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
[xemacs-hg @ 2002-05-09 07:15:20 by ben] fix two bugs noted by Steve doprnt.c: Use make_int() not make_char() when error about bad charval, or abort will occur. extents.c: Loop over children, not ourself -- avoid infinite loop. lisp-disunion.h, lisp-union.h: Rename make_char() to make_char_1 for error-checking purposes. lread.c: Syntax error if escape is outside of ISO-8859-1 range. Remove hopelessly broken (and unworkable) FSF_KEYS code. mule-coding.c, search.c: Spacing changes. text.h: New make_char() -- verify that the char value is legal.
author ben
date Thu, 09 May 2002 07:16:38 +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/