Mercurial > emacs
view BUGS @ 97683:02243cbabf8e
(Fortran): Change description of free form and
fixed form a bit. Mention hideshow and imenu.
(Fortran Motion): Mention fortran-end-of-subprogram,
fortran-beginning-of-subprogram, fortran-mark-do, fortran-mark-if.
(Fortran Indent): Minor re-word.
(ForIndent Commands): Mention fortran-fill-paragraph and
fortran-fill-statement.
(ForIndent Cont): Mention fortran-tab-mode-string.
(Fortran Comments): Mention fortran-comment-line-start-skip.
(Fortran Columns): Mention font-locking.
(Fortran Abbrev): Word syntax not relevant with new-style abbrev.
author | Glenn Morris <rgm@gnu.org> |
---|---|
date | Sat, 23 Aug 2008 23:29:54 +0000 |
parents | 8ce686bd7f4f |
children | fb8bf24d2eb9 |
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 C-e in Emacs) to make sure it isn't a known issue.