view BUGS @ 107645:6e29ba4351e0

Fix glyph_row reversed_p flag in empty lines between paragraphs. bidi.c (bidi_get_next_char_visually): Improve commentary. dispextern.h (PRODUCE_GLYPHS): Set the reversed_p flag in the iterator's glyph_row here. xdisp.c (handle_invisible_prop, set_iterator_to_next) (next_element_from_buffer): Don't set the reversed_p flag in the iterator's glyph_row here.
author Eli Zaretskii <eliz@gnu.org>
date Sun, 28 Mar 2010 11:18:10 -0400
parents fb8bf24d2eb9
children ac52af4a044c
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-p in Emacs) to
make sure it isn't a known issue.