As we used to say back in the day, "Wow, psychedelic, man!" I don't normally top post, but today I make an exception because I want you to see what your reply looks like on my newly built pan (pulled from the git repo you very kindly made for us).
I didn't want you to conclude that I'm wacko before you finally get to my response w-a-a-a-y down at the bottom ;o) I have not edited the quoted text below in any way -- it's exactly as I see it in the Body Pane when reading your reply. I count four copies, if I'm counting correctly. The pan I built from the svn repo at gnome.org displays the same article correctly -- one quote from me and one reply from you. Any idea what's going astray here? On Tue, 23 Jun 2009 17:14:53 -0600, K. Haley wrote: > walt wrote: >> WFM too, thanks. If you're still bored, there is an obvious bug in how >> pan marks articles as read/unread after fetching new headers, but no >> one has so far been able to identify the buggy code. >> >> > Well, I looked through the code and couldn't find anything wrong. I did > a little cleanup on the newsrc code but I don't think that will fix your > problem. Since pan uses the newsrc files to track read articles and I'm > not seeing the problem, the only thing I can think of is that the > article numbers are changing on the server or perhaps out of sync round > robin servers. > > > walt wrote: >> WFM too, thanks. If you're still bored, there is an obvious bug in how >> pan marks articles as read/unread after fetching new headers, but no >> one has so far been able to identify the buggy code. >> >> > Well, I looked through the code and couldn't find anything wrong. I did > a little cleanup on the newsrc code but I don't think that will fix your > problem. Since pan uses the newsrc files to track read articles and I'm > not seeing the problem, the only thing I can think of is that the > article numbers are changing on the server or perhaps out of sync round > robin servers. > > > walt wrote: >> WFM too, thanks. If you're still bored, there is an obvious bug in how >> pan marks articles as read/unread after fetching new headers, but no >> one has so far been able to identify the buggy code. >> >> > Well, I looked through the code and couldn't find anything wrong. I did > a little cleanup on the newsrc code but I don't think that will fix your > problem. Since pan uses the newsrc files to track read articles and I'm > not seeing the problem, the only thing I can think of is that the > article numbers are changing on the server or perhaps out of sync round > robin servers. > > > walt wrote: >> WFM too, thanks. If you're still bored, there is an obvious bug in how >> pan marks articles as read/unread after fetching new headers, but no >> one has so far been able to identify the buggy code. >> >> > Well, I looked through the code and couldn't find anything wrong. I did > a little cleanup on the newsrc code but I don't think that will fix your > problem. Since pan uses the newsrc files to track read articles and I'm > not seeing the problem, the only thing I can think of is that the > article numbers are changing on the server or perhaps out of sync round > robin servers. _______________________________________________ Pan-users mailing list Pan-users@nongnu.org http://lists.nongnu.org/mailman/listinfo/pan-users
