From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/79217 Path: news.gmane.org!not-for-mail From: Harry Putnam Newsgroups: gmane.emacs.gnus.general Subject: Re: Cursor movement after restart of nntp connections Date: Mon, 27 Jun 2011 08:39:27 -0500 Organization: Still searching... Message-ID: <8762nrwfzk.fsf@newsguy.com> References: <87tybcwtoq.fsf@newsguy.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: dough.gmane.org 1309182010 5380 80.91.229.12 (27 Jun 2011 13:40:10 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Mon, 27 Jun 2011 13:40:10 +0000 (UTC) To: ding@gnus.org Original-X-From: ding-owner+M27514@lists.math.uh.edu Mon Jun 27 15:40:03 2011 Return-path: Envelope-to: ding-account@gmane.org Original-Received: from util0.math.uh.edu ([129.7.128.18]) by lo.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1QbC2j-0005NT-U5 for ding-account@gmane.org; Mon, 27 Jun 2011 15:40:02 +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 1QbC2W-00006T-6v; Mon, 27 Jun 2011 08:39:48 -0500 Original-Received: from mx1.math.uh.edu ([129.7.128.32]) by util0.math.uh.edu with esmtps (TLSv1:AES256-SHA:256) (Exim 4.63) (envelope-from ) id 1QbC2U-00006E-Dw for ding@lists.math.uh.edu; Mon, 27 Jun 2011 08:39:46 -0500 Original-Received: from quimby.gnus.org ([80.91.231.51]) by mx1.math.uh.edu with esmtps (TLSv1:AES256-SHA:256) (Exim 4.76) (envelope-from ) id 1QbC2Q-0003lW-3A for ding@lists.math.uh.edu; Mon, 27 Jun 2011 08:39:46 -0500 Original-Received: from lo.gmane.org ([80.91.229.12]) by quimby.gnus.org with esmtp (Exim 4.72) (envelope-from ) id 1QbC2O-0002Op-N9 for ding@gnus.org; Mon, 27 Jun 2011 15:39:40 +0200 Original-Received: from list by lo.gmane.org with local (Exim 4.69) (envelope-from ) id 1QbC2M-0005Dl-KT for ding@gnus.org; Mon, 27 Jun 2011 15:39:38 +0200 Original-Received: from c-98-215-231-30.hsd1.in.comcast.net ([98.215.231.30]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 27 Jun 2011 15:39:38 +0200 Original-Received: from reader by c-98-215-231-30.hsd1.in.comcast.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 27 Jun 2011 15:39:38 +0200 X-Injected-Via-Gmane: http://gmane.org/ Original-Lines: 37 Original-X-Complaints-To: usenet@dough.gmane.org X-Gmane-NNTP-Posting-Host: c-98-215-231-30.hsd1.in.comcast.net User-Agent: Gnus/5.110018 (No Gnus v0.18) Emacs/24.0.50 (gnu/linux) Cancel-Lock: sha1:EMgbYAy5o+/9pUJNFKE7izXVrlo= X-Spam-Score: -4.9 (----) List-ID: Precedence: bulk Xref: news.gmane.org gmane.emacs.gnus.general:79217 Archived-At: Lars Magne Ingebrigtsen writes: > Harry Putnam writes: > >> I've noticed for sometime that when I occasionally have to restart the >> nntp connections by going to the server buffer and doing a close and >> open on each nntp server, that when I return to the group buffer... my >> cursor has jumped to the top of my display. > > I'm unable to reproduce this. > > When stuff like that happens, it usually means that something is killing > a buffer and then trying to move point, which will then be in a > different buffer. Which, in Gnus, is usually the Group buffer. > > But these bugs are very difficult to track down where they happen > exactly. > > Does this happen when you `C' all your nntp servers, or just some? Now I can't reproduce it either. It must be related to whatever is causing the Denied to happen. When I do Close and go back to group point is still where I left it. Doing close/open same story. I have gnus setup to scan for new periodically, and often there will come a point where one of those scans freezes gnus. Then I will notice its frozen and do C-g. At that point I often forget that the servers are probably denied and try to open something and get the notice that the group can't be opened Then comes a trip to server buffer close/open usually on at least Gmane but sometimes both nntp servers are denied. Its at that point when I return to `group' that point jumps to the top. So there is, no doubt, more going on related to whatever froze the session. I'll set `debug on error' and see if I can get a handy backtrace.