annotate BUGS @ 96126:fcd827c4a553

Fix up docstring conventions. Move vars to before their first use. (rst-mode): Don't mess with font-lock-support-mode. (rst-suggest-new-decoration, rst-adjust-decoration): Avoid CL's copy-list. (rst-delete-entire-line): Use line-beginning-position. (rst-position): New fun. (rst-straighten-decorations): Use it instead of CL's position. (rst-straighten-bullets-region): Avoid CL's mapcar*. (rst-toc-mode): Use define-derived-mode. (rst-iterate-leftmost-paragraphs, rst-iterate-leftmost-paragraphs-2): Remove unused var `in-par'. Use `point' rather than `point-marker'. (rst-line-block-region): Reduce redundancy. Use the `pfxarg' arg. (rst-replace-lines): Simplify.

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 C-e in Emacs) to
make sure it isn't a known issue.