view modules/README @ 4318:4d0f773d5e21

Fix the test failures introduced by the non-ISO-2022 coding systems. APPROVE COMMIT NOTE: this patch has been committed. This is patch http://mid.gmane.org/18264.25814.828088.486899@parhasard.net tests/ChangeLog addition: 2007-12-06 Aidan Kehoe <kehoea@parhasard.net> * automated/mule-tests.el: Add a Known-Bug-Expect-Error call testing and documenting that we don't support all of the Unicode code space in a single session. * automated/test-harness.el (Known-Bug-Expect-Error): Provide Known-Bug-Expect-Error, analagous to Known-Bug-Expect-Failure and Check-Error. * automated/test-harness.el (Silence-Message): Dynamically bind the function definition of #'clear-message, as well as that of #'append-message, to nil. src/ChangeLog addition: 2007-12-06 Aidan Kehoe <kehoea@parhasard.net> * tests.c (Ftest_data_format_conversion): Move those tests that expect that iso-8859-2 is ISO 2022-compatible to testing iso-latin-2-with-esc instead.
author Aidan Kehoe <kehoea@parhasard.net>
date Sun, 09 Dec 2007 15:10:46 +0100
parents 25e260cb7994
children da1365dd3f07
line wrap: on
line source

This directory contains a number of XEmacs dynamic modules.  These
modules can be loaded directly with the command 'M-x load-module'.
However, the preferred method of loading a module is to issue a
"(require 'module-name)" command to the Lisp interpreter.  This will
store information so that a later "(unload-feature 'module-name)" can
succeed.

To compile one of these modules, simply enter the desired directory,
type 'configure', and then 'make'.  If you are building the module for
an installed XEmacs, then 'make install' will place the module in the
appropriate directory for XEmacs to find it later (assuming you have
permission to write to that directory).  A subsequent 'load-module' or
'require' will then load the module, as described above.

Each of these demonstrates different features and limitations of the
XEmacs module loading technology.  For a complete discussion on XEmacs
dynamic modules, please consult the XEmacs Module Writers Guide, which
can be found in the ../info directory.

For those wanting to get started with module writing, please see the
'sample' directory.  It contains two subdirectories: internal and
external.  The 'internal' subdirectory contains the framework needed to
migrate some core piece of XEmacs functionality into code that can
either be compiled into the core or built as a separate module.  The
'external' subdirectory contains the somewhat simpler framework needed
to build a module separately from XEmacs.  These should be considered
starting places for module writing.