Mercurial > emacs
view BUGS @ 99299:8460775a4023
(Types of Log File): Change logs are older than version control.
(VCS Concepts): Simplify and rearrange.
(Version Control Systems): Make it clear that Linux is only the kernel.
(VC Mode Line): Shorten reference to menu item.
(Basic VC Editing): Clarify VC fileset. Shorten and simplify.
(VC Directory Mode): Minor cleanup.
Unchanged files are hidden, not omitted.
(VC Directory Commands): Shorten and simplify.
(Change Log Commands): New node, split from Change Logs.
(VC Directory Buffer): New node, split from VC Directory Mode.
author | Richard M. Stallman <rms@gnu.org> |
---|---|
date | Sat, 01 Nov 2008 01:58:13 +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.