[xemacs-hg @ 2002-07-31 07:14:49 by michaels] 2002-07-17 Marcus Crestani <crestani@informatik.uni-tuebingen.de> Markus Kaltenbach <makalten@informatik.uni-tuebingen.de> Mike Sperber <mike@xemacs.org> configure flag to turn these changes on: --use-kkcc First we added a dumpable flag to lrecord_implementation. It shows, if the object is dumpable and should be processed by the dumper. * lrecord.h (struct lrecord_implementation): added dumpable flag (MAKE_LRECORD_IMPLEMENTATION): fitted the different makro definitions to the new lrecord_implementation and their calls. Then we changed mark_object, that it no longer needs a mark method for those types that have pdump descritions. * alloc.c: (mark_object): If the object has a description, the new mark algorithm is called, and the object is marked according to its description. Otherwise it uses the mark method like before. These procedures mark objects according to their descriptions. They are modeled on the corresponding pdumper procedures. (mark_with_description): (get_indirect_count): (structure_size): (mark_struct_contents): These procedures still call mark_object, this is needed while there are Lisp_Objects without descriptions left. We added pdump descriptions for many Lisp_Objects: * extents.c: extent_auxiliary_description * database.c: database_description * gui.c: gui_item_description * scrollbar.c: scrollbar_instance_description * toolbar.c: toolbar_button_description * event-stream.c: command_builder_description * mule-charset.c: charset_description * device-msw.c: devmode_description * dialog-msw.c: mswindows_dialog_id_description * eldap.c: ldap_description * postgresql.c: pgconn_description pgresult_description * tooltalk.c: tooltalk_message_description tooltalk_pattern_description * ui-gtk.c: emacs_ffi_description emacs_gtk_object_description * events.c: * events.h: * event-stream.c: * event-Xt.c: * event-gtk.c: * event-tty.c: To write a pdump description for Lisp_Event, we converted every struct in the union event to a Lisp_Object. So we created nine new Lisp_Objects: Lisp_Key_Data, Lisp_Button_Data, Lisp_Motion_Data, Lisp_Process_Data, Lisp_Timeout_Data, Lisp_Eval_Data, Lisp_Misc_User_Data, Lisp_Magic_Data, Lisp_Magic_Eval_Data. We also wrote makro selectors and mutators for the fields of the new designed Lisp_Event and added everywhere these new abstractions. We implemented XD_UNION support in (mark_with_description), so we can describe exspecially console/device specific data with XD_UNION. To describe with XD_UNION, we added a field to these objects, which holds the variant type of the object. This field is initialized in the appendant constructor. The variant is an integer, it has also to be described in an description, if XD_UNION is used. XD_UNION is used in following descriptions: * console.c: console_description (get_console_variant): returns the variant (create_console): added variant initialization * console.h (console_variant): the different console types * console-impl.h (struct console): added enum console_variant contype * device.c: device_description (Fmake_device): added variant initialization * device-impl.h (struct device): added enum console_variant devtype * objects.c: image_instance_description font_instance_description (Fmake_color_instance): added variant initialization (Fmake_font_instance): added variant initialization * objects-impl.h (struct Lisp_Color_Instance): added color_instance_type * objects-impl.h (struct Lisp_Font_Instance): added font_instance_type * process.c: process_description (make_process_internal): added variant initialization * process.h (process_variant): the different process types

Introduction

Thank you for downloading XEmacs.  We of the XEmacs development team
believe user satisfaction is our number one priority, and we hope that
you will be pleased with the power of our editor.  Please follow all
of the instructions in order to enjoy a quick and easy installation.


Getting Started

In this guide, information which you will need to supply will be enclosed in
angle brackets, <like this>.  Commands which you will have to enter will be
indented,

	like this.

You will need to provide a loading directory, in which to load the
material from tape (/tmp/xemacs is recommended), and a permanent
installation directory (/usr/local/xemacs is recommended).


Loading From Tape

First create and change directory to the loading directory:

	mkdir <working directory>
	cd <working directory>

Now you are ready to load the software from tape.

The specific device name needed to load the tape varies with hardware vendors,
and may be found in Appendix A, "Vendors and Device Names".

Load the software from tape:

	tar xvf /dev/<device name>

You have now loaded all of the software from tape, and are ready to compile and
install the XEmacs Text Editor.


Compiling and Installing the XEmacs Editor

Compiling and installing the libraries is handled by a user-friendly shell
script.  You will need to provide some information to the script, such as your
organization name and registration number.  To run the script, type

	/bin/sh xemacs/xemacs.install -d <installation directory>

Follow the script's directions, and provide the information which it prompts
for.

When the script prompts you for the directory in which the distribution files
are located, you will find that you are unable to provide it with any directory
which the script will deem satisfactory.  That is because it is necessary to
order the following additional parts which are necessary to continue with the
installation:

	Part Number	Qty	Name				Price

	GM-96-3026	1	Goat, male			 1000.00
	CB-13-2395	1	Candle, black			   50.00
	CG-63-6376	1	Chalk dust container		   10.00
	IB-89-3335	5	Incense sticks			    5.00
	DE-44-8846	1	Dagger, ebon, curved		  500.00
	AS-87-2319	1	Altar, silver			10000.00

Wait until the additional parts arrive; you will be ready to continue the
installation the next Friday the 13th at midnight.


Ritual for Successfully Completing Installation

Stand in front of the computer.  Pour out the chalk dust in an inscribed
pentagram around you; be sure that it is without breaks.  Set an incense stick
at each of the five corners, the altar in front of the computer, and the candle
in front of the altar.

Light each of the incense sticks and the candles, chanting in a low voice:

	Daemons and spirits of the netherworld
	Forces of all that is chaotic and mysterious
	Essence of Netscape and MicroSoft

	I am coming here to appease you
	I offer you this goat
	That my software may work

	I bind you here
	Do not make my system crash
	Let the software install as advertised

Place the goat on the altar, and slaughter it with the dagger.

	May this goat feed you
	Sate your lust for blood
	Into it may your mischief fly
	Not my computer
	Make the software work
	For this is the only way

Then spit into the computer's ventilation slots.  This will complete different
circuits inside the computer, causing its motherboard and cards to function in
ways that the engineers never intended, thereby making your system compatible
with our libraries.

Reboot your computer.  The installation is now complete.

[This has undergone a minor rewrite for XEmacs.  It originally
appeared on rec.humor.funny courtesy of jonathan seth hayward
<jhayward@students.uiuc.edu>, and is included by permission of the
author].