view BUGS @ 64678:2fdca9c174be

(ibuffer-columnize-and-insert-list, ibuffer-mouse-toggle-mark, ibuffer-count-marked-lines, ibuffer-unmark-all, ibuffer-toggle-marks, ibuffer-unmark-forward, ibuffer-unmark-backward, ibuffer-compile-make-format-form, ibuffer-format-column, ibuffer-current-buffers-with-marks, ibuffer-update-title-and-summary): "?\ " -> "?\s". (ibuffer): Doc fix. (ibuffer-mode): Fix typo in docstring. (ibuffer-hooks, ibuffer-mode-hooks): Make obsolete and declare with `define-obsolete-variable-alias'. (ibuffer-elide-long-columns): Mark as obsolete. Doc fix.
author Juanma Barranquero <lekktu@gmail.com>
date Fri, 29 Jul 2005 15:10:37 +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.