[Pan-users] Re: Re: Article Threading in Pan 0.101

[Duncan]

Douglas Bollinger <address@hidden> posted
address@hidden, excerpted below, on  Sat, 01 Jul 2006
08:00:39 -0400:

> In the above case, "AMD patent about inverse hyperthreading" is
> double-underlined.  If I select it, all the subthreads are displayed
> correctly with new articles in bold.  That's fine.
> 
> I think before the way it worked for me was: I grabbed new headers.  Pan
> displayed unexpanded threads, but _only_ the threads that had new posts,
> the double-underlined threads in new Pan.  When I expanded the thread, I
> seen all the old articles and the new ones were in bold.
> 
> Can I get this behavior with new Pan?

Try the match only unread articles, but then select Show matching
articles' threads.  As Jim H suggested, that would appear to be what you
want.

A couple additional comments:

1) Old pan also made a distinction between old but still unread headers,
and freshly downloaded headers.  Charles decided that was unnecessary
complexity for the limited benefit achieved and the number of folks who
really used that feature, so it's not available in the new pan thereby
reducing bloat by that bit more.  Perhaps it's just because while I new
the distinction and used the bit of extra data it provided, I didn't
really /use/ the feature, but I tend to agree with Charles -- the
distinction between old but unread and new... isn't really needed and
isn't really missed.  IMO, it's nice to have, but not a good tradeoff given
the cost of the increased code complexity.

So anyway, you don't get the distinction between old unread and new
messages that old-pan had, but neither Charles nor myself believe that's a
big issue.  Read/unread is good enough.

2)  New-pan doesn't yet track and remember all that stuff per-group like
old-pan did.  You may find that you need to reset your choice when
restarting pan, and will find that the same choice is now globally
applied.  Per group state retention looks to be one of the big features
lined up to return for 1.1, as a lot of folks' favorite sub-features are
wrapped up in it!  With 1.0 stable targeted for around August, and a couple
1.0.x stable updates likely after that, we're probably looking at Sept/Oct
for per-group state retention, my guess.  What sub-features will come with
it and which ones will wait for later, I couldn't guess at this point.

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman