I have been having a crazy problem in gnus every time I have
tested betas b7, b8, and now b9.
If I enter "c" to catchup a group, the original
newsgroup+article number line remains, and the updated line is placed
elsewhere in the Groups buffer. For example:
8920: comp.protocols.dns.bind
1523: comp.protocols.dns.std
8: comp.unix.solaris
If I was to do a catchup on comp.unix.solaris, I would end up with
something like this:
0: comp.unix.solaris
8920: comp.protocols.dns.bind
1523: comp.protocols.dns.std
8: comp.unix.solaris
I finally traced this down today and the problem appears to happen
in gnus-dribble-enter. The function uses the *Groups* buffer & tne
.newsrc-dribble buffer. In a nutshell, the point in the *Groups*
buffer is changed to the point in the .newsrc-dribble buffer and
that's why the updated newsgroup line is put in the wrong place.
I took gnus-dribble-enter and made a little test-case. In 21.5-b5 (
and Emacs 21.1), the points printed out will be the same. In 21.5-b7
and above, the point moves (starting up normally & with -vanilla)
Seems like this should be causing all kinds of problems for people, so
I'm wondering if i'm the only one seeing it...
redhat 7.3 /non mulle.
Jeff
(defun jdm-test-case ()
""
(interactive)
(let ((obuf (current-buffer))
(original-point (point))
(string "testing.....")
(test-buffer (get-buffer-create "TEST-BUFFER")))
(set-buffer test-buffer)
(goto-char (point-max))
(insert string "\n")
(set-window-point (get-buffer-window (current-buffer)) (point-max))
(bury-buffer test-buffer)
(save-excursion
(set-buffer obuf)
(message "original point is %s, current point is %s"
original-point
(point))
)
(set-buffer obuf))
)
Show replies by thread