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

[Douglas Bollinger]

On Sat, 1 Jul 2006 17:20:41 +0000 (UTC)
"Duncan" <address@hidden> wrote:

> 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.

No, it doesn't do what I want.  In fact, the thread display with Show
matching/match only unread is exactly the same as the screenshot I posted
earlier.  That's what I'm try to get at:  Is this a bug?

Just to nail this down completely, I'm using "Show Matching Article's Threads"
and "Match only unread articles".  I expect to see unread articles threaded
correctly with read articles, _IF_ that particular thread has any unread
articles.  If the thread is all read articles, I shouldn't see any of that
particular thread in the header pane.

Right now I get a jumbled mess of unread articles out-of-context with each
other because the read articles won't display and then threading is broken.
If I activate the read articles by deactivating "Match only unread articles",
ALL the threads in the group are displayed which is a huge list because I
don't expire articles.  But then threading works correctly.

Again, this isn't something new, I'm just try to replicate old Pan behavior
that I'ved used for years (and just last week).  What I'm trying to determine
if the threading shown in the screenshot I posted is a bug or just how things
work now.

> 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
<snip>

Good riddance.  I never used new/old either and usually found it confusing.
Glad to see it gone.  Anyway, in any post that I make, new=unread and old=read
if I don't correct it.  It's still confusing even when the feature is gone. :)

-- 
It is very vulgar to talk like a dentist when one isn't a dentist.
It produces a false impression.
                -- Oscar Wilde.