Thread View: gnu.emacs.gnews
3 messages
3 total messages
Started by Jean-Francois Rit
Wed, 04 Nov 1992 15:39
Gnews 2.0 and 18.58?
Author: Jean-Francois Rit
Date: Wed, 04 Nov 1992 15:39
Date: Wed, 04 Nov 1992 15:39
8 lines
756 bytes
756 bytes
We recently upgraded emacs to 18.58 and since then gnews appears to be broken. The connection to the nntp newshost dies instantly and gnews exits with the message "connection died out etc.". Did this happen to anybody and is there a fix for this? It is quite hard to investigate this since gnews exits cleanly and no trace of the NNTP session can be found. I'll appreciate any clue. J-F Rit
Re: Gnews 2.0 and 18.58?
Author: Rich Alderson
Date: Sat, 07 Nov 1992 01:45
Date: Sat, 07 Nov 1992 01:45
21 lines
1818 bytes
1818 bytes
In article <1992Nov4.153902.24082@edf.fr>, rit@chp28aa (Jean-Francois Rit) writes:
>We recently upgraded emacs to 18.58 and since then gnews appears to be broken.
>The connection to the nntp newshost dies instantly and gnews exits with the
>message "connection died out etc.".
>
>Did this happen to anybody and is there a fix for this? It is quite hard to
>investigate this since gnews exits cleanly and no trace of the NNTP session
>can be found.
I had this problem with 18.57, but it was fixed in 18.58. At least, I thought
it was.
There was a re-write of the TCP code in 18.57 that was the cause of the break;
maybe the fixed code got backed out later?
I'll check the current sources and see if they differ from mine.
--
Rich Alderson 'I wish life was not so short,' he thought. 'Languages take
such a time, and so do all the things one wants to know about.'
--J. R. R. Tolkien,
alderson@leland.stanford.edu _The Lost Road_
Re: Gnews 2.0 and 18.58?
Author: Matthew P Wiener
Date: Sun, 08 Nov 1992 14:47
Date: Sun, 08 Nov 1992 14:47
26 lines
1882 bytes
1882 bytes
In article <1992Nov7.014555.14017@leland.Stanford.EDU>, alderson@elaine46 (Rich Alderson) writes:
>>The connection to the nntp newshost dies instantly and gnews exits with the
>>message "connection died out etc.".
>There was a re-write of the TCP code in 18.57 that was the cause of the break;
>maybe the fixed code got backed out later?
The Gnews function nntp-run-p (inside NNTP.el) invokes process-status.
According to p-s's documentation, p-s is supposed to return 'open for
network connections. Instead, it's actually returning 'run, like a
normal process. So Gnews thinks no NNTP connection occurs, and the
connection is terminated.
The fix is easy. You can change the one symbol, or you can use the
following which checks for both. I suppose this latter will have to
become the official version anyway.
(defun nntp-run-p ()
"Return t if the NNTP process is running, nil otherwise."
(and (boundp 'nntp)
(processp nntp)
(or (eq (process-status nntp) 'run)
(eq (process-status nntp) 'open))))
--
-Matthew P Wiener (weemba@sagi.wistar.upenn.edu) If Apple owned
NBC, they would sue Nike for comedy-interface copyright violation.
Thread Navigation
This is a paginated view of messages in the thread with full content displayed inline.
Messages are displayed in chronological order, with the original post highlighted in green.
Use pagination controls to navigate through all messages in large threads.
Back to All Threads