view BUGS @ 30744:6181f12f7f51

(trace_move) [GLYPH_DEBUG]: New variable. (TRACE_MOVE) [GLYPH_DEBUG]: New macro. (move_it_in_display_line_to): Record iterator's ascent and descent before producing glyphs, and restore them when we know the glyph doesn't fit on the line. (move_it_to): Restructured so that it's easier to debug. If moving to a vpos, and not moving to an x or character position, stop as soon as the specified vpos is reached; don't move further into that line because that might change the computed line height. (try_cursor_movement): New function, extracted from the cursor movement branch of redisplay_window. If ending on a partially visible line, don't try to scroll if the cursor line is taller than the window. (redisplay_window): Use try_cursor_movement.
author Gerd Moellmann <gerd@gnu.org>
date Thu, 10 Aug 2000 19:15:37 +0000
parents 354e0c45cedf
children af68d12218d0
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,"