Mercurial > hg > xemacs-beta
annotate modules/README @ 1279:cd0abfdb9e9d
[xemacs-hg @ 2003-02-09 09:33:42 by ben]
walk-windows, redisplay fixes
console-stream.c: Abort when any attempts to output a stream console are made.
Should be caught sooner.
event-msw.c: Don't redisplay() during sizing when the frame has not yet been
initialized completely.
event-stream.c, menubar-msw.c, menubar-x.c, menubar.c, menubar.h: Restore in_menu_callback. Bind it in menubar-{msw,x}.c when
calling filter functions and the like. Conditionalize on it, not
in_modal_loop, when issuing error in `next-event', otherwise we
bite the dust immediately -- event-msw.c purposely calls
Fnext_event() in a modal loop, and knows what it's doing.
redisplay-output.c: Formatting fixes.
redisplay.c, window.c, winslots.h: Delete lots of carcasses of attempts to add redisplay support for
font-lock -- `pre/post-redisplay-hook', unimplemented junk from
FSF (redisplay-end-trigger, `window-scroll-functions',
`window-size-change-functions'). If we want to port some
redisplay support from FSF, port the `fontified' property.
redisplay.c: Put in a check here (as well as redisplay_device()) for a stream
frame. We can get here directly through Lisp fun
`redisplay-frame'. Abort if frame not initialized.
redisplay.c: Check for stream frames/devices.
window.el: walk-windows was broken when a frame was given to WHICH-FRAMES.
it would loop forever. The FSF version fixes this but i didn't
sync to them because (a) it conses (bad for lazy-lock), (b) it
calls select-window.
author | ben |
---|---|
date | Sun, 09 Feb 2003 09:33:48 +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. |