view BUGS @ 32045:74db1ffe4fe8

(latex-metasection-list): New var. (latex-imenu-create-index): Use it. Move the regexp construction outside loops (and use push). (tex-font-lock-keywords-1, tex-font-lock-keywords-2) (tex-font-lock-keywords): Moved from font-lock.el. (tex-comment-indent): Remove. (tex-common-initialization): Don't set comment-indent-function. (latex-block-default): New var. (tex-latex-block): Use it to provide a default choice. Add any unknown choice to latex-block-names. Insert [...] after {...}. (tex-last-unended-begin): Simplify regexp. (tex-goto-last-unclosed-latex-block, latex-backward-sexp-1) (latex-forward-sexp-1, latex-forward-sexp): New functions. (latex-mode): Set forward-sexp-function.
author Stefan Monnier <monnier@iro.umontreal.ca>
date Sun, 01 Oct 2000 00:47:41 +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,"