view BUGS @ 85617:4cbfa6e02bcd

(f90-keywords-re, f90-keywords-level-3-re): Add `non_intrinsic'. (f90-constants-re): Add ieee modules. (f90-typedef-matcher, f90-typedec-matcher) (f90-imenu-type-matcher): New functions. (f90-font-lock-keywords-1): Give module procedures function-name face. Use `f90-typedef-matcher' for derived types. Fix `abstract interface'. Add `use, intrinsic'. (f90-font-lock-keywords-2): Use `f90-typedec-matcher' for derived types. Move start of `enum' blocks to separate entry. (f90-start-block-re): Fix `type', `abstract interface'. (f90-imenu-generic-expression): Use `f90-imenu-type-matcher' for derived types. (f90-mode-abbrev-table): Add `abstract interface', `asynchronous', `elemental', change `enumerator'. (f90-no-block-limit): Fix `abstract interface'.

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.