view BUGS @ 29037:238233843fc1

(comment-styles): New `box-multi'. (comment-normalize-vars): Better default for comment-continue to avoid whitespace-only continuations. (comment-search-forward): Always move even in the no-syntax case. (comment-padright): Only obey N if it's only obeyed for padleft. (comment-make-extra-lines): Better handling of empty continuations. Use `=' for the filler if comment-start has only one character. (uncomment-region): Try handling the special `=' filler. (comment-region): Allow LINES even if MULTI is nil. (comment-box): Choose box style based on comment-style.

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,"