Mercurial > emacs
view BUGS @ 41649:41d73d9565de
(Copyright): Add '(C)' as per coding guidelines.
The following changes are derived from suggestions by Bob Chapman
<rechapman@compuserve.com>.
(printlogline): Also allow tab and newline to separate
'(function):' from the rest of a comment.
(reformat the sorted log entries): Require date and author to
match the clumpname.
author | Paul Eggert <eggert@twinsun.com> |
---|---|
date | Wed, 28 Nov 2001 23:55:08 +0000 |
parents | af68d12218d0 |
children | 8ce686bd7f4f |
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 P in Emacs) to make sure it isn't a known issue.