Re: Bad cursor postion when dormat theads activate

["Jose A. Ortega Ruiz" <jao@gnu.org>]

Andreas Schwab <schwab@linux-m68k.org> writes:

> You'll have to trace it to see what arguments it needs to handle, and
> how the behaviour differs from forward-line.  Most likely N = 0 is
> problematic.

Thanks for the pointers. I've been trying to solve the problem without
success so far, but i do think that it has to do with dormant (ticked)
articles. There's in fact a very easy way to reproduce it, at least
here:

  1) Put yourself at the beginning of a thread with 2 unread messages
  2) T s/ T h work as expected, no surprises
  3) With the thread hidden, move to the end of the line with C-e:
    point moves not to the end of line, but to the end of the whole
    threads; i.e., you see it *after* the ellipsis (...)
  4) T s won't show the thread: point moves right before the ellipsis
    and the thread remains hidden
  5) If you T s again, now the thread is shown

If now you tick (U) the first article in the thread, exit the group and
re-enter it, you'll see the point is in state (3): seems like the fact
that the article is ticked causes gnus-summary-read-group to position
the point at the end of its thread (after or before hiding all threads,
i'm not sure), so that gnus-summary-show-thread does not have the
desired effect.

Unfortunately, the code is a bit convoluted, and it's not easy for me to
see where/how this state is reached. So i thought that maybe explaining
the situation would ring a bell to someone more familiar with Gnus code.

Thanks!
jao
--
The day Microsoft makes something that doesn't suck is probably the day
they start making vacuum cleaners - Ernst Jan Plugge