From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.user/2210 Path: news.gmane.org!not-for-mail From: Kinkie Newsgroups: gmane.emacs.gnus.user Subject: Re: Aget woes in oort gnus Date: Sun, 16 Mar 2003 10:30:28 +0100 Message-ID: References: NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1138668724 14330 80.91.229.2 (31 Jan 2006 00:52:04 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Tue, 31 Jan 2006 00:52:04 +0000 (UTC) Original-X-From: nobody Tue Jan 17 17:30:21 2006 Original-Path: quimby.gnus.org!newsfeed.gazeta.pl!fu-berlin.de!uni-berlin.de!dial-up-mi-702.lombardiacom.IT!not-for-mail Original-Newsgroups: gnu.emacs.gnus Original-NNTP-Posting-Host: dial-up-mi-702.lombardiacom.it (212.34.227.194) Original-X-Trace: fu-berlin.de 1047806869 72485194 212.34.227.194 (16 [94405]) Attribution: Kinkie User-Agent: Gnus/5.090016 (Oort Gnus v0.16) XEmacs/21.4 (Informed Management, linux) Cancel-Lock: sha1:D3J6YoqozeQxVdyxKg6a7xEDO6w= Original-Xref: bridgekeeper.physik.uni-ulm.de gnus-emacs-gnus:2350 Original-Lines: 45 X-Gnus-Article-Number: 2350 Tue Jan 17 17:30:21 2006 Xref: news.gmane.org gmane.emacs.gnus.user:2210 Archived-At: Kevin Greiner writes: >>>>>>>> - with 0.15 I had this problem where despite being started as >>>>>>>> gnus-unplugged, it complained that it couldn't select my >>>>>>>> gnus-select-method server at startup. Having it denied, going >>>>>>>> to the server buffer, re-enabling it and >>>>>>>> gnus-group-get-new-news'ing would allow me to see the groups >>>>>>>> from that server. I'm not sure this is still true (I've just >>>>>>>> updated). >>>>>>> >>> >>> Check the value of gnus-server-unopen-status. It needs to be >>> either nil or offline. >> >> In a freshly started gnus, after accepting to continue after the >> failure but before doing anything else, it's nil. > > OK, it looks like we'll be doing this one the hard way. > > Please do the following in a freshly started emacs. > 1) M-: (setq gnus-verbose 10) > 2) M-x gnus-unplugged > > Do whatever you usually do to get the group buffer to appear then > stop. What I'd like to see is the contents of your message buffer. > I'm hoping to use the message text to trace the execution path. If > this doesn't work, I'll probably have to send a patched file with > custom instrumentation in it. I didn't get the trace, but MAYBE I understood the problem. It looks like a problem of crossed wires. I have a few servers in my gnus: two nntp servers (including gnus-select-method), a couple of nnfolders and an nnimap which I really don't use. Only the nntp servers are agentized. It appears that if I start gnus up when not-connected, for some reason it misunderstands the failure to open the nnimap as problems with the select-method server. If I'm online when I fire up gnus, then no errors occur. I've disabled the nnimap server, and everything appears to be working fine. -- kinkie (kinkie-ml [at] tiscalinet [dot] it) Random fortune, unrelated to the message: The meek shall inherit the earth, but *not* its mineral rights. -- J.P. Getty