Hi, all -- A while back (1.3.22, perhaps) I reported a problem where sorting by threads, collapsing all threads, sorting unsorted, selecting a message that would be inside a collapsed thread, and resorting by thread caused first a blank display and second, upon movement, a segfault. A patch was posted for this and integrated into the source.
Now when I perform the same operation I am taken to the first new message in my mailbox as soon as I change from unsorted to threaded; the status line reports "Parent message is not available" and, while the direct parent of the message I selected *is* availale, that parent is orphaned to thread levels deep. To wit: 8934 Jan 08 Ought! ( 31) ?-?-?->Re: maildir (number of lines 8935 N Jan 08 Curt Zirzow ( 46) `->Re: maildir (number of lines I went back and tried this with the virgin source and no muttrc to confirm; I set $ascii_chars manually in the example above before pasting. Any ideas? :-D -- David T-G * It's easier to fight for one's principles (play) [EMAIL PROTECTED] * than to live up to them. -- fortune cookie (work) [EMAIL PROTECTED] http://www.justpickone.org/davidtg/ Shpx gur Pbzzhavpngvbaf Qrprapl Npg!
msg22665/pgp00000.pgp
Description: PGP signature
