From: Harry Putnam <reader@newsguy.com>
To: ding@gnus.org
Subject: Re: Cursor movement after restart of nntp connections
Date: Mon, 27 Jun 2011 08:39:27 -0500 [thread overview]
Message-ID: <8762nrwfzk.fsf@newsguy.com> (raw)
In-Reply-To: <m3liwoocnt.fsf@quimbies.gnus.org>
Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
> Harry Putnam <reader@newsguy.com> 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.
next prev parent reply other threads:[~2011-06-27 13:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-26 14:31 Harry Putnam
2011-06-26 15:06 ` Lars Magne Ingebrigtsen
2011-06-27 13:39 ` Harry Putnam [this message]
2011-06-28 19:20 ` Tom Tromey
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8762nrwfzk.fsf@newsguy.com \
--to=reader@newsguy.com \
--cc=ding@gnus.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).