view BUGS @ 71366:1a62b8cd2100

(next_overlay_string): Fix assert. (push_it, pop_it): Handle composition and stretch specific values. Only handle it->slice in image (for now). (back_to_previous_visible_line_start): Continue search if newline is part of a compisition. Simplify. (reseat_1): Set it->object to buffer. (set_iterator_to_next): Set it->object to string or buffer, when setting it->method to GET_FROM_STRING or GET_FROM_BUFFER. (next_element_from_composition): Set it->object to buffer if not from string. (set_cursor_from_row): Only save start of string if not already done to handle multiple strings in a row.
author Kim F. Storm <storm@cua.dk>
date Fri, 16 Jun 2006 11:53:12 +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.