view BUGS @ 33472:1de979dabe6f

(tex-font-lock-keywords-1): Use `keep' rather than `prepend' and add an interesting comment. (tex-math-face, tex-font-lock-syntactic-face-function): New face and function to use it. (tex-define-common-keys, tex-mode-map): Use menu-item rather than `menu-enable' symbol property. (tex-mode-map): Bind {, (, [ and $ to skeleton-pair-insert-maybe. (tex-mode): Add some latex-mode commands for auto-selection. Use tex-font-lock-syntactic-face-function. (tex-insert-quote): Simplify. (tex-shell): New mode. (tex-start-shell): Use it. (tex-shell-proc, tex-shell-buf): New functions. (tex-send-command): Use it. (tex-main-file): Fix the meaning of the new arg REALFILE. (tex-send-tex-command): New function split from `tex-start-tex'. Set compilation-last-buffer and compilation-parsing-end.
author Stefan Monnier <monnier@iro.umontreal.ca>
date Tue, 14 Nov 2000 11:41:35 +0000
parents 354e0c45cedf
children af68d12218d0
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,"