Mercurial > emacs
view BUGS @ 47024:15430c8d0eaa
* startup.el (normal-splash-screen): Ensure splash buffer is
killed. Use tabs in output. Fix test whether previous buffer was
*scratch* buffer.
* progmodes/simula.el (simula-abbrev-keyword-default)
(simula-abbrev-keyword, simula-abbrev-stdproc-default)
(simula-abbrev-stdproc): Doc fix - escape open parens in column 0.
* apropos.el (command-apropos): Use `defalias' instead of `fset'.
* mail/rmail.el (rmail-speedbar-match-folder-regexp): Doc fix.
author | John Paul Wallington <jpw@pobox.com> |
---|---|
date | Sat, 24 Aug 2002 14:26:06 +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.