Anyone else having problems with Sourceforge CVS? I hope it's
just a transient thing and I tried on the wrong night.
Justin Mason writes:
(Lots of useful answers -- thanks! I'll make a to-do list of
some of these things and try to work on some of them.)
> Akkana Peck writes:
> > 4. What do -site and -sites expect? I've tried formats like
> > the_register, tech/the_register, tech/the_register.site,
> > site_samples/tech/the_register.site, and none of them work. It
>
> Yeah, the path should work! I've generally had no problems with
> it. Here's an example:
>
> cd /path/to/sitescoopercvsdir
> ./sitescooper.pl -html -site site_samples/tech/risks.site
The first line is the missing piece. The man page didn't mention
having to cd anywhere first. Since sitescooper already knows where
to look for site_samples, shouldn't we spare the user from needing
to figure out where site_samples/.. is?
> > 7. Is there a way to update site_samples.txt, for when new site
> > files are added? I couldn't find that anywhere in the docs.
>
> No, unfortunately it's only built if it doesn't already exist.
Corrolary to that question: site_choices.txt has three lines:
long name (with checkbox), url, and filename. I guess the long
name line is needed because that's where the checkbox goes, and
the filename is surely needed, but is the URL used for anything?
It's likely to be wrong, if the site files keep being updated
and site_choices.txt never is. Can I just remove that line in
each entry? (I guess I should try it and see. :-) If not,
would this be a useful change?
Corrolary 2: I guess it's safe, then (and probably desirable, less
parsing time as well as easier maintenance) to remove lines from
site_choices.txt for any site I'm not actually scooping.
> I think they can be already. -- see the "CommandLine:" setting.
That's great! Sounds ideal.
But how does it work? sitescooper.cf doesn't mention it, nor does
anything in doc/*; comments in the code say it's for mac, but it
looks like it should be straightforward enough.
I took a guess and put in sitescooper.cf:
CommandLine: -mplucker -debug -filename "Day_Site" -prctitle "Day Site"
and that did *something*, because when I tried to test it with
sitescooper -site site_samples/blah/blah.site it spewed tons of
errors, and failed to get anything.
Aha, I see it in the code now: the quotes and spaces don't work,
because Main.pm splits at spaces before passing to parse_commandLine.
Changing to -prctitle Day_Site seems to have fixed it. I can live
with that (though it's too bad since that's the string that actually
gets displayed as a title), but it's surprising in a feature aimed
primarily at mac users (who tend to care much more than anyone else
about wanting to see spaces between words).
> > 9. Do the iSilo users of Sitescooper still outnumber the Plucker
[ ... ]
> I think, though, that perhaps there should be *no* default?
Good point -- that's really better than assuming either one.
What should it do in that case? Complain and exit, or prompt the user?
If it prompts, should it remember the setting?
...Akkana
_______________________________________________
Sitescooper-talk mailing list
[EMAIL PROTECTED]
http://sitescooper.org/mailman/listinfo/sitescooper-talk
