Re: silly feature re: collapsed threads

[Peter Bloomfield <PeterBloomfield MindSpring com>]

On 2001.10.25 06:15 urgrue wrote:
> theres a silly feature in collapsed threads. if i hit D on one, it 
> deletes the first message THEN jumps to the next message that is NOT 
> part of that thread.
> which is a bit silly, why does it jump past the thread, just cause i 
> deleted the first message in it? i think it should delete the first 
> message and show me the next one in the thread.
> (or even have D delete the whole thread? or ask to? or maybe a 
> logical way to do it would be that pressing D on a collapsed thread 
> uncollapses it first, and from then on D will delete. i dunno, these 
> are just suggestions.)
> 
> keep up the good work.

That's funny, I was just thinking the same thing.  It jumps past the 
thread because it moves to the `next' message, but looks only at 
viewable nodes in defining `next'.  It's annoying, because when you 
take an action on part of a thread, either deleting or moving, you most 
often want to continue working with the same thread.

Arguably, the `Open next' button should also auto-expand threads, 
although that's at least debatable.  There are at least three different 
actions that we might want:
(1) open next viewable (current action);
(2) open head of next thread;
(3) open next in current thread, auto-expanding if necessary.
and of course the current `open next unread'.  Any or all of these 
could be implemented, although I'm not going to argue for all those 
buttons.  I *will* argue that (1) is the least likely to be what we 
really want.

Comments?

Peter