[agd-cvs] server README,1.3,1.4

[Peep P. <so...@us...>]

Update of /cvsroot/agd/server
In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv4043

Modified Files:
	README 
Log Message:
Formatted for a 80-character display.

Index: README
===================================================================
RCS file: /cvsroot/agd/server/README,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -d -r1.3 -r1.4
--- README	16 Mar 2004 20:17:32 -0000	1.3
+++ README	20 Mar 2004 16:04:20 -0000	1.4
@@ -5,49 +5,53 @@
 	Peep Pullerits <so...@es...>
 --------------------------------------
 
-	This is a small LPMUD driver, intended to run graphical MUDs with Sierra AGI-like graphics.
-	Currently no graphics are implemented, as even the LPC compiler/interpreter is a
-	work-in-progress.
-	It can act as a basic chat server with the default lib.
-	If you write anything in LPC, I would be glad if you send it to me.
+This is a small LPMUD driver, intended to run graphical MUDs
+with Sierra AGI-like graphics.
+Currently no graphics are implemented, as even the LPC
+compiler/interpreter is a work-in-progress.
+It can act as a basic chat server with the default lib.
+If you write anything in LPC, I would be glad if you send it to me.
  
- Installing.
-	Follow the instructions in the INSTALL file that came with this package.
+1. Installing.
+Follow the instructions in the INSTALL file that came with
+this package.
 
- Running.
-	AGD comes with a default configuration in /usr/share/agd/options, and
-	it will use this file if it isn't given a parameter. This, however,
-	expects you to have done 'make install', but probably not everyone
-	who wants to run this driver will have root access to their machine.
-	So, you can copy the binary, options file and library to your
-	home directory and provide a configuration file path as an argument
-	each time you run the driver (using a shell script, for example).
+2. Running.
+AGD comes with a default configuration in /usr/share/agd/options,
+and it will use this file if it isn't given a parameter.
+This, however, expects you to have done 'make install', but
+probably not everyone who wants to run this driver will have
+root access to their machine.
+So, you can copy the binary, options file and library to your
+home directory and provide a configuration file path as an argument
+each time you run the driver (using a shell script, for example).
 	
-	So, in short:
-	  If you have root access, do 'make install' and run agd
-	with 'agd'. AGD will use /usr/share/agd/options for the configuration.
-	  If you don't have root access, run agd with './agd options',
-	assuming the 'agd' binary and the 'options' file are in the same directory.
+So, in short:
+If you have root access, do 'make install' and run agd
+with 'agd'. AGD will use /usr/share/agd/options for the configuration.
+If you don't have root access, run agd with './agd options',
+assuming the 'agd' binary and the 'options' file are in the
+same directory.
 
-	  There might be a 'make userinstall' target in the future that will do this
-	automatically.
+There might be a 'make userinstall' target in the future that
+will do this automatically.
 
-	You might also want to separate stderr and stdout, by redirecting one or both
-	of them to a file, because some lines don't have newlines, so stdout and stderr
-	could get mixed up. Like this:
-	'./agd >agd.out 2>agd.err'
-	Or write a shell script to do it.
+You might also want to separate stderr and stdout, by redirecting
+one or both of them to a file, because some lines don't have
+newlines, so stdout and stderr could get mixed up. Like this:
+  './agd >agd.out 2>agd.err'
+Or write a shell script to do it.
 
- Bugs.
-	This is an alpha release. As such, it most probably is infestated with bugs.
-	Please do try to break it, and report everything you find.
+3. Bugs.
+This is an alpha release. As such, it most probably is
+full of bugs.
+Please do try to break it, and report everything you find.
 	
-	If the driver crashes with a segmentation fault, do this:
-	$ gdb agd
-	(gdb) run
-	<reproduce the bug>
-	Program received signal SIGSEGV, Segmentation fault.
-	(gdb) backtrace
-
-	And include the output in your bug report.
+If the driver crashes with a segmentation fault, do this:
+  $ gdb agd
+  (gdb) run
+  <reproduce the bug>
+  Program received signal SIGSEGV, Segmentation fault.
+  (gdb) backtrace
 
+  And include the output in your bug report.