annotate BUGS @ 85451:e1af3a725ca4

* textmodes/two-column.el (2C-split, 2C-merge): * textmodes/bib-mode.el (bib-find-key, mark-bib): * progmodes/idlw-shell.el (idlwave-shell-move-or-history): * progmodes/etags.el (find-tag-in-order, etags-tags-apropos) * progmodes/ada-xref.el (ada-get-all-references): * obsolete/mlsupport.el (ml-next-line, ml-previous-line): * emulation/vi.el (vi-previous-line-first-nonwhite) (vi-effective-range, vi-put-before): * emulation/edt.el (edt-next-line, edt-previous-line) (edt-paragraph-forward): Use forward-line. * progmodes/etags.el (tags-apropos): Require apropos at compile time too. * progmodes/prolog.el: Require comint when compiling. (inferior-prolog-flavor): Move defvar before use.

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.