Mercurial > hg > xemacs-beta
view man/lispref/x-windows.texi @ 4885:6772ce4d982b
Fix hash tables, #'member*, #'assoc*, #'eql compiler macros if bignums
lisp/ChangeLog addition:
2010-01-24 Aidan Kehoe <kehoea@parhasard.net>
Correct the semantics of #'member*, #'eql, #'assoc* in the
presence of bignums; change the integerp byte code to fixnump
semantics.
* bytecomp.el (fixnump, integerp, byte-compile-integerp):
Change the integerp byte code to fixnump; add a byte-compile
method to integerp using fixnump and numberp and avoiding a
funcall most of the time, since in the non-core contexts where
integerp is used, it's mostly distinguishing between fixnums and
things that are not numbers at all.
* byte-optimize.el (side-effect-free-fns, byte-after-unbind-ops)
(byte-compile-side-effect-and-error-free-ops):
Replace the integerp bytecode with fixnump; add fixnump to the
side-effect-free-fns. Add the other extended number type
predicates to the list in passing.
* obsolete.el (floatp-safe): Mark this as obsolete.
* cl.el (eql): Go into more detail in the docstring here. Don't
bother checking whether both arguments are numbers; one is enough,
#'equal will fail correctly if they have distinct types.
(subst): Replace a call to #'integerp (deciding whether to use
#'memq or not) with one to #'fixnump.
Delete most-positive-fixnum, most-negative-fixnum from this file;
they're now always in C, so they can't be modified from Lisp.
* cl-seq.el (member*, assoc*, rassoc*):
Correct these functions in the presence of bignums.
* cl-macs.el (cl-make-type-test): The type test for a fixnum is
now fixnump. Ditch floatp-safe, use floatp instead.
(eql): Correct this compiler macro in the presence of bignums.
(assoc*): Correct this compiler macro in the presence of bignums.
* simple.el (undo):
Change #'integerp to #'fixnump here, since we use #'delq with the
same value as ELT a few lines down.
src/ChangeLog addition:
2010-01-24 Aidan Kehoe <kehoea@parhasard.net>
Fix problems with #'eql, extended number types, and the hash table
implementation; change the Bintegerp bytecode to fixnump semantics
even on bignum builds, since #'integerp can have a fast
implementation in terms of #'fixnump for most of its extant uses,
but not vice-versa.
* lisp.h: Always #include number.h; we want the macros provided in
it, even if the various number types are not available.
* number.h (NON_FIXNUM_NUMBER_P): New macro, giving 1 when its
argument is of non-immediate number type. Equivalent to FLOATP if
WITH_NUMBER_TYPES is not defined.
* elhash.c (lisp_object_eql_equal, lisp_object_eql_hash):
Use NON_FIXNUM_NUMBER_P in these functions, instead of FLOATP,
giving more correct behaviour in the presence of the extended
number types.
* bytecode.c (Bfixnump, execute_optimized_program):
Rename Bintegerp to Bfixnump; change its semantics to reflect the
new name on builds with bignum support.
* data.c (Ffixnump, Fintegerp, syms_of_data, vars_of_data):
Always make #'fixnump available, even on non-BIGNUM builds;
always implement #'integerp in this file, even on BIGNUM builds.
Move most-positive-fixnum, most-negative-fixnum here from
number.c, so they are Lisp constants even on builds without number
types, and attempts to change or bind them error.
Use the NUMBERP and INTEGERP macros even on builds without
extended number types.
* data.c (fixnum_char_or_marker_to_int):
Rename this function from integer_char_or_marker_to_int, to better
reflect the arguments it accepts.
* number.c (Fevenp, Foddp, syms_of_number):
Never provide #'integerp in this file. Remove #'oddp,
#'evenp; their implementations are overridden by those in cl.el.
* number.c (vars_of_number):
most-positive-fixnum, most-negative-fixnum are no longer here.
man/ChangeLog addition:
2010-01-23 Aidan Kehoe <kehoea@parhasard.net>
Generally: be careful to say fixnum, not integer, when talking
about fixed-precision integral types. I'm sure I've missed
instances, both here and in the docstrings, but this is a decent
start.
* lispref/text.texi (Columns):
Document where only fixnums, not integers generally, are accepted.
(Registers):
Remove some ancient char-int confoundance here.
* lispref/strings.texi (Creating Strings, Creating Strings):
Be more exact in describing where fixnums but not integers in
general are accepted.
(Creating Strings): Use a more contemporary example to illustrate
how concat deals with lists including integers about #xFF. Delete
some obsolete documentation on same.
(Char Table Types): Document that only fixnums are accepted as
values in syntax tables.
* lispref/searching.texi (String Search, Search and Replace):
Be exact in describing where fixnums but not integers in general
are accepted.
* lispref/range-tables.texi (Range Tables): Be exact in describing
them; only fixnums are accepted to describe ranges.
* lispref/os.texi (Killing XEmacs, User Identification)
(Time of Day, Time Conversion):
Be more exact about using fixnum where only fixed-precision
integers are accepted.
* lispref/objects.texi (Integer Type): Be more exact (and
up-to-date) about the possible values for
integers. Cross-reference to documentation of the bignum extension.
(Equality Predicates):
(Range Table Type):
(Array Type): Use fixnum, not integer, to describe a
fixed-precision integer.
(Syntax Table Type): Correct some English syntax here.
* lispref/numbers.texi (Numbers): Change the phrasing here to use
fixnum to mean the fixed-precision integers normal in emacs.
Document that our terminology deviates from that of Common Lisp,
and that we're working on it.
(Compatibility Issues): Reiterate the Common Lisp versus Emacs
Lisp compatibility issues.
(Comparison of Numbers, Arithmetic Operations):
* lispref/commands.texi (Command Loop Info, Working With Events):
* lispref/buffers.texi (Modification Time):
Be more exact in describing where fixnums but not integers in
general are accepted.
author | Aidan Kehoe <kehoea@parhasard.net> |
---|---|
date | Sun, 24 Jan 2010 15:21:27 +0000 |
parents | 33f0f28b945c |
children | 9fae6227ede5 |
line wrap: on
line source
@c -*-texinfo-*- @c This is part of the XEmacs Lisp Reference Manual. @c Copyright (C) 1990, 1991, 1992, 1993 Free Software Foundation, Inc. @c See the file lispref.texi for copying conditions. @setfilename ../../info/x-windows.texinfo @node X-Windows, ToolTalk Support, System Interface, Top @chapter Functions Specific to the X Window System @cindex X @cindex X-Windows @c This section is largely different from the one in FSF Emacs. XEmacs provides the concept of @dfn{devices}, which generalizes connections to an X server, a TTY device, etc. Most information about an X server that XEmacs is connected to can be determined through general console and device functions. @xref{Consoles and Devices}. However, there are some features of the X Window System that do not generalize well, and they are covered specially here. @menu * X Selections:: Transferring text to and from other X clients. * X Server:: Information about the X server connected to a particular device. * X Miscellaneous:: Other X-specific functions and variables. @end menu @node X Selections @section X Selections @cindex selection (for X windows) The X server records a set of @dfn{selections} which permit transfer of data between application programs. The various selections are distinguished by @dfn{selection types}, represented in XEmacs by symbols. X clients including XEmacs can read or set the selection for any given type. @defun x-own-selection data &optional type This function sets a ``selection'' in the X server. It takes two arguments: a value, @var{data}, and the selection type @var{type} to assign it to. @var{data} may be a string, a cons of two markers, or an extent. In the latter cases, the selection is considered to be the text between the markers, or between the extent's endpoints. Each possible @var{type} has its own selection value, which changes independently. The usual values of @var{type} are @code{PRIMARY} and @code{SECONDARY}; these are symbols with upper-case names, in accord with X Windows conventions. The default is @code{PRIMARY}. (In FSF Emacs, this function is called @code{x-set-selection} and takes different arguments.) @end defun @defun x-get-selection This function accesses selections set up by XEmacs or by other X clients. It returns the value of the current primary selection. @end defun @defun x-disown-selection &optional secondary-p Assuming we own the selection, this function disowns it. If @var{secondary-p} is non-@code{nil}, the secondary selection instead of the primary selection is discarded. @end defun @cindex cut buffer The X server also has a set of numbered @dfn{cut buffers} which can store text or other data being moved between applications. Cut buffers are considered obsolete, but XEmacs supports them for the sake of X clients that still use them. @defun x-get-cutbuffer &optional n This function returns the contents of cut buffer number @var{n}. (This function is called @code{x-get-cut-buffer} in FSF Emacs.) @end defun @defun x-store-cutbuffer string &optional push This function stores @var{string} into the first cut buffer (cut buffer 0). Normally, the contents of the first cut buffer are simply replaced by @var{string}. However, if optional argument @var{push} is non-@code{nil}, the cut buffers are rotated. This means that the previous value of the first cut buffer moves to the second cut buffer, and the second to the third, and so on, moving the other values down through the series of cut buffers, kill-ring-style. There are 8 cut buffers altogether. Cut buffers are considered obsolete; you should use selections instead. This function has no effect if support for cut buffers was not compiled in. This function is called @code{x-set-cut-buffer} in FSF Emacs. @end defun @node X Server @section X Server This section describes how to access and change the overall status of the X server XEmacs is using. @menu * Resources:: Getting resource values from the server. * Server Data:: Getting info about the X server. * Grabs:: Restricting access to the server by other apps. @end menu @node Resources @subsection Resources @defun default-x-device This function return the default X device for resourcing. This is the first-created X device that still exists. @end defun @defun x-get-resource name class type &optional locale device noerror This function retrieves a resource value from the X resource manager. @itemize @bullet @item The first arg is the name of the resource to retrieve, such as @samp{"font"}. @item The second arg is the class of the resource to retrieve, like @samp{"Font"}. @item The third arg should be one of the symbols @code{string}, @code{integer}, @code{natnum}, or @code{boolean}, specifying the type of object that the database is searched for. @item The fourth arg is the locale to search for the resources on, and can currently be a buffer, a frame, a device, or the symbol @code{global}. If omitted, it defaults to @code{global}. @item The fifth arg is the device to search for the resources on. (The resource database for a particular device is constructed by combining non-device- specific resources such any command-line resources specified and any app-defaults files found [or the fallback resources supplied by XEmacs, if no app-defaults file is found] with device-specific resources such as those supplied using @samp{xrdb}.) If omitted, it defaults to the device of @var{locale}, if a device can be derived (i.e. if @var{locale} is a frame or device), and otherwise defaults to the value of @code{default-x-device}. @item The sixth arg @var{noerror}, if non-@code{nil}, means do not signal an error if a bogus resource specification was retrieved (e.g. if a non-integer was given when an integer was requested). In this case, a warning is issued instead. @end itemize The resource names passed to this function are looked up relative to the locale. If you want to search for a subresource, you just need to specify the resource levels in @var{name} and @var{class}. For example, @var{name} could be @samp{"modeline.attributeFont"}, and @var{class} @samp{"Face.AttributeFont"}. Specifically, @enumerate @item If @var{locale} is a buffer, a call @example @code{(x-get-resource "foreground" "Foreground" 'string @var{some-buffer})} @end example is an interface to a C call something like @example @code{XrmGetResource (db, "xemacs.buffer.@var{buffer-name}.foreground", "Emacs.EmacsLocaleType.EmacsBuffer.Foreground", "String");} @end example @item If @var{locale} is a frame, a call @example @code{(x-get-resource "foreground" "Foreground" 'string @var{some-frame})} @end example is an interface to a C call something like @example @code{XrmGetResource (db, "xemacs.frame.@var{frame-name}.foreground", "Emacs.EmacsLocaleType.EmacsFrame.Foreground", "String");} @end example @item If @var{locale} is a device, a call @example @code{(x-get-resource "foreground" "Foreground" 'string @var{some-device})} @end example is an interface to a C call something like @example @code{XrmGetResource (db, "xemacs.device.@var{device-name}.foreground", "Emacs.EmacsLocaleType.EmacsDevice.Foreground", "String");} @end example @item If @var{locale} is the symbol @code{global}, a call @example @code{(x-get-resource "foreground" "Foreground" 'string 'global)} @end example is an interface to a C call something like @example @code{XrmGetResource (db, "xemacs.foreground", "Emacs.Foreground", "String");} @end example @end enumerate Note that for @code{global}, no prefix is added other than that of the application itself; thus, you can use this locale to retrieve arbitrary application resources, if you really want to. The returned value of this function is @code{nil} if the queried resource is not found. If @var{type} is @code{string}, a string is returned, and if it is @code{integer}, an integer is returned. If @var{type} is @code{boolean}, then the returned value is the list @code{(t)} for true, @code{(nil)} for false, and is @code{nil} to mean ``unspecified''. @end defun @defun x-put-resource resource-line &optional device This function adds a resource to the resource database for @var{device}. @var{resource-line} specifies the resource to add and should be a standard resource specification. @end defun @defvar x-emacs-application-class This variable holds The X application class of the XEmacs process. This controls, among other things, the name of the ``app-defaults'' file that XEmacs will use. For changes to this variable to take effect, they must be made before the connection to the X server is initialized, that is, this variable may only be changed before XEmacs is dumped, or by setting it in the file @file{lisp/term/x-win.el}. By default, this variable is @code{nil} at startup. When the connection to the X server is first initialized, the X resource database will be consulted and the value will be set according to whether any resources are found for the application class ``XEmacs''. @end defvar @node Server Data @subsection Data about the X Server This section describes functions and a variable that you can use to get information about the capabilities and origin of the X server corresponding to a particular device. The device argument is generally optional and defaults to the selected device. @defun x-server-version &optional device This function returns the list of version numbers of the X server @var{device} is on. The returned value is a list of three integers: the major and minor version numbers of the X protocol in use, and the vendor-specific release number. @end defun @defun x-server-vendor &optional device This function returns the vendor supporting the X server @var{device} is on. @end defun @defun x-display-visual-class &optional device This function returns the visual class of the display @var{device} is on. The value is one of the symbols @code{static-gray}, @code{gray-scale}, @code{static-color}, @code{pseudo-color}, @code{true-color}, and @code{direct-color}. (Note that this is different from previous versions of XEmacs, which returned @code{StaticGray}, @code{GrayScale}, etc.) @end defun @node Grabs @subsection Restricting Access to the Server by Other Apps @defun x-grab-keyboard &optional device This function grabs the keyboard on the given device (defaulting to the selected one). So long as the keyboard is grabbed, all keyboard events will be delivered to XEmacs---it is not possible for other X clients to eavesdrop on them. Ungrab the keyboard with @code{x-ungrab-keyboard} (use an @code{unwind-protect}). Returns @code{t} if the grab was successful; @code{nil} otherwise. @end defun @defun x-ungrab-keyboard &optional device This function releases a keyboard grab made with @code{x-grab-keyboard}. @end defun @defun x-grab-pointer &optional device cursor ignore-keyboard This function grabs the pointer and restricts it to its current window. If optional @var{device} argument is @code{nil}, the selected device will be used. If optional @var{cursor} argument is non-@code{nil}, change the pointer shape to that until @code{x-ungrab-pointer} is called (it should be an object returned by the @code{make-cursor} function). If the second optional argument @var{ignore-keyboard} is non-@code{nil}, ignore all keyboard events during the grab. Returns @code{t} if the grab is successful, @code{nil} otherwise. @end defun @defun x-ungrab-pointer &optional device This function releases a pointer grab made with @code{x-grab-pointer}. If optional first arg @var{device} is @code{nil} the selected device is used. If it is @code{t} the pointer will be released on all X devices. @end defun @node X Miscellaneous @section Miscellaneous X Functions and Variables @defvar x-bitmap-file-path This variable holds a list of the directories in which X bitmap files may be found. If @code{nil}, this is initialized from the @samp{"*bitmapFilePath"} resource. This is used by the @code{make-image-instance} function (however, note that if the environment variable @samp{XBMLANGPATH} is set, it is consulted first). @end defvar @defvar x-library-search-path This variable holds the search path used by @code{read-color} to find @file{rgb.txt}. @end defvar @defun x-valid-keysym-name-p keysym This function returns true if @var{keysym} names a keysym that the X library knows about. Valid keysyms are listed in the files @file{/usr/include/X11/keysymdef.h} and in @file{/usr/lib/X11/XKeysymDB}, or whatever the equivalents are on your system. @end defun @defun x-window-id &optional frame This function returns the ID of the X11 window. This gives us a chance to manipulate the Emacs window from within a different program. Since the ID is an unsigned long, we return it as a string. @end defun @defvar x-allow-sendevents If non-@code{nil}, synthetic events are allowed. @code{nil} means they are ignored. Beware: allowing XEmacs to process SendEvents opens a big security hole. @end defvar @defun x-debug-mode arg &optional device With a true arg, make the connection to the X server synchronous. With false, make it asynchronous. Synchronous connections are much slower, but are useful for debugging. (If you get X errors, make the connection synchronous, and use a debugger to set a breakpoint on @code{x_error_handler}. Your backtrace of the C stack will now be useful. In asynchronous mode, the stack above @code{x_error_handler} isn't helpful because of buffering.) If @var{device} is not specified, the selected device is assumed. Calling this function is the same as calling the C function @code{XSynchronize}, or starting the program with the @samp{-sync} command line argument. @end defun @defvar x-debug-events If non-zero, debug information about events that XEmacs sees is displayed. Information is displayed on stderr. Currently defined values are: @itemize @bullet @item 1 == non-verbose output @item 2 == verbose output @end itemize @end defvar