Mercurial > hg > xemacs-beta
annotate modules/README @ 1346:01c57eb70ae9
[xemacs-hg @ 2003-03-09 02:27:27 by ben]
To: xemacs-patches@xemacs.org
i.c: Sleep between calls to check for I/O, since these calls are non-blocking.
behavior.el: Allow other keywords for forward compatibility.
cl-macs.el: Rewrite to eliminate byte-compiler warning when `return' is used
without `finally'.
cmdloop.el: Avoid truncated error messages for `end-of-file' and the like.
cmdloop.el: Avoid char-int error after syncing.
files.el: Eliminate byte-compile warnings.
printer.el: Fix line-width calculations.
#### This used to work. Someone's changes (perhaps by
Michael Sperber?) seem to have messed something up.
simple.el: Use new clear-left-side functions to avoid messages ending up on
the same line as other output.
xemacs.mak: Add override for info/ as well when separate source/build dirs.
xemacs.mak: Order sections in main build process and add comments. Add
additional dependencies to try and prevent later steps from
happening when failures in earlier steps have occurred.
Makefile.in.in: Order sections in main build process and add comments. Add
additional dependencies to try and prevent later steps from
happening when failures in earlier steps have occurred.
alloc.c: Don't arbitrarily clear Vconfigure_info_directory since it
messes up separate build/source dirs.
console.c, console.h, device-msw.c, device.c: Add accidentally omitted msprinter console and data descriptions.
print.c, console-msw.c: Add clear-left-side functionality to help keep stdio/stderr
output from separate sources on separate lines. Generalize
the different kinds of debugging output. Add dpa().
profile.c: Add better docs on Unix/Windows differences.
regex.c: Fix problems with rel-alloc compilation caused by previous patch.
emacs.c: Seg fault rather than abort on Cygwin, since gdb doesn't trap
aborts properly.
console-gtk-impl.h, console-gtk.h, console-msw.h, console-x-impl.h, console-x.h, dialog-gtk.c, dialog-x.c, event-msw.c, frame-gtk.c, frame-x.c, frameslots.h, glyphs-gtk.c, glyphs-x.c, gui-gtk.c, gui-x.c, inline.c, menubar-gtk.c, menubar-msw.c, menubar-x.c, scrollbar-gtk.c, scrollbar-x.c, ui-gtk.c: Delete popup-data object. Delete menubar_data field from frames,
since its usage is frame-specific. Delete menubar-msw.h,
gui-x.h, gui-gtk.h. Clean up handling of lwlib callback data
GCPRO'ing and add missing GCPRO recomputation in widget code.
author | ben |
---|---|
date | Sun, 09 Mar 2003 02:27:46 +0000 |
parents | 25e260cb7994 |
children | da1365dd3f07 |
rev | line source |
---|---|
996 | 1 This directory contains a number of XEmacs dynamic modules. These |
2 modules can be loaded directly with the command 'M-x load-module'. | |
3 However, the preferred method of loading a module is to issue a | |
4 "(require 'module-name)" command to the Lisp interpreter. This will | |
5 store information so that a later "(unload-feature 'module-name)" can | |
6 succeed. | |
388 | 7 |
996 | 8 To compile one of these modules, simply enter the desired directory, |
9 type 'configure', and then 'make'. If you are building the module for | |
10 an installed XEmacs, then 'make install' will place the module in the | |
11 appropriate directory for XEmacs to find it later (assuming you have | |
12 permission to write to that directory). A subsequent 'load-module' or | |
13 'require' will then load the module, as described above. | |
388 | 14 |
996 | 15 Each of these demonstrates different features and limitations of the |
16 XEmacs module loading technology. For a complete discussion on XEmacs | |
17 dynamic modules, please consult the XEmacs Module Writers Guide, which | |
18 can be found in the ../info directory. | |
388 | 19 |
996 | 20 For those wanting to get started with module writing, please see the |
21 'sample' directory. It contains two subdirectories: internal and | |
22 external. The 'internal' subdirectory contains the framework needed to | |
23 migrate some core piece of XEmacs functionality into code that can | |
24 either be compiled into the core or built as a separate module. The | |
25 'external' subdirectory contains the somewhat simpler framework needed | |
26 to build a module separately from XEmacs. These should be considered | |
27 starting places for module writing. |