view BUGS @ 73201:16a7031b0447

(allout-expose-topic): Rectify implementation of "+" spec, so that bodies are not exposed with headlines. (allout-current-depth): Do aberrent check only at or below doublecheck depth. (allout-chart-subtree): Make it explicit that LEVELS being nil means unlimited depth. Drop undocumented support for LEVELS value t meaning unlimited depth. (This is consistent with allout-chart-to-reveal, but contrary to allout-show-children, which needs to use nil to default to depth of 1.) (allout-goto-prefix-doublechecked): Wrap long docstring line. (allout-chart-to-reveal): Be explicit in docstring about meaning of nil LEVELS, and drop support for LEVELS value t. (allout-show-children): Translate the level spec used by this routine to that used by allout-chart-subtree and allout-chart-to-reveal. (allout-show-to-offshoot): Retry once when stuck, after opening subtree - improvements in discontinuity handling likely will enable progress.

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.