view BUGS @ 44180:e7a365c909ff

Don't require `custom'. (xml-lite-parse-tag-name): Properly treat non-ASCII chars. (xml-lite-parse-tag-backward): Obey sgml-empty-tags. (xml-lite-get-context): Drop nested tags not just for comments. (xml-lite-indent-line): Be more careful about moving point. (xml-lite-insert-end-tag, xml-lite-slash): Use indent-according-to-mode instead of xml-lite-indent-line. (xml-lite-mode): Make xml-lite-orig-indent-line-function buffer-local. Set sgml-xml-mode. Don't call force-mode-line-update. (xml-lite-mode-map): Don't bind TAB.
author Stefan Monnier <monnier@iro.umontreal.ca>
date Wed, 27 Mar 2002 18:02:36 +0000
parents af68d12218d0
children 8ce686bd7f4f
line wrap: on
line source

If you think you may have found a bug in GNU Emacs, please
read the Bugs section of the Emacs 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 Emacs manual.
You can order one from the Free Software Foundation;
see the file etc/ORDERS.  But if you don't have a copy on
hand and you think you have found a bug, you shouldn't wait
to get a printed manual; you should read the section right away
as described below.

(2) With Info.  Start Emacs, do C-h i to enter Info,
then m Emacs 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 Emacs distribution.)

(3) By hand.  Do
    cat info/emacs* | more "+/^File: emacs,  Node: Bugs,"

Please first check the file etc/PROBLEMS (e.g. with C-h P in Emacs) to
make sure it isn't a known issue.