* one last gnus-async bug
@ 1998-12-03 6:42 Felix Lee
0 siblings, 0 replies; only message in thread
From: Felix Lee @ 1998-12-03 6:42 UTC (permalink / raw)
if the nntp server closes the connection (eg, idled out),
then you get a spurious error popup if you have
debug-on-error set. if you don't have debug-on-error set,
umm, I think nothing special happens, and it just works.
*** nntp.el 1998/12/03 06:32:37 1.1
--- nntp.el 1998/12/03 06:32:44
***************
*** 945,951 ****
;; we only care about insertions at eob
(when (and (eq 0 len) (eq (point-max) end))
(save-match-data
! (nntp-async-trigger (get-buffer-process (current-buffer)))))
;; any throw from after-change-functions will leave it
;; set to nil. so we reset it here, if necessary.
(when quit-flag
--- 945,953 ----
;; we only care about insertions at eob
(when (and (eq 0 len) (eq (point-max) end))
(save-match-data
! (let ((proc (get-buffer-process (current-buffer))))
! (when proc
! (nntp-async-trigger proc)))))
;; any throw from after-change-functions will leave it
;; set to nil. so we reset it here, if necessary.
(when quit-flag
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~1998-12-03 6:42 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
1998-12-03 6:42 one last gnus-async bug Felix Lee
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).