comparison admin/FOR-RELEASE @ 58404:c491aac34318

Fixed this redisplay bug: ** Problem with cursor border around images and window-margins: The border around the image when the cursor is on the image flows into the right fringe and margin. (progn (auto-image-file-mode 1) (find-file (concat data-directory "splash.xpm")) (set-window-margins (selected-window) 25 25))
author Kim F. Storm <storm@cua.dk>
date Sun, 21 Nov 2004 15:50:08 +0000
parents 0f51d789a78e
children 8cf051896b6b 2a3f27a45698
comparison
equal deleted inserted replaced
58403:c936fa56eb60 58404:c491aac34318
47 Date: Tue, 28 Sep 2004 16:13:13 +0100 47 Date: Tue, 28 Sep 2004 16:13:13 +0100
48 48
49 Fetching a url with url-retrieve can reult in an anrbitrary buffer 49 Fetching a url with url-retrieve can reult in an anrbitrary buffer
50 being killed if a 401 (or possibly a 407) result is encountered: 50 being killed if a 401 (or possibly a 407) result is encountered:
51 51
52 url-http-parse-headers calls url-http-handle-authentication, 52 url-http-parse-headers calls url-http-handle-authentication,
53 which can call url-retrieve. 53 which can call url-retrieve.
54 54
55 This results in the current buffer being killed, and a new http buffer 55 This results in the current buffer being killed, and a new http buffer
56 being generated. However, when the old http buffer is killed, emacs 56 being generated. However, when the old http buffer is killed, emacs
57 picks the top buffer from the list as the new current buffer, so by the 57 picks the top buffer from the list as the new current buffer, so by the
58 time we get to the end of url-http-parse-headers, _that_ buffer is marked 58 time we get to the end of url-http-parse-headers, _that_ buffer is marked
59 as dead even though it is not necessarily a url buffer, so next time the 59 as dead even though it is not necessarily a url buffer, so next time the
60 url libraries reap their dead buffers, an innocent bystander buffer is 60 url libraries reap their dead buffers, an innocent bystander buffer is
61 killed instead (and an obsolete http buffer may be left lying around too). 61 killed instead (and an obsolete http buffer may be left lying around too).
62 62
63 A possible fix (which I am currently using) is to call set-buffer 63 A possible fix (which I am currently using) is to call set-buffer
64 on the return value of url-http-parse-headers: 64 on the return value of url-http-parse-headers:
65 65
72 ;; Authorization header field. 72 ;; Authorization header field.
73 (url-mark-buffer-as-dead (current-buffer)) 73 (url-mark-buffer-as-dead (current-buffer))
74 (set-buffer (url-http-handle-authentication nil))) 74 (set-buffer (url-http-handle-authentication nil)))
75 etc .... 75 etc ....
76 76
77 which makes sure that it is the right http buffer that is current when 77 which makes sure that it is the right http buffer that is current when
78 we come to mark the http buffers as dead. 78 we come to mark the http buffers as dead.
79 79
80 80
81 81
82 * GTK RELATED BUGS 82 * GTK RELATED BUGS
91 Redisplay may loop if there is an error in some display property, e.g. 91 Redisplay may loop if there is an error in some display property, e.g.
92 (space 'left-margin) 92 (space 'left-margin)
93 93
94 A fix would be to somehow disable handling of display properties if an error 94 A fix would be to somehow disable handling of display properties if an error
95 is encountered. 95 is encountered.
96
97 ** Problem with cursor border around images and window-margins:
98
99 The border around the image when the cursor is on the image
100 flows into the right fringe and margin.
101
102 (progn
103 (auto-image-file-mode 1)
104 (find-file (concat data-directory "splash.xpm"))
105 (set-window-margins (selected-window) 25 25))
106 96
107 97
108 ** Problem with modeline and window margins: 98 ** Problem with modeline and window margins:
109 99
110 The mode line's right "box" line is misplaced under the right margin, 100 The mode line's right "box" line is misplaced under the right margin,