view BUGS @ 30402:cc4564c9cd55

(c-append-paragraph-start): New variable used by c-common-init to get paragraph-start correct. (c-common-init): Use c-append-paragraph-start to initialize paragraph-start to make it correct both with and without the javadoc special case. (c-Pike-inexpr-class-key): New constant, since "class" can introduce an in-expression class in Pike nowadays. (c-Java-javadoc-paragraph-start): Brought up-to-date with javadoc 1.2. (c-common-init): Handling of obsolete variables moved to c-initialize-cc-mode. More compatible style override when using global style variables.
author Gerd Moellmann <gerd@gnu.org>
date Mon, 24 Jul 2000 11:11:01 +0000
parents 354e0c45cedf
children af68d12218d0
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,"