Mercurial > hg > xemacs-beta

view BUGS @ 952:c10d0c3f965f

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
[xemacs-hg @ 2002-08-02 16:54:11 by youngs] 2002-05-29 Katsumi Yamaoka <yamaoka@jpl.org> * mule/japan-util.el (setup-japanese-environment-internal): Use proper coding-systems. 2002-05-28 Katsumi Yamaoka <yamaoka@jpl.org> * mule/japan-util.el: Use `characterp' instead of `integerp' while defining char properties for katakana. * mule/mule-category.el: Clear the category table before defining categories for `predefined-category-list'. * mule/mule-cmds.el (finish-set-language-environment): Fit the charsets preferences in unicode conversions for the language environment. Suggested by ARISAWA Akihiro <ari@mbf.sphere.ne.jp>.
author youngs
date Fri, 02 Aug 2002 16:54:25 +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/