Mercurial > hg > xemacs-beta
annotate etc/InstallGuide @ 814:a634e3b7acc8
[xemacs-hg @ 2002-04-14 12:41:59 by ben]
latest changes
TODO.ben-mule-21-5: Update.
make-docfile.c: Add basic support for handling ISO 2022 doc strings -- we parse
the basic charset designation sequences so we know whether we're
in ASCII and have to pay attention to end quotes and such.
Reformat code according to coding standards.
abbrev.el: Add `global-abbrev-mode', which turns on or off abbrev-mode in all
buffers. Added `defining-abbrev-turns-on-abbrev-mode' -- if
non-nil, defining an abbrev through an interactive function will
automatically turn on abbrev-mode, either globally or locally
depending on the command. This is the "what you'd expect"
behavior.
indent.el: general function for indenting a balanced expression in a
mode-correct way. Works similar to indent-region in that a mode
can specify a specific command to do the whole operation; if not,
figure out the region using forward-sexp and indent each line
using indent-according-to-mode.
keydefs.el: Removed.
Modify M-C-backslash to do indent-region-or-balanced-expression.
Make S-Tab just insert a TAB char, like it's meant to do.
make-docfile.el: Now that we're using the call-process-in-lisp, we need to load
an extra file win32-native.el because we're running a bare temacs.
menubar-items.el: Totally redo the Cmds menu so that most used commands appear
directly on the menu and less used commands appear in submenus.
The old way may have been very pretty, but rather impractical.
process.el: Under Windows, don't ever use old-call-process-internal, even
in batch mode. We can do processes in batch mode.
subr.el: Someone recoded truncate-string-to-width, saying "the FSF version
is too complicated and does lots of hard-to-understand stuff" but
the resulting recoded version was *totally* wrong! it
misunderstood the basic point of this function, which is work in
*columns* not chars. i dumped ours and copied the version from
FSF 21.1. Also added truncate-string-with-continuation-dots,
since this idiom is used often.
config.inc.samp, xemacs.mak: Separate out debug and optimize flags.
Remove all vestiges of USE_MINIMAL_TAGBITS,
USE_INDEXED_LRECORD_IMPLEMENTATION, and GUNG_HO, since those
ifdefs have long been removed.
Make error-checking support actually work.
Some rearrangement of config.inc.samp to make it more logical.
Remove callproc.c and ntproc.c from xemacs.mak, no longer used.
Make pdump the default.
lisp.h: Add support for strong type-checking of Bytecount, Bytebpos,
Charcount, Charbpos, and others, by making them classes,
overloading the operators to provide integer-like operation and
carefully controlling what operations are allowed. Not currently
enabled in C++ builds because there are still a number of compile
errors, and it won't really work till we merge in my "8-bit-Mule"
workspace, in which I make use of the new types Charxpos,
Bytexpos, Memxpos, representing a "position" either in a buffer or
a string. (This is especially important in the extent code.)
abbrev.c, alloc.c, eval.c, buffer.c, buffer.h, editfns.c, fns.c, text.h: Warning fixes, some of them related to new C++ strict type
checking of Bytecount, Charbpos, etc.
dired.c: Caught an actual error due to strong type checking -- char len
being passed when should be byte len.
alloc.c, backtrace.h, bytecode.c, bytecode.h, eval.c, sysdep.c: Further optimize Ffuncall:
-- process arg list at compiled-function creation time, converting
into an array for extra-quick access at funcall time.
-- rewrite funcall_compiled_function to use it, and inline this
function.
-- change the order of check for magic stuff in
SPECBIND_FAST_UNSAFE to be faster.
-- move the check for need to garbage collect into the allocation
code, so only a single flag needs to be checked in funcall.
buffer.c, symbols.c: add debug funs to check on mule optimization info in buffers and
strings.
eval.c, emacs.c, text.c, regex.c, scrollbar-msw.c, search.c: Fix evil crashes due to eistrings not properly reinitialized under
pdump. Redo a bit some of the init routines; convert some
complex_vars_of() into simple vars_of(), because they didn't need
complex processing.
callproc.c, emacs.c, event-stream.c, nt.c, process.c, process.h, sysdep.c, sysdep.h, syssignal.h, syswindows.h, ntproc.c: Delete. Hallelujah, praise the Lord, there is no god
but Allah!!!
fix so that processes can be invoked in bare temacs -- thereby
eliminating any need for callproc.c. (currently only eliminated
under NT.) remove all crufty and unnecessary old process code in
ntproc.c and elsewhere. move non-callproc-specific stuff (mostly
environment) into process.c, so callproc.c can be left out under
NT.
console-tty.c, doc.c, file-coding.c, file-coding.h, lstream.c, lstream.h: fix doc string handling so it works with Japanese, etc docs.
change handling of "character mode" so callers don't have to
manually set it (quite error-prone).
event-msw.c: spacing fixes.
lread.c: eliminate unused crufty vintage-19 "FSF defun hack" code.
lrecord.h: improve pdump description docs.
buffer.c, ntheap.c, unexnt.c, win32.c, emacs.c: Mule-ize some unexec and startup code. It was pseudo-Mule-ized
before by simply always calling the ...A versions of functions,
but that won't cut it -- eventually we want to be able to run
properly even if XEmacs has been installed in a Japanese
directory. (The current problem is the timing of the loading of
the Unicode tables; this will eventually be fixed.) Go through and
fix various other places where the code was not Mule-clean.
Provide a function mswindows_get_module_file_name() to get our own
name without resort to PATH_MAX and such. Add a big comment in
main() about the problem with Unicode table load timing that I
just alluded to.
emacs.c: When error-checking is enabled (interpreted as "user is developing
XEmacs"), don't ask user to "pause to read messages" when a fatal
error has occurred, because it will wedge if we are in an inner
modal loop (typically when a menu is popped up) and make us unable
to get a useful stack trace in the debugger.
text.c: Correct update_entirely_ascii_p_flag to actually work.
lisp.h, symsinit.h: declarations for above changes.
author | ben |
---|---|
date | Sun, 14 Apr 2002 12:43:31 +0000 |
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]. |