view BUGS @ 84463:999e91a73e9d

(startup-screen-inhibit-startup-screen) (pure-space-overflow-message): New vars. (fancy-splash-insert): Allow functions for face and link specs. (fancy-splash-head): Remove unused arg. Move splash text... (fancy-startup-text, fancy-about-text): ...here. (fancy-startup-tail): Rename from fancy-splash-tail. (fancy-startup-screen, fancy-about-screen): Split off from fancy-splash-screens. (display-startup-screen): New function. (display-about-screen): Rename from display-splash-screen. (command-line-1): Use concise startup screen if necessary.
author Chong Yidong <cyd@stupidchicken.com>
date Mon, 10 Sep 2007 22:07:27 +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.