unset strict_threads not working?
Hi! I'm using Mutt 1.2, but I think my problem has not too much to do with the version, because it's likely a misconfiguration thing. The problem is that I have a bunch of messages that I gate from news to mail (and the news messages are from a fido gate :-)). These messages haven't got too much of a "rfc compliant" References and/or In-Reply-To fields: most of them just have the reference to another message, and no more than one message. So, when I want to see the folder threaded, there are messages that don't appear in the same thread even when they share the same subject. Reading the docs, this would be the case when "strict_threads" is set; but I haven't set it at all :-m Reading again, the docs say that when strict_threads is not set the threading will take place in all the messages that share subject. But I've got quite a lot of them that fall inside this cathegory and aren't in the same thread :-m So, am I doing something wrong? Setting or unsetting "strict_threads" doesn't any visible effect at all. Any hint? Am I forgetting anything? Thanks in advance :-) -- Roberto Suarez Soto · Wrap the Net [EMAIL PROTECTED]· around every brain in the Planet, Corgo/Lugo/Galicia/Spain · and Software will flow in the wires.
Re: unset strict_threads not working?
Roberto Suarez Soto <[EMAIL PROTECTED]> wrote on Sat, 27 May 2000: > Hi! Hi! > I'm using Mutt 1.2, but I think my problem has not too much to do with > the version, because it's likely a misconfiguration thing. That part sounds right. [...] > So, when I want to see the folder threaded, there are > messages that don't appear in the same thread even when they share the same > subject. Ok, Mutt certainly should thread these messages, if you don't have $strict_threads set. The first thing to do would be to check the value of $strict_threads, even if you're not changing the value in your .muttrc, maybe the system Muttrc does, or something else like that. It's easy enough to verify the value: :set ?strict_threads That will tell you the current state. (That same command can be used to view the state of any other Mutt variable too, BTW...) Once you're sure it's not set, you can start thinking about the other things: 1) I *think* (not sure) that if you have had it set, and unset it, you need to make Mutt re-sort the folder. Either re-open it, or change the sort older... Not sure, although it would be easy enough to test. :-) 2) Often the messages don't have an *identical* subject, but instead have "Re: " or something like that in the beginning. Mutt will still know to group messages together in a thread by the subject, ignoring that leading bit -- this because of $reply_regexp, a regular expression defining all possible reply/forward/etc. subject line prefixes that are to be ignored. The default should be adequate for all normal situations, but if the language is different or the subjects are somehow mangled besides the usual "Re: ", you may need to tweak this setting. 3) As it was recently discussed, Mutt pays attention to the timestamps in messages (the Date header), and will know thread a message that is dated earlier (older) under a message that is dated later (newer). This may cause problems if someone's computer's clock is off. Because of this, some messages that should be part of some thread may appear before that thread. I hope that helps. If it doesn't, please post us more details... (variable states, message Subject/References sample headers, etc.) Regards, Mikko -- // Mikko Hänninen, aka. Wizzu // [EMAIL PROTECTED] // http://www.iki.fi/wiz/ // The Corrs list maintainer // net.freak // DALnet IRC operator / // Interests: roleplaying, Linux, the Net, fantasy & scifi, the Corrs / Being paranoid doesn't mean that they *aren't* out to get you.
Re: unset strict_threads not working?
On May/28/2000, Mikko Hänninen wrote: > 1) I *think* (not sure) that if you have had it set, and unset it, you > need to make Mutt re-sort the folder. Either re-open it, or change the > sort older... Not sure, although it would be easy enough to test. :-) Hmmm ... that was one thing I didn't know :-m I'll try :-) > 2) Often the messages don't have an *identical* subject, but instead > have "Re: " or something like that in the beginning. Mutt will still No, in this case they really have the same subject. As I said before, this messages are gated from a Fidonet echo. Usually, readers for this echos remove the leading "Re:" in subjects, so this shouldn't be a problem. But I'm glad to see that I had looked at the right points before mailing my problem, because I already knew the $reply_regexp thing :-) > 3) As it was recently discussed, Mutt pays attention to the timestamps > in messages (the Date header), and will know thread a message that is Yes, I'll have a look at this right now, because this could have some relevance in my problem :-m I'll tell what I find out :-) > I hope that helps. If it doesn't, please post us more details... > (variable states, message Subject/References sample headers, etc.) I'll do :-) Anyway, another non related (and I hope easier :-)) question: in the kind of mails that I was talking about, the quoted lines usually appear like this: AGG> This is a quoted line. I mean, a few letters (the initials of the poster) and the usual ">" sign. I find something similar in posts with Gnus. Anyone has a $quote_regexp for this? I could do it myself, but ... well, you know, Open Source is about using the work of others ;-) -- Roberto Suarez Soto ·Sure there's no way to turn it [EMAIL PROTECTED]· Back to the old days Corgo/Lugo/Galicia/Spain ·Of bliss and cheerful laughter
Re: unset strict_threads not working?
> Roberto Suarez Soto: > AGG> This is a quoted line. set quote_regexp="^([A-Za-z ]+>|[]%>:|}-][]>:|}-]*)" -- clemens [EMAIL PROTECTED]
Re: unset strict_threads not working?
On May/28/2000, clemensF wrote: > > AGG> This is a quoted line. > set quote_regexp="^([A-Za-z ]+>|[]%>:|}-][]>:|}-]*)" Thanks! :-) -- Roberto Suarez Soto ·If it doesn't work, force it. [EMAIL PROTECTED]· If it breaks, it needed replacing anyway. Corgo/Lugo/Galicia/Spain ·
Re: unset strict_threads not working?
Mikko Hänninen muttered: > 1) I *think* (not sure) that if you have had it set, and unset it, you > need to make Mutt re-sort the folder. Either re-open it, or change the > sort older... Not sure, although it would be easy enough to test. :-) Just tested it. If you set strict_threads mutt performs the new threading on the instance. > Being paranoid doesn't mean that they *aren't* out to get you. Wisely spoken ;-) HTH, Michael -- The steady state of disks is full. -- Ken Thompson PGP-fingerprint: DECA E9D2 EBDD 0FE0 0A65 40FA 5967 ACA1 0B57 7C13
Re: unset strict_threads not working?
I reply to myself, because I found out what was my problem :-) It was as simple as unsetting "sort_re", and I had the threading I liked. With "sort_re" set, the threading took into account the "Re:" part of the Subject, which actually didn't exist :-) So, unsetting this option makes every message with the same Subject appear in the same thread. After knowing this, a quick folder-hook put everything just as I wanted it to be :-) Thanks anyway for your effort :-) -- Roberto Suarez Soto ·Sure there's no way to turn it [EMAIL PROTECTED]· Back to the old days Corgo/Lugo/Galicia/Spain ·Of bliss and cheerful laughter
