Chris Koenigsberg <ckk@uchicago.edu> said:
> Or maybe the list config file could be split into two files, into the "novice
> or "basic" part and the "expert" or "advanced" part..... then you would have
> set of new commands to deal with the advanced part, so the traditional
> "config/newconfig" would only deal with the novice/basic part.
Sorting the config items would be a very good step in the right direction.
I bet that anything on the config file would be comprehensible to humans if it
was just written by a person who was ignorant enough, (with help of course) and
not afraid to explain things from a novice point of view.
For instance, the config file begins with an enormous road block:
# There is no way to escape the # character. The file
# uses either a key = value for simple (i.e. a single) values, or uses
# a here document
...is this specialist information for a perl hacker designing the system? Then
it should be in a context sensitive place, deep down in the config file after
the easily understood commands. If it is an attempt to explain the basic syntax
of the config file then it is just plain nutty, and should be translated by a
novice user. I wondered what the erratic "<<end" statements meant that were
scattered throughout the config file, but his beginning section doesn't explain
it very clearly.
Best Regards,
David Briars
-----------------------------------------------------------------------
U.S. McLibel Support Campaign Press Office
PO Box 62 Phone/Fax 802-586-9628
Craftsbury VT 05826-0062 Email dbriars@world.std.com
|
|
