view BUGS @ 55717:50b099e608af

(allout-chart-subtree, allout-rebullet-topic-grunt): Don't mention in the docstring these arguments meant for internal (recursive) use only. (allout-char-spec): Comment out (it's not implemented). (allout-old-expose-topic, allout-exposure): Fix docstring and add obsolescence declaration. (allout-flatten-exposed-to-buffer, allout-indented-exposed-to-buffer): Fix typos in docstring. (my-mark-marker): Doc fix. (produce-allout-mode-map, allout-sibling-index, allout-isearch-expose) (allout-distinctive-bullet, allout-open-topic, allout-reindent-body) (allout-rebullet-heading, allout-process-exposed, allout-insert-listified) (allout-latex-verb-quote, allout-insert-latex-header) (allout-insert-latex-trailer): Make arguments match their use in docstring. (allout-primary-bullet, allout-old-style-prefixes, allout-inhibit-protection) (allout-init, allout-mode, allout-before-change-protect, allout-flag-region): Use "Emacs" instead of "emacs" in docstrings.
author Juanma Barranquero <lekktu@gmail.com>
date Fri, 21 May 2004 18:10:21 +0000
parents 8ce686bd7f4f
children fb8bf24d2eb9
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,"

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.