* NEW FEATURES
-** Test the mbox branch of Rmail.
-
-** Install the mbox branch of Rmail.
-
** Face remapping.
** Let mouse-1 follow links.
** Clean up flymake.el to follow Emacs Lisp conventions.
+** Fix up url-ldap.el.
+
+* BUGS
+
+** Mailabbrev should quote addresses to correspond to RFC 822.
+See http://article.gmane.org/gmane.emacs.devel/27585
+
+** The '@' character should not expand addresses in mailabbrev
+See http://article.gmane.org/gmane.emacs.devel/27585
+
+** Bug in url-http-parse-headers, reported in
+From: Vivek Dasmohapatra <vivek@zeus.com>
+Date: Tue, 28 Sep 2004 16:13:13 +0100
+
+Fetching a url with url-retrieve can reult in an anrbitrary buffer
+being killed if a 401 (or possibly a 407) result is encountered:
+
+url-http-parse-headers calls url-http-handle-authentication,
+which can call url-retrieve.
+
+This results in the current buffer being killed, and a new http buffer
+being generated. However, when the old http buffer is killed, emacs
+picks the top buffer from the list as the new current buffer, so by the
+time we get to the end of url-http-parse-headers, _that_ buffer is marked
+as dead even though it is not necessarily a url buffer, so next time the
+url libraries reap their dead buffers, an innocent bystander buffer is
+killed instead (and an obsolete http buffer may be left lying around too).
+
+A possible fix (which I am currently using) is to call set-buffer
+on the return value of url-http-parse-headers:
+
+ (case url-http-response-status
+ (401
+ ;; The request requires user authentication. The response
+ ;; MUST include a WWW-Authenticate header field containing a
+ ;; challenge applicable to the requested resource. The
+ ;; client MAY repeat the request with a suitable
+ ;; Authorization header field.
+ (url-mark-buffer-as-dead (current-buffer))
+ (set-buffer (url-http-handle-authentication nil)))
+etc ....
+
+which makes sure that it is the right http buffer that is current when
+we come to mark the http buffers as dead.
+
+
+
* GTK RELATED BUGS
** Make GTK scrollbars behave like others w.r.t. overscrolling.
A fix would be to somehow disable handling of display properties if an error
is encountered.
-** 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))
-
** Problem with modeline and window margins:
lispref/compile.texi "Luc Teirlinck"
lispref/control.texi "Luc Teirlinck"
lispref/customize.texi
-lispref/debugging.texi
+lispref/debugging.texi Joakim Verona <joakim@verona.se>
lispref/display.texi
lispref/edebug.texi
lispref/elisp.texi "Luc Teirlinck"