Mercurial > emacs
view BUGS @ 51844:c5036e7cc93b
(overlay_strings, recenter_overlay_lists): Fix typo in eassert in last commit.
(unchain_overlay): New function.
(add_overlay_mod_hooklist): Use AREF.
(copy_overlays, reset_buffer, overlays_at, overlays_in)
(overlay_touches_p, overlay_strings, recenter_overlay_lists)
(fix_overlays_in_range, fix_overlays_before, Fmake_overlay)
(Fmove_overlay, Fdelete_overlay, Foverlay_lists)
(report_overlay_modification, evaporate_overlays, init_buffer_once):
Adjust to new type of overlays_(before|after).
author | Stefan Monnier <monnier@iro.umontreal.ca> |
---|---|
date | Wed, 09 Jul 2003 15:09:12 +0000 |
parents | af68d12218d0 |
children | 8ce686bd7f4f |
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 P in Emacs) to make sure it isn't a known issue.