Cursor movement after restart of nntp connections

Cursor movement after restart of nntp connections

[Harry Putnam]

Running todays git of gnus

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.

No matter where I left the cursor, after doing above it jumps to the
top loosing whatever group I was attempting to open.

Is that something that just has to happen because a restart has
occured or can something be done by about retaining point in the
groups buffer?

Re: Cursor movement after restart of nntp connections

[Lars Magne Ingebrigtsen]

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?

-- 
(domestic pets only, the antidote for overdose, milk.)
  bloggy blog http://lars.ingebrigtsen.no/

Re: Cursor movement after restart of nntp connections

[Harry Putnam]

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.

Re: Cursor movement after restart of nntp connections

[Tom Tromey]

>>>>> "Harry" == 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.
[...]
Harry> Now I can't reproduce it either.

FWIW, this happens for me all the time with Emacs 24.
It doesn't seem to be gnus-specific.

Tom