	Can we have a key which has within it the rel/col fmt info to
	allow the switches in build_{rel,col} to be identical?

	should make a note if a change format requires a prev val and no
	key has been specified.

	push key or otherwise do non-extern 

	Should be able to handle corrupt history files better
		history file is a database.  Does this idea help?

	Reg expressions allowable in string change formats?

	Right to left parsing as option instead of always l-r.  It may
		be easier at times to specify that the useful info is
		located in the fifth from the right column rather than
		the eighth from the left.
	
	have metacharacter for end of line so we can have something that
		specifies "40-$"

	have option to not report on items already reported on.

	A problem I had that I eventually solved. I was trying to 
		include a space character in a string value of a change
		format.  I eventually hit on using something like "'
		'", using the tics within the double-quotes to preserve
		the white space in the intended string.  When the tics
		are omitted, the everything including and beyond the
		space was dropped. (In case you're interested, I was
		trying to watch the output of ps -ax to make sure that
		a particular process had not been swapped out by making
		sure there was a space in the status field where the W
		would normally go.)  The clue that led me to the
		solution was a remark in the man page about including
		white space in names. Maybe that could be clarified to
		include all strings?

	Have ability to mix column and relative output format.

	I can think of some other ways to make the control file specification
		more flexible, and which would make watcher more
		efficent.  One in particular involves a scheme for
		avoiding repeated invocations of relatively expensive
		commands such as ps by saving the output of a single
		invocation in a temporary file for use in several
		different pipelines.

	From mcooper%oberon.USC.EDU%ucbvax%unmvax.UNM.EDU@skat.usc.edu 
	The second major change I'm thinking of is a general facility
	for printing messages ala printf().  I'd like to be able to force
	the message format.  Here's a possible syntax:

	(ps -aux | /usr/ucb/tail +2)
	  { 'ps with no daemons' }
		 1-8user%s  9-14 pid%k  15-19 percentcpu%d  42-45 cputime%d:
			cputime 15%;
			cputime 0 20;
			print("User %s exceeds max cpu time (%d) with %d minutes.",
				user, cputime[2], cputime[0]).

	Where "user" is set to the contents of column 1-8, cputime[0] is set to
	the parsed value for "cputime", cputime[1] is set to the first argument
	to "cputime" right before the printf, and cputime[2] is set to the
	second argument to "cputime".

	So, what do you think?  Any suggestions?

		mike

