Mercurial > emacs
comparison admin/FOR-RELEASE @ 90054:f2ebccfa87d4
Revision: miles@gnu.org--gnu-2004/emacs--unicode--0--patch-74
Merge from emacs--cvs-trunk--0
Patches applied:
* miles@gnu.org--gnu-2004/emacs--cvs-trunk--0--patch-709
Update from CVS: src/indent.c (Fvertical_motion): Fix last change.
* miles@gnu.org--gnu-2004/emacs--cvs-trunk--0--patch-710
- miles@gnu.org--gnu-2004/emacs--cvs-trunk--0--patch-715
Update from CVS
* miles@gnu.org--gnu-2004/emacs--cvs-trunk--0--patch-716
Merge from gnus--rel--5.10
* miles@gnu.org--gnu-2004/gnus--rel--5.10--patch-74
Update from CVS
| author | Miles Bader <miles@gnu.org> |
|---|---|
| date | Wed, 08 Dec 2004 05:02:30 +0000 |
| parents | 8cf051896b6b |
| children | f7098e12436d 549734260e34 |
comparison
equal
deleted
inserted
replaced
| 90053:fff5f1a61d92 | 90054:f2ebccfa87d4 |
|---|---|
| 34 | 34 |
| 35 ** Fix up url-ldap.el. | 35 ** Fix up url-ldap.el. |
| 36 | 36 |
| 37 * BUGS | 37 * BUGS |
| 38 | 38 |
| 39 ** Ange-ftp should ignore irrelevant IPv6 errors: | |
| 40 | |
| 41 Message-Id: <4121-Tue23Mar2004165249+0100-piet@cs.uu.nl> | |
| 42 From: "Piet van Oostrum" <piet@cs.uu.nl> | |
| 43 To: emacs-pretest-bug@gnu.org | |
| 44 Subject: Ange-ftp can't deal with IPV6/IPV4 fallback | |
| 45 | |
| 46 Symptoms: | |
| 47 | |
| 48 C-x C-f /ftp.nluug.nl:/ | |
| 49 | |
| 50 The problem is that the DNS first gives an IPV6 address. However our | |
| 51 router doesn't do IPV6. Ftp then falls back to IPV4: | |
| 52 | |
| 53 ftp> open ftp.nluug.nl | |
| 54 Trying 2001:610:1:80aa:192:87:102:36... | |
| 55 ftp: connect to address 2001:610:1:80aa:192:87:102:36: No route to host | |
| 56 Trying 192.87.102.36... | |
| 57 Connected to ftp.nluug.nl. | |
| 58 | |
| 59 Ange-ftp chokes on the `No route to host' message and doesn't look any | |
| 60 further. | |
| 61 | |
| 62 I think in the near future we will see more of this problem, so it might be | |
| 63 time to make anfe-ftp more intelligent. | |
| 64 | |
| 39 ** Mailabbrev should quote addresses to correspond to RFC 822. | 65 ** Mailabbrev should quote addresses to correspond to RFC 822. |
| 40 See http://article.gmane.org/gmane.emacs.devel/27585 | 66 See http://article.gmane.org/gmane.emacs.devel/27585 |
| 41 | 67 |
| 42 ** The '@' character should not expand addresses in mailabbrev | 68 ** The '@' character should not expand addresses in mailabbrev |
| 43 See http://article.gmane.org/gmane.emacs.devel/27585 | 69 See http://article.gmane.org/gmane.emacs.devel/27585 |
| 47 Date: Tue, 28 Sep 2004 16:13:13 +0100 | 73 Date: Tue, 28 Sep 2004 16:13:13 +0100 |
| 48 | 74 |
| 49 Fetching a url with url-retrieve can reult in an anrbitrary buffer | 75 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: | 76 being killed if a 401 (or possibly a 407) result is encountered: |
| 51 | 77 |
| 52 url-http-parse-headers calls url-http-handle-authentication, | 78 url-http-parse-headers calls url-http-handle-authentication, |
| 53 which can call url-retrieve. | 79 which can call url-retrieve. |
| 54 | 80 |
| 55 This results in the current buffer being killed, and a new http buffer | 81 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 | 82 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 | 83 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 | 84 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 | 85 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 | 86 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). | 87 killed instead (and an obsolete http buffer may be left lying around too). |
| 62 | 88 |
| 63 A possible fix (which I am currently using) is to call set-buffer | 89 A possible fix (which I am currently using) is to call set-buffer |
| 64 on the return value of url-http-parse-headers: | 90 on the return value of url-http-parse-headers: |
| 65 | 91 |
| 72 ;; Authorization header field. | 98 ;; Authorization header field. |
| 73 (url-mark-buffer-as-dead (current-buffer)) | 99 (url-mark-buffer-as-dead (current-buffer)) |
| 74 (set-buffer (url-http-handle-authentication nil))) | 100 (set-buffer (url-http-handle-authentication nil))) |
| 75 etc .... | 101 etc .... |
| 76 | 102 |
| 77 which makes sure that it is the right http buffer that is current when | 103 which makes sure that it is the right http buffer that is current when |
| 78 we come to mark the http buffers as dead. | 104 we come to mark the http buffers as dead. |
| 79 | 105 |
| 80 | 106 |
| 81 | 107 |
| 82 * GTK RELATED BUGS | 108 * GTK RELATED BUGS |
| 91 Redisplay may loop if there is an error in some display property, e.g. | 117 Redisplay may loop if there is an error in some display property, e.g. |
| 92 (space 'left-margin) | 118 (space 'left-margin) |
| 93 | 119 |
| 94 A fix would be to somehow disable handling of display properties if an error | 120 A fix would be to somehow disable handling of display properties if an error |
| 95 is encountered. | 121 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 | 122 |
| 107 | 123 |
| 108 ** Problem with modeline and window margins: | 124 ** Problem with modeline and window margins: |
| 109 | 125 |
| 110 The mode line's right "box" line is misplaced under the right margin, | 126 The mode line's right "box" line is misplaced under the right margin, |
