From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/83789 Path: news.gmane.org!not-for-mail From: Harry Putnam Newsgroups: gmane.emacs.gnus.general Subject: Re: How to get this debugged (pressing g fails) Date: Tue, 01 Oct 2013 10:56:43 -0400 Organization: Still searching... Message-ID: <874n913uqc.fsf@newsguy.com> References: <871u4cwiwu.fsf@newsguy.com> <87ioxngx9b.fsf@newsguy.com> <87zjqydkm3.fsf@newsguy.com> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1380639497 1476 80.91.229.3 (1 Oct 2013 14:58:17 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 1 Oct 2013 14:58:17 +0000 (UTC) To: ding@gnus.org Original-X-From: ding-owner+M32045@lists.math.uh.edu Tue Oct 01 16:58:20 2013 Return-path: Envelope-to: ding-account@gmane.org Original-Received: from util0.math.uh.edu ([129.7.128.18]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1VR1Oy-0006hp-Hf for ding-account@gmane.org; Tue, 01 Oct 2013 16:58:16 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.math.uh.edu) by util0.math.uh.edu with smtp (Exim 4.63) (envelope-from ) id 1VR1Nn-0007MX-EV; Tue, 01 Oct 2013 09:57:03 -0500 Original-Received: from mx2.math.uh.edu ([129.7.128.33]) by util0.math.uh.edu with esmtps (TLSv1:AES256-SHA:256) (Exim 4.63) (envelope-from ) id 1VR1Nl-0007M9-0l for ding@lists.math.uh.edu; Tue, 01 Oct 2013 09:57:01 -0500 Original-Received: from quimby.gnus.org ([80.91.231.51]) by mx2.math.uh.edu with esmtps (TLSv1:AES256-SHA:256) (Exim 4.76) (envelope-from ) id 1VR1Ni-0006da-GB for ding@lists.math.uh.edu; Tue, 01 Oct 2013 09:57:00 -0500 Original-Received: from plane.gmane.org ([80.91.229.3]) by quimby.gnus.org with esmtp (Exim 4.72) (envelope-from ) id 1VR1Ng-0006c9-KL for ding@gnus.org; Tue, 01 Oct 2013 16:56:56 +0200 Original-Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1VR1Ne-0005f5-55 for ding@gnus.org; Tue, 01 Oct 2013 16:56:54 +0200 Original-Received: from z65-50-57-227.ips.direcpath.com ([65.50.57.227]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 01 Oct 2013 16:56:54 +0200 Original-Received: from reader by z65-50-57-227.ips.direcpath.com with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 01 Oct 2013 16:56:54 +0200 X-Injected-Via-Gmane: http://gmane.org/ Original-Lines: 78 Original-X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: z65-50-57-227.ips.direcpath.com User-Agent: Gnus/5.130008 (Ma Gnus v0.8) Emacs/24.0.92 (gnu/linux) Cancel-Lock: sha1:NCgzDV0aFABpqqsOUTUm47yMM5k= X-Spam-Score: -2.6 (--) List-ID: Precedence: bulk Xref: news.gmane.org gmane.emacs.gnus.general:83789 Archived-At: Harry Putnam writes: [...] Katsumi wrote: >> Grep doesn't hit such a words combination in the Gnus source or >> the Emacs source, but Google does. For instance, bitbucket[1] >> shows this: >> >> (defadvice gnus-group-get-new-news (around gnus-timeout activate) >> "Timeout for Gnus." >> (with-timeout >> (5 (message "Gnus timed out.") (debug)) >> ad-do-it)) >> >> Do you have the one like that in your ~/.gnus.el file? If so, >> too small timeout seconds (5 in that case) may cause the problem. >> >> [1] Harry responded: > Haa, you got it Katsumi. Now I remember a good while back being > disgusted with long stalls from gnus and so thought I was being very > clever by putting that code in .gnus, making gnus fail and tell me > why. Instead of just setting there endlessly. [...] I may have been overly optimistic above. Increasing the timeout seemed to do the job at first but after a few refreshes it needed to be increased repeatedly. Finally, after commenting that timeout code, I see why I'd put it there long ago. I was experiencing endless waits when pressing 'g'. I've just been working around the problem for so long... I forgot. What happens is: calling gnus-group-get-new-news leads to a never ending wait that never finishes. All my nnimap, nnml groups go thru the process ending with nndrafts. >From there is goes to the nntp groups... once that starts its going to just set there to eternity until I hit C-g. I don't believe it is a connection issue because a manual refresh of individual nntp (`gnus-group-get-new-news-this-group') groups finishes with only a small pause. Further, a restart happens in a normal amount of time which also calls that code gnus-group-get-new-news (I think). So in summary: I I can refresh all groups by closing and restarting gnus in a normal amount of time. I can refresh groups individually or even en-masse by process marking and pressing M-g (gnus-group-get-new-news-this-group) However pressing 'g' in a group buffer ( `gnus-group-get-new-news' ) leads to a never ending process that only stops with C-g Watching the nntp-log buffer when I press C-g to terminate the wait I see it stopped at the first nntp newsguy group. So I'm thinking there is some cantankerous newsguy group. However, Pressing A M newsguy to find all newsguy groups, then process marking and pressing M-g (`gnus-group-get-new-news-this-group'), they all get processed with only a brief wait... maybe 10 seconds. So doesn't seem to be a problem newsguy group causing the trouble ------- --------- ---=--- --------- -------- I suspect the trouble is caused by something I've done but not sure how get to root of the trouble. How can I determine what gnus is doing during that never ending wait produced by pressing 'g' (`gnus-group-get-new-news') in group buffer?