|
0
|
1 @c -*-texinfo-*-
|
|
|
2 @c This is part of the XEmacs Lisp Reference Manual.
|
|
|
3 @c Copyright (C) 1995, 1996 Ben Wing.
|
|
|
4 @c See the file lispref.texi for copying conditions.
|
|
|
5 @setfilename ../../info/specifiers.info
|
|
|
6 @node Specifiers, Faces and Window-System Objects, Extents, top
|
|
|
7 @chapter Specifiers
|
|
|
8 @cindex specifier
|
|
|
9
|
|
|
10 A specifier is an object used to keep track of a property whose value
|
|
|
11 may vary depending on the particular situation (e.g. particular buffer
|
|
|
12 displayed in a particular window) that it is used in. The value of many
|
|
|
13 built-in properties, such as the font, foreground, background, and such
|
|
|
14 properties of a face and variables such as
|
|
|
15 @code{modeline-shadow-thickness} and @code{top-toolbar-height}, is
|
|
|
16 actually a specifier object. The specifier object, in turn, is
|
|
|
17 ``instanced'' in a particular situation to yield the real value
|
|
|
18 of the property in that situation.
|
|
|
19
|
|
|
20 @defun specifierp object
|
|
|
21 This function returns non-@code{nil} if @var{object} is a specifier.
|
|
|
22 @end defun
|
|
|
23
|
|
|
24 @menu
|
|
|
25 * Introduction to Specifiers:: Specifiers provide a clean way for
|
|
|
26 display and other properties to vary
|
|
|
27 (under user control) in a wide variety
|
|
|
28 of contexts.
|
|
|
29 * Specifiers In-Depth:: Gory details about specifier innards.
|
|
|
30 * Specifier Instancing:: Instancing means obtaining the ``value'' of
|
|
|
31 a specifier in a particular context.
|
|
|
32 * Specifier Types:: Specifiers come in different flavors.
|
|
|
33 * Adding Specifications:: Specifications control a specifier's ``value''
|
|
|
34 by giving conditions under which a
|
|
|
35 particular value is valid.
|
|
|
36 * Retrieving Specifications:: Querying a specifier's specifications.
|
|
|
37 * Specifier Tag Functions:: Working with specifier tags.
|
|
|
38 * Specifier Instancing Functions::
|
|
|
39 Functions to instance a specifier.
|
|
|
40 * Specifier Example:: Making all this stuff clearer.
|
|
|
41 * Creating Specifiers:: Creating specifiers for your own use.
|
|
|
42 * Specifier Validation Functions::
|
|
|
43 Validating the components of a specifier.
|
|
|
44 * Other Specification Functions::
|
|
|
45 Other ways of working with specifications.
|
|
|
46 @end menu
|
|
|
47
|
|
|
48 @node Introduction to Specifiers
|
|
|
49 @section Introduction to Specifiers
|
|
|
50
|
|
|
51 Sometimes you may want the value of a property to vary depending on
|
|
|
52 the context the property is used in. A simple example of this in XEmacs
|
|
|
53 is buffer-local variables. For example, the variable
|
|
|
54 @code{modeline-format}, which controls the format of the modeline, can
|
|
|
55 have different values depending on the particular buffer being edited.
|
|
|
56 The variable has a default value which most modes will use, but a
|
|
|
57 specialized package such as Calendar might change the variable so
|
|
|
58 as to tailor the modeline to its own purposes.
|
|
|
59
|
|
|
60 Other properties (such as those that can be changed by the
|
|
|
61 @code{modify-frame-parameters} function, for example the color of the
|
|
|
62 text cursor) can have frame-local values, although it might also make
|
|
|
63 sense for them to have buffer-local values. In other cases, you might
|
|
|
64 want the property to vary depending on the particular window within the
|
|
|
65 frame that applies (e.g. the top or bottom window in a split frame), the
|
|
|
66 device type that that frame appears on (X or tty), etc. Perhaps you can
|
|
|
67 envision some more complicated scenario where you want a particular
|
|
|
68 value in a specified buffer, another value in all other buffers
|
|
|
69 displayed on a particular frame, another value in all other buffers
|
|
|
70 displayed in all other frames on any mono (two-color, e.g. black and
|
|
|
71 white only) displays, and a default value in all other circumstances.
|
|
|
72
|
|
|
73 A @dfn{specifier} is a generalization of this, allowing a great deal
|
|
|
74 of flexibility in controlling exactly what value a property has in which
|
|
|
75 circumstances. It is most commonly used for display properties, such as
|
|
|
76 an image or the foreground color of a face. As a simple example, you can
|
|
|
77 specify that the foreground of the default face be
|
|
|
78
|
|
|
79 @itemize @bullet
|
|
|
80 @item
|
|
|
81 blue for a particular buffer
|
|
|
82 @item
|
|
|
83 green for all other buffers
|
|
|
84 @end itemize
|
|
|
85
|
|
|
86 As a more complicated example, you could specify that the foreground of
|
|
|
87 the default face be
|
|
|
88
|
|
|
89 @itemize @bullet
|
|
|
90 @item
|
|
|
91 forest green for all buffers displayed in a particular Emacs window, or
|
|
|
92 green if the X server doesn't recognize the color @samp{forest green}
|
|
|
93 @item
|
|
|
94 blue for all buffers displayed in a particular frame
|
|
|
95 @item
|
|
|
96 red for all other buffers displayed on a color device
|
|
|
97 @item
|
|
|
98 white for all other buffers
|
|
|
99 @end itemize
|
|
|
100
|
|
|
101 @node Specifiers In-Depth
|
|
|
102 @section In-Depth Overview of a Specifier
|
|
|
103 @cindex specification (in a specifier)
|
|
|
104 @cindex domain (in a specifier)
|
|
|
105 @cindex locale (in a specifier)
|
|
|
106 @cindex instantiator (in a specifier)
|
|
|
107 @cindex instancing (in a specifier)
|
|
|
108 @cindex instance (in a specifier)
|
|
|
109 @cindex inst-list (in a specifier)
|
|
|
110 @cindex inst-pair (in a specifier)
|
|
|
111 @cindex tag (in a specifier)
|
|
|
112 @cindex tag set (in a specifier)
|
|
|
113 @cindex specifier, specification
|
|
|
114 @cindex specifier, domain
|
|
|
115 @cindex specifier, locale
|
|
|
116 @cindex specifier, instantiator
|
|
|
117 @cindex specifier, instancing
|
|
|
118 @cindex specifier, instance
|
|
|
119 @cindex specifier, inst-list
|
|
|
120 @cindex specifier, inst-pair
|
|
|
121 @cindex specifier, tag
|
|
|
122 @cindex specifier, tag set
|
|
|
123
|
|
|
124 A specifier object encapsulates a set of @dfn{specifications}, each of
|
|
|
125 which says what its value should be if a particular condition applies.
|
|
|
126 For example, one specification might be ``The value should be
|
|
|
127 darkseagreen2 on X devices'' another might be ``The value should be blue
|
|
|
128 in the *Help* buffer''. In specifier terminology, these conditions are
|
|
|
129 called @dfn{locales} and the values are called @dfn{instantiators}.
|
|
|
130 Given a specifier, a logical question is ``What is its value in a
|
|
|
131 particular situation?'' This involves looking through the specifications
|
|
|
132 to see which ones apply to this particular situation, and perhaps
|
|
|
133 preferring one over another if more than one applies. In specifier
|
|
|
134 terminology, a ``particular situation'' is called a @dfn{domain}, and
|
|
|
135 determining its value in a particular domain is called @dfn{instancing}.
|
|
|
136 Most of the time, a domain is identified by a particular window. For
|
|
|
137 example, if the redisplay engine is drawing text in the default face in
|
|
|
138 a particular window, it retrieves the specifier for the foreground color
|
|
|
139 of the default face and @dfn{instances} it in the domain given by that
|
|
|
140 window; in other words, it asks the specifier, ``What is your value in
|
|
|
141 this window?''.
|
|
|
142
|
|
|
143 More specifically, a specifier contains a set of @dfn{specifications},
|
|
|
144 each of which associates a @dfn{locale} (a buffer object, a window
|
|
|
145 object, a frame object, a device object, or the symbol @code{global})
|
|
|
146 with an @dfn{inst-list}, which is a list of one or more
|
|
|
147 @dfn{inst-pairs}. (For each possible locale, there can be at most one
|
|
|
148 specification containing that locale.) Each inst-pair is a cons of a
|
|
|
149 @dfn{tag set} (an unordered list of zero or more symbols, or @dfn{tags})
|
|
|
150 and an @dfn{instantiator} (the allowed form of this varies depending on
|
|
|
151 the type of specifier). In a given specification, there may be more
|
|
|
152 than one inst-pair with the same tag set; this is unlike for locales.
|
|
|
153
|
|
|
154 The tag set is used to restrict the sorts of devices over which the
|
|
|
155 instantiator is valid and to uniquely identify instantiators added by a
|
|
|
156 particular application, so that different applications can work on the
|
|
|
157 same specifier and not interfere with each other. Each tag can have a
|
|
|
158 @dfn{predicate} associated with it, which is a function of one argument
|
|
|
159 (a device) that specifies whether the tag matches that particular
|
|
|
160 device. (If a tag does not have a predicate, it matches all devices.)
|
|
|
161 All tags in a tag set must match a device for the associated inst-pair
|
|
|
162 to be instantiable over that device. (A null tag set is perfectly
|
|
|
163 valid.)
|
|
|
164
|
|
|
165 The valid device types (normally @code{x}, @code{tty}, and
|
|
|
166 @code{stream}) and device classes (normally @code{color},
|
|
|
167 @code{grayscale}, and @code{mono}) can always be used as tags, and match
|
|
|
168 devices of the associated type or class (@pxref{Consoles and Devices}).
|
|
|
169 User-defined tags may be defined, with an optional predicate specified.
|
|
|
170 An application can create its own tag, use it to mark all its
|
|
|
171 instantiators, and be fairly confident that it will not interfere with
|
|
|
172 other applications that modify the same specifier -- Functions that add
|
|
|
173 a specification to a specifier usually only overwrite existing
|
|
|
174 inst-pairs with the same tag set as was given, and a particular tag or
|
|
|
175 tag set can be specified when removing instantiators.
|
|
|
176
|
|
|
177 When a specifier is instanced in a domain, both the locale and the tag
|
|
|
178 set can be viewed as specifying necessary conditions that must apply in
|
|
|
179 that domain for an instantiator to be considered as a possible result of
|
|
|
180 the instancing. More specific locales always override more general
|
|
|
181 locales (thus, there is no particular ordering of the specifications in
|
|
|
182 a specifier); however, the tag sets are simply considered in the order
|
|
|
183 that the inst-pairs occur in the specification's inst-list.
|
|
|
184
|
|
|
185 Note also that the actual object that results from the instancing
|
|
|
186 (called an @dfn{instance object}) may not be the same as the instantiator
|
|
|
187 from which it was derived. For some specifier types (such as integer
|
|
|
188 specifiers and boolean specifiers), the instantiator will be returned
|
|
|
189 directly as the instance object. For other types, however, this
|
|
|
190 is not the case. For example, for font specifiers, the instantiator
|
|
|
191 is a font-description string and the instance object is a font-instance
|
|
|
192 object, which describes how the font is displayed on a particular device.
|
|
|
193 A font-instance object encapsulates such things as the actual font name
|
|
|
194 used to display the font on that device (a font-description string
|
|
|
195 under X is usually a wildcard specification that may resolve to
|
|
|
196 different font names, with possibly different foundries, widths, etc.,
|
|
|
197 on different devices), the extra properties of that font on that
|
|
|
198 device, etc. Furthermore, this conversion (called @dfn{instantiation})
|
|
|
199 might fail -- a font or color might not exist on a particular device,
|
|
|
200 for example.
|
|
|
201
|
|
|
202 @node Specifier Instancing
|
|
|
203 @section How a Specifier Is Instanced
|
|
|
204 @cindex fallback (in a specifier)
|
|
|
205 @cindex specifier, fallback
|
|
|
206
|
|
|
207 Instancing of a specifier in a particular window domain proceeds as
|
|
|
208 follows:
|
|
|
209
|
|
|
210 @itemize @bullet
|
|
|
211 @item
|
|
|
212 First, XEmacs searches for a specification whose locale is the same as
|
|
|
213 the window's buffer. If that fails, the search is repeated, looking for
|
|
|
214 a locale that is the same as the window itself. If that fails, the
|
|
|
215 search is repeated using the window's frame, then using the device that
|
|
|
216 frame is on. Finally, the specification whose locale is the symbol
|
|
|
217 @code{global} (if there is such a specification) is considered.
|
|
|
218 @item
|
|
|
219 The inst-pairs contained in the specification that was found are
|
|
|
220 considered in their order in the inst-list, looking for one whose tag
|
|
|
221 set matches the device that is derived from the window domain. (The
|
|
|
222 tag set is an unordered list of zero or more tag symbols. For all
|
|
|
223 tags that have predicates associated with them, the predicate must
|
|
|
224 match the device.)
|
|
|
225 @item
|
|
|
226 If a matching tag set is found, the corresponding instantiator is passed
|
|
|
227 to the specifier's instantiation method, which is specific to the type
|
|
|
228 of the specifier. If it succeeds, the resulting instance object is
|
|
|
229 returned as the result of the instancing and the instancing is done.
|
|
|
230 Otherwise, the operation continues, looking for another matching
|
|
|
231 inst-pair in the current specification.
|
|
|
232 @item
|
|
|
233 When there are no more inst-pairs to be considered in the current
|
|
|
234 specification, the search starts over, looking for another specification
|
|
|
235 as in the first step above.
|
|
|
236 @item
|
|
|
237 If all specifications are exhausted and no instance object can be
|
|
|
238 derived, the instancing fails. (Actually, this is not completely true.
|
|
|
239 Some specifier objects for built-in properties have a @dfn{fallback}
|
|
|
240 value, which is either an inst-list or another specifier object, that is
|
|
|
241 consulted if the instancing is about to fail. If it is an inst-list,
|
|
|
242 the searching proceeds using the inst-pairs in that list. If it is a
|
|
|
243 specifier, the entire instancing starts over using that specifier
|
|
|
244 instead of the given one. Fallback values are set by the C code and
|
|
|
245 cannot be modified, except perhaps indirectly, using any Lisp functions.
|
|
|
246 The purpose of them is to supply some values to make sure that
|
|
|
247 instancing of built-in properties can't fail and to implement some basic
|
|
|
248 specifier inheritance, such as the fact that faces inherit their
|
|
|
249 properties from the @code{default} face.)
|
|
|
250 @end itemize
|
|
|
251
|
|
|
252 It is also possible to instance a specifier over a frame domain or
|
|
|
253 device domain instead of over a window domain. The C code, for example,
|
|
|
254 instances the @code{top-toolbar-height} variable over a frame domain in
|
|
|
255 order to determine the height of a frame's top toolbar. Instancing over
|
|
|
256 a frame or device is similar to instancing over a window except that
|
|
|
257 specifications for locales that cannot be derived from the domain are
|
|
|
258 ignored. Specifically, instancing over a frame looks first for frame
|
|
|
259 locales, then device locales, then the @code{global} locale. Instancing
|
|
|
260 over a device domain looks only for device locales and the @code{global}
|
|
|
261 locale.
|
|
|
262
|
|
|
263 @node Specifier Types
|
|
|
264 @section Specifier Types
|
|
|
265
|
|
|
266 There are various different types of specifiers. The type of a
|
|
|
267 specifier controls what sorts of instantiators are valid, how an
|
|
|
268 instantiator is instantiated, etc. Here is a list of built-in specifier
|
|
|
269 types:
|
|
|
270
|
|
|
271 @table @code
|
|
|
272 @item boolean
|
|
|
273 The valid instantiators are the symbols @code{t} and @code{nil}.
|
|
|
274 Instance objects are the same as instantiators so no special
|
|
|
275 instantiation function is needed.
|
|
|
276
|
|
|
277 @item integer
|
|
|
278 The valid instantiators are integers. Instance objects are the same as
|
|
|
279 instantiators so no special instantiation function is needed.
|
|
|
280 @code{modeline-shadow-thickness} is an example of an integer specifier
|
|
|
281 (negative thicknesses indicate that the shadow is drawn recessed instead
|
|
|
282 of raised).
|
|
|
283
|
|
|
284 @item natnum
|
|
|
285 The valid instantiators are natnums (non-negative integers). Instance
|
|
|
286 objects are the same as instantiators so no special instantiation
|
|
|
287 function is needed. Natnum specifiers are used for dimension variables
|
|
|
288 such as @code{top-toolbar-height}.
|
|
|
289
|
|
|
290 @item generic
|
|
|
291 All Lisp objects are valid instantiators. Instance objects are the same
|
|
|
292 as instantiators so no special instantiation function is needed.
|
|
|
293
|
|
|
294 @item font
|
|
|
295 The valid instantiators are strings describing fonts or vectors
|
|
|
296 indicating inheritance from the font of some face. Instance objects
|
|
|
297 are font-instance objects, which are specific to a particular device.
|
|
|
298 The instantiation method in this specifier can fail, unlike for
|
|
|
299 integer, natnum, boolean, and generic specifiers.
|
|
|
300
|
|
|
301 @item color
|
|
|
302 The valid instantiators are strings describing colors or vectors
|
|
|
303 indicating inheritance from the foreground or background of some face.
|
|
|
304 Instance objects are color-instance objects, which are specific to a
|
|
|
305 particular device. The instantiation method in this specifier can fail,
|
|
|
306 as for font specifiers.
|
|
|
307
|
|
|
308 @item image
|
|
|
309 Images are perhaps the most complicated type of built-in specifier. The
|
|
|
310 valid instantiators are strings (a filename, inline data for a pixmap,
|
|
|
311 or text to be displayed in a text glyph) or vectors describing inline
|
|
|
312 data of various sorts or indicating inheritance from the
|
|
|
313 background-pixmap property of some face. Instance objects are either
|
|
|
314 strings (for text images), image-instance objects (for pixmap images),
|
|
|
315 or subwindow objects (for subwindow images). The instantiation method
|
|
|
316 in this specifier can fail, as for font and color specifiers.
|
|
|
317
|
|
|
318 @item face-boolean
|
|
|
319 The valid instantiators are the symbols @code{t} and @code{nil} and
|
|
|
320 vectors indicating inheritance from a boolean property of some face.
|
|
|
321 Specifiers of this sort are used for all of the built-in boolean
|
|
|
322 properties of faces. Instance objects are either the symbol @code{t}
|
|
|
323 or the symbol @code{nil}.
|
|
|
324
|
|
|
325 @item toolbar
|
|
|
326 The valid instantiators are toolbar descriptors, which are lists
|
|
|
327 of toolbar-button descriptors (each of which is a vector of two
|
|
|
328 or four elements). @xref{Toolbar} for more information.
|
|
|
329 @end table
|
|
|
330
|
|
|
331 @xref{Faces and Window-System Objects} for more information on fonts,
|
|
|
332 colors, and face-boolean specifiers. @xref{Glyphs} for more information
|
|
|
333 about image specifiers. @xref{Toolbar} for more information on toolbar
|
|
|
334 specifiers.
|
|
|
335
|
|
|
336 @defun specifier-type specifier
|
|
|
337 This function returns the type of @var{specifier}. The returned value
|
|
|
338 will be a symbol: one of @code{integer}, @code{boolean}, etc., as
|
|
|
339 listed in the above table.
|
|
|
340 @end defun
|
|
|
341
|
|
|
342 Functions are also provided to query whether an object is a particular
|
|
|
343 kind of specifier:
|
|
|
344
|
|
|
345 @defun boolean-specifier-p object
|
|
|
346 This function returns non-@code{nil} if @var{object} is a boolean
|
|
|
347 specifier.
|
|
|
348 @end defun
|
|
|
349
|
|
|
350 @defun integer-specifier-p object
|
|
|
351 This function returns non-@code{nil} if @var{object} is an integer
|
|
|
352 specifier.
|
|
|
353 @end defun
|
|
|
354
|
|
|
355 @defun natnum-specifier-p object
|
|
|
356 This function returns non-@code{nil} if @var{object} is a natnum
|
|
|
357 specifier.
|
|
|
358 @end defun
|
|
|
359
|
|
|
360 @defun generic-specifier-p object
|
|
|
361 This function returns non-@code{nil} if @var{object} is a generic
|
|
|
362 specifier.
|
|
|
363 @end defun
|
|
|
364
|
|
|
365 @defun face-boolean-specifier-p object
|
|
|
366 This function returns non-@code{nil} if @var{object} is a face-boolean
|
|
|
367 specifier.
|
|
|
368 @end defun
|
|
|
369
|
|
|
370 @defun toolbar-specifier-p object
|
|
|
371 This function returns non-@code{nil} if @var{object} is a toolbar
|
|
|
372 specifier.
|
|
|
373 @end defun
|
|
|
374
|
|
|
375 @defun font-specifier-p object
|
|
|
376 This function returns non-@code{nil} if @var{object} is a font
|
|
|
377 specifier.
|
|
|
378 @end defun
|
|
|
379
|
|
|
380 @defun color-specifier-p object
|
|
|
381 This function returns non-@code{nil} if @var{object} is a color
|
|
|
382 specifier.
|
|
|
383 @end defun
|
|
|
384
|
|
|
385 @defun image-specifier-p object
|
|
|
386 This function returns non-@code{nil} if @var{object} is an image
|
|
|
387 specifier.
|
|
|
388 @end defun
|
|
|
389
|
|
|
390 @node Adding Specifications
|
|
|
391 @section Adding specifications to a Specifier
|
|
|
392
|
|
|
393 @defun add-spec-to-specifier specifier instantiator &optional locale tag-set how-to-add
|
|
|
394 This function adds a specification to @var{specifier}. The
|
|
|
395 specification maps from @var{locale} (which should be a buffer, window,
|
|
|
396 frame, device, or the symbol @code{global}, and defaults to
|
|
|
397 @code{global}) to @var{instantiator}, whose allowed values depend on the
|
|
|
398 type of the specifier. Optional argument @var{tag-set} limits the
|
|
|
399 instantiator to apply only to the specified tag set, which should be a
|
|
|
400 list of tags all of which must match the device being instantiated over
|
|
|
401 (tags are a device type, a device class, or tags defined with
|
|
|
402 @code{define-specifier-tag}). Specifying a single symbol for
|
|
|
403 @var{tag-set} is equivalent to specifying a one-element list containing
|
|
|
404 that symbol. Optional argument @var{how-to-add} specifies what to do if
|
|
|
405 there are already specifications in the specifier. It should be one of
|
|
|
406
|
|
|
407 @table @code
|
|
|
408 @item prepend
|
|
|
409 Put at the beginning of the current list of instantiators for @var{locale}.
|
|
|
410 @item append
|
|
|
411 Add to the end of the current list of instantiators for @var{locale}.
|
|
|
412 @item remove-tag-set-prepend
|
|
|
413 This is the default. Remove any existing instantiators whose tag set is
|
|
|
414 the same as @var{tag-set}; then put the new instantiator at the
|
|
|
415 beginning of the current list.
|
|
|
416 @item remove-tag-set-append
|
|
|
417 Remove any existing instantiators whose tag set is the same as
|
|
|
418 @var{tag-set}; then put the new instantiator at the end of the current
|
|
|
419 list.
|
|
|
420 @item remove-locale
|
|
|
421 Remove all previous instantiators for this locale before adding the new
|
|
|
422 spec.
|
|
|
423 @item remove-locale-type
|
|
|
424 Remove all specifications for all locales of the same type as
|
|
|
425 @var{locale} (this includes @var{locale} itself) before adding the new
|
|
|
426 spec.
|
|
|
427 @item remove-all
|
|
|
428 Remove all specifications from the specifier before adding the new spec.
|
|
|
429 @end table
|
|
|
430
|
|
|
431 @code{remove-tag-set-prepend} is the default.
|
|
|
432
|
|
|
433 You can retrieve the specifications for a particular locale or locale type
|
|
|
434 with the function @code{specifier-spec-list} or @code{specifier-specs}.
|
|
|
435 @end defun
|
|
|
436
|
|
|
437 @defun add-spec-list-to-specifier specifier spec-list &optional how-to-add
|
|
|
438 This function adds a @dfn{spec-list} (a list of specifications) to
|
|
|
439 @var{specifier}. The format of a spec-list is
|
|
|
440
|
|
|
441 @example
|
|
|
442 @code{((@var{locale} (@var{tag-set} . @var{instantiator}) ...) ...)}
|
|
|
443 @end example
|
|
|
444
|
|
|
445 where
|
|
|
446
|
|
|
447 @itemize @bullet
|
|
|
448 @item
|
|
|
449 @var{locale} := a buffer, a window, a frame, a device, or @code{global}
|
|
|
450 @item
|
|
|
451 @var{tag-set} := an unordered list of zero or more @var{tags}, each of
|
|
|
452 which is a symbol
|
|
|
453 @item
|
|
|
454 @var{tag} := a device class (@pxref{Consoles and Devices}), a device type,
|
|
|
455 or a tag defined with @code{define-specifier-tag}
|
|
|
456 @item
|
|
|
457 @var{instantiator} := format determined by the type of specifier
|
|
|
458 @end itemize
|
|
|
459
|
|
|
460 The pair @code{(@var{tag-set} . @var{instantiator})} is called an
|
|
|
461 @dfn{inst-pair}. A list of inst-pairs is called an @dfn{inst-list}.
|
|
|
462 The pair @code{(@var{locale} . @var{inst-list})} is called a
|
|
|
463 @dfn{specification}. A spec-list, then, can be viewed as a list of
|
|
|
464 specifications.
|
|
|
465
|
|
|
466 @var{how-to-add} specifies how to combine the new specifications with
|
|
|
467 the existing ones, and has the same semantics as for
|
|
|
468 @code{add-spec-to-specifier}.
|
|
|
469
|
|
|
470 In many circumstances, the higher-level function @code{set-specifier} is
|
|
|
471 more convenient and should be used instead.
|
|
|
472 @end defun
|
|
|
473
|
|
|
474 @defun set-specifier specifier value &optional how-to-add
|
|
|
475 This function adds some specifications to @var{specifier}. @var{value}
|
|
|
476 can be a single instantiator or tagged instantiator (added as a global
|
|
|
477 specification), a list of tagged and/or untagged instantiators (added as
|
|
|
478 a global specification), a cons of a locale and instantiator or locale
|
|
|
479 and instantiator list, a list of such conses, or nearly any other
|
|
|
480 reasonable form. More specifically, @var{value} can be anything
|
|
|
481 accepted by @code{canonicalize-spec-list}.
|
|
|
482
|
|
|
483 @var{how-to-add} is the same as in @code{add-spec-to-specifier}.
|
|
|
484
|
|
|
485 Note that @code{set-specifier} is exactly complementary to
|
|
|
486 @code{specifier-specs} except in the case where @var{specifier} has no
|
|
|
487 specs at all in it but @code{nil} is a valid instantiator (in that case,
|
|
|
488 @code{specifier-specs} will return @code{nil} (meaning no specs) and
|
|
|
489 @code{set-specifier} will interpret the @code{nil} as meaning ``I'm
|
|
|
490 adding a global instantiator and its value is @code{nil}''), or in
|
|
|
491 strange cases where there is an ambiguity between a spec-list and an
|
|
|
492 inst-list, etc. (The built-in specifier types are designed in such a way
|
|
|
493 as to avoid any such ambiguities.)
|
|
|
494
|
|
|
495 If you want to work with spec-lists, you should probably not use these
|
|
|
496 functions, but should use the lower-level functions
|
|
|
497 @code{specifier-spec-list} and @code{add-spec-list-to-specifier}. These
|
|
|
498 functions always work with fully-qualified spec-lists; thus, there is no
|
|
|
499 ambiguity.
|
|
|
500 @end defun
|
|
|
501
|
|
|
502 @defun canonicalize-inst-pair inst-pair specifier-type &optional noerror
|
|
|
503 This function canonicalizes the given @var{inst-pair}.
|
|
|
504
|
|
|
505 @var{specifier-type} specifies the type of specifier that this
|
|
|
506 @var{spec-list} will be used for.
|
|
|
507
|
|
|
508 Canonicalizing means converting to the full form for an inst-pair, i.e.
|
|
|
509 @code{(@var{tag-set} . @var{instantiator})}. A single, untagged
|
|
|
510 instantiator is given a tag set of @code{nil} (the empty set), and a
|
|
|
511 single tag is converted into a tag set consisting only of that tag.
|
|
|
512
|
|
|
513 If @var{noerror} is non-@code{nil}, signal an error if the inst-pair is
|
|
|
514 invalid; otherwise return @code{t}.
|
|
|
515 @end defun
|
|
|
516
|
|
|
517 @defun canonicalize-inst-list inst-list specifier-type &optional noerror
|
|
|
518 This function canonicalizes the given @var{inst-list} (a list of
|
|
|
519 inst-pairs).
|
|
|
520
|
|
|
521 @var{specifier-type} specifies the type of specifier that this @var{inst-list}
|
|
|
522 will be used for.
|
|
|
523
|
|
|
524 Canonicalizing means converting to the full form for an inst-list, i.e.
|
|
|
525 @code{((@var{tag-set} . @var{instantiator}) ...)}. This function
|
|
|
526 accepts a single inst-pair or any abbrevation thereof or a list of
|
|
|
527 (possibly abbreviated) inst-pairs. (See @code{canonicalize-inst-pair}.)
|
|
|
528
|
|
|
529 If @var{noerror} is non-@code{nil}, signal an error if the inst-list is
|
|
|
530 invalid; otherwise return @code{t}.
|
|
|
531 @end defun
|
|
|
532
|
|
|
533 @defun canonicalize-spec spec specifier-type &optional noerror
|
|
|
534 This function canonicalizes the given @var{spec} (a specification).
|
|
|
535
|
|
|
536 @var{specifier-type} specifies the type of specifier that this
|
|
|
537 @var{spec-list} will be used for.
|
|
|
538
|
|
|
539 Canonicalizing means converting to the full form for a spec, i.e.
|
|
|
540 @code{(@var{locale} (@var{tag-set} . @var{instantiator}) ...)}. This
|
|
|
541 function accepts a possibly abbreviated inst-list or a cons of a locale
|
|
|
542 and a possibly abbreviated inst-list. (See
|
|
|
543 @code{canonicalize-inst-list}.)
|
|
|
544
|
|
|
545 If @var{noerror} is @code{nil}, signal an error if the specification is
|
|
|
546 invalid; otherwise return @code{t}.
|
|
|
547 @end defun
|
|
|
548
|
|
|
549 @defun canonicalize-spec-list spec-list specifier-type &optional noerror
|
|
|
550 This function canonicalizes the given @var{spec-list} (a list of
|
|
|
551 specifications).
|
|
|
552
|
|
|
553 @var{specifier-type} specifies the type of specifier that this
|
|
|
554 @var{spec-list} will be used for.
|
|
|
555
|
|
|
556 Canonicalizing means converting to the full form for a spec-list, i.e.
|
|
|
557 @code{((@var{locale} (@var{tag-set} . @var{instantiator}) ...) ...)}.
|
|
|
558 This function accepts a possibly abbreviated specification or a list of
|
|
|
559 such things. (See @code{canonicalize-spec}.) This is the function used
|
|
|
560 to convert spec-lists accepted by @code{set-specifier} and such into a
|
|
|
561 form suitable for @code{add-spec-list-to-specifier}.
|
|
|
562
|
|
|
563 This function tries extremely hard to resolve any ambiguities,
|
|
|
564 and the built-in specifier types (font, image, toolbar, etc.) are
|
|
|
565 designed so that there won't be any ambiguities.
|
|
|
566
|
|
|
567 If @var{noerror} is @code{nil}, signal an error if the spec-list is
|
|
|
568 invalid; otherwise return @code{t}.
|
|
|
569 @end defun
|
|
|
570
|
|
|
571 @node Retrieving Specifications
|
|
|
572 @section Retrieving the Specifications from a Specifier
|
|
|
573
|
|
|
574 @defun specifier-spec-list specifier &optional locale tag-set exact-p
|
|
|
575 This function returns the spec-list of specifications for
|
|
|
576 @var{specifier} in @var{locale}.
|
|
|
577
|
|
|
578 If @var{locale} is a particular locale (a buffer, window, frame, device,
|
|
|
579 or the symbol @code{global}), a spec-list consisting of the
|
|
|
580 specification for that locale will be returned.
|
|
|
581
|
|
|
582 If @var{locale} is a locale type (i.e. a symbol @code{buffer},
|
|
|
583 @code{window}, @code{frame}, or @code{device}), a spec-list of the
|
|
|
584 specifications for all locales of that type will be returned.
|
|
|
585
|
|
|
586 If @var{locale} is @code{nil} or the symbol @code{all}, a spec-list of
|
|
|
587 all specifications in @var{specifier} will be returned.
|
|
|
588
|
|
|
589 @var{locale} can also be a list of locales, locale types, and/or
|
|
|
590 @code{all}; the result is as if @code{specifier-spec-list} were called
|
|
|
591 on each element of the list and the results concatenated together.
|
|
|
592
|
|
|
593 Only instantiators where @var{tag-set} (a list of zero or more tags) is
|
|
|
594 a subset of (or possibly equal to) the instantiator's tag set are
|
|
|
595 returned. (The default value of@code{ nil} is a subset of all tag sets,
|
|
|
596 so in this case no instantiators will be screened out.) If @var{exact-p}
|
|
|
597 is non-@code{nil}, however, @var{tag-set} must be equal to an
|
|
|
598 instantiator's tag set for the instantiator to be returned.
|
|
|
599 @end defun
|
|
|
600
|
|
|
601 @defun specifier-specs specifier &optional locale tag-set exact-p
|
|
|
602 This function returns the specification(s) for @var{specifier} in
|
|
|
603 @var{locale}.
|
|
|
604
|
|
|
605 If @var{locale} is a single locale or is a list of one element
|
|
|
606 containing a single locale, then a ``short form'' of the instantiators
|
|
|
607 for that locale will be returned. Otherwise, this function is identical
|
|
|
608 to @code{specifier-spec-list}.
|
|
|
609
|
|
|
610 The ``short form'' is designed for readability and not for ease of use
|
|
|
611 in Lisp programs, and is as follows:
|
|
|
612
|
|
|
613 @enumerate
|
|
|
614 @item
|
|
|
615 If there is only one instantiator, then an inst-pair (i.e. cons of tag
|
|
|
616 and instantiator) will be returned; otherwise a list of inst-pairs will
|
|
|
617 be returned.
|
|
|
618 @item
|
|
|
619 For each inst-pair returned, if the instantiator's tag is @code{any},
|
|
|
620 the tag will be removed and the instantiator itself will be returned
|
|
|
621 instead of the inst-pair.
|
|
|
622 @item
|
|
|
623 If there is only one instantiator, its value is @code{nil}, and its tag
|
|
|
624 is @code{any}, a one-element list containing @code{nil} will be returned
|
|
|
625 rather than just @code{nil}, to distinguish this case from there being
|
|
|
626 no instantiators at all.
|
|
|
627 @end enumerate
|
|
|
628
|
|
|
629 @end defun
|
|
|
630
|
|
|
631 @defun specifier-fallback specifier
|
|
|
632 This function returns the fallback value for @var{specifier}. Fallback
|
|
|
633 values are provided by the C code for certain built-in specifiers to
|
|
|
634 make sure that instancing won't fail even if all specs are removed from
|
|
|
635 the specifier, or to implement simple inheritance behavior (e.g. this
|
|
|
636 method is used to ensure that faces other than @code{default} inherit
|
|
|
637 their attributes from @code{default}). By design, you cannot change the
|
|
|
638 fallback value, and specifiers created with @code{make-specifier} will
|
|
|
639 never have a fallback (although a similar, Lisp-accessible capability
|
|
|
640 may be provided in the future to allow for inheritance).
|
|
|
641
|
|
|
642 The fallback value will be an inst-list that is instanced like
|
|
|
643 any other inst-list, a specifier of the same type as @var{specifier}
|
|
|
644 (results in inheritance), or @code{nil} for no fallback.
|
|
|
645
|
|
|
646 When you instance a specifier, you can explicitly request that the
|
|
|
647 fallback not be consulted. (The C code does this, for example, when
|
|
|
648 merging faces.) See @code{specifier-instance}.
|
|
|
649 @end defun
|
|
|
650
|
|
|
651 @node Specifier Tag Functions
|
|
|
652 @section Working With Specifier Tags
|
|
|
653
|
|
|
654 A specifier tag set is an entity that is attached to an instantiator
|
|
|
655 and can be used to restrict the scope of that instantiator to a
|
|
|
656 particular device class or device type and/or to mark instantiators
|
|
|
657 added by a particular package so that they can be later removed.
|
|
|
658
|
|
|
659 A specifier tag set consists of a list of zero of more specifier tags,
|
|
|
660 each of which is a symbol that is recognized by XEmacs as a tag. (The
|
|
|
661 valid device types and device classes are always tags, as are any tags
|
|
|
662 defined by @code{define-specifier-tag}.) It is called a ``tag set'' (as
|
|
|
663 opposed to a list) because the order of the tags or the number of times
|
|
|
664 a particular tag occurs does not matter.
|
|
|
665
|
|
|
666 Each tag has a predicate associated with it, which specifies whether
|
|
|
667 that tag applies to a particular device. The tags which are device
|
|
|
668 types and classes match devices of that type or class. User-defined
|
|
|
669 tags can have any predicate, or none (meaning that all devices match).
|
|
|
670 When attempting to instance a specifier, a particular instantiator is
|
|
|
671 only considered if the device of the domain being instanced over matches
|
|
|
672 all tags in the tag set attached to that instantiator.
|
|
|
673
|
|
|
674 Most of the time, a tag set is not specified, and the instantiator gets
|
|
|
675 a null tag set, which matches all devices.
|
|
|
676
|
|
|
677 @defun valid-specifier-tag-p tag
|
|
|
678 This function returns non-@code{nil} if @var{tag} is a valid specifier
|
|
|
679 tag.
|
|
|
680 @end defun
|
|
|
681
|
|
|
682 @defun valid-specifier-tag-set-p tag-set
|
|
|
683 This function returns non-@code{nil} if @var{tag-set} is a valid
|
|
|
684 specifier tag set.
|
|
|
685 @end defun
|
|
|
686
|
|
|
687 @defun canonicalize-tag-set tag-set
|
|
|
688 This function canonicalizes the given tag set. Two canonicalized tag
|
|
|
689 sets can be compared with @code{equal} to see if they represent the same
|
|
|
690 tag set. (Specifically, canonicalizing involves sorting by symbol name
|
|
|
691 and removing duplicates.)
|
|
|
692 @end defun
|
|
|
693
|
|
|
694 @defun device-matches-specifier-tag-set-p device tag-set
|
|
|
695 This function returns non-@code{nil} if @var{device} matches specifier
|
|
|
696 tag set @var{tag-set}. This means that @var{device} matches each tag in
|
|
|
697 the tag set.
|
|
|
698 @end defun
|
|
|
699
|
|
|
700 @defun define-specifier-tag tag &optional predicate
|
|
|
701 This function defines a new specifier tag. If @var{predicate} is
|
|
|
702 specified, it should be a function of one argument (a device) that
|
|
|
703 specifies whether the tag matches that particular device. If
|
|
|
704 @var{predicate} is omitted, the tag matches all devices.
|
|
|
705
|
|
|
706 You can redefine an existing user-defined specifier tag. However, you
|
|
|
707 cannot redefine the built-in specifier tags (the device types and
|
|
|
708 classes) or the symbols @code{nil}, @code{t}, @code{all}, or
|
|
|
709 @code{global}.
|
|
|
710 @end defun
|
|
|
711
|
|
|
712 @defun device-matching-specifier-tag-list &optional device
|
|
|
713 This function returns a list of all specifier tags matching
|
|
|
714 @var{device}. @var{device} defaults to the selected device if omitted.
|
|
|
715 @end defun
|
|
|
716
|
|
|
717 @defun specifier-tag-list
|
|
|
718 This function returns a list of all currently-defined specifier tags.
|
|
|
719 This includes the built-in ones (the device types and classes).
|
|
|
720 @end defun
|
|
|
721
|
|
|
722 @defun specifier-tag-predicate tag
|
|
|
723 This function returns the predicate for the given specifier tag.
|
|
|
724 @end defun
|
|
|
725
|
|
|
726 @node Specifier Instancing Functions
|
|
|
727 @section Functions for Instancing a Specifier
|
|
|
728
|
|
|
729 @defun specifier-instance specifier &optional domain default no-fallback
|
|
|
730 This function instantiates @var{specifier} (return its value) in
|
|
|
731 @var{domain}. If no instance can be generated for this domain, return
|
|
|
732 @var{default}.
|
|
|
733
|
|
|
734 @var{domain} should be a window, frame, or device. Other values that
|
|
|
735 are legal as a locale (e.g. a buffer) are not valid as a domain because
|
|
|
736 they do not provide enough information to identify a particular device
|
|
|
737 (see @code{valid-specifier-domain-p}). @var{domain} defaults to the
|
|
|
738 selected window if omitted.
|
|
|
739
|
|
|
740 @dfn{Instantiating} a specifier in a particular domain means determining
|
|
|
741 the specifier's ``value'' in that domain. This is accomplished by
|
|
|
742 searching through the specifications in the specifier that correspond to
|
|
|
743 all locales that can be derived from the given domain, from specific to
|
|
|
744 general. In most cases, the domain is an Emacs window. In that case
|
|
|
745 specifications are searched for as follows:
|
|
|
746
|
|
|
747 @enumerate
|
|
|
748 @item
|
|
|
749 A specification whose locale is the window's buffer;
|
|
|
750 @item
|
|
|
751 A specification whose locale is the window itself;
|
|
|
752 @item
|
|
|
753 A specification whose locale is the window's frame;
|
|
|
754 @item
|
|
|
755 A specification whose locale is the window's frame's device;
|
|
|
756 @item
|
|
|
757 A specification whose locale is the symbol @code{global}.
|
|
|
758 @end enumerate
|
|
|
759
|
|
|
760 If all of those fail, then the C-code-provided fallback value for this
|
|
|
761 specifier is consulted (see @code{specifier-fallback}). If it is an
|
|
|
762 inst-list, then this function attempts to instantiate that list just as
|
|
|
763 when a specification is located in the first five steps above. If the
|
|
|
764 fallback is a specifier, @code{specifier-instance} is called recursively
|
|
|
765 on this specifier and the return value used. Note, however, that if the
|
|
|
766 optional argument @var{no-fallback} is non-@code{nil}, the fallback
|
|
|
767 value will not be consulted.
|
|
|
768
|
|
|
769 Note that there may be more than one specification matching a particular
|
|
|
770 locale; all such specifications are considered before looking for any
|
|
|
771 specifications for more general locales. Any particular specification
|
|
|
772 that is found may be rejected because it is tagged to a particular
|
|
|
773 device class (e.g. @code{color}) or device type (e.g. @code{x}) or both
|
|
|
774 and the device for the given domain does not match this, or because the
|
|
|
775 specification is not valid for the device of the given domain (e.g. the
|
|
|
776 font or color name does not exist for this particular X server).
|
|
|
777
|
|
|
778 The returned value is dependent on the type of specifier. For example,
|
|
|
779 for a font specifier (as returned by the @code{face-font} function), the
|
|
|
780 returned value will be a font-instance object. For images, the returned
|
|
|
781 value will be a string, pixmap, or subwindow.
|
|
|
782 @end defun
|
|
|
783
|
|
|
784 @defun specifier-instance-from-inst-list specifier domain inst-list &optional default
|
|
|
785 This function attempts to convert a particular inst-list into an
|
|
|
786 instance. This attempts to instantiate @var{inst-list} in the given
|
|
|
787 @var{domain}, as if @var{inst-list} existed in a specification in
|
|
|
788 @var{specifier}. If the instantiation fails, @var{default} is returned.
|
|
|
789 In most circumstances, you should not use this function; use
|
|
|
790 @code{specifier-instance} instead.
|
|
|
791 @end defun
|
|
|
792
|
|
|
793 @node Specifier Example
|
|
|
794 @section Example of Specifier Usage
|
|
|
795
|
|
|
796 Now let us present an example to clarify the theoretical discussions we
|
|
|
797 have been through. In this example, we will use the general specifier
|
|
|
798 functions for clarity. Keep in mind that many types of specifiers, and
|
|
|
799 some other types of objects that are associated with specifiers
|
|
|
800 (e.g. faces), provide convenience functions making it easier to work
|
|
|
801 with objects of that type.
|
|
|
802
|
|
|
803 Let us consider the background color of the default face. A specifier
|
|
|
804 is used to specify how that color will appear in different domains.
|
|
|
805 First, let's retrieve the specifier:
|
|
|
806
|
|
|
807 @example
|
|
|
808 (setq sp (face-property 'default 'background))
|
|
|
809 @result{} #<color-specifier 0x3da>
|
|
|
810 @end example
|
|
|
811
|
|
|
812 @example
|
|
|
813 (specifier-specs sp)
|
|
|
814 @result{} ((#<buffer "device.c"> (nil . "forest green"))
|
|
|
815 (#<window on "Makefile" 0x8a2b> (nil . "hot pink"))
|
|
|
816 (#<x-frame "emacs" 0x4ac> (nil . "puke orange")
|
|
|
817 (nil . "moccasin"))
|
|
|
818 (#<x-frame "VM" 0x4ac> (nil . "magenta"))
|
|
|
819 (global ((tty) . "cyan") (nil . "white"))
|
|
|
820 )
|
|
|
821 @end example
|
|
|
822
|
|
|
823 Then, say we want to determine what the background color of the default
|
|
|
824 face is for the window currently displaying the buffer @samp{*scratch*}.
|
|
|
825 We call
|
|
|
826
|
|
|
827 @example
|
|
|
828 (get-buffer-window "*scratch*")
|
|
|
829 @result{} #<window on "*scratch*" 0x4ad>
|
|
|
830 (window-frame (get-buffer-window "*scratch*"))
|
|
|
831 @result{} #<x-frame "emacs" 0x4ac>
|
|
|
832 (specifier-instance sp (get-buffer-window "*scratch*"))
|
|
|
833 @result{} #<color-instance moccasin 47=(FFFF,E4E4,B5B5) 0x6309>
|
|
|
834 @end example
|
|
|
835
|
|
|
836 Note that we passed a window to @code{specifier-instance}, not a buffer.
|
|
|
837 We cannot pass a buffer because a buffer by itself does not provide enough
|
|
|
838 information. The buffer might not be displayed anywhere at all, or
|
|
|
839 could be displayed in many different frames on different devices.
|
|
|
840
|
|
|
841 The result is arrived at like this:
|
|
|
842
|
|
|
843 @enumerate
|
|
|
844 @item
|
|
|
845 First, we look for a specification matching the buffer displayed in the
|
|
|
846 window, i.e. @samp{*scratch}. There are none, so we proceed.
|
|
|
847 @item
|
|
|
848 Then, we look for a specification matching the window itself. Again, there
|
|
|
849 are none.
|
|
|
850 @item
|
|
|
851 Then, we look for a specification matching the window's frame. The
|
|
|
852 specification @code{(#<x-frame "emacs" 0x4ac> . "puke orange")} is
|
|
|
853 found. We call the instantiation method for colors, passing it the
|
|
|
854 locale we were searching over (i.e. the window, in this case) and the
|
|
|
855 instantiator (@samp{"puke orange"}). However, the particular device
|
|
|
856 which this window is on (let's say it's an X connection) doesn't
|
|
|
857 recognize the color @samp{"puke orange"}, so the specification is
|
|
|
858 rejected.
|
|
|
859 @item
|
|
|
860 So we continue looking for a specification matching the window's frame.
|
|
|
861 We find @samp{(#<x-frame "emacs" 0x4ac> . "moccasin")}. Again, we
|
|
|
862 call the instantiation method for colors. This time, the X server
|
|
|
863 our window is on recognizes the color @samp{moccasin}, and so the
|
|
|
864 instantiation method succeeds and returns a color instance.
|
|
|
865 @end enumerate
|
|
|
866
|
|
|
867 @node Creating Specifiers
|
|
|
868 @section Creating New Specifier Objects
|
|
|
869
|
|
|
870 @defun make-specifier type
|
|
|
871 This function creates a new specifier.
|
|
|
872
|
|
|
873 A specifier is an object that can be used to keep track of a property
|
|
|
874 whose value can be per-buffer, per-window, per-frame, or per-device,
|
|
|
875 and can further be restricted to a particular device-type or device-class.
|
|
|
876 Specifiers are used, for example, for the various built-in properties of a
|
|
|
877 face; this allows a face to have different values in different frames,
|
|
|
878 buffers, etc. For more information, see `specifier-instance',
|
|
|
879 `specifier-specs', and `add-spec-to-specifier'; or, for a detailed
|
|
|
880 description of specifiers, including how they are instantiated over a
|
|
|
881 particular domain (i.e. how their value in that domain is determined),
|
|
|
882 see the chapter on specifiers in the XEmacs Lisp Reference Manual.
|
|
|
883
|
|
|
884 @var{type} specifies the particular type of specifier, and should be one
|
|
|
885 of the symbols @code{generic}, @code{integer}, @code{natnum},
|
|
|
886 @code{boolean}, @code{color}, @code{font}, @code{image},
|
|
|
887 @code{face-boolean}, or @code{toolbar}.
|
|
|
888
|
|
|
889 For more information on particular types of specifiers, see the
|
|
|
890 functions @code{generic-specifier-p}, @code{integer-specifier-p},
|
|
|
891 @code{natnum-specifier-p}, @code{boolean-specifier-p},
|
|
|
892 @code{color-specifier-p}, @code{font-specifier-p},
|
|
|
893 @code{image-specifier-p}, @code{face-boolean-specifier-p}, and
|
|
|
894 @code{toolbar-specifier-p}.
|
|
|
895 @end defun
|
|
|
896
|
|
|
897 @defun make-specifier-and-init type spec-list &optional dont-canonicalize
|
|
|
898 This function creates and initialize a new specifier.
|
|
|
899
|
|
|
900 This is a front-end onto @code{make-specifier} that allows you to create
|
|
|
901 a specifier and add specs to it at the same time. @var{type} specifies
|
|
|
902 the specifier type. @var{spec-list} supplies the specification(s) to be
|
|
|
903 added to the specifier. Normally, almost any reasonable abbreviation of
|
|
|
904 the full spec-list form is accepted, and is converted to the full form;
|
|
|
905 however, if optional argument @var{dont-canonicalize} is non-@code{nil},
|
|
|
906 this conversion is not performed, and the @var{spec-list} must already
|
|
|
907 be in full form. See @code{canonicalize-spec-list}.
|
|
|
908 @end defun
|
|
|
909
|
|
|
910 @node Specifier Validation Functions
|
|
|
911 @section Functions for Checking the Validity of Specifier Components
|
|
|
912
|
|
|
913 @defun valid-specifier-domain-p domain
|
|
|
914 This function returns non-@code{nil} if @var{domain} is a valid
|
|
|
915 specifier domain. A domain is used to instance a specifier
|
|
|
916 (i.e. determine the specifier's value in that domain). Valid domains
|
|
|
917 are a window, frame, or device. (@code{nil} is not valid.)
|
|
|
918 @end defun
|
|
|
919
|
|
|
920 @defun valid-specifier-locale-p locale
|
|
|
921 This function returns non-@code{nil} if @var{locale} is a valid
|
|
|
922 specifier locale. Valid locales are a device, a frame, a window, a
|
|
|
923 buffer, and @code{global}. (@code{nil} is not valid.)
|
|
|
924 @end defun
|
|
|
925
|
|
|
926 @defun valid-specifier-locale-type-p locale-type
|
|
|
927 Given a specifier @var{locale-type}, this function returns non-nil if it
|
|
|
928 is valid. Valid locale types are the symbols @code{global},
|
|
|
929 @code{device}, @code{frame}, @code{window}, and @code{buffer}. (Note,
|
|
|
930 however, that in functions that accept either a locale or a locale type,
|
|
|
931 @code{global} is considered an individual locale.)
|
|
|
932 @end defun
|
|
|
933
|
|
|
934 @defun valid-specifier-type-p specifier-type
|
|
|
935 Given a @var{specifier-type}, this function returns non-@code{nil} if it
|
|
|
936 is valid. Valid types are @code{generic}, @code{integer},
|
|
|
937 @code{boolean}, @code{color}, @code{font}, @code{image},
|
|
|
938 @code{face-boolean}, and @code{toolbar}.
|
|
|
939 @end defun
|
|
|
940
|
|
|
941 @defun valid-specifier-tag-p tag
|
|
|
942 This function returns non-@code{nil} if @var{tag} is a valid specifier
|
|
|
943 tag.
|
|
|
944 @end defun
|
|
|
945
|
|
|
946 @defun valid-instantiator-p instantiator specifier-type
|
|
|
947 This function returns non-@code{nil} if @var{instantiator} is valid for
|
|
|
948 @var{specifier-type}.
|
|
|
949 @end defun
|
|
|
950
|
|
|
951 @defun valid-inst-list-p inst-list type
|
|
|
952 This function returns non-@code{nil} if @var{inst-list} is valid for
|
|
|
953 specifier type @var{type}.
|
|
|
954 @end defun
|
|
|
955
|
|
|
956 @defun valid-spec-list-p spec-list type
|
|
|
957 This function returns non-@code{nil} if @var{spec-list} is valid for
|
|
|
958 specifier type @var{type}.
|
|
|
959 @end defun
|
|
|
960
|
|
|
961 @defun check-valid-instantiator instantiator specifier-type
|
|
|
962 This function signals an error if @var{instantiator} is invalid for
|
|
|
963 @var{specifier-type}.
|
|
|
964 @end defun
|
|
|
965
|
|
|
966 @defun check-valid-inst-list inst-list type
|
|
|
967 This function signals an error if @var{inst-list} is invalid for
|
|
|
968 specifier type @var{type}.
|
|
|
969 @end defun
|
|
|
970
|
|
|
971 @defun check-valid-spec-list spec-list type
|
|
|
972 This function signals an error if @var{spec-list} is invalid for
|
|
|
973 specifier type @var{type}.
|
|
|
974 @end defun
|
|
|
975
|
|
|
976 @node Other Specification Functions
|
|
|
977 @section Other Functions for Working with Specifications in a Specifier
|
|
|
978
|
|
|
979 @defun copy-specifier specifier &optional dest locale tag-set exact-p how-to-add
|
|
|
980 This function copies @var{specifier} to @var{dest}, or creates a new one
|
|
|
981 if @var{dest} is @code{nil}.
|
|
|
982
|
|
|
983 If @var{dest} is @code{nil} or omitted, a new specifier will be created
|
|
|
984 and the specifications copied into it. Otherwise, the specifications
|
|
|
985 will be copied into the existing specifier in @var{dest}.
|
|
|
986
|
|
|
987 If @var{locale} is @code{nil} or the symbol @code{all}, all
|
|
|
988 specifications will be copied. If @var{locale} is a particular locale,
|
|
|
989 the specification for that particular locale will be copied. If
|
|
|
990 @var{locale} is a locale type, the specifications for all locales of
|
|
|
991 that type will be copied. @var{locale} can also be a list of locales,
|
|
|
992 locale types, and/or @code{all}; this is equivalent to calling
|
|
|
993 @code{copy-specifier} for each of the elements of the list. See
|
|
|
994 @code{specifier-spec-list} for more information about @var{locale}.
|
|
|
995
|
|
|
996 Only instantiators where @var{tag-set} (a list of zero or more tags) is
|
|
|
997 a subset of (or possibly equal to) the instantiator's tag set are
|
|
|
998 copied. (The default value of @code{nil} is a subset of all tag sets,
|
|
|
999 so in this case no instantiators will be screened out.) If @var{exact-p}
|
|
|
1000 is non-@code{nil}, however, @var{tag-set} must be equal to an
|
|
|
1001 instantiator's tag set for the instantiator to be copied.
|
|
|
1002
|
|
|
1003 Optional argument @var{how-to-add} specifies what to do with existing
|
|
|
1004 specifications in @var{dest}. If nil, then whichever locales or locale
|
|
|
1005 types are copied will first be completely erased in @var{dest}.
|
|
|
1006 Otherwise, it is the same as in @code{add-spec-to-specifier}.
|
|
|
1007 @end defun
|
|
|
1008
|
|
|
1009 @defun remove-specifier specifier &optional locale tag-set exact-p
|
|
|
1010 This function removes specification(s) for @var{specifier}.
|
|
|
1011
|
|
|
1012 If @var{locale} is a particular locale (a buffer, window, frame, device,
|
|
|
1013 or the symbol @code{global}), the specification for that locale will be
|
|
|
1014 removed.
|
|
|
1015
|
|
|
1016 If instead, @var{locale} is a locale type (i.e. a symbol @code{buffer},
|
|
|
1017 @code{window}, @code{frame}, or @code{device}), the specifications for
|
|
|
1018 all locales of that type will be removed.
|
|
|
1019
|
|
|
1020 If @var{locale} is @code{nil} or the symbol @code{all}, all
|
|
|
1021 specifications will be removed.
|
|
|
1022
|
|
|
1023 @var{locale} can also be a list of locales, locale types, and/or
|
|
|
1024 @code{all}; this is equivalent to calling @code{remove-specifier} for
|
|
|
1025 each of the elements in the list.
|
|
|
1026
|
|
|
1027 Only instantiators where @var{tag-set} (a list of zero or more tags) is
|
|
|
1028 a subset of (or possibly equal to) the instantiator's tag set are
|
|
|
1029 removed. (The default value of @code{nil} is a subset of all tag sets,
|
|
|
1030 so in this case no instantiators will be screened out.) If @var{exact-p}
|
|
|
1031 is non-@code{nil}, however, @var{tag-set} must be equal to an
|
|
|
1032 instantiator's tag set for the instantiator to be removed.
|
|
|
1033 @end defun
|
|
|
1034
|
|
|
1035 @defun map-specifier specifier func &optional locale maparg
|
|
|
1036 This function applies @var{func} to the specification(s) for
|
|
|
1037 @var{locale} in @var{specifier}.
|
|
|
1038
|
|
|
1039 If @var{locale} is a locale, @var{func} will be called for that locale.
|
|
|
1040 If @var{locale} is a locale type, @var{func} will be mapped over all
|
|
|
1041 locales of that type. If @var{locale} is @code{nil} or the symbol
|
|
|
1042 @code{all}, @var{func} will be mapped over all locales in
|
|
|
1043 @var{specifier}.
|
|
|
1044
|
|
|
1045 @var{func} is called with four arguments: the @var{specifier}, the
|
|
|
1046 locale being mapped over, the inst-list for that locale, and the
|
|
|
1047 optional @var{maparg}. If any invocation of @var{func} returns
|
|
|
1048 non-@code{nil}, the mapping will stop and the returned value becomes the
|
|
|
1049 value returned from @code{map-specifier}. Otherwise,
|
|
|
1050 @code{map-specifier} returns @code{nil}.
|
|
|
1051 @end defun
|
|
|
1052
|
|
|
1053 @defun specifier-locale-type-from-locale locale
|
|
|
1054 Given a specifier @var{locale}, this function returns its type.
|
|
|
1055 @end defun
|
|
|
1056
|
