<<< Date Index >>>     <<< Thread Index >>>

mutt/2171: previous-thread doesn't jumps to first message if parent not available



>Number:         2171
>Notify-List:    344766@xxxxxxxxxxxxxxx
>Category:       mutt
>Synopsis:       previous-thread doesn't jumps to first message if parent not 
>available
>Confidential:   no
>Severity:       minor
>Priority:       medium
>Responsible:    mutt-dev
>State:          open
>Keywords:       
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Sun Jan 29 23:18:52 +0100 2006
>Originator:     Mike Dornberger
>Release:        1.5.11
>Organization:
>Environment:
>Description:
This is from Debian Bug#344766; in a nutshell, if a thread is missing the root 
message, doing next-thread from the previous thread goes to the first message, 
but doing previous-thread from the next one does not. Here is the original 
report:

-----------------------------------
Hi,

when in threaded mode, mutt doesn't jump to the first available message when
executing previous-thread (default binding: ^P) when the parent of two
replies is not available, which is at least unexpected. In my case it goes
to the second subthread. I wanted to read all what I have of this thread and
expected ^P to jump to the first message, so I can read all the messages by
pressing <right>.

You can test this with the file prev_thread-test.mbox that is compressed in
the attached file mutt_test_prev_thread.tar.bz2 [1]. Maybe an automated test can
be done with the muttrc I wrote. After executing

$ mutt -f prev_thread-test.1.mbox -F muttrc

the created file "content" should be the same as "content.expected".
Actually it gives the same as in "content.not_expected".

Greeting,
 Mike Dornberger
-----------------------------------

[1] 
http://people.debian.org/~adeodato/tmp/2006-01-29/mutt_test_prev_thread.tar.bz2
>How-To-Repeat:
>Fix:
Unknown
>Add-To-Audit-Trail:

>Unformatted: