Mercurial > hg > xemacs-beta
view lisp/x-win-sun.el @ 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 | 7039e6323819 |
children | 4cad7ff4a200 |
line wrap: on
line source
;;; x-win-sun.el --- runtime initialization for Sun X servers and keyboards ;; Copyright (C) 1993, 1994 Free Software Foundation, Inc. ;; Authors: jwz, ben, martin ;; Keywords: terminals ;; This file is part of XEmacs. ;; XEmacs is free software; you can redistribute it and/or modify it ;; under the terms of the GNU General Public License as published by ;; the Free Software Foundation; either version 2, or (at your option) ;; any later version. ;; XEmacs is distributed in the hope that it will be useful, but ;; WITHOUT ANY WARRANTY; without even the implied warranty of ;; MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU ;; General Public License for more details. ;; You should have received a copy of the GNU General Public License ;; along with XEmacs; see the file COPYING. If not, write to the ;; Free Software Foundation, Inc., 59 Temple Place - Suite 330, ;; Boston, MA 02111-1307, USA. ;;; Commentary: ;; This file is loaded by x-win.el at run-time when we are sure that XEmacs ;; is running on the display of a Sun. ;; The Sun X server (both the MIT and OpenWindows varieties) have extremely ;; stupid names for their keypad and function keys. For example, the key ;; labeled 3 / PgDn, with R15 written on the front, is actually called F35. ;; There are 3 methods of dealing with the Sun key brokenness: ;; ;; - Use xmodmap to give all keys more sensible names for all apps: ;; I use this shell script: ;; ;; for i in 0 1 2 3 4 5 6 7 8 9 Add Subtract Multiply Divide Decimal ; do ;; echo "keysym KP-$i = KP-$i" ;; done | xmodmap ;; ;; Clearly, as a good X11 citizen, we can't do this. ;; ;; - Use keyboard-translate-table to remap the keybindings at a low level. ;; This approach is taken in the function `sun-x11-keyboard-translate'. ;; This is like running xmodmap within XEmacs only. ;; This is not the default, however, so that legacy keybindings in users' ;; .emacs files like (global-set-key [(f35)] 'foo) continue to work ;; ;; - Use keyboard macros to provide indirection for keybindings. ;; If we do (global-set-key [(f35)] [(kp-3)]), then the user's keybindings ;; work whether he uses `f35' or `kp-3'. ;; This is also compatible with FSF Emacs and other X11 apps. ;; Although this has the disadvantage that these remappings ;; only work with the global key map, we use this as the default. ;; ;; - The Right Way to do this remains to be written... ;; OK, here's another try at doing things the right way. ;; We use function-key-map, which honors explicit key-bindings for the ;; stupid Sun names, but also allows indirection if no explicit ;; key-binding exists. ;;; Code: (globally-declare-fboundp '(x-keysym-on-keyboard-sans-modifiers-p)) ;;;###autoload (defun x-win-init-sun () ;; help is ok ;; num_lock is ok ;; up is ok ;; left is ok ;; right is ok ;; kp-add is ok ;; down is ok ;; insert is ok ;; delete is ok ;; kp-enter is ok ;; Sun Function keys (loop for (from-key to-key) in `((f21 pause) (f22 print) (f23 scroll_lock) ;; X11 R6 mappings (SunProps props) (SunFront front) (SunOpen open) (SunFind find) (cancel stop) (Undo undo) (SunCopy copy) (SunPaste paste) (SunCut cut) (f13 props) (f14 undo) (f15 front) (f16 copy) (f17 open) (f18 paste) (f19 find) (f20 cut) (f25 kp-divide) (f26 kp-multiply) (f31 kp-5) ;; Map f33 and r13 to end or kp-end ,@(cond ((not (x-keysym-on-keyboard-sans-modifiers-p 'end)) '((f33 end) (r13 end))) ((not (x-keysym-on-keyboard-sans-modifiers-p 'kp-end)) '((f33 kp-end) (r13 kp-end)))) ,@(when (x-keysym-on-keyboard-sans-modifiers-p 'f36) '((f36 stop) (f37 again))) ;; Type 4 keyboards have a real kp-subtract and a f24 labelled `=' ;; Type 5 keyboards have no key labelled `=' and a f24 labelled `-' ,@(when (x-keysym-on-keyboard-sans-modifiers-p 'f24) `((f24 ,(if (x-keysym-on-keyboard-sans-modifiers-p 'kp-subtract) 'kp-equal 'kp-subtract)))) ;; Map f27 to home or kp-home, as appropriate ,@(cond ((not (x-keysym-on-keyboard-sans-modifiers-p 'home)) '((f27 home))) ((not (x-keysym-on-keyboard-sans-modifiers-p 'kp-home)) '((f27 kp-home)))) ;; Map f29 to prior or kp-prior, as appropriate ,@(cond ((not (x-keysym-on-keyboard-sans-modifiers-p 'prior)) '((f29 prior))) ((not (x-keysym-on-keyboard-sans-modifiers-p 'kp-prior)) '((f29 kp-prior)))) ;; Map f35 to next or kp-next, as appropriate ,@(cond ((not (x-keysym-on-keyboard-sans-modifiers-p 'next)) '((f35 next))) ((not (x-keysym-on-keyboard-sans-modifiers-p 'kp-next)) '((f35 kp-next)))) ,@(cond ((x-keysym-on-keyboard-sans-modifiers-p 'apRead) ; SunOS 4.1.1 '((apRead f11) (apEdit f12))) ((x-keysym-on-keyboard-sans-modifiers-p 'SunF36) ; SunOS 5 '((SunF36 f11) (SunF37 f12) (f11 stop) (f12 again)))) ) do (when (x-keysym-on-keyboard-sans-modifiers-p from-key) (dolist (prefix '(() (shift) (control) (meta) (alt) (shift control) (shift alt) (shift meta) (control alt) (control meta) (alt meta) (shift control alt) (shift control meta) (shift alt meta) (control alt meta) (shift control alt meta))) (define-key function-key-map (append prefix (list from-key)) (vector (append prefix (list to-key))))))) ;; for each element in the left column of the above table, alias it ;; to the thing in the right column. Then do the same for many, but ;; not all, modifier combinations. ;; ;; (Well, we omit hyper and super. #### Handle this some other way!) ;; (while mapping ;; (let ((mods '(() (shift) (control) (meta) (alt)))) ;; (while mods ;; (let ((k1 (vector (append (car mods) (list (car (car mapping)))))) ;; (k2 (vector (append (car mods) (list (cdr (car mapping))))))) ;; (define-key global-map k1 k2)) ;; (setq mods (cdr mods)))) ;; (setq mapping (cdr mapping)))) ;;; I've extended keyboard-translate-table to work over keysyms. ;;; [FSF Emacs has something called `system-key-alist' that is ;;; supposed to accomplish approximately the same thing. Unfortunately, ;;; it's brain-dead in the typically FSF way, and associates *numbers* ;;; (who knows where the hell they come from?) with symbols.] --ben ;;; And I've made it into a function which is NOT called by default --martin (defun sun-x11-keyboard-translate () "Remap Sun's X11 keyboard. Keys with names like `f35' are remapped, at a low level, to more mnemonic ones,like `kp-3'." (interactive) (keyboard-translate 'f11 'stop ; the type4 keyboard Sun/MIT name 'f36 'stop ; the type5 keyboard Sun name 'cancel 'stop ; R6 binding 'f12 'again ; the type4 keyboard Sun/MIT name 'f37 'again ; the type5 keyboard Sun name 'f13 'props ; 'SunProps 'props ; R6 binding 'f14 'undo ; 'f15 'front ; 'SunFront 'front ; R6 binding 'f16 'copy ; 'SunCopy 'copy ; R6 binding 'f17 'open ; 'SunOpen 'open ; R6 binding 'f18 'paste ; 'SunPaste 'paste ; R6 binding 'f19 'find ; 'f20 'cut ; 'SunCut 'cut ; R6 binding ;; help is ok 'f21 'pause 'f22 'prsc 'f23 'scroll ;; num_lock is ok ;;'f24 'kp-equal) ; type4 only! 'f25 'kp-divide ; 'f26 'kp-multiply ; 'f24 'kp-subtract ; type5 only! 'f27 'kp-7 ; ;; up is ok 'f29 'kp-9 ;; left is ok 'f31 'kp-5 ;; right is ok ;; kp-add is ok 'f33 'kp-1 ; the Sun name 'r13 'end ; the MIT name ;; down is ok 'f35 'kp-3 ;; insert is ok ;; delete is ok ;; kp-enter is ok 'SunF36 'f11 ; Type 5 keyboards 'SunF37 'f12 ; Used to be Stop & Again )) ;;; OpenWindows-like "find" processing. ;;; As far as I know, the `find' key is a Sunism, so we do that binding ;;; here. This is the only Sun-specific keybinding. (The functions ;;; themselves are in x-win.el in case someone wants to use them when ;;; not running on a Sun display.) (or (lookup-key global-map 'find) (define-key global-map 'find 'ow-find)) (or (lookup-key global-map '(shift find)) (define-key global-map '(shift find) 'ow-find-backward)) ) ;;; x-win-sun.el ends here