bug#11404: 24.1.50; gnus-summary: "Hiding the thread moved us backwards, aborting!" impedes workflow

[Detlev Zundel]

Hi Lars,

> Detlev Zundel <dzu@denx.de> writes:
>
>> That means I'm using the default setting.  Isn't that supported?
>
> Sure.  But I'm unable to reproduce this bug.  `C-M-k' works on all the
> threads I've tried it on.  Do you have a recipe for how to reproduce
> this bug?

Let me give an example from the recent linux-arm Gmane newsgroup
(gmane.linux.ports.arm.kernel) with screenshots for clarity:

I select only ten messages as I'm sure that I will see at least one
thread:

Now I read the third message into the thread (without looking at the
thread head):

Having read that, I want to kill the whole thread, so I move the cursor
to the first message in the thread (could also be done by
'gnus-summary-top-thread') - again without reading it - and do
'gnus-summary-kill-thread':

I hope this is a more clear recipy on how to reproduce that.

Thanks
  Detlev

-- 
Greenspun's Tenth Rule of Programming: "Any sufficiently complicated C
or Fortran program contains an ad-hoc, informally-specified bug-ridden
slow implementation of half of Common Lisp."
--
DENX Software Engineering GmbH,      MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich,  Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-40 Fax: (+49)-8142-66989-80 Email: dzu@denx.de