IndentMaster was written out of frustration with the standard unix utility indent and all its options.  I found myself spending far too much time (tm) messing with all the options and wondering what was going to happen next time I hit <command>-I from edit.

So here you have (almost) all the options presented to you in all their glory.  The ones left out are the ones that don't make much sense for this app (troff formatting, stdin to stdout processing, etc).

A backup of the previous .indent.pro is created called .indent.pro.bak

Hopefully you will use this app once or twice and never have to think about it again (until you upgrade to that HP and forget to bring along your .indent.pro file...).  It would please me greatly for NeXT to pay me a tiny sum of money and distribute this APP; that way when I get an account on a 'SNAKE' running OpenStep at my next job :-) I'll be able to fire up this APP and fix my damn .indent.pro file so it doesn't nestle else's with preceding }'s.

By:	;about.Kurt.rtf;Kurt Werle;¬	Kurt Werle

Bugs:	(really, 'bugs')

	Indent is less than perfect.  Check out the man page.
	
	I use temporary files because I didn't want to mess with pipes (popen), or whatever it is that NeXTSTeP would have me use.  The temporary files are called .indent.code.c, and .indent.code.c.bak.  Both these files are created in the .indent.pro directory.  In theory I delete both these files when I'm done with them.  I hope you don't name your code files .indent.pro.c!!
	
	I always write out all options to the .indent.pro file, even if they match the defaults.  Cope.
	
	I couldn't figure out how to make the 'filename extention' for this app '.indent.pro', so it's just '.pro' (is this possible?).  Although I don't know of any other '.pro' files, I'm sure they exist somewhere.  Besides, what if I wanted to write a '.cshrc' editor.  how do I make that app the default one for all '.cshrc' files???