On Feb 06, Daniel Eisenbud [[EMAIL PROTECTED]] wrote: > I've been planning to do this for a while. > > It seems to me that the only time that more than two levels of sorting > is useful is when the first level is threads. If anyone can give me a > plausible scenario where they'd want more than three, or more than two > unthreaded, I'll think about my approach. But for the moment the right > thing to do seems to be to break threading out into its own config > variable. So you can set > > threads=forward > threads=reverse > or > threads=off > > and then sort and sort_aux are what's used for secondary and tertiary > sorting, or primary and secondary if threads=off. Make sense to people?
Heh, I had the exact same thought reading this thread, so I certainly concur. The only other possibility I was thinking of was trying to accomodate the guy who wants all "Debian Weekly News [date]" sorted together. Date won't do it, and subject won't do it. He could munge the subject in procmail, but that's probably not desirable. Without having time to give it too much thought, the two approaches that immediately come to mind are scoring (and using scoring for anything like this always limits what else you can use it for) and some kind of sorting based on arbitrary message headers, because having procmail add those headers _would_ make sense. Both of this have problems if they're taken literally, but they also both point toward some kind of combination of sorting with pattern matching. You can get this in a limited way now if you score based on patterns and sort based on score, but again, that limits what else you can use scoring for. I guess that's also an example of where one would want more than your above listed tertiary sorting... you could want to sort on subject first, followed by date, but all able to be overridden by score. Anyway, just rambling, since I don't have a good idea of how to approach this. But maybe someone else will.
msg24246/pgp00000.pgp
Description: PGP signature
