Mercurial > hg > xemacs-beta
annotate etc/InstallGuide @ 4477:e34711681f30
Don't determine whether to call general device-type code at startup,
rather decide in the device-specific code itself.
lisp/ChangeLog addition:
2008-07-07 Aidan Kehoe <kehoea@parhasard.net>
Patch to make it up to the device-specific code whether
various Lisp functions should be called during device creation,
not relying on the startup code to decide this. Also, rename
initial-window-system to initial-device-type (which makes more
sense in this scheme), always set it.
* startup.el (command-line):
Use initial-device-type, not initial-window-system; just call
#'make-device, leave the special behaviour to be done the first
time a console type is initialised to be decided on by the
respective console code.
* x-init.el (x-app-defaults-directory): Declare that it should be
bound.
(x-define-dead-key): Have the macro take a DEVICE argument.
(x-initialize-compose): Have the function take a DEVICE argument,
and use it when checking if various keysyms are available on the
keyboard.
(x-initialize-keyboard): Have the function take a DEVICE argument,
allowing device-specific keyboard initialisation.
(make-device-early-x-entry-point-called-p): New.
(make-device-late-x-entry-point-called-p): New. Rename
pre-x-win-initted, x-win-initted.
(make-device-early-x-entry-point): Rename init-pre-x-win, take the
call to make-x-device out (it should be called from the
device-creation code, not vice-versa).
(make-device-late-x-entry-point): Rename init-post-x-win, have it
take a DEVICE argument, use that DEVICE argument when working out
what device-specific things need doing. Don't use
create-console-hook in core code.
* x-win-xfree86.el (x-win-init-xfree86): Take a DEVICE argument;
use it.
* x-win-sun.el (x-win-init-sun): Take a DEVICE argument; use it.
* mule/mule-x-init.el: Remove #'init-mule-x-win, an empty
function.
* tty-init.el (make-device-early-tty-entry-point-called-p): New.
Rename pre-tty-win-initted.
(make-device-early-tty-entry-point): New.
Rename init-pre-tty-win.
(make-frame-after-init-entry-point): New.
Rename init-post-tty-win to better reflect when it's called.
* gtk-init.el (gtk-early-lisp-options-file): New.
Move this path to a documented variable.
(gtk-command-switch-alist): Wrap the docstring to fewer than 79
columns.
(make-device-early-gtk-entry-point-called-p): New.
(make-device-late-gtk-entry-point-called-p): New.
Renamed gtk-pre-win-initted, gtk-post-win-initted to these.
(make-device-early-gtk-entry-point): New.
(make-device-late-gtk-entry-point): New.
Renamed init-pre-gtk-win, init-post-gtk-win to these.
Have make-device-late-gtk-entry-point take a device argument, and use
it; have make-device-early-gtk-entry-point load the GTK-specific
startup code, instead of doing that in C.
(init-gtk-win): Deleted, functionality moved to the GTK device
creation code.
(gtk-define-dead-key): Have it take a DEVICE argument; use this
argument.
(gtk-initialize-compose): Ditto.
* coding.el (set-terminal-coding-system):
Correct the docstring; the function isn't broken.
src/ChangeLog addition:
2008-07-07 Aidan Kehoe <kehoea@parhasard.net>
Patch to make it up to the device-specific code whether
various Lisp functions should be called during device creation,
not relying on the startup code to decide this. Also, rename
initial-window-system to initial-device-type (which makes more
sense in this scheme), always set it.
* redisplay.c (Vinitial_device_type): New.
(Vinitial_window_system): Removed.
Rename initial-window-system to initial-device type, making it
a stream if we're noninteractive. Update its docstring.
* device-x.c (Qmake_device_early_x_entry_point,
Qmake_device_late_x_entry_point): New.
Rename Qinit_pre_x_win, Qinit_post_x_win.
(x_init_device): Call #'make-device-early-x-entry-point earlier,
now we rely on it to find the application class and the
app-defaults directory.
(x_finish_init_device): Call #'make-device-late-x-entry-point with
the created device.
(Vx_app_defaults_directory): Always make this available, to
simplify code in x-init.el.
* device-tty.c (Qmake_device_early_tty_entry_point): New.
Rename Qinit_pre_tty_win, rename Qinit_post_tty_win and move to
frame-tty.c as Qmake_frame_after_init_entry_point.
(tty_init_device): Call #'make-device-early-tty-entry-point before
doing anything.
* frame-tty.c (Qmake_frame_after_init_entry_point): New.
* frame-tty.c (tty_after_init_frame): Have it call the
better-named #'make-frame-after-init-entry-point function
instead of #'init-post-tty-win (since it's called after frame, not
device, creation).
* device-msw.c (Qmake_device_early_mswindows_entry_point,
Qmake_device_late_mswindows_entry_point): New.
Rename Qinit_pre_mswindows_win, Qinit_post_mswindows_win.
(mswindows_init_device): Call
#'make-device-early-mswindows-entry-point here, instead of having
its predecessor call us.
(mswindows_finish_init_device): Call
#'make-device-early-mswindows-entry-point, for symmetry with the
other device types (though it's an empty function).
* device-gtk.c (Qmake_device_early_gtk_entry_point,
Qmake_device_late_gtk_entry_point): New.
Rename Qinit_pre_gtk_win, Qinit_post_gtk_win.
(gtk_init_device): Call #'make-device-early-gtk-entry-point; don't
load ~/.xemacs/gtk-options.el ourselves, leave that to lisp.
(gtk_finish_init_device): Call #'make-device-late-gtk-entry-point
with the created device as an argument.
| author | Aidan Kehoe <kehoea@parhasard.net> |
|---|---|
| date | Wed, 09 Jul 2008 20:46:22 +0200 |
| parents | 9ad43877534d |
| children |
| rev | line source |
|---|---|
| 179 | 1 Introduction |
| 2 | |
| 3 Thank you for downloading XEmacs. We of the XEmacs development team | |
| 4 believe user satisfaction is our number one priority, and we hope that | |
| 5 you will be pleased with the power of our editor. Please follow all | |
| 6 of the instructions in order to enjoy a quick and easy installation. | |
| 7 | |
| 8 | |
| 9 Getting Started | |
| 10 | |
| 11 In this guide, information which you will need to supply will be enclosed in | |
| 12 angle brackets, <like this>. Commands which you will have to enter will be | |
| 13 indented, | |
| 14 | |
| 15 like this. | |
| 16 | |
| 17 You will need to provide a loading directory, in which to load the | |
| 18 material from tape (/tmp/xemacs is recommended), and a permanent | |
| 19 installation directory (/usr/local/xemacs is recommended). | |
| 20 | |
| 21 | |
| 22 Loading From Tape | |
| 23 | |
| 24 First create and change directory to the loading directory: | |
| 25 | |
| 26 mkdir <working directory> | |
| 27 cd <working directory> | |
| 28 | |
| 29 Now you are ready to load the software from tape. | |
| 30 | |
| 31 The specific device name needed to load the tape varies with hardware vendors, | |
| 32 and may be found in Appendix A, "Vendors and Device Names". | |
| 33 | |
| 34 Load the software from tape: | |
| 35 | |
| 36 tar xvf /dev/<device name> | |
| 37 | |
| 38 You have now loaded all of the software from tape, and are ready to compile and | |
| 39 install the XEmacs Text Editor. | |
| 40 | |
| 41 | |
| 42 Compiling and Installing the XEmacs Editor | |
| 43 | |
| 44 Compiling and installing the libraries is handled by a user-friendly shell | |
| 45 script. You will need to provide some information to the script, such as your | |
| 46 organization name and registration number. To run the script, type | |
| 47 | |
| 48 /bin/sh xemacs/xemacs.install -d <installation directory> | |
| 49 | |
| 50 Follow the script's directions, and provide the information which it prompts | |
| 51 for. | |
| 52 | |
| 53 When the script prompts you for the directory in which the distribution files | |
| 54 are located, you will find that you are unable to provide it with any directory | |
| 55 which the script will deem satisfactory. That is because it is necessary to | |
| 56 order the following additional parts which are necessary to continue with the | |
| 57 installation: | |
| 58 | |
| 59 Part Number Qty Name Price | |
| 60 | |
| 61 GM-96-3026 1 Goat, male 1000.00 | |
| 62 CB-13-2395 1 Candle, black 50.00 | |
| 63 CG-63-6376 1 Chalk dust container 10.00 | |
| 64 IB-89-3335 5 Incense sticks 5.00 | |
| 65 DE-44-8846 1 Dagger, ebon, curved 500.00 | |
| 66 AS-87-2319 1 Altar, silver 10000.00 | |
| 67 | |
| 68 Wait until the additional parts arrive; you will be ready to continue the | |
| 69 installation the next Friday the 13th at midnight. | |
| 70 | |
| 71 | |
| 72 Ritual for Successfully Completing Installation | |
| 73 | |
| 74 Stand in front of the computer. Pour out the chalk dust in an inscribed | |
| 75 pentagram around you; be sure that it is without breaks. Set an incense stick | |
| 76 at each of the five corners, the altar in front of the computer, and the candle | |
| 77 in front of the altar. | |
| 78 | |
| 79 Light each of the incense sticks and the candles, chanting in a low voice: | |
| 80 | |
| 81 Daemons and spirits of the netherworld | |
| 82 Forces of all that is chaotic and mysterious | |
| 83 Essence of Netscape and MicroSoft | |
| 84 | |
| 85 I am coming here to appease you | |
| 86 I offer you this goat | |
| 87 That my software may work | |
| 88 | |
| 89 I bind you here | |
| 90 Do not make my system crash | |
| 91 Let the software install as advertised | |
| 92 | |
| 93 Place the goat on the altar, and slaughter it with the dagger. | |
| 94 | |
| 95 May this goat feed you | |
| 96 Sate your lust for blood | |
| 97 Into it may your mischief fly | |
| 98 Not my computer | |
| 99 Make the software work | |
| 100 For this is the only way | |
| 101 | |
| 102 Then spit into the computer's ventilation slots. This will complete different | |
| 103 circuits inside the computer, causing its motherboard and cards to function in | |
| 104 ways that the engineers never intended, thereby making your system compatible | |
| 105 with our libraries. | |
| 106 | |
| 107 Reboot your computer. The installation is now complete. | |
| 108 | |
| 109 [This has undergone a minor rewrite for XEmacs. It originally | |
| 110 appeared on rec.humor.funny courtesy of jonathan seth hayward | |
| 111 <jhayward@students.uiuc.edu>, and is included by permission of the | |
| 112 author]. |