view BUGS @ 61637:54eea2db9773

(overlay_arrow_string_or_property): Remove PBITMAP arg. Calls changed. Don't check for overlay-arrow-bitmap property here. (overlay_arrow_at_row): Remove PBITMAP arg. Instead, if left fringe is present, return Lisp integer for bitmap (or -1 for default). Fix value of overlay-arrow-bitmap property to be a symbol, use lookup_fringe_bitmap to parse it. (display_line): Change call to overlay_arrow_at_row. Store integer return value as overlay bitmap in row rather than window. Only show overlay arrow if row displays text, or if no other overlay arrow is seen in window (if overlay marker is at point-max).
author Kim F. Storm <storm@cua.dk>
date Mon, 18 Apr 2005 14:10:09 +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.