view BUGS @ 67262:c3cfae9a5571

(eval-when-compile): Remove unnecessary load of 'cl. Add fset of allout-real-isearch-abort during compile to alleviate unnecessary byte-compilation warnings. (allout-mode-p): Move definition of this macro above all uses, or byte compilation in barren emacs (eg, during emacs build) will lack the definition. (allout-mode): Move this variable above any uses, or byte compilation will fail. (allout-resolve-xref): Remove use of personal file-reference function. (allout-toggle-current-subtree-encryption): Do the current (ie, visible containing) topic, rather than nearest around point. Doc fix. (allout-toggle-subtree-encryption): New function, workhorse that works on nearest topic containing point. (allout-encrypt-string): Signal requirement for newer version of pgg. (allout-resumptions): Doc fix.
author Eli Zaretskii <eliz@gnu.org>
date Fri, 02 Dec 2005 14:09:53 +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.