annotate modules/README @ 3025:facf3239ba30
[xemacs-hg @ 2005-10-25 11:16:19 by ben]
rename new->new_, convert 'foo to `foo'
EmacsFrame.c, ExternalClient.c, ExternalShell.c, chartab.c, cmdloop.c, compiler.h, console.c, database.c, device-msw.c, device-x.c, device.c, doc.c, dragdrop.c, eval.c, event-msw.c, event-stream.c, events.c, extents.c, file-coding.c, fns.c, frame-tty.c, frame.c, gpmevent.c, gutter.c, hash.c, imgproc.c, indent.c, keymap.c, lisp-union.h, macros.c, malloc.c, marker.c, menubar-x.c, menubar.c, mule-charset.c, number.c, process.c, profile.h, ralloc.c, redisplay.c, select-common.h, select.c, syntax.c, sysfile.h, sysproc.h, systime.h, syswindows.h, toolbar.c, tooltalk.c, tparam.c, unexaix.c, unexalpha.c, unexconvex.c, unexec.c, unexhp9k800.c, unexmips.c, unicode.c, window.c: new -> new_.
'foo -> `foo'.
lwlib-internal.h: redo assert macros to follow lisp.h and not trigger warnings.
lwlib.c, xlwtabs.c: new -> new_.
| author |
ben |
| date |
Tue, 25 Oct 2005 11:16:49 +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.
|
