#344766 mutt: previous-thread jumps not to first message if parent not available

Package:
mutt
Source:
mutt
Description:
text-based mailreader supporting MIME, GPG, PGP and threading
Submitter:
Mike Dornberger
Date:
2026-06-24 01:55:02 UTC
Severity:
normal
Tags:
#344766#5
Date:
2005-12-25 21:16:10 UTC
From:
To:
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. 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
#344766#10
Date:
2006-01-29 22:18:53 UTC
From:
To:
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
Unknown
#344766#13
Date:
2006-01-29 23:15:02 UTC
From:
To:
The following reply was made to PR mutt/2171; it has been noted by GNATS.

From: owner@bugs.debian.org (Debian Bug Tracking System)
To: bug-any@bugs.mutt.org
Cc:
Subject: Bug#344766: Info received (was mutt/2171: previous-thread doesn't jumps to first message if parent not available)
Date: Sun, 29 Jan 2006 14:33:14 -0800

 Thank you for the additional information you have supplied regarding
 this problem report.  It has been forwarded to the package maintainer(s)
 and to other interested parties to accompany the original report.

 Your message has been sent to the package maintainer(s):
  Adeodato Simó <dato@net.com.org.es>

 If you wish to continue to submit further information on your problem,
 please send it to 344766@bugs.debian.org, as before.

 Please do not reply to the address at the top of this message,
 unless you wish to report a problem with the Bug-tracking system.

 Debian bug tracking system administrator
 (administrator, Debian Bugs database)
#344766#20
Date:
2009-01-25 15:25:45 UTC
From:
To:
Still reproducible in 1.5.18-4
#344766#23
Date:
2009-02-07 13:17:43 UTC
From:
To:
#2171: previous-thread doesn't jumps to first message if parent not available
-------------------------------------+--------------------------------------
  Reporter:  Mike.Dornberger@gmx.de  |       Owner:  mutt-dev
      Type:  defect                  |      Status:  new
  Priority:  trivial                 |   Milestone:
 Component:  mutt                    |     Version:  1.5.19
Resolution:                          |    Keywords:
-------------------------------------+--------------------------------------
Changes (by antonio@dyne.org):

  * version:  1.5.11 => 1.5.19


Comment:

 still seen in 1.5.19
#344766#26
Date:
2010-08-06 04:37:15 UTC
From:
To:
------------------------------------+---------------------------------------

Old description:

New 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: