The trouble with using sequences is that all the existing nmh programs
ignore order within sequences and just handle the messages in ascending
numerical order; this is pretty useless for threading and means we can't
just tweak sortm and pick. (Unless you want to maintain folders in thread
order, which would require enough intelligence in refile to insert new
messages without having to rethread the entire folder.)
Maintaining folders in thread order with incremental updates is
*very* difficult, AFAICT.
I realise sequences are effectively unordered; my suggestion was for a
*hierarchy* of sequences, i.e. multiple sequences to reflect (some of)
the threading information. Listings of subthreads would still be done
using spin by giving it a sequence, for instance, but having a
hierachy of sequences means thread navigation would be possible, i.e.
the thread navigation consists of moving from one sequence to another,
using the sequence name itself to determine where to move to.
Cheers,
- Joel
_______________________________________________
Nmh-workers mailing list
Nmh-workers@nongnu.org
http://lists.nongnu.org/mailman/listinfo/nmh-workers