view BUGS @ 72050:d79208e62ea9

(allout-unprotected, allout-e-o-prefix-p) (allout-beginning-of-current-line, allout-end-of-current-line) (allout-next-visible-heading, allout-open-topic) (allout-kill-topic, allout-yank-processing, allout-resolve-xref) (allout-flag-current-subtree, allout-show-to-offshoot) (allout-hide-current-entry, allout-show-current-branches) (allout-hide-region-body, allout-old-expose-topic) (allout-listify-exposed, allout-latex-verbatim-quote-curr-line) (allout-mark-topic, allout-adjust-file-variable): Enclose scopes containing `beginning-of-line' and `end-of-line' with `inhibit-field-text-motion' t.

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.