Paul Fox wrote:
it occurred to me yesterday that this script might be quite
useful (instead of just pretty :-) if it had one simple feature:
the ability to add each thread to a separate, temporary, mh
sequence (t1, t2, t3, ...). the output would then include
Instead of creating, multiple
Instead of creating, multiple sequences, I use a script which just
creates a single sequence given a message number to start with. It's a
zsh function I'm afraid. Cut down to the essentials, it is as follows:
local -a msgs refer ref rep mid
msgs=( ${@:-cur} )
ref=( $(scan -width
I think that if you want to keep the threading support out of the main
nmh utilities (scan/show/etc) you need to at least add an option to them
to respect the order of message numbers on the command line.
(But I still think that actually having the core utilities know about
threads would be
Ralph Corderoy wrote:
Yes, I'm hitting it daily and having to work around it. Given the
increase in space and time of computing resources, it's now practical to
have +inbox containing thousands of emails and have a script that picks
them into many different sequences in reasonable time
Josh Bressers [EMAIL PROTECTED] wrote:
It may be worth looking at this and expanding on the idea:
http://jmason.org/software/mhthread/
I ran across that some time ago and played with it a bit. I like the idea,
but it could use some refining.
See also the 3rd screenshot here:
