view BUGS @ 53891:4b85b1e3d610

(prolog-program-name): Use gprolog if available. (prolog-mode-syntax-table, prolog-mode-abbrev-table, prolog-mode-map): Bring together declaration and initialization. (prolog-mode-variables): Don't set the syntax table. Don't set paragraph-start and comment-indent-function. Add /*..*/ to the comment regexps. (prolog-mode-commands): Remove. Do it during init of prolog-mode-map. (prolog-mode-map): Don't bind TAB. (prolog-mode): Set the syntax table. (prolog-comment-indent): Remove. (inferior-prolog-mode-map): Initialize in the declaration. (inferior-prolog-mode-syntax-table) (inferior-prolog-mode-abbrev-table): New vars. (inferior-prolog-mode): Derive from comint-mode. (run-prolog): Avoid switch-to-buffer which can fail in dedicated and minibuffer windows.

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 P in Emacs) to
make sure it isn't a known issue.