view BUGS @ 73767:a44deabfa735

Finish minor changes seen from DVI output. Replace 22.1.100 with 22.1.1. (current-kill): Mention functions that directly or indirectly call `kill-new', which sets `kill-ring-yank-pointer'. (Understanding current-kill): Change `lasted' to `last'. Remove extraneous parenthesis. Reword item about returning `car' of list. (yank): Remove mention of `rotate-yank-pointer'. (Y Axis Element): Add comment regarding replacement of blank space. (print-Y-axis Penultimate): Explain that `print-graph' will pass `height-of-top-line' so `print-Y-axis' does not have a bug.
author Robert J. Chassell <bob@rattlesnake.com>
date Mon, 06 Nov 2006 15:08:45 +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.