Mercurial > emacs
view BUGS @ 29858:54f927c5f436
(handle_stop): Initialize it->add_overlay_start to zero.
(handle_invisible_prop): Record the start of invisible text in
it->add_overlay_start.
(struct overlay_entry): Add member `overlay'.
(handle_overlay_change): Simplify.
(next_overlay_string): After having processed overlay strings at the
end of the buffer, record that fact in
it->overlay_strings_at_end_processed_p.
(compare_overlay_entries): If before- and after-strings come
from the same overlay, let before-strings come first.
(RECORD_OVERLAY_STRING): Record the overlay that strings come from.
(load_overlay_strings): Take it->add_overlay_start into account
when adding overlay strings.
author | Gerd Moellmann <gerd@gnu.org> |
---|---|
date | Thu, 22 Jun 2000 19:32:09 +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,"