view src/README @ 54163:09b6da7723eb

(kbd_buffer_store_event_hold): New function to store an event into kbd fifo, but with special handling of quit event; a quit event is saved for later, and further events are discarded until the saved quit event has been processed. (kbd_buffer_store_event): Use kbd_buffer_store_event_hold. (gen_help_event): Store help event in kbd fifo. (NREAD_INPUT_EVENTS): Remove. (read_avail_input): Adapt to new read_socket_hook interface. Remove allocation and initialization of local input_event buffer, as read_socket_hook stores events directly in fifo. Allocate and initialize local hold_quit event to handle postponed quit event (and store it if set by kbd_buffer_store_event_hold).
author Kim F. Storm <storm@cua.dk>
date Fri, 27 Feb 2004 23:46:31 +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.