view BUGS @ 97667:898ab684db68

(msdos-create-frame-with-faces): Renamed from make-msdos-frame. (terminal-init-internal): New function, errors out if called. (msdos-initialize-window-system): New function. (msdos-create-frame-with-faces): Set the terminal's `terminal-initted' (sic!) parameter. (frame-creation-function-alist): Add msdos-create-frame-with-faces. (window-system-initialization-alist): Add msdos-initialize-window-system. (handle-args-function-alist): Use tty-handle-args for `pc' ``window system'' as well. (pc-win): Provide.
author Eli Zaretskii <eliz@gnu.org>
date Sat, 23 Aug 2008 17:01:46 +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.