+
+* REDISPLAY RELATED BUGS
+
+** Avoid unbreakable loops in redisplay.
+
+Redisplay may loop if there is an error in some display property, e.g.
+ (space 'left-margin)
+
+A fix would be to somehow disable handling of display properties if an error
+is encountered.
+
+
+** Problem with modeline and window margins:
+
+The mode line's right "box" line is misplaced under the right margin,
+rather than at the right window edge.
+
+emacs -Q
+(set-window-margins nil 25 25)
+C-x 2
+
+
+** custom mode-line face makes Emacs freeze up
+
+From: Stephen Berman <Stephen.Berman@gmx.net>
+Date: Sun, 24 Oct 2004 02:08:56 +0200
+
+1. Start Emacs with -q -no-site-file.
+
+2. Type `M-x customize-face' and at the prompt `mode-line'.
+
+3. In the Custom buffer for mode-line face
+ a. check width and give it the value `narrow';
+ b. check height and give it the value 120 in 1/10 pt;
+ c. check underline and give it the value `on' (or `colored');
+ d. check overline and give it the value `on' (or `colored').
+
+4. Set for current session.
+
+5. Invoke Ediff on any two files.
+
+6. Now Emacs is frozen and consumes 95-99% of CPU.
+
+The customizations in step 3 appear to be the minimum necessary to
+induce this bug. Leave out any one of them and Ediff runs without a
+problem. Also if the 1/10 point value of height is 130 or greater
+there's no bug (with the default font family; with e.g. Helvetica the
+bug is induced only by a value of 100 or less).
+
+I've noticed this freeze up only when invoking Ediff. The only thing
+I've been able to do is kill Emacs externally, via top or with kill
+when run in gdb, after interrupting. When the freeze up happens
+within a gdb session, there is no automatic debugging feedback. After
+interrupting I can get a backtrace, here's an example:
+
+Update: Maybe only reveals itself when compiled with GTK+
+
+
+** line-spacing and Electric-pop-up-window
+
+From: SAITO Takuya <tabmore@rivo.mediatti.net>
+Date: Mon, 31 May 2004 02:08:10 +0900 (JST)
+
+Electric-pop-up-window does not work well
+if truncate long lines disabled and/or
+`line-spacing' is set to positive integer.
+
+For example, start emacs -Q --line-spacing 1, and type M-` .
+Then, the last line of *Completions* buffer is not visible.
+
+fit-window-to-buffer works well for me, so I guess
+Electric-pop-up-window can use it.
+
+
+** Partial highlighting of wrapped overlay
+
+From: Ralf Angeli <angeli@iwi.uni-sb.de>
+Date: Mon, 18 Oct 2004 19:09:19 +0200
+
+If you put
+
+(let* ((length (+ (- (window-width) (current-column)) 40))
+ (start (point))
+ (end (+ (point) length))
+ (string (make-string length ?x))
+ ov)
+ (insert string)
+ (setq ov (make-overlay start end))
+ (overlay-put ov 'mouse-face 'highlight)
+ (overlay-put ov 'display string))
+
+into the *scratch* buffer and type `C-x C-e' with point at the last
+parenthesis, you will get a string which does not fit into the line
+and has to be wrapped. If you move over it with your mouse, you
+should see that only the part on the second line is being highlighted.
+The full string is highlighted only if the 'display property is not
+set.
+
+