Mercurial > hg > xemacs-beta

view BUGS @ 1069:13daf40fb997

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
[xemacs-hg @ 2002-10-24 14:59:22 by youngs] 2002-10-25 Scott Evans <gse@antisleep.com> * replace.el (operate-on-non-matching-lines) (operate-on-non-matching-lines): Generalized from delete-non-matching-lines and delete-matching-lines. The "operate" versions work with regions, can copy to the kill ring, and return the number of lines copied/deleted. (delete-non-matching-lines): Use operate-on-non-matching-lines. (delete-matching-lines): Use operate-on-matching-lines. (kill-non-matching-lines): New. (copy-non-matching-lines): New. (kill-matching-lines): New. (copy-matching-lines): New.
author youngs
date Thu, 24 Oct 2002 14:59:27 +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/