pan-users
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Pan-users] Re: Messed up scorefile


From: Duncan
Subject: [Pan-users] Re: Messed up scorefile
Date: Sun, 28 Dec 2003 03:59:51 -0700
User-agent: Pan/0.14.2.90 (A Bouquet of Corpses)

Lenroc posted <address@hidden>, excerpted below,  on Sun, 28
Dec 2003 01:06:19 -0700:

> I've somehow messed up my scorefile. I see a plethora of identical errors
> in my status log (the error is "scorefile [...], line 1: unexpected line.
> (%BOS)"...), and, of course, my scores aren't working ;)
> 
> Can anyone please tell me what the first line of my scorefile _should_ be?

It doesn't have any specific required "first" line.    Lines starting with
"%" are comments, and I go thru and weed them out fairly regularly, to
keep the file of manageable size. Thus, the "first" line (of any effect)
should be the same format as any first uncommented line of any filter. 
More specifically, it should be the line that determines the group scope
of the first filter, thus, a regex enclosed by "[]" (without the quotes,
of course).

Since you are on Cox as well, perhaps yours will be similar to mine, since
my first filter pertains to anything posted to the Cox internal groups. 
Thus, my first line is:

[^cox\.]

..  Well, I SHOULD be specific and say that's my SECOND line, just in case
it matters..  <g>  The FIRST line of my file is a blank line, just a bare
line-feed char. (This being Linux, as with most *ix, that's the text line
termination sequence.  On MSWormOS, I assume that would be the char pair
carriage-return, line-feed, sequence.  Since the Mac port is BSD/X based,
I assume it is the same LF char, tho a standard Mac text file of course
uses the CR line termination instead, from what I've read.  Come to think
of it.. U run both platforms, don't U?  Maybe that's the issue, and you
may need to use a separate scorefile for each, or run some sort of
conversion script when switching platforms, or something.)

Please post your results, as I'm curious, now, just what's going on.

If either of those suggestions isn't it, perhaps something further down
the file is messed up so bad it isn't parsing the top of the file right,
either..  I've had that happen with file corruption, for instance, tho the
top of the file was right, and the corruption was later in the config
file, but it could be a royally screwed up filter, I suppose, as well.

Like I said, I'm interested in the results..

-- 
Duncan - List replies preferred.   No HTML msgs.
"They that can give up essential liberty to obtain a little
temporary safety, deserve neither liberty nor safety." --
Benjamin Franklin






reply via email to

[Prev in Thread] Current Thread [Next in Thread]