Mercurial > emacs
view src/README @ 53880:c3e8576e5ba2
(FRINGE_ID_BITS): New definition for number of
bits allocated to hold a fringe number. Increase number of bits
from 4 to 8 to allow user defined fringe bitmaps.
(struct glyph_row, struct it): New members left_user_fringe_bitmap,
left_user_fringe_face_id, right_user_fringe_bitmap,
right_user_fringe_face_id.
(enum fringe_bitmap_type, struct fringe_bitmap, fringe_bitmaps):
Move to new file fringe.c.
(MAX_FRINGE_BITMAPS): Define here.
(struct draw_fringe_bitmap_params): New members bits, cursor_p,
and overlay_p. Change member which to int.
(struct redisplay_interface): New members define_fringe_bitmap
and destroy_fringe_bitmap.
(valid_fringe_bitmap_id_p): Add prototype.
(w32_init_fringe, w32_reset_fringes) [WINDOWS_NT]: Add prototypes.
author | Kim F. Storm <storm@cua.dk> |
---|---|
date | Sun, 08 Feb 2004 23:18:36 +0000 |
parents | 7ca787d18982 |
children | 68cfc1db0d26 |
line wrap: on
line source
This directory contains the source files for the C component of GNU Emacs. Nothing in this directory is needed for using Emacs once it is built and installed, if the dumped Emacs (on Unix systems) or the Emacs executable and map files (on VMS systems) are copied elsewhere. See the files ../README and then ../INSTALL for installation instructions. Under GNU and Unix systems, the file `Makefile.in' is used as a template by the script `../configure' to produce `Makefile.c'. The same script then uses `cpp' to produce the machine-dependent `Makefile' from `Makefile.c'; `Makefile' is the file which actually controls the compilation of Emacs. Most of this should work transparently to the user; you should only need to run `../configure', and then type `make'. See the file VMSBUILD in this directory for instructions on compiling, linking and building Emacs on VMS. The files `*.com' and `temacs.opt' are used on VMS only. The files `vlimit.h', `ioclt.h' and `param.h' are stubs to allow compilation on VMS with the minimum amount of #ifdefs. `uaf.h' contains VMS uaf structure definitions. This is only needed if you define READ_SYSUAF. This should only be done for single-user systems where you are not overly concerned with security, since it either requires that you install Emacs with SYSPRV or make SYSUAF.DAT world readable. Otherwise, Emacs can determine information about the current user, but no one else.