Mercurial > hg > xemacs-beta
comparison README.packages @ 826:6728e641994e
[xemacs-hg @ 2002-05-05 11:30:15 by ben]
syntax cache, 8-bit-format, lots of code cleanup
README.packages: Update info about --package-path.
i.c: Create an inheritable event and pass it on to XEmacs, so that ^C
can be handled properly. Intercept ^C and signal the event.
"Stop Build" in VC++ now works.
bytecomp-runtime.el: Doc string changes.
compat.el: Some attempts to redo this to
make it truly useful and fix the "multiple versions interacting
with each other" problem. Not yet done. Currently doesn't work.
files.el: Use with-obsolete-variable to avoid warnings in new revert-buffer code.
xemacs.mak: Split up CFLAGS into a version without flags specifying the C
library. The problem seems to be that minitar depends on zlib,
which depends specifically on libc.lib, not on any of the other C
libraries. Unless you compile with libc.lib, you get errors --
specifically, no _errno in the other libraries, which must make it
something other than an int. (#### But this doesn't seem to obtain
in XEmacs, which also uses zlib, and can be linked with any of the
C libraries. Maybe zlib is used differently and doesn't need
errno, or maybe XEmacs provides an int errno; ... I don't
understand.
Makefile.in.in: Fix so that packages are around when testing.
abbrev.c, alloc.c, buffer.c, buffer.h, bytecode.c, callint.c, casefiddle.c, casetab.c, casetab.h, charset.h, chartab.c, chartab.h, cmds.c, console-msw.h, console-stream.c, console-x.c, console.c, console.h, data.c, device-msw.c, device.c, device.h, dialog-msw.c, dialog-x.c, dired-msw.c, dired.c, doc.c, doprnt.c, dumper.c, editfns.c, elhash.c, emacs.c, eval.c, event-Xt.c, event-gtk.c, event-msw.c, event-stream.c, events.c, events.h, extents.c, extents.h, faces.c, file-coding.c, file-coding.h, fileio.c, fns.c, font-lock.c, frame-gtk.c, frame-msw.c, frame-x.c, frame.c, frame.h, glade.c, glyphs-gtk.c, glyphs-msw.c, glyphs-msw.h, glyphs-x.c, glyphs.c, glyphs.h, gui-msw.c, gui-x.c, gui.h, gutter.h, hash.h, indent.c, insdel.c, intl-win32.c, intl.c, keymap.c, lisp-disunion.h, lisp-union.h, lisp.h, lread.c, lrecord.h, lstream.c, lstream.h, marker.c, menubar-gtk.c, menubar-msw.c, menubar-x.c, menubar.c, minibuf.c, mule-ccl.c, mule-charset.c, mule-coding.c, mule-wnnfns.c, nas.c, objects-msw.c, objects-x.c, opaque.c, postgresql.c, print.c, process-nt.c, process-unix.c, process.c, process.h, profile.c, rangetab.c, redisplay-gtk.c, redisplay-msw.c, redisplay-output.c, redisplay-x.c, redisplay.c, redisplay.h, regex.c, regex.h, scrollbar-msw.c, search.c, select-x.c, specifier.c, specifier.h, symbols.c, symsinit.h, syntax.c, syntax.h, syswindows.h, tests.c, text.c, text.h, tooltalk.c, ui-byhand.c, ui-gtk.c, unicode.c, win32.c, window.c: Another big Ben patch.
-- FUNCTIONALITY CHANGES:
add partial support for 8-bit-fixed, 16-bit-fixed, and
32-bit-fixed formats. not quite done yet. (in particular, needs
functions to actually convert the buffer.) NOTE: lots of changes
to regex.c here. also, many new *_fmt() inline funs that take an
Internal_Format argument.
redo syntax cache code. make the cache per-buffer; keep the cache
valid across calls to functions that use it. also keep it valid
across insertions/deletions and extent changes, as much as is
possible. eliminate the junky regex-reentrancy code by passing in
the relevant lisp info to the regex routines as local vars.
add general mechanism in extents code for signalling extent changes.
fix numerous problems with the case-table implementation; yoshiki
never properly transferred many algorithms from old-style to
new-style case tables.
redo char tables to support a default argument, so that mapping
only occurs over changed args. change many chartab functions to
accept Lisp_Object instead of Lisp_Char_Table *.
comment out the code in font-lock.c by default, because
font-lock.el no longer uses it. we should consider eliminating it
entirely.
Don't output bell as ^G in console-stream when not a TTY.
add -mswindows-termination-handle to interface with i.c, so we can
properly kill a build.
add more error-checking to buffer/string macros.
add some additional buffer_or_string_() funs.
-- INTERFACE CHANGES AFFECTING MORE CODE:
switch the arguments of write_c_string and friends to be
consistent with write_fmt_string, which must have printcharfun
first.
change BI_* macros to BYTE_* for increased clarity; similarly for
bi_* local vars.
change VOID_TO_LISP to be a one-argument function. eliminate
no-longer-needed CVOID_TO_LISP.
-- char/string macro changes:
rename MAKE_CHAR() to make_emchar() for slightly less confusion
with make_char(). (The former generates an Emchar, the latter a
Lisp object. Conceivably we should rename make_char() -> wrap_char()
and similarly for make_int(), make_float().)
Similar changes for other *CHAR* macros -- we now consistently use
names with `emchar' whenever we are working with Emchars. Any
remaining name with just `char' always refers to a Lisp object.
rename macros with XSTRING_* to string_* except for those that
reference actual fields in the Lisp_String object, following
conventions used elsewhere.
rename set_string_{data,length} macros (the only ones to work with
a Lisp_String_* instead of a Lisp_Object) to set_lispstringp_*
to make the difference clear.
try to be consistent about caps vs. lowercase in macro/inline-fun
names for chars and such, which wasn't the case before. we now
reserve caps either for XFOO_ macros that reference object fields
(e.g. XSTRING_DATA) or for things that have non-function semantics,
e.g. directly modifying an arg (BREAKUP_EMCHAR) or evaluating an
arg (any arg) more than once. otherwise, use lowercase.
here is a summary of most of the macros/inline funs changed by all
of the above changes:
BYTE_*_P -> byte_*_p
XSTRING_BYTE -> string_byte
set_string_data/length -> set_lispstringp_data/length
XSTRING_CHAR_LENGTH -> string_char_length
XSTRING_CHAR -> string_emchar
INTBYTE_FIRST_BYTE_P -> intbyte_first_byte_p
INTBYTE_LEADING_BYTE_P -> intbyte_leading_byte_p
charptr_copy_char -> charptr_copy_emchar
LEADING_BYTE_* -> leading_byte_*
CHAR_* -> EMCHAR_*
*_CHAR_* -> *_EMCHAR_*
*_CHAR -> *_EMCHAR
CHARSET_BY_ -> charset_by_*
BYTE_SHIFT_JIS* -> byte_shift_jis*
BYTE_BIG5* -> byte_big5*
REP_BYTES_BY_FIRST_BYTE -> rep_bytes_by_first_byte
char_to_unicode -> emchar_to_unicode
valid_char_p -> valid_emchar_p
Change intbyte_strcmp -> qxestrcmp_c (duplicated functionality).
-- INTERFACE CHANGES AFFECTING LESS CODE:
use DECLARE_INLINE_HEADER in various places.
remove '#ifdef emacs' from XEmacs-only files.
eliminate CHAR_TABLE_VALUE(), which duplicated the functionality
of get_char_table().
add BUFFER_TEXT_LOOP to simplify iterations over buffer text.
define typedefs for signed and unsigned types of fixed sizes
(INT_32_BIT, UINT_32_BIT, etc.).
create ALIGN_FOR_TYPE as a higher-level interface onto ALIGN_SIZE;
fix code to use it.
add charptr_emchar_len to return the text length of the character
pointed to by a ptr; use it in place of
charcount_to_bytecount(..., 1). add emchar_len to return the text
length of a given character.
add types Bytexpos and Charxpos to generalize Bytebpos/Bytecount
and Charbpos/Charcount, in code (particularly, the extents code
and redisplay code) that works with either kind of index. rename
redisplay struct params with names such as `charbpos' to
e.g. `charpos' when they are e.g. a Charxpos, not a Charbpos.
eliminate xxDEFUN in place of DEFUN; no longer necessary with
changes awhile back to doc.c.
split up big ugly combined list of EXFUNs in lisp.h on a
file-by-file basis, since other prototypes are similarly split.
rewrite some "*_UNSAFE" macros as inline funs and eliminate the
_UNSAFE suffix.
move most string code from lisp.h to text.h; the string code and
text.h code is now intertwined in such a fashion that they need
to be in the same place and partially interleaved. (you can't
create forward references for inline funs)
automated/lisp-tests.el, automated/symbol-tests.el, automated/test-harness.el: Fix test harness to output FAIL messages to stderr when in
batch mode.
Fix up some problems in lisp-tests/symbol-tests that were
causing spurious failures.
author | ben |
---|---|
date | Sun, 05 May 2002 11:33:57 +0000 |
parents | e7ef97881643 |
children | 712931b4b71d |
comparison
equal
deleted
inserted
replaced
825:eb3bc15a6e0f | 826:6728e641994e |
---|---|
8 For general XEmacs navigation tips: Press C-h t | 8 For general XEmacs navigation tips: Press C-h t |
9 | 9 |
10 The XEmacs Packages Quick Start Guide | 10 The XEmacs Packages Quick Start Guide |
11 ------------------------------------- | 11 ------------------------------------- |
12 | 12 |
13 This text is intended to help you get started installing a new XEmacs | 13 This text is intended to help you get started installing a new XEmacs and |
14 and its packages from start. For details see the 'Startup Paths' and | 14 its packages. For more details see the 'Startup Paths' and 'Packages' |
15 'Packages' sections of the XEmacs info manual. | 15 sections of the XEmacs info manual. |
16 | 16 |
17 * Real Real Quickstart FAQ | 17 * Real Real Quickstart FAQ |
18 -------------------------- | 18 -------------------------- |
19 | 19 |
20 Q. Do I need to have the packages to compile XEmacs? | 20 Q. Do I need to have the packages to compile XEmacs? |
21 A. No, XEmacs will build and install just fine without any packages | 21 |
22 installed. However, only the most basic editing functions will be | 22 A. Theoretically, no -- XEmacs will build and install just fine without any |
23 available with no packages installed, so installing packages is an | 23 packages installed. However, only the most basic editing functions will |
24 be available with no packages installed, so installing packages is an | |
24 essential part of making your installed XEmacs _useful_. | 25 essential part of making your installed XEmacs _useful_. |
25 | 26 |
26 Q. I really liked the old way that packages were bundled and do not | 27 Q. I really liked the old way that packages were bundled and do not |
27 want to mess with packages at all. | 28 want to mess with packages at all. |
29 | |
28 A. You can grab all the packages at once like you used to with old | 30 A. You can grab all the packages at once like you used to with old |
29 XEmacs versions, skip to the 'Sumo Tarball' section below. | 31 XEmacs versions, skip to the 'Sumo Tarball' section below. |
32 | |
33 Q. How do I tell XEmacs where to find the packages? | |
34 | |
35 A. Normally, you put the packages under $prefix/lib/packages, where | |
36 $prefix is specified using the `--prefix' parameter to `configure'. | |
37 (See `Package hierarchies' below). However, if you have the packages | |
38 somewhere else (e.g. you're a developer and are compiling the packages | |
39 yourself, and want your own private copy of everything), use the | |
40 `--package-path' parameter, something like this: | |
41 | |
42 configure --package-path="~/.xemacs::/src/xemacs/site-packages:/src/xemacs/xemacs-packages:/src/xemacs/mule-packages" ... | |
30 | 43 |
31 Q. After installing, I want XEmacs to do `foo', but when I invoke it | 44 Q. After installing, I want XEmacs to do `foo', but when I invoke it |
32 (or click the toolbar button or select the menu item), nothing (or | 45 (or click the toolbar button or select the menu item), nothing (or |
33 an error) happens, and it used to work. | 46 an error) happens, and it used to work. |
47 | |
34 A. See the first FAQ; you may be missing a package that is essential to | 48 A. See the first FAQ; you may be missing a package that is essential to |
35 you. You can either track it down and install it, or install the | 49 you. You can either track it down and install it, or install the |
36 `Sumo Tarball' (see the second FAQ). | 50 `Sumo Tarball' (see the second FAQ). |
37 | 51 |
38 * A note of caution | 52 * A note of caution |
42 minor hurdles on the way. Also neither the interface nor the structure is | 56 minor hurdles on the way. Also neither the interface nor the structure is |
43 set in stone. The XEmacs maintainers reserve the right to sacrifice | 57 set in stone. The XEmacs maintainers reserve the right to sacrifice |
44 backwards compatibility as quirks are worked out over the coming | 58 backwards compatibility as quirks are worked out over the coming |
45 releases. | 59 releases. |
46 | 60 |
47 * Some Package Theory | 61 * Some package theory |
48 --------------------- | 62 --------------------- |
49 | 63 |
50 In order to reduce the size and increase the maintainability of XEmacs, | 64 In order to reduce the size and increase the maintainability of XEmacs, |
51 the majority of the Elisp packages that came with previous releases | 65 the majority of the Elisp packages that came with previous releases |
52 have been unbundled. They have been replaced by the package system. | 66 have been unbundled. They have been replaced by the package system. |
58 path correctly, install autoloads, etc, etc. | 72 path correctly, install autoloads, etc, etc. |
59 | 73 |
60 * Package hierarchies | 74 * Package hierarchies |
61 --------------------- | 75 --------------------- |
62 | 76 |
63 On Startup XEmacs looks for packages in so called package hierarchies. | 77 On Startup XEmacs looks for packages in so-called package hierarchies. |
64 These can be specified by the 'package-path' parameter to the | 78 Normally, there are three system wide hierarchies, like this: |
65 'configure' script. However by default there are three system wide | 79 |
66 hierarchies. ("$prefix" defaults to "/usr/local") | 80 $prefix/lib/xemacs/xemacs-packages/ |
67 | |
68 $prefix/lib/xemacs/xemacs-packages | |
69 Normal packages go here. | 81 Normal packages go here. |
70 | 82 |
71 $prefix/lib/xemacs/mule-packages | 83 $prefix/lib/xemacs/mule-packages/ |
72 Mule packages go here and are only searched by MULE-enabled XEmacsen. | 84 Mule packages go here and are only searched by MULE-enabled XEmacsen. |
73 | 85 |
74 $prefix/lib/xemacs/site-packages/ | 86 $prefix/lib/xemacs/site-packages/ |
75 Local and 3rd party packages go here. | 87 Local and 3rd party packages go here. |
76 | 88 |
89 This is what you get when you untar the SUMO tarballs under | |
90 $prefix/lib/xemacs. | |
91 | |
92 $prefix is specified using the `--prefix' parameter to `configure', and | |
93 defaults to `usr/local'. | |
94 | |
95 If your packages are located in the above directories, XEmacs will | |
96 automatically find them at startup; however, if you have your packages | |
97 somewhere else (e.g. you're a developer and are compiling the packages | |
98 yourself, and want your own private copy of everything), you can tell | |
99 XEmacs specifically where to look for the packages by using the | |
100 `--package-path' parameter to the 'configure' script. Normally, it looks | |
101 like this: | |
102 | |
103 configure --package-path="~/.xemacs::/src/xemacs/site-packages:/src/xemacs/xemacs-packages:/src/xemacs/mule-packages" ... | |
104 | |
105 See `configure.usage' for more info about the format of this parameter. | |
77 | 106 |
78 * Where to get the packages | 107 * Where to get the packages |
79 --------------------------- | 108 --------------------------- |
80 | 109 |
81 Packages are available from ftp://ftp.xemacs.org/pub/xemacs/packages | 110 Packages are available from ftp://ftp.xemacs.org/pub/xemacs/packages |