comparison admin/FOR-RELEASE @ 57845:d68febf099b4

Add redisplay related errors.
author Kim F. Storm <storm@cua.dk>
date Mon, 01 Nov 2004 14:06:54 +0000
parents 95e2d2018daa
children 41263d3a8d8b
comparison
equal deleted inserted replaced
57844:b6104b08e544 57845:d68febf099b4
5 ** Test the mbox branch of Rmail. 5 ** Test the mbox branch of Rmail.
6 6
7 ** Install the mbox branch of Rmail. 7 ** Install the mbox branch of Rmail.
8 8
9 ** Face remapping. 9 ** Face remapping.
10
11 ** Let mouse-1 follow links.
10 12
11 13
12 * FATAL ERRORS 14 * FATAL ERRORS
13 15
14 ** Investigate face cache related crash. 16 ** Investigate face cache related crash.
16 Indications: Face cache seems to have been cleared, but 18 Indications: Face cache seems to have been cleared, but
17 redisplay uses an invalidated face_id with FACE_FROM_ID 19 redisplay uses an invalidated face_id with FACE_FROM_ID
18 which then returns a NULL pointer. Said to happen with 20 which then returns a NULL pointer. Said to happen with
19 isearch faces. 21 isearch faces.
20 22
23 ** Investigate reported crashes in compact_small_strings.
24
25 ** Investigate reported crashes related to using an
26 invalid pointer from string_free_list.
27
28
21 * LOSSAGE 29 * LOSSAGE
22 30
23 ** Clean up flymake.el to follow Emacs Lisp conventions. 31 ** Clean up flymake.el to follow Emacs Lisp conventions.
32
24 33
25 * GTK RELATED BUGS 34 * GTK RELATED BUGS
26 35
27 ** Make GTK scrollbars behave like others w.r.t. overscrolling. 36 ** Make GTK scrollbars behave like others w.r.t. overscrolling.
28 37
29 ** Make GTK update the menu bar in two stages, as with Xt, 38 ** Make GTK update the menu bar in two stages, as with Xt,
30 so that the first can run Lisp code, while only the second 39 so that the first can run Lisp code, while only the second
31 needs BLOCK_INPUT. 40 needs BLOCK_INPUT.
41
42
43 * REDISPLAY RELATED BUGS
44
45 ** Avoid unbreakable loops in redisplay.
46
47 Redisplay may loop if there is an error in some display property, e.g.
48 (space 'left-margin)
49
50 A fix would be to somehow disable handling of display properties if an error
51 is encountered.
52
53 ** Problem with cursor border around images and window-margins:
54
55 The border around the image when the cursor is on the image
56 flows into the right fringe and margin.
57
58 (progn
59 (auto-image-file-mode 1)
60 (find-file (concat data-directory "splash.xpm"))
61 (set-window-margins (selected-window) 25 25))
62
63
64 ** Problem with modeline and window margins:
65
66 The mode line's right "box" line is misplaced under the right margin,
67 rather than at the right window edge.
68
69 emacs -Q
70 (set-window-margins nil 25 25)
71 C-x 2
72
73
74 ** custom mode-line face makes Emacs freeze up
75
76 From: Stephen Berman <Stephen.Berman@gmx.net>
77 Date: Sun, 24 Oct 2004 02:08:56 +0200
78
79 1. Start Emacs with -q -no-site-file.
80
81 2. Type `M-x customize-face' and at the prompt `mode-line'.
82
83 3. In the Custom buffer for mode-line face
84 a. check width and give it the value `narrow';
85 b. check height and give it the value 120 in 1/10 pt;
86 c. check underline and give it the value `on' (or `colored');
87 d. check overline and give it the value `on' (or `colored').
88
89 4. Set for current session.
90
91 5. Invoke Ediff on any two files.
92
93 6. Now Emacs is frozen and consumes 95-99% of CPU.
94
95 The customizations in step 3 appear to be the minimum necessary to
96 induce this bug. Leave out any one of them and Ediff runs without a
97 problem. Also if the 1/10 point value of height is 130 or greater
98 there's no bug (with the default font family; with e.g. Helvetica the
99 bug is induced only by a value of 100 or less).
100
101 I've noticed this freeze up only when invoking Ediff. The only thing
102 I've been able to do is kill Emacs externally, via top or with kill
103 when run in gdb, after interrupting. When the freeze up happens
104 within a gdb session, there is no automatic debugging feedback. After
105 interrupting I can get a backtrace, here's an example:
106
107
108 ** Mouse-face overlay bleeds into header line
109
110 From: Stephen Berman <Stephen.Berman@gmx.net>
111 Date: Thu, 21 Oct 2004 18:11:01 +0200
112
113 Mouse-face overlays bleed into the header line when the beginning of
114 the overlay is above (point-min). To reproduce:
115
116 1. Start Emacs with -q -no-site-file.
117
118 2. In *scratch* eval (setq ov (make-overlay 66 92)), (overlay-put ov
119 'mouse-face 'highlight), and (setq header-line-format "test").
120
121 3. Drag the mouse over the string "evaluation.\n;; If you want" and
122 notice the highlighting of only this string.
123
124 4. Now click on the down arrow in the scroll bar until the line
125 beginning ";; If you want" is directly below the header line.
126
127 5. Drag the mouse over ";; If you want" and notice that not only it
128 but also the header line are highlighted.
129
130
131 ** scroll-preserve-screen-position doesn't work with a header-line-format
132
133 From: jbyler+emacs-lists@anon41.eml.cc
134 Date: Tue, 17 Aug 2004 17:10:14 -0400
135
136 There seems to be an off-by-one error triggered by using a header line
137 together with scroll-preserve-screen-position. The symptom: instead of
138 staying in the same position on the screen when scrolling, the cursor
139 moves one screen line down each time the buffer is scrolled. Put
140 another way: repeatedly typing C-v M-v or using a mouse scroll wheel to
141 scroll up and down causes the cursor to migrate slowly down the screen
142 instead of staying put as it should.
143
144 To reproduce:
145
146 emacs -q --no-site-file
147 (setq scroll-preserve-screen-position t)
148 (setq header-line-format "")
149 C-v M-v C-v M-v C-v M-v etc.
150
151
152 ** Clicking on partially visible lines fails
153
154 From: David Kastrup <dak@gnu.org>
155 Date: 27 Apr 2004 16:42:58 +0200
156
157 This bug report will be sent to the Free Software Foundation,
158 not to your local site managers!
159 Please write in English if possible, because the Emacs maintainers
160 usually do not have translators to read other languages for them.
161
162 Your bug report will be posted to the emacs-pretest-bug@gnu.org mailing list.
163
164 Please describe exactly what actions triggered the bug
165 and the precise symptoms of the bug:
166
167 I had gnus display a mouse-highlighted line (a URL from browse-url)
168 partially at the bottom of its window. If I click with middle mouse
169 key on it, the window gets recentered while I hold the mouse key
170 pressed. If I release it, the window returns into its old position
171 (cursor in top row) and nothing happens, presumably because the click
172 was not registered on the line itself, but on the magically
173 recentered version.
174
175 That is a nuisance. Recentering of even partially visible click
176 targets should only happen if window-point moves there, but not at
177 the time of the click. From the moment I hold down a key until it
178 gets released, the displayed window portion should not change, with
179 the sole exception of scrolling when dragging at the edge of the
180 screen.
181
182
183 ** Can't drag modeline when mouse-autoselect-window is set
184
185 From: Klaus Zeitler <kzeitler@lucent.com>
186 Date: Mon, 11 Oct 2004 11:14:49 +0200
187
188 1. start emacs -q --no-site-file
189 2. set variable mouse-autoselect-window to t
190 3. split-window-vertically
191
192 now I can drag the modeline only upwards but not downwards
193
194
195 ** line-spacing and (recenter -1)
196
197 From: SAITO Takuya <tabmore@rivo.mediatti.net>
198 Date: Mon, 31 May 2004 02:07:57 +0900 (JST)
199
200 (recenter -1) does not show point at the bottom of the window
201 if line-spacing is set to positive integer.
202
203 Start emacs -Q, and evaluate below:
204
205 (progn
206 (setq line-spacing 1)
207 (dotimes (i (window-height))
208 (insert "\n" (int-to-string i)))
209 (recenter -1))
210
211 Then, point is displayed at the center of the window.
212 But point should be displayed at the bottom of the window like Emacs-21.3.
213
214
215 ** line-spacing and garbage in fringe
216
217 From: SAITO Takuya <tabmore@rivo.mediatti.net>
218 Date: Mon, 31 May 2004 02:08:05 +0900 (JST)
219
220 Start emacs -Q and evaluate below with C-xC-e:
221
222 (let ((lines 2)
223 (spacing 1))
224 (setq line-spacing spacing
225 indicate-buffer-boundaries t)
226 (insert (make-string (window-height) ?\n))
227 (goto-char (point-min))
228 (message (make-string (* (window-width) lines) ?.))
229 (scroll-up 1))
230
231 then, garbage is displayed in right fringe.
232
233 Above code reproduces this bug with
234 (frame-parameter nil 'font)
235 => "-Adobe-Courier-Medium-R-Normal--12-120-75-75-M-70-ISO8859-1"
236
237 If you use different font, you may need different value of
238 `lines' and/or `spacing'.
239
240
241 ** line-spacing and Electric-pop-up-window
242
243 From: SAITO Takuya <tabmore@rivo.mediatti.net>
244 Date: Mon, 31 May 2004 02:08:10 +0900 (JST)
245
246 Electric-pop-up-window does not work well
247 if truncate long lines disabled and/or
248 `line-spacing' is set to positive integer.
249
250 For example, start emacs -Q --line-spacing 1, and type M-` .
251 Then, the last line of *Completions* buffer is not visible.
252
253 fit-window-to-buffer works well for me, so I guess
254 Electric-pop-up-window can use it.
255
32 256
33 * DOCUMENTATION 257 * DOCUMENTATION
34 258
35 ** Finish updating the Emacs Lisp manual. 259 ** Finish updating the Emacs Lisp manual.
36 260