| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
XEmacs provides the concept of 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. See section 40. Consoles and Devices. However, there are some features of the X Window System that do not generalize well, and they are covered specially here.
| 58.1 X Selections | Transferring text to and from other X clients. | |
| 58.2 X Server | Information about the X server connected to a particular device. | |
| 58.3 Miscellaneous X Functions and Variables | Other X-specific functions and variables. |
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
The X server records a set of selections which permit transfer of data between application programs. The various selections are distinguished by selection types, represented in XEmacs by symbols. X clients including XEmacs can read or set the selection for any given type.
Each possible type has its own selection value, which changes
independently. The usual values of type are PRIMARY and
SECONDARY; these are symbols with upper-case names, in accord
with X Windows conventions. The default is PRIMARY.
(In FSF Emacs, this function is called x-set-selection and
takes different arguments.)
nil, the secondary selection instead of
the primary selection is discarded.
The X server also has a set of numbered 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.
x-get-cut-buffer in FSF Emacs.)
Normally, the contents of the first cut buffer are simply replaced by
string. However, if optional argument push is
non-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 x-set-cut-buffer in FSF Emacs.
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
This section describes how to access and change the overall status of the X server XEmacs is using.
| 58.2.1 Resources | Getting resource values from the server. | |
| 58.2.2 Data about the X Server | Getting info about the X server. | |
| 58.2.3 Restricting Access to the Server by Other Apps | Restricting access to the server by other apps. |
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
string,
integer, natnum, or boolean, specifying the type of
object that the database is searched for.
global.
If omitted, it defaults to global.
default-x-device.
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.
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 name and class. For example, name could be `"modeline.attributeFont"', and class `"Face.AttributeFont"'.
Specifically,
|
is an interface to a C call something like
|
|
is an interface to a C call something like
|
|
is an interface to a C call something like
|
global, a call
|
is an interface to a C call something like
|
Note that for 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 nil if the queried
resource is not found. If type is string, a string is
returned, and if it is integer, an integer is returned. If
type is boolean, then the returned value is the list
(t) for true, (nil) for false, and is nil to mean
"unspecified".
By default, this variable is 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".
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
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.
static-gray,
gray-scale, static-color, pseudo-color,
true-color, and direct-color. (Note that this is different
from previous versions of XEmacs, which returned StaticGray,
GrayScale, etc.)
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
x-ungrab-keyboard
(use an unwind-protect). Returns t if the grab was
successful; nil otherwise.
x-grab-keyboard.
nil, the selected device
will be used. If optional cursor argument is non-nil,
change the pointer shape to that until x-ungrab-pointer is called
(it should be an object returned by the make-cursor function).
If the second optional argument ignore-keyboard is non-nil,
ignore all keyboard events during the grab. Returns t if the
grab is successful, nil otherwise.
x-grab-pointer.
If optional first arg device is nil the selected device is
used. If it is t the pointer will be released on all X devices.
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
nil, this is initialized from the
`"*bitmapFilePath"' resource. This is used by the
make-image-instance function (however, note that if the
environment variable `XBMLANGPATH' is set, it is consulted first).
read-color to find
`rgb.txt'.
nil, synthetic events are allowed. nil means
they are ignored. Beware: allowing XEmacs to process SendEvents opens a
big security hole.
x_error_handler. Your backtrace of the C stack will now be
useful. In asynchronous mode, the stack above x_error_handler
isn't helpful because of buffering.) If device is not specified,
the selected device is assumed.
Calling this function is the same as calling the C function
XSynchronize, or starting the program with the `-sync'
command line argument.
| [ << ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |