#CENSORSHIP

etc/COOKIES

@@ -0,0 +1,157 @@
+[Someone sent this in from California, and we decided to extend
+our campaign against information hoarding to recipes as well
+as software.  (Recipes are the closest thing, not involving computers,
+to software.)
+
+The story appears to be a myth, according to the Chicago Tribune,
+which says that Mrs Fields Cookies hoards the information completely.
+Therefore, this recipe can be thought of as a compatible replacement.
+We have reports that the cookies it makes are pretty good.]
+
+Someone at PG&E called the Mrs. Fields Cookie office
+and requested the recipe for her cookies. They asked
+her for her charge card number, and she gave it to them
+thinking the cost would be $15 to $25.  It turned out
+to be $200!
+
+Therefore, this person is giving the recipe to anyone 
+and everyone she knows (and doesn't know) so that 
+someone can get use of her $200.  Anyway, just keep
+passing it on.
+
+Cream together:		2 cups butter
+			2 cups sugar
+			2 cups brown sugar
+
+Add:			4 eggs
+			2 tsp. vanilla
+
+Mis together in
+separate bowl:		4 cups flour 
+			5 cups oatmeal (put small
+ amounts of oatmeal in blender until it turns to
+ powder.  Measure out 5 cups of oatmeal and only
+ "powderize" that, NOT 5 cups "powderized" oatmeal)
+
+			1 tsp salt
+			2 tsp baking powder
+			2 tsp baking soda
+
+Mix:			All of the above
+
+Add:			24 oz. bag of chocolate chips and
+			1 finely grated 8 oz Hershey bar (plain)
+
+Add:			3 cups chopped nuts (any kind)
+
+Bake on greased cookie sheet (make golf ball sized balls) and
+bake about two inches apart.  Bake at 350 degrees for 8 - 10 
+minutes. DO NOT OVERBAKE.  Makes 112.
+
+From: ucdavis!lll-lcc!hplabs!parcvax!bane@ucbvax.berkeley.edu (John R. Bane)
+Subject: Re: free cookie foundation?
+
+Hi! I "stole" your very expensive cookie recipe off the net. If you
+want to send me your SnailMail address, I'll be glad to send you a
+dollar (I would like to suggest this to the net, but I think there is
+some netiquette rule against asking for money - or is that only money
+for oneself?) to help defray the cost (it's not much, but if EVERYone
+who took the recipe sent you a dollar, it would help). 
+
+Here also is another cookie recipe which I'm very fond of. 
+
+Makes 6-8 dozen
+Bake at 375 degrees for ~10 min.
+
+Cream together: 
+
+1 cup shortening (I use Weight Watcher's Reduced Calorie Margarine!)
+1/4 cup peanut butter (I recommend the non-sugared kind)
+1/2 cup sugar
+1/2 cup brown sugar
+2 eggs
+1 teaspoon vanilla
+
+Add:
+
+1/2 cup flour
+1 teaspoon soda
+1/2 teaspoon salt
+2 cups rolled oats (I use the 5-min variety)
+1-2 cups chocolate chips (I use 2 cups semi-sweet - ummmm!)
+1 cup nuts (I use pecan pieces - don't get them crushed, or the extra
+	    oil will make greasy cookies)
+1 cup shredded or flaked coconut
+
+(The nuts were listed as optional and I added the coconut myself, but
+I really love them there! You could also add things like m&m's, or
+raisins (I don't care for raisins in cookies, but you might).  I've
+always wanted to try banana chips.)
+
+Mix well. Drop by teaspoonfuls on greased cookie sheet (I use pam).
+Bake at 375 degrees for approx. 10 min.
+
+My aunt found this recipe in an Amish book called something like
+"Eating Well When The Whole World Is Starving," and although I thought
+a cookie recipe was a bit odd for a book like that, they are about the
+healthiest a cookie is ever likely to get.
+
+They are also very easy to make (no blending, sifting, rolling, etc.)
+and extremely delicious.  I get rave reviews and recipe requests whenever
+I make them.
+
+				- rene
+
+Chocolate Chip Cookies - Glamorous, crunchy, rich with chocolate bits & nuts.
+
+Also known as "Toll House" Cookies ... from Kenneth and Ruth Wakefield's 
+charming New England Toll House on the outskirts of Whitman, Massachusetts.
+These cookies were first introduced to American homemakers in 1939 through
+our series of radio talks on "Famous Foods From Famous Eating Places."
+
+Mix Thoroughly :
+	2/3 cup soft shortening ( part butter )
+	1/2 cup granulated sugar
+	1/2 cup brown sugar ( packed )
+	1 egg
+	1 tsp vanilla
+
+Sift together and stir in :
+	1-1/2 cups sifted flour (*)
+	1/2 tsp soda
+	1/2 tsp salt
+
+Stir in :
+	1/2 cup cut-up nuts
+	6 oz package of semi-sweet chocolate pieces ( about 1-1/4 cups )
+
+
+(*) for a softer, more rounded cookie, use 1-3/4 cups sifted flour.
+
+
+Drop rounded teaspoonfuls about 2" apart on ungreased baking sheet. Bake until
+delicately browned ... cookies should still be soft. Cool slightly before you
+remove them from the baking sheet.
+
+Temperature:		375 F. ( modern oven )
+Time:			bake 8 - 10 minutes
+Amount:			4 - 5 dozen 2" cookies
+
+
+=====
+
+Personal comments :
+
+I find it tastes better with a mixture of shortening and butter, as they say.
+
+You don't need << all >> of that sugar, and it can be whatever color you want.
+
+The nuts are optional. Feel free to play with the recipe. I put oatmeal in it,
+reducing flour accordingly, and sometimes cinnamon.
+
+I also find it useful to grease the cookie sheets.
+
+I think I'm going to go bake some now ...
+
+-- richard
+

etc/celibacy.1

@@ -0,0 +1,12 @@
+CELIBACY(1)              UNIX Programmer's Manual           CELIBACY(1)
+
+
+
+NAME
+     celibacy - don't have sex
+
+SYNOPSIS
+     celibacy
+
+DESCRIPTION
+     Does nothing worth mentioning.

etc/condom.1

@@ -0,0 +1,148 @@
+CONDOM(1)	      EUNUCH Programmer's Manual		CONDOM(1)
+
+
+
+NAME
+	condom - Protection against viruses and prevention of child 
+		 processes
+
+SYNOPSIS
+	condom [options] [processid]
+
+DESCRIPTION
+	_condom_ provides protection against System Transmitted
+Viruses (STVs) that may invade your system.  Although the spread of
+such viruses across a network can only be abated by aware and cautious
+users, _condom_ is the only highly-effective means of preventing
+viruses from entering your system (see celibacy(1)).  Any data passed
+to _condom_ by the protected process will be blocked, as specified by
+the value of the -s option (see OPTIONS below).  _condom_ is known to
+defend against the following viruses and other malicious
+afflictions...
+
+	o AIDS
+	o Herpes Simplex (genital varieties)
+	o Syphilis
+	o Crabs
+	o Genital warts
+	o Gonorrhea
+	o Chlamydia
+	o Michelangelo
+	o Jerusalem
+
+	When used alone or in conjunction with pill(1), sponge(1),
+foam(1), and/or setiud(3), _condom_ also prevents the conception of a
+child process.  If invoked from within a synchronous process, _condom_
+has, by default, an 80% chance of preventing the external processes
+from becoming parent processes (see the -s option below).  When other
+process contraceptives are used, the chance of preventing a child
+process from being forked becomes much greater.  See pill(1),
+sponge(1), foam(1), and setiud(3) for more information.
+	If no options are given, the current user's login process (as
+determined by the environment variable USER) is protected with a
+Trojan rough-cut latex condom without a reservoir tip.  The optional
+'processid' argument is an integer specifying the process to protect.
+	NOTE: _condom_ may only be used with a hard disk.  _condom_
+will terminate abnormally with exit code -1 if used with a floppy
+disk (see DIAGNOSTICS below).
+
+OPTIONS
+     The following options may be given to _condom_...
+
+	-b BRAND	BRANDs are as follows...
+
+			trojan (default)
+			ramses
+			sheik
+			goldcoin
+			fourex
+
+	-m MATERIAL	The valid MATERIALs are...
+
+			latex (default)
+			saranwrap
+			membrane -- WARNING!  The membrane option is _not_
+			endorsed by the System Administrator General as an 
+			effective barrier against certain viruses.  It is 
+			supported only for the sake of tradition.
+
+	-f FLAVOR	The following FLAVORs are currently supported...
+
+			plain (default)
+			apple
+			banana
+			cherry
+			cinnamon
+			licorice
+			orange
+			peppermint
+			raspberry
+			spearmint
+			strawberry
+
+	-r		Toggle reservoir tip (default is no reservoir tip)
+
+	-s STRENGTH	STRENGTH is an integer between 20 and 100 specifying
+			the resilience of _condom_ against data passed to
+			_condom_ by the protected process.  Using a larger
+			value of STRENGTH increases _condom_'s protective
+			abilities, but also reduces interprocess communication.
+			A smaller value of STRENGTH increases interprocess
+			communication, but also increases the likelihood of a
+			security breach.  An extremely vigorous process or
+			one passing an enormous amount of data to _condom_ 
+			will increase the chance of _condom_'s failure.  The
+			default STRENGTH is 80%.
+
+	-t TEXTURE	Valid TEXTUREs are...
+
+			rough (default)
+			ribbed
+			bumps
+			lubricated (provides smoother interaction between 
+			            processes)
+
+	WARNING: The use of an external application to _condom_ in
+order to reduce friction between processes has been proven in
+benchmark tests to decrease _condom_'s strength factor!  If execution
+speed is important to your process, use the '-t lubricated' option.
+
+DIAGNOSTICS
+	_condom_ terminates with one of the following exit codes...
+
+	-1	An attempt was made to use _condom_ on a floppy disk.
+
+	 0	_condom_ exited successfully (no data was passed to
+		the synchronous process).
+
+	 1	_condom_ failed and data was allowed through.  The
+		danger of transmission of an STV or the forking of a child 
+		process is inversely proportional to the number of other 
+		protections employed and is directly proportional to 
+		the ages of the processes involved.
+
+BUGS
+	_condom_ is NOT 100% effective at preventing a child process
+from being forked or at deterring the invasion of a virus (although
+the System Administrator General has deemed that _condom_ is the most
+effective means of preventing the spread of system transmitted
+viruses).  See celibacy(1) for information on a 100% effective program
+for preventing these problems.
+	Remember... the use of sex(1) and other related routines
+should only occur between mature, consenting processes.  If you must
+use sex(1), please employ _condom_ to protect your process and your
+synchronous process.  If we are all responsible, we can stop the
+spread of STVs.
+
+AUTHORS and HISTORY
+	The original version of _condom_ was released in Roman times
+and was only marginally effective.  With the advent of modern
+technology, _condom_ now supports many more options and is much more
+effective.
+	The current release of _condom_ was written by Ken Maupin at
+the University of Washington (maupin@cs.washington.edu) and was last
+updated on 10/7/92.
+
+SEE ALSO
+	celibacy(1), sex(1), pill(1), sponge(1), foam(1), and
+setiud(3)

etc/emacs.1

@@ -0,0 +1,495 @@
+.TH EMACS 1 "1995 December 7"
+.UC 4
+.SH NAME
+emacs \- GNU project Emacs
+.SH SYNOPSIS
+.B emacs
+[
+.I command-line switches
+] [
+.I files ...
+]
+.br
+.SH DESCRIPTION
+.I GNU Emacs
+is a version of 
+.I Emacs,
+written by the author of the original (PDP-10) 
+.I Emacs,
+Richard Stallman.
+.br
+The primary documentation of GNU Emacs is in the GNU Emacs Manual,
+which you can read on line using Info, a subsystem of Emacs.  Please
+look there for complete and up-to-date documentation.  This man page
+is updated only when someone volunteers to do so; the Emacs
+maintainers' priority goal is to minimize the amount of time this man
+page takes away from other more useful projects.
+.br
+The user functionality of GNU Emacs encompasses
+everything other 
+.I Emacs 
+editors do, and it is easily extensible since its
+editing commands are written in Lisp.
+.PP
+.I Emacs
+has an extensive interactive help facility,
+but the facility assumes that you know how to manipulate
+.I Emacs
+windows and buffers.
+CTRL-h (backspace
+or CTRL-h) enters the Help facility.  Help Tutorial (CTRL-h t)
+requests an interactive tutorial which can teach beginners the fundamentals
+of 
+.I Emacs 
+in a few minutes.
+Help Apropos (CTRL-h a) helps you
+find a command given its functionality, Help Character (CTRL-h c)
+describes a given character's effect, and Help Function (CTRL-h f)
+describes a given Lisp function specified by name.
+.PP
+.I Emacs's
+Undo can undo several steps of modification to your buffers, so it is
+easy to recover from editing mistakes.
+.PP
+.I GNU Emacs's
+many special packages handle mail reading (RMail) and sending (Mail),
+outline editing (Outline), compiling (Compile), running subshells
+within
+.I Emacs
+windows (Shell), running a Lisp read-eval-print loop
+(Lisp-Interaction-Mode), and automated psychotherapy (Doctor).
+.PP
+There is an extensive reference manual, but
+users of other Emacses
+should have little trouble adapting even
+without a copy.  Users new to
+.I Emacs
+will be able
+to use basic features fairly rapidly by studying the tutorial and
+using the self-documentation features.
+.PP
+.SM Emacs Options
+.PP
+The following options are of general interest:
+.TP 8
+.I file
+Edit
+.I file.
+.TP
+.BI \+ number
+Go to the line specified by
+.I number
+(do not insert a space between the "+" sign and
+the number).
+.TP
+.B \-q
+Do not load an init file.
+.TP
+.BI \-u " user"
+Load
+.I user's
+init file.
+.TP
+.BI \-t " file"
+Use specified
+.I file
+as the terminal instead of using stdin/stdout.
+This must be the first argument specified in the command line.
+.PP
+The following options are lisp-oriented
+(these options are processed in the order encountered):
+.TP 8
+.BI \-f " function"
+Execute the lisp function
+.I function.
+.TP
+.BI \-l " file"
+Load the lisp code in the file
+.I file.
+.PP
+The following options are useful when running
+.I Emacs
+as a batch editor:
+.TP 8
+.BI \-batch
+Edit in batch mode.  The editor will send messages to stderr.  This
+option must be the first in the argument list.  You must use -l and -f
+options to specify files to execute and functions to call.
+.TP
+.B \-kill
+Exit 
+.I Emacs 
+while in batch mode.
+.\" START DELETING HERE IF YOU'RE NOT USING X
+.PP
+.SM Using Emacs with X
+.PP
+.I Emacs
+has been tailored to work well with the X window system.
+If you run
+.I Emacs
+from under X windows, it will create its own X window to
+display in.  You will probably want to start the editor
+as a background process
+so that you can continue using your original window.
+.PP
+.I Emacs
+can be started with the following X switches:
+.TP 8
+.BI \-name " name"
+Specifies the name which should be assigned to the initial
+.I Emacs
+window.  This controls looking up X resources as well as the window title.
+.TP 8
+.BI \-title " name"
+Specifies the title for the initial X window.
+.TP 8
+.B \-r
+Display the
+.I Emacs
+window in reverse video.
+.TP
+.B \-i
+Use the "kitchen sink" bitmap icon when iconifying the
+.I Emacs
+window.
+.TP
+.BI \-font " font, " \-fn " font"
+Set the
+.I Emacs
+window's font to that specified by
+.I font.
+You will find the various
+.I X
+fonts in the
+.I /usr/lib/X11/fonts
+directory.
+Note that
+.I Emacs
+will only accept fixed width fonts.
+Under the X11 Release 4 font-naming conventions, any font with the
+value "m" or "c" in the eleventh field of the font name is a fixed
+width font.  Furthermore, fonts whose name are of the form
+.IR width x height
+are generally fixed width, as is the font
+.IR fixed .
+See
+.IR xlsfonts (1)
+for more information.
+
+When you specify a font, be sure to put a space between the
+switch and the font name.
+.TP
+.BI \-b " pixels"
+Set the
+.I Emacs
+window's border width to the number of pixels specified by
+.I pixels.
+Defaults to one pixel on each side of the window.
+.TP
+.BI \-ib " pixels"
+Set the window's internal border width to the number of pixels specified
+by 
+.I pixels.
+Defaults to one pixel of padding on each side of the window.
+.PP
+.TP 8
+.BI \-geometry " geometry"
+Set the
+.I Emacs
+window's width, height, and position as specified.  The geometry
+specification is in the standard X format; see
+.IR X (1)
+for more information.
+The width and height are specified in characters; the default is 80 by
+24.
+.PP
+.TP 8
+.BI \-fg " color"
+On color displays, sets the color of the text.
+
+See the file
+.I /usr/lib/X11/rgb.txt
+for a list of valid
+color names.
+.TP
+.BI \-bg " color"
+On color displays,
+sets the color of the window's background.
+.TP
+.BI \-bd " color"
+On color displays,
+sets the color of the window's border.
+.TP
+.BI \-cr " color"
+On color displays,
+sets the color of the window's text cursor.
+.TP
+.BI \-ms " color"
+On color displays,
+sets the color of the window's mouse cursor.
+.TP
+.BI \-d " displayname, " \-display " displayname"
+Create the
+.I Emacs
+window on the display specified by
+.IR displayname .
+Must be the first option specified in the command line.
+.TP
+.B \-nw
+Tells
+.I Emacs
+not to use its special interface to X.  If you use this
+switch when invoking
+.I Emacs
+from an
+.IR xterm (1)
+window, display is done in that window.
+This must be the first option specified in the command line.
+.PP
+You can set
+.I X
+default values for your
+.I Emacs
+windows in your
+.I \.Xresources
+file (see
+.IR xrdb (1)).
+Use the following format:
+.IP
+emacs.keyword:value
+.PP
+where
+.I value
+specifies the default value of
+.I keyword.
+.I Emacs
+lets you set default values for the following keywords:
+.TP 8
+.B font (\fPclass\fB Font)
+Sets the window's text font.
+.TP
+.B reverseVideo (\fPclass\fB ReverseVideo)
+If
+.I reverseVideo's
+value is set to
+.I on,
+the window will be displayed in reverse video.
+.TP
+.B bitmapIcon (\fPclass\fB BitmapIcon)
+If
+.I bitmapIcon's
+value is set to
+.I on,
+the window will iconify into the "kitchen sink."
+.TP
+.B borderWidth (\fPclass\fB BorderWidth)
+Sets the window's border width in pixels.
+.TP
+.B internalBorder (\fPclass\fB BorderWidth)
+Sets the window's internal border width in pixels.
+.TP
+.B foreground (\fPclass\fB Foreground)
+For color displays,
+sets the window's text color.
+.TP
+.B background (\fPclass\fB Background)
+For color displays,
+sets the window's background color.
+.TP
+.B borderColor (\fPclass\fB BorderColor)
+For color displays,
+sets the color of the window's border.
+.TP
+.B cursorColor (\fPclass\fB Foreground)
+For color displays,
+sets the color of the window's text cursor.
+.TP
+.B pointerColor (\fPclass\fB Foreground)
+For color displays,
+sets the color of the window's mouse cursor.
+.TP
+.B geometry (\fPclass\fB Geometry)
+Sets the geometry of the
+.I Emacs
+window (as described above).
+.TP
+.B title (\fPclass\fB Title)
+Sets the title of the
+.I Emacs
+window.
+.TP
+.B iconName (\fPclass\fB Title)
+Sets the icon name for the
+.I Emacs
+window icon.
+.PP
+If you try to set color values while using a black and white display,
+the window's characteristics will default as follows:
+the foreground color will be set to black,
+the background color will be set to white,
+the border color will be set to grey,
+and the text and mouse cursors will be set to black.
+.PP
+.SM Using the Mouse 
+.PP
+The following lists the mouse button bindings for the
+.I Emacs
+window under X11.
+
+.in +\w'CTRL-SHIFT-middle'u+4n
+.ta \w'CTRL-SHIFT-middle'u+4n
+.ti -\w'CTRL-SHIFT-middle'u+4n
+MOUSE BUTTON	FUNCTION
+.br
+.ti -\w'CTRL-SHIFT-middle'u+4n
+left	Set point.
+.br
+.ti -\w'CTRL-SHIFT-middle'u+4n
+middle	Paste text.
+.br
+.ti -\w'CTRL-SHIFT-middle'u+4n
+right	Cut text into X cut buffer.
+.br
+.ti -\w'CTRL-SHIFT-middle'u+4n
+SHIFT-middle	Cut text into X cut buffer.
+.br
+.ti -\w'CTRL-SHIFT-middle'u+4n
+SHIFT-right	Paste text.
+.br
+.ti -\w'CTRL-SHIFT-middle'u+4n
+CTRL-middle	Cut text into X cut buffer and kill it.
+.br
+.ti -\w'CTRL-SHIFT-middle'u+4n
+CTRL-right	Select this window, then split it into 
+two windows.  Same as typing CTRL-x 2.
+.\" START DELETING HERE IF YOU'RE NOT USING X MENUS
+.br
+.ti -\w'CTRL-SHIFT-middle'u+4n
+CTRL-SHIFT-left	X buffer menu--hold the buttons and keys
+down, wait for menu to appear, select 
+buffer, and release.  Move mouse out of
+menu and release to cancel.
+.br
+.ti -\w'CTRL-SHIFT-middle'u+4n
+CTRL-SHIFT-middle	X help menu--pop up index card menu for
+Emacs help.
+.\" STOP DELETING HERE IF YOU'RE NOT USING X MENUS
+.br
+.ti -\w'CTRL-SHIFT-middle'u+4n
+CTRL-SHIFT-right	Select window with mouse, and delete all
+other windows.  Same as typing CTRL-x 1.
+.\" STOP DELETING HERE IF YOU'RE NOT USING X
+.PP
+.SH MANUALS
+You can order printed copies of the GNU Emacs Manual from the Free
+Software Foundation, which develops GNU software.  See the file ORDERS
+for ordering information.
+.br
+Your local Emacs maintainer might also have copies available.  As
+with all software and publications from FSF, everyone is permitted to
+make and distribute copies of the Emacs manual.  The TeX source to the
+manual is also included in the Emacs source distribution.
+.PP
+.SH FILES
+/usr/local/info - files for the Info documentation browser
+(a subsystem of Emacs) to refer to.  Currently not much of Unix
+is documented here, but the complete text of the Emacs reference
+manual is included in a convenient tree structured form.
+
+/usr/local/share/emacs/$VERSION/src - C source files and object files
+
+/usr/local/share/emacs/$VERSION/lisp - Lisp source files and compiled files
+that define most editing commands.  Some are preloaded;
+others are autoloaded from this directory when used.
+  
+/usr/local/share/emacs/$VERSION/etc - various programs that are used with
+GNU Emacs, and some files of information.
+
+/usr/local/share/emacs/$VERSION/etc/DOC.* - contains the documentation
+strings for the Lisp primitives and preloaded Lisp functions
+of GNU Emacs.  They are stored here to reduce the size of
+Emacs proper.
+
+/usr/local/share/emacs/$VERSION/etc/OTHER.EMACSES discusses GNU Emacs
+vs. other versions of Emacs.
+.br
+/usr/local/share/emacs/$VERSION/etc/SERVICE lists people offering
+various services to assist users of GNU Emacs, including education,
+troubleshooting, porting and customization.
+.br
+These files also have information useful to anyone wishing to write
+programs in the Emacs Lisp extension language, which has not yet been fully
+documented.
+
+/usr/local/com/emacs/lock - holds lock files that are made for all
+files being modified in Emacs, to prevent simultaneous modification
+of one file by two users.
+
+.\" START DELETING HERE IF YOU'RE NOT USING X
+/usr/lib/X11/rgb.txt - list of valid X color names.
+.\" STOP DELETING HERE IF YOU'RE NOT USING X
+.PP
+.SH BUGS
+There is a mailing list, bug-gnu-emacs@prep.ai.mit.edu on the internet
+(ucbvax!prep.ai.mit.edu!bug-gnu-emacs on UUCPnet), for reporting Emacs
+bugs and fixes.  But before reporting something as a bug, please try
+to be sure that it really is a bug, not a misunderstanding or a
+deliberate feature.  We ask you to read the section ``Reporting Emacs
+Bugs'' near the end of the reference manual (or Info system) for hints
+on how and when to report bugs.  Also, include the version number of
+the Emacs you are running in \fIevery\fR bug report that you send in.
+
+Do not expect a personal answer to a bug report.  The purpose of reporting
+bugs is to get them fixed for everyone in the next release, if possible.
+For personal assistance, look in the SERVICE file (see above) for
+a list of people who offer it.
+
+Please do not send anything but bug reports to this mailing list.
+Send requests to be added to mailing lists to the special list
+info-gnu-emacs-request@prep.ai.mit.edu (or the corresponding UUCP
+address).  For more information about Emacs mailing lists, see the
+file /usr/local/emacs/etc/MAILINGLISTS.  Bugs tend actually to be
+fixed if they can be isolated, so it is in your interest to report
+them in such a way that they can be easily reproduced.
+.PP
+Bugs that I know about are: shell will not work with programs
+running in Raw mode on some Unix versions.
+.SH UNRESTRICTIONS
+.PP
+.I Emacs 
+is free; anyone may redistribute copies of 
+.I Emacs 
+to
+anyone under the terms stated in the 
+.I Emacs 
+General Public License,
+a copy of which accompanies each copy of 
+.I Emacs 
+and which also
+appears in the reference manual.
+.PP
+Copies of
+.I Emacs
+may sometimes be received packaged with distributions of Unix systems,
+but it is never included in the scope of any license covering those
+systems.  Such inclusion violates the terms on which distribution
+is permitted.  In fact, the primary purpose of the General Public
+License is to prohibit anyone from attaching any other restrictions
+to redistribution of 
+.I Emacs.
+.PP
+Richard Stallman encourages you to improve and extend 
+.I Emacs, 
+and urges that
+you contribute your extensions to the GNU library.  Eventually GNU
+(Gnu's Not Unix) will be a complete replacement for Berkeley
+Unix.
+Everyone will be free to use, copy, study and change the GNU system.
+.SH SEE ALSO
+X(1), xlsfonts(1), xterm(1), xrdb(1)
+.SH AUTHORS
+.PP
+.I Emacs
+was written by Richard Stallman and the Free Software Foundation.
+Joachim Martillo and Robert Krawitz added the X features.

etc/emacstool.1

@@ -0,0 +1,134 @@
+.TH EMACSTOOL 1
+.SH NAME
+.I emacstool 
+\- run emacs under Sun windows with function-key and mouse support.
+.SH SYNOPSIS
+.I emacstool
+[{window_args} {-rc run_command_path} args ... ]
+.SH TYPICAL USAGE
+In ~/.suntools or ~/.rootmenu include a line like this:
+.br
+"Emacstool"     emacstool -WI emacs.icon -f emacstool-init
+.SH DESCRIPTION
+.B  Emacstool
+creates a SunView frame and a tty subwindow within which mouse events
+and function keys are translated to ASCII sequences which Emacs can
+parse.  The translated input events are sent to the process running in
+the tty subwindow, which is typically GNU Emacs.  Emacstool thereby
+allows GNU Emacs users to make full use of the mouse and function keys.
+GNU Emacs can be loaded with functions to interpret the mouse and
+function-key events to make a truly fine screen oriented editor for
+the Sun Workstation.
+.PP
+(Note that GNU Emacs has a special interface to the X window system as
+well.  The X window system has many technical advantages, it is an
+industry standard, and it is also free software.  The Free Software
+Foundation urges you to try X windows, and distributes a free copy of
+X on Emacs distribution tapes.)
+.PP
+Function keys are translated to a sequence of the form
+`^X*[a-o][lrt]'.  The last character is `l', `r', or `t' corresponding
+to whether the key is among the Left, Right, or Top function keys.
+The third character indicates which button of the group
+was pressed.  Thus, the function key in the lower right corner will
+transmit the sequence `^X*or'.  In addition, the [lrt] is affected by
+the Control, Meta, and Shift keys.  Unshifted Control keys will be
+non-alphabetic: C-l is [,], C-r is [2], C-t is [4].
+.PP 
+Mouse buttons are encoded as `^X^@([124] x y)\\n'.  ^X^@ is the
+standard GNU Emacs mouse event prefix, it is followed by a list
+indicating the button pressed and the character row and column of the
+point in the window where the mouse cursor is, and followed by a
+newline character.  In GNU Emacs, the ^X^@ dispatches to a
+mouse event handler which then reads the following list.
+.SH OPTIONS
+.B Emacstool
+supports all the standard window arguments, including font and icon 
+specifiers.  
+.PP
+By default, Emacstool runs the program 
+.I emacs
+in the created subwindow.  
+The value of the environment variable 
+.I EMACSTOOL
+can be used to override this if your version of 
+.B Emacs
+is not accessible on your search path by the name 
+.I Emacs.
+In addition, the run command can be set by the 
+.I pathname 
+following the last occurrence of the
+.I \-rc
+flag.
+This is convenient for using Emacstool to run on remote machines.
+.PP
+All other command line arguments not used by the window system are passed
+as arguments to the program that runs in the Emacstool window.
+.PP
+For example: 
+.PP
+local% (emacstool -rc rlogin remote -8 &)&
+.PP
+will create an Emacstool window logged in to a machine named
+.I remote.
+If Emacs is run from this window, 
+Emacstool will encode mouse and function keys, and send them to rlogin.
+If Emacs is run from this shell on the remote machine, it will see
+the mouse and function keys properly.
+However, since the remote host does not have access to the screen,
+the cursor cannot be changed, menus will not appear, and the selection
+buffer (STUFF) is limited.
+.SH Using With GNU Emacs:
+The GNU Emacs files
+lisp/term/sun.el,
+lisp/sun-mouse.el, 
+lisp/sun-fns.el, 
+and 
+src/sunfns.c
+provide emacs support for the Emacstool and function keys.
+Emacstool will automatically set the TERM environment variable to be "sun"
+and unset the environment variable TERMCAP.  That is, these variables will
+not be inherited from the shell that starts Emacstool.
+Since the terminal type is
+.I SUN
+(that is, the environment variable TERM is set to 
+.I SUN), 
+Emacs will automatically load the file lisp/term/sun.
+This, in turn, will ensure that sun-mouse.el is autoloaded when any mouse
+events are detected.  It is suggested that 
+.I sun-mouse 
+and
+.I sun-fns
+be loaded in your site-init.el file, so that they will always be loaded
+when running on a Sun workstation.
+.PP
+In addition, Emacstool sets the environment variable IN_EMACSTOOL = "t".
+Lisp code in your ~/.emacs can use (getenv "IN_EMACSTOOL")
+to determine whether to do Emacstool specific initialization.
+Sun.el uses this to automatically call emacstool-init (getenv "IN_EMACSTOOL")
+is defined.
+.PP
+The file src/sunfns.c defines several useful functions for emacs on
+the Sun.  Among these are procedures to pop-up SunView 
+.I menus, 
+put and get from the SunView
+.I STUFF
+buffer, and a procedure for changing the cursor 
+.I icon.
+If you want to define or edit cursor icons, 
+there is a rudimentary mouse driven icon editor in the file
+lisp/sun-cursors.el.  Try invoking (sc:edit-cursor)
+.SH BUGS
+It takes a few milliseconds to create a menu before it pops up.
+.SH ENVIRONMENT VARIABLES
+EMACSTOOL
+IN_EMACSTOOL
+TERM
+TERMCAP
+.SH FILES
+.DT
+emacs
+.SH "SEE ALSO"
+emacs(1)
+ .../etc/SUN-SUPPORT
+ .../lisp/term/sun.el

etc/future-bug

@@ -0,0 +1,37 @@
+Date: Tue, 23 Feb 2199 21:03:50 -0600
+From: Karl Fogel <kfogel@floss.cyclic.com>
+To: bug-gnu-emacs@prep.ai.mit.edu
+Subject: M-x search-backward-in-time broken...
+X-Windows: you'll envy the dead.
+
+In GNU Emacs 51.70.4 (i9986-unknown-linux-gnu, X toolkit) of Sat Feb  20 2199 on floss
+configured using `configure  --with-x-toolkit=yes'
+
+        The `search-backward-in-time' function appears to be broken in
+Emacs 51.70.  
+
+        Unfortunately, I can never seem to start the debugger early
+enough to catch the error as it happens.  However I have traced the
+problem through source by eye, and it looks like `time-forward' can't
+handle negative arguments anymore.  This is consistent with other
+symptoms: for example, `undo' (which since 51.25 has worked by passing
+a negative arg to `time-forward') is also broken.  However, `do' still
+works -- it seems that `time-forward' continues to handle positive
+arguments just fine.
+
+        No one here-and-now can figure out how to fix the problem,
+because the code for `time-forward' is so hairy.  We're using M-x
+report-future-emacs-bug to request that you folks include more
+comments when you write it (sometime in 2198 as I recall).
+
+        Thanks!
+
+-Karl Fogel   <kfogel@red-bean.com>
+
+
+P.S. You'll be pleased to know that since (time-forward N) still works
+     for N >= 0, we've used it to pre-emptively update configure.in.
+     Emacs now configures and builds on every platform that will ever
+     be made.  It wasn't easy, but at least that's one problem out of
+     the way for good.  If you'd like the patch, just ask.
+

etc/gnus-tut.txt

@@ -0,0 +1,294 @@
+From lars Thu Feb 23 23:20:38 1995
+From: larsi@ifi.uio.no (ding)
+Date: Fri Feb 24 13:40:45 1995
+Subject: So you want to use the new Gnus
+Message-ID: <lars-doc1@eyesore.no>
+
+Actually, since you are reading this, chances are you are already
+using the new Gnus.  Congratulations.
+
+This entire newsgroup you are reading is, in fact, no real newsgroup
+at all, in the traditional sense.  It is an example of one of the
+"foreign" select methods that Gnus may use.
+
+The text you are now reading is stored in the "etc" directory with the
+rest of the Emacs sources.  You are using the "nndoc" backend for
+accessing it.  Scary, isn't it?
+
+This isn't the real documentation.  `M-x info', `m gnus <RET>' to read
+that.  This "newsgroup" is intended as a kinder, gentler way of getting
+people started.
+
+Gnus is a rewrite of GNUS 4.1, written by Masanobu Umeda.  The rewrite
+was done by moi, yours truly, your humble servant, Lars Magne
+Ingebrigtsen.  If you have a WWW browser, you can investigate to your
+heart's delight at <URL:http://www.ifi.uio.no/~larsi/larsi.html>.
+
+;; Copyright (C) 1995 Free Software Foundation, Inc.
+
+;; Author: Lars Magne Ingebrigtsen <larsi@ifi.uio.no>
+;; Keywords: news
+
+;; This file is part of GNU Emacs.
+
+;; GNU Emacs is free software; you can redistribute it and/or modify
+;; it under the terms of the GNU General Public License as published by
+;; the Free Software Foundation; either version 2, or (at your option)
+;; any later version.
+
+;; GNU Emacs is distributed in the hope that it will be useful,
+;; but WITHOUT ANY WARRANTY; without even the implied warranty of
+;; MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
+;; GNU General Public License for more details.
+
+;; You should have received a copy of the GNU General Public License
+;; along with GNU Emacs; see the file COPYING.  If not, write to the
+;; Free Software Foundation, Inc., 59 Temple Place - Suite 330,
+;; Boston, MA 02111-1307, USA.
+
+From lars Thu Feb 23 23:20:38 1995
+From: larsi@ifi.uio.no (ding)
+Date: Fri Feb 24 13:40:45 1995
+Subject: Starting up
+Message-ID: <lars-doc2@eyesore.no>
+
+If you are having problems with Gnus not finding your server, you have
+to set `gnus-select-method'.  A "method" is a way of specifying *how*
+the news is to be found, and from *where*.
+
+Say you want to read news from you local, friendly nntp server
+"news.my.local.server". 
+
+(setq gnus-select-method '(nntp "news.my.local.server"))
+
+Quite easy, huh?
+
+From the news spool:
+
+(setq gnus-select-method '(nnspool ""))
+
+From your mh-e spool:
+
+(setq gnus-select-method '(nnmh ""))
+
+There's a whole bunch of other methods for reading mail and news, see
+the "Foreign groups" article for that.
+
+
+From lars Thu Feb 23 23:20:38 1995
+From: larsi@ifi.uio.no (ding)
+Date: Fri Feb 24 13:40:45 1995
+Subject: Where are all the groups, then?
+Message-ID: <lars-doc3@eyesore.no>
+
+If this is the first time you have used a newsreader, you won't have a
+.newsrc file.  This means that Gnus will think that all the newsgroups
+on the server are "new", and kill them all.
+
+If you have a .newsrc file, the new groups will be processed with the
+function in the `gnus-subscribe-newsgroup-method' variable, which is
+`gnus-subscribe-zombies' by default.
+
+This means that all the groups have been made into "zombies" - not
+quite dead, but not exactly alive, either.
+
+Jump back to the *Group* buffer, and type `A z' to list all the zombie
+groups.  Look though the list, and subscribe to the groups you want to
+read by pressing `u' on the one you think look interesting.
+
+If all the groups have been killed, type `A k' to list all the killed
+groups.  Subscribe to them the same way.
+
+When you are satisfied, press `S z' to kill all the zombie groups.
+
+Now you should have a nice list of all groups you are interested in.
+
+(If you later want to subscribe to more groups, press `A k' to
+list all the kill groups, and repeat.  You can also type `U' and be
+prompted for groups to subscribe to.)
+
+
+From lars Thu Feb 23 23:20:38 1995
+From: larsi@ifi.uio.no (ding)
+Date: Fri Feb 24 13:40:45 1995
+Subject: I want to read my mail!
+Message-ID: <lars-doc4@eyesore.no>
+
+Yes, Virginia, you can read mail with Gnus.
+
+First you have to decide which mail backend you want to use.  You have
+nnml, which is a one-file-one-mail backend, which is quite nice, but
+apt to make your systems administrator go crazy and come after you
+with a shotgun.
+
+nnmbox uses a Unix mail box to store mail.  Nice, but slow.
+
+nnmh uses mh-e folders, which is also a one-file-one-mail thingie, but
+slower than nnml.  (It doesn't support NOV files.)
+
+So if you want to go with nnmbox, you can simply say:
+
+(setq gnus-secondary-select-methods '((nnmbox "")))
+
+(The same for the other methods, kind of.)
+
+You should also set `nnmail-split-methods' to something sensible: 
+
+(setq nnmail-split-methods 
+      '(("mail.junk" "From:.*Lars")
+	("mail.misc "")))
+
+This will put all mail from me in you junk mail group, and the rest in
+"mail.misc". 
+
+These groups will be subscribe the same way as the normal groups, so
+you will probably find them among the zombie groups after you set
+these variables and re-start Gnus.
+
+
+From lars Thu Feb 23 23:20:38 1995
+From: larsi@ifi.uio.no (ding)
+Date: Fri Feb 24 13:40:45 1995
+Subject: Foreign newsgroups
+Message-ID: <lars-doc5@eyesore.no>
+
+These are groups that do not come from `gnus-select-method'. 
+
+Say you want to read "alt.furniture.couches" from "news.funet.fi".  You
+can then either type `B news.funet.fi <RET>' to browse that server and
+subscribe to that group, or you can type 
+`G m alt.furniture.couches<RET>nntp<RET>news.funet.fi<RET>', if you
+like to type a lot.
+
+If you want to read a directory as a newsgroup, you can create an
+nndir group, much the same way.  There's a shorthand for that,
+though.  If, for instance, you want to read the (ding) list archives,
+you could type `G d /ftp <RET>'.
+
+There's lots more to know about foreign groups, but you have to read
+the info pages to find out more.
+
+
+From lars Thu Feb 23 23:20:38 1995
+From: larsi@ifi.uio.no (ding)
+Date: Fri Feb 24 13:40:45 1995
+Subject: Low level changes in GNUS, or, Wrong type argument: stringp, nil
+Message-ID: <lars-doc6@eyesore.no>
+
+Gnus really isn't GNUS, even though it looks like it.  If you scrape
+the surface, you'll find that most things have changed.
+
+This means that old code that relies on GNUS internals will fail.  
+
+In particular, `gnus-newsrc-hashtb', `gnus-newsrc-assoc',
+`gnus-killed-list', the `nntp-header-' macros and the display formats
+have all changed.  If you have some code lying around that depend on
+these, or change these, you'll have to re-write your code.
+
+Old hilit19 code does not work at all.  In fact, you should probably
+remove all hilit code from all the Gnus hooks
+(`gnus-group-prepare-hook', `gnus-summary-prepare-hook' and
+`gnus-summary-article-hook').  (Well, at the very least the first
+two.)  Gnus provides various integrated functions for highlighting,
+which are both faster and more accurated.
+
+There is absolutely no chance, whatsoever, of getting Gnus to work
+with Emacs 18.  It won't even work on Emacsen older than Emacs
+19.30/XEmacs 19.13.  Upgrade your Emacs or die.
+
+	
+From lars Thu Feb 23 23:20:38 1995
+From: larsi@ifi.uio.no (ding)
+Date: Fri Feb 24 13:40:45 1995
+Subject: How do I re-scan my mail groups?
+Message-ID: <lars-doc8@eyesore.no>
+
+Reading the active file from the nntp server is a drag.
+
+Just press `M-g' on the mail groups, and they will be re-scanned.
+
+You can also re-scan all the mail groups by putting them on level 1
+(`S l 1'), and saying `1 g' to re-scan all level 1 groups.
+
+
+From lars Thu Feb 23 23:20:38 1995
+From: larsi@ifi.uio.no (ding)
+Date: Fri Feb 24 13:40:45 1995
+Subject: How do I set up virtual newsgroups?
+Message-ID: <lars-doc9@eyesore.no>
+
+Virtual newsgroups are collections of other newsgroups.  Why people
+want this is beyond me, but here goes:
+
+Create the group by saying
+
+`M-a my.virtual.newsgroup<RET>nnvirtual<RET>^rec\.aquaria\.*<RET>'
+
+This will create the group "nnvirtual:my.virtual.newsgroup", which
+will collect all articles from all the groups in the "rec.aquaria"
+hierarchy.  
+
+If you want to edit the regular expression, just type `M-e' on the
+group line.
+
+Note that all the groups that are part of the virtual group have to be
+alive.  This means that the cannot, absolutely not, be zombie or
+killed.  They can be unsubscribed; that's no problem.
+
+You can combine groups from different servers in the same virtual
+newsgroup, something that may actually be useful.  Say you have the
+group "comp.headers" on the server "news.server.no" and the same group
+on "news.server.edu".  If people have posted articles with Distribution
+headers that stop propagation of their articles, combining these two
+newsgroups into one virtual newsgroup should give you a better view of
+what's going on.
+
+One caveat, though: The virtual group article numbers from the first
+source group (group A) will always be lower than the article numbers
+from the second (group B).  This means that Gnus will believe that
+articles from group A are older than articles from group B.  Threading
+will lessen these problems, but it might be a good idea to sort the
+threads over the date of the articles to get a correct feel for the
+flow of the groups:
+
+(setq gnus-thread-sort-functions '(gnus-thread-sort-by-date))
+
+If you only want this in virtual groups, you could say something along
+the lines of:
+
+(setq gnus-select-group-hook
+      (lambda ()
+  	(if (eq 'nnvirtual (car (gnus-find-method-for-group 
+	                          gnus-newsgroup-name)))
+	    (progn
+	      (make-local-variable 'gnus-thread-sort-functions)
+	      (setq gnus-thread-sort-functions '(gnus-thread-sort-by-date))))))
+
+
+From lars Thu Feb 23 23:20:38 1995
+From: larsi@ifi.uio.no (ding)
+Date: Fri Feb 24 13:40:45 1995
+Subject: Bugs & stuff
+Message-ID: <lars-doc7@eyesore.no>
+
+If you want to report a bug, please type `M-x gnus-bug'.  This will
+give me a precise overview of your Gnus and Emacs version numbers,
+along with a look at all Gnus variables you have changed.
+
+Du not expect a reply back, but your bug should be fixed in the next
+version.  If the bug persists, please re-submit your bug report.
+
+When a bug occurs, I need a recipe for how to trigger the bug.  You
+have to tell me exactly what you do to uncover the bug, and you should
+(setq debug-on-error t) and send me the backtrace along with the bug
+report.  
+
+If I am not able to reproduce the bug, I won't be able to fix it.
+
+I would, of course, prefer that you locate the bug, fix it, and mail
+me the patches, but one can't have everything.
+
+If you have any questions on usage, the "ding@ifi.uio.no" mailing list
+is where to post the questions.
+
+