[Pan-users] Re: 0.129 - a few minor issues

[Jim Henderson]

On Sat, 12 May 2007 05:35:54 +0000, Duncan wrote:

> Jim Henderson <address@hidden> posted
> address@hidden, excerpted below, on  Fri, 11 May 2007
> 16:08:10 +0000:
> 
> [On unread messages not displaying until read/unread is toggled.]
> 
>> I rarely do binaries, and I see it frequently - even in text-only
>> groups with a low traffic rate.  For instance, I monitor a private
>> server's control.cancel group, and usually there's only a handful of
>> messages in there, but I almost never see the new messages without
>> doing the read/ unread thing.
> 
> Hmm...  I wonder what the difference is?  I see from a different reply
> you pull headers automatically at startup, but not upon entering a
> group, or I'd suggest the group entry pull might be the trigger.  Maybe
> it's simply a race condition I don't see, with my dual Opteron and huge
> memory. <shrug>

Could be; this laptop is a P4 with 2 GB of memory in it, but it is a 
single core processor.  I might have to profile it if I end up with a 
larger group again.

>> Maybe for you, but not for me.  I use forums.novell.com,
>> news.povray.org, news.vmware.com, and a couple others - all
>> special-purpose servers with their own distinct sets of newsgroups.
> 
> True.  I'm actually that way on my text groups too, since the gmane
> groups don't appear elsewhere, and the Cox groups don't appear elsewhere
> either, and that's most of my text groups.  However, in the general
> case, groups will appear on multiple servers, so sorting by server
> doesn't work that well.  As I mentioned and you agreed would work,
> however, another level in the tree, so subscribed groups could be
> categorized by the user, is a requested feature that should make it in
> post-1.0.

Cool.  I'll find a few minutes and search to see if there's a bug open on 
it and add my vote. :-)

> Yes, that's an issue.  Eventually the user categorization feature will
> resolve it, but meanwhile, one either has to get used to "thinking back
> and forth", or go to the trouble of multiple pan sessions, neither of
> which is optimal.

Agreed.

> It remembers the profile you set per group, but you have to set it
> first.  If you set it, and pan didn't crash so didn't save it, it should
> remember what you used last time and use the same profile the next time
> you post from the same group.  If it doesn't, there's a bug.  However,
> it may be that you just haven't set it for all groups yet, and that's
> what you are seeing the first time you try to post from a group that's
> not yet been set.

Yeah, it's not crashing, but it's picking up (for groups where it's 
unassigned) a setting that was just added for a different server (first 
one alphabetically as it turns out).  I may just have to script adding 
the setting for all groups into the profile XML file - I've got nearly 
200 groups in my list, so setting each one by hand would be very time 
consumint.

>> I also noticed that if you view "watched" (with the button), it shows
>> just the messages that are watched rather than the thread - because of
>> the way I work, this is less useful, because I need to be able to see
>> the whole thread.
> 
> You need to change what's shown.  You probably have it set to show only
> matching articles.  You want to show either the subthread or the entire
> thread.  Look in the menu under View/header-pane/show...  That
> functionality was in old-pan as well, so I'm surprised you didn't pickup
> on it.  Maybe you'd set it long ago and forgotten about it...

Nope, that was the first thing I did - in fact, I noticed that in new 
pan, the setting sticks for all groups rather than being set per-group - 
I like that.  The problem seems to be that I flag my messages as watched, 
but they're already read and apparently fail to match the filter.  I'll 
have to look more closely at it; I also have a fairly complex set of 
rules set up in old pan, so it could be something in my old rules that's 
causing the behaviour I expect that's not being carried over to new pan 
(sans rules, obviously).

Jim