Mercurial > hg > xemacs-beta

view BUGS @ 898:b0c24ea6a2a8

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
[xemacs-hg @ 2002-07-03 07:18:39 by michaels] 2002-07-01 Mike Sperber <mike@xemacs.org> * process-unix.c (unix_send_process): Mark coding_outstream as non-open upon SIGPIPE. * event-stream.c (execute_internal_event): Reinstate code to deactivate a dead network connection that got lost during the stdout/stderr separation. * event-stream.c (Fnext_event): Reorder switch cases to something that makes sense.
author michaels
date Wed, 03 Jul 2002 07:18:41 +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/