Mercurial > hg > xemacs-beta

view BUGS @ 757:516c347c4479

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
[xemacs-hg @ 2002-02-22 17:13:59 by michaels] 2002-02-13 Ben Wing <ben@xemacs.org> * event-stream.c (reset_key_echo): * event-stream.c (reset_this_command_keys): * event-stream.c (execute_command_event): If console is dead as a result of C-x 5 0, then post-command stuff needs to be careful and do only non-console-specific stuff.
author michaels
date Fri, 22 Feb 2002 17:14:00 +0000 (2002-02-22)
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/