annotate BUGS @ 70028:d81780942bb8

* mh-acros.el (struct, x, y): No need to wrap defvar with eval-when-compile when shushing compiler, even when mh-do-in-xemacs or another construct is used. * mh-comp.el (sendmail-coding-system): Ditto. * mh-e.el (mark-active): Ditto. * mh-folder.el (desktop-save-buffer, font-lock-auto-fontify) (image-load-path, font-lock-defaults): Ditto. * mh-letter.el (image-load-path, font-lock-defaults): Ditto. * mh-mime.el (dots, type, ov) (mm-verify-function-alist, mm-decrypt-function-alist) (pressed-details): Ditto. * mh-search.el (pick-folder, mh-do-in-xemacs) (mh-mairix-folder, mh-flists-search-folders) (which-func-mode, mh-speed-flists-inhibit-flag): Ditto. * mh-seq.el (tool-bar-mode): Ditto. * mh-utils.el (completion-root-regexp) (minibuffer-completing-file-name): Ditto. * mh-xface.el (default-enable-multibyte-characters): Ditto.

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.