making configs is still at a pretty primitive level..

a config for vif or xgsh is currently an object file generated from
a "cc -c xxx.c" compile of static initialized data.

most of the config is an initialized C structure that is defined in
include/xgshconf.h for xgsh
include/vifconf.h  for vif

in the case of vif, there are optionally lex filters for the keyboard
and screen data streams on the pty connection.
- these are defined by simple lex(1) programs that only do
	"return(N);" as actions for recognized regular expressions where
	N is the index of the associated action in the vif_actc structure
	table

first - print out the include/xgshconf.h or include/vifconf.h file along
	with the sample configs (if you are not familiar with C structure
		initialization, get help)

hack away at the sample configs to figure out what the components do...

a few hints:

- don't wory about icons or helplibs at first, they can easily be added later

- for vif leave the lex filters out until the end
	(ie. don't set VC_KBFILTER or VC_PTYFILTER flags)

- most options are enabled by the bit flags or'd together in the xx_flags
	field of the structures

- test them by running the config from a tty window so that you get
	stderr messages about them

- the comments in the .h files is probably the best info. on what the
	fields are for

