view BUGS @ 85500:0dcd1f3c9909

* textmodes/reftex.el: Move require easymenu before first use. (reftex-info): Require info at compile too. * textmodes/org-publish.el (org-publish-org-to-html) (org-publish-org-to): Require org at compile time too. (org-publish-attachment): Require at compile time too. * term/tty-colors.el (w32-tty-standard-colors): Pacify byte-compiler. * term/pc-win.el (frame-creation-function-alist): Add to this instead of setting frame-creation-function. * play/blackbox.el (bb-up, bb-down): Use forward-line. * net/rcirc.el (rcirc-markup-text-functions): Move definition earlier. * calendar/todo-mode.el: Require calendar at compile time. * calendar/cal-islam.el: Require diary-lib at compile time. * calendar/cal-hebrew.el: Require diary-lib and holidays at compile time. * w32-vars.el: Provide w32-vars. * term/w32-win.el: Require w32-vars. (w32-color-map): Pacify byte-compiler. * loadup.el: Load w32-wars before term/w32-win.

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.