Mercurial > hg > xemacs-beta
view etc/gnuserv.README @ 938:0391335b65dc
[xemacs-hg @ 2002-07-31 07:14:49 by michaels]
2002-07-17 Marcus Crestani <crestani@informatik.uni-tuebingen.de>
Markus Kaltenbach <makalten@informatik.uni-tuebingen.de>
Mike Sperber <mike@xemacs.org>
configure flag to turn these changes on: --use-kkcc
First we added a dumpable flag to lrecord_implementation. It shows,
if the object is dumpable and should be processed by the dumper.
* lrecord.h (struct lrecord_implementation): added dumpable flag
(MAKE_LRECORD_IMPLEMENTATION): fitted the different makro definitions
to the new lrecord_implementation and their calls.
Then we changed mark_object, that it no longer needs a mark method for
those types that have pdump descritions.
* alloc.c:
(mark_object): If the object has a description, the new mark algorithm
is called, and the object is marked according to its description.
Otherwise it uses the mark method like before.
These procedures mark objects according to their descriptions. They
are modeled on the corresponding pdumper procedures.
(mark_with_description):
(get_indirect_count):
(structure_size):
(mark_struct_contents):
These procedures still call mark_object, this is needed while there are
Lisp_Objects without descriptions left.
We added pdump descriptions for many Lisp_Objects:
* extents.c: extent_auxiliary_description
* database.c: database_description
* gui.c: gui_item_description
* scrollbar.c: scrollbar_instance_description
* toolbar.c: toolbar_button_description
* event-stream.c: command_builder_description
* mule-charset.c: charset_description
* device-msw.c: devmode_description
* dialog-msw.c: mswindows_dialog_id_description
* eldap.c: ldap_description
* postgresql.c: pgconn_description
pgresult_description
* tooltalk.c: tooltalk_message_description
tooltalk_pattern_description
* ui-gtk.c: emacs_ffi_description
emacs_gtk_object_description
* events.c:
* events.h:
* event-stream.c:
* event-Xt.c:
* event-gtk.c:
* event-tty.c:
To write a pdump description for Lisp_Event, we converted every struct
in the union event to a Lisp_Object. So we created nine new
Lisp_Objects: Lisp_Key_Data, Lisp_Button_Data, Lisp_Motion_Data,
Lisp_Process_Data, Lisp_Timeout_Data, Lisp_Eval_Data,
Lisp_Misc_User_Data, Lisp_Magic_Data, Lisp_Magic_Eval_Data.
We also wrote makro selectors and mutators for the fields of the new
designed Lisp_Event and added everywhere these new abstractions.
We implemented XD_UNION support in (mark_with_description), so
we can describe exspecially console/device specific data with XD_UNION.
To describe with XD_UNION, we added a field to these objects, which
holds the variant type of the object. This field is initialized in
the appendant constructor. The variant is an integer, it has also to
be described in an description, if XD_UNION is used.
XD_UNION is used in following descriptions:
* console.c: console_description
(get_console_variant): returns the variant
(create_console): added variant initialization
* console.h (console_variant): the different console types
* console-impl.h (struct console): added enum console_variant contype
* device.c: device_description
(Fmake_device): added variant initialization
* device-impl.h (struct device): added enum console_variant devtype
* objects.c: image_instance_description
font_instance_description
(Fmake_color_instance): added variant initialization
(Fmake_font_instance): added variant initialization
* objects-impl.h (struct Lisp_Color_Instance): added color_instance_type
* objects-impl.h (struct Lisp_Font_Instance): added font_instance_type
* process.c: process_description
(make_process_internal): added variant initialization
* process.h (process_variant): the different process types
author | michaels |
---|---|
date | Wed, 31 Jul 2002 07:14:49 +0000 |
parents | 3ecd8885ac67 |
children | 807b51903ed4 |
line wrap: on
line source
This file is not meant to be proper documentation. See the file gnuserv.1 for more information. **** NOTE: This version of gnuserv has some enhancements over the original version distributed by Andy Norman. See the end of this file for more details. **** To install, copy gnuserv.el into a directory on your GNU Emacs load-path. Edit Makefile and change INCLUDES to point to the src directory underneath your emacs source tree (or make yourself a config.h file in this directory by hand, starting with config.h.proto as a first cut) and type: make This should compile the server and the two clients. Now put gnuserv, gnuclient and gnudoit in a directory that users have in their executable search paths. File : Description ---------------------------------------------------------------- Makefile : Makefile to build gnuserv LICENSE : GNU General License README : this file gnuclient.c : editor client C code gnudoit.c : eval client C code gnuserv.1 : gnuserv man page gnuserv.c : server C code gnuserv.el : server LISP code for GNU Emacs V18,V19, XEmacs/Lucid Emacs and Epoch V4 gnuserv.h : server/client C header file gnuslib.c : server/client C common code src.x11fns.diff : diffs to src/x11fns to raise window (for emacs18) config.h.proto : Use this file as the starting point for constructing a config.h if you don't have access to the one that was used when compiling your emacs. If you find *any* problems at all with gnuserv, or you can think of better ways of doing things (especially remote file access), please e-mail me at one of the addresses below. ange@hplb.hpl.hp.com ange@hpl.hp.co.uk ...!hplabs!hplb!ange ...!ukc!hplb!ange This version of gnuserv has been enhanced by a number of people, including Bob Weiner <weiner@mot.com>, Darrell Kindred <dkindred@cmu.edu>, Arup Mukherjee <arup@cmu.edu>, and Ben Wing <ben@xemacs.org>. The modifications are basically as follows: Bob Weiner: Integrated support for several versions of emacs. New requests from gnuclient cause the creation of new frames. Removed the restriction on the length of the string passed to gnudoit. Later added a server-done-function variable to control what happens to a buffer after the user is done with it. Mods to each of the .c files as well as gnuserv.el. Darrell Kindred: Removed the restriction on the length of the string returned from a gnudoit request, for the purposes of unix/internet sockets. Allow the gnudoit request to be read from stdin if it's not specified on the command line. Internet sockets are not opened unless the GNU_SECURE variable is specified. Unix sockets are created in a protected ancestral directory, since many Unix variants don't enforce socket permissions properly. An internet socket accepting local connections is not opened by default because this would make it possibly to override all security on the unix socket. See the man page for details. Unless told to do otherwise by a command-line argument, gnuclient and gnudoit now try to open a unix socket by default if support for them was compiled in. Mods to each of the .c files and to gnuserv.el. Arup Mukherjee: Removed the restriction on the length of the string returned from a gnudoit request, for the purposes of sysv ipc. Added support for the "gnuserv-frame" variable allowing you to specify control whether or not new screens are created in response to each gnuclient request. Made a number of other bugfixes and changes to the lisp part of the code, allowing gnuserv to work properly with newer emacs versions. All the changes are listed in the changelog at the beginning of gnuserv.el. Also fixed up the man page to reflect the new gnuserv features. On HPs, stopped the "-r" parameter (in gnuclient) from defaulting to /net/<remotehost>. Not all installations want this, and it's much harder to debug when things stop working. Changed the man page to reflect this. Mods to each of the .c files, gnuserv.el and gnuserv.1 More recently - added Xauth(1X11)-style authentication to gnuserv (as of version 2.1). Although the code is completely new, credit is due to Richard Caley <rjc@cogsci.edinburgh.ac.uk> ... he wrote a prototype implementation from which I borrowed the basic mechanism for hooking Xauth into gnuserv. Ben Wing: Added gnuattach.