WrenGROGGS .grogprefs format
WrenGROGG's primary way of determining what your preferences are is by
reading your .groggprefs file, which is by default a file called
.groggprefs in your home directory (~/.groggprefs).
Unless you want to do unusual things (like having two servers configured),
you should never need to touch your .groggprefs file yourself - it will
not be needed whilst you have guest access only (assuming you're using
your site's default server), and will
be created the first time you run the
grogprofile command (typically
to set your shared secret).
However, in case you want to play (or parse) , the format of the file
is as follows.
Applications should ignore any unrecognised keys they come across.
- A .groggprefs file consists of a series of lines, terminated by a
newline character (ASCII 10).
- A word is a non-empty sequence of characters, none of which may be
space (ASCII 32) or linefeed (ASCII 10).
- A line consists of a sequence of space-separated words. There need
be no spaces between the end of the last word and the terminating
- The first character of the first word on a line must be the first
character on the line.
- The first word on a line is known as the 'key'. Each subsequent
word is known as an 'argument', and the 'argument list' is an
ordered list containing all the arguments in the order in which
they appear on the line.
Application-specific configuration should be done using keys with names
beginning '<appname>_'. This reduces the possibility of clashes.
The standard keys are :
And WrenGROGGS defines the application-specific key :
- server <hostname> - use server <hostname>.
- port <portnumber> - use port atoi(<portnumber>)
(where atoi() is defined as in standard C).
- user <userid> - user id should be <userid>.
- level <level> - desired access level is atoi(<level>).
- grogname <grogname> - desired grogname.
- wrengroggs_options <options> - prepend <options>
to the command line.
Back to WrenGROGGS configuration, or to the
WrenGROGGS home page.
Last modified: Mon Oct 9 11:32:51 1995
Richard Watts <Richard.Watts@cl.cam.ac.uk>