[xemacs-hg @ 2002-03-21 07:29:57 by ben] chartab.c: Fix bugs in implementation and doc strings. config.h.in: Add foo_checking_assert_at_line() macros. Not clear whether these are actually useful, though; I'll take them out if not. symsinit.h, emacs.c: Some improvements to the timeline. Rearrange a bit the init calls. Add call for reinit_vars_of_object_mswindows() and declare in symsinit.h. event-Xt.c, event-gtk.c, event-msw.c, event-stream.c, event-tty.c, events.c, events.h: Introduce new event methods for printing, comparing, and hashing magic events, to avoid event-type-specific stuff that had crept into events.c. (And was crashing, since the channel in MS Windows magic events may be nil.) Implement the methods in event-{tty,gtk,Xt,mswindows}.c. Make wrapping functions event_stream_{compare,hash,format}_magic_event() to check if everything's OK and call the actual callback. Fix events.c to use the new methods. Add a new event-stream-operation EVENT_STREAM_NOTHING -- event stream not actually required to be able to do anything, just be open. (#### This event-stream-operation stuff needs to be rethought.) Fixed describe_event() in event-Xt.c to print its output to a stream, not always to stderr, so it can be used elsewhere. (e.g. in print-event when a magic event is encountered?) lisp.h, lrecord.h: Define new assert_at_line(), for use in asserts inside of inline functions. The assert will report the line and file of the inline function, which is almost certainly not what you want as it's useless. what you want to see is where the pseudo-macro was called from. So, when error-checking is on, we pass in the line and file into the macros, for accurate printout using assert_at_line(). Happens only when error-checking is defined so doesn't slow down non-error-checking builds. Fix XCHAR, XINT, XCHAR_OR_INT, XFOO, and wrap_foo() in this fashion. lstream.c, lstream.h: Add resizing_buffer_to_lisp_string(). objects-gtk.c: Fix typo. objects-msw.c: Implement a smarter way of determining whether a font matches a charset. Formerly we just looked at the "script" element of the font spec, converted it to a code page, and compared it with the code page derived from the charset. Now, as well as doing this, we ask the font for the list of unicode ranges it supports, see what range the charset falls into (#### bogus! need to do this char-by-char), and see if any of the font's supported ranges include the charset's range. also do some caching in Vfont_signature_data of previous inquiries. charset.h, text.c, mule-charset.c: New fun; extracted out of Fmake_char() and declare prototype in charset.h. text.h: introduce assert_by_line() to make REP_BYTES_BY_FIRST_BYTE report the file and line more accurately in an assertion failure. unicode.c: make non-static (used in objects-msw.c), declare in charset.h. mule\mule-category.el: Start implementing a category API compatible with FSF. Not there yet. We need improvements to char-tables. mule\mule-charset.el: Copy translation table code from FSF 21.1 and fix up. Eventually we'll have them in XEmacs. (used in ccl) Not here quite yet, and we need some improvements to char-tables. mule\cyril-util.el, mule\cyrillic.el, mule\devan-util.el, mule\ethio-util.el, mule\korea-util.el, mule\mule-tty-init.el, mule\tibet-util.el, mule\viet-util.el, mule\vietnamese.el: Fix numerous compilation warnings. Fix up code related to translation tables and other types of char-tables. menubar-items.el: Move the frame commands from the View menu to the File menu, to be consistent with how most other programs do things. Move less-used revert/recover items to a submenu. Make "recover" not prompt for a file, but recover the current buffer. TODO.ben-mule-21-5: Create bug list for latest problems.

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].