Mercurial > hg > xemacs-beta
comparison lisp/specifier.el @ 771:943eaba38521
[xemacs-hg @ 2002-03-13 08:51:24 by ben]
The big ben-mule-21-5 check-in!
Various files were added and deleted. See CHANGES-ben-mule.
There are still some test suite failures. No crashes, though.
Many of the failures have to do with problems in the test suite itself
rather than in the actual code. I'll be addressing these in the next
day or so -- none of the test suite failures are at all critical.
Meanwhile I'll be trying to address the biggest issues -- i.e. build
or run failures, which will almost certainly happen on various platforms.
All comments should be sent to ben@xemacs.org -- use a Cc: if necessary
when sending to mailing lists. There will be pre- and post- tags,
something like
pre-ben-mule-21-5-merge-in, and
post-ben-mule-21-5-merge-in.
| author | ben |
|---|---|
| date | Wed, 13 Mar 2002 08:54:06 +0000 |
| parents | ff9d7f21f8d0 |
| children | 79c6ff3eef26 |
comparison
equal
deleted
inserted
replaced
| 770:336a418893b5 | 771:943eaba38521 |
|---|---|
| 288 e.g. `make-color-specifier', `make-font-specifier', | 288 e.g. `make-color-specifier', `make-font-specifier', |
| 289 `make-image-specifier' -- or in the global variable holding the most | 289 `make-image-specifier' -- or in the global variable holding the most |
| 290 common specifier for that type (`default-toolbar', `default-gutter', | 290 common specifier for that type (`default-toolbar', `default-gutter', |
| 291 `current-display-table'). | 291 `current-display-table'). |
| 292 | 292 |
| 293 NOTE: It does *not* work to give a VALUE of nil as a way of | 293 NOTE: It does *not* work to give a VALUE of nil as a way of removing the |
| 294 removing the specifications for a locale. Use `remove-specifier' | 294 specifications for a locale -- for many specifier types, such as `boolean', |
| 295 instead. (And keep in mind that, if you omit the LOCALE argument | 295 nil is a perfectly legitimate value to set. Use `remove-specifier' |
| 296 to `remove-specifier', it removes *all* specifications! If you | 296 instead. (And keep in mind that, if you omit the LOCALE argument to |
| 297 want to remove just the `global' specification, make sure to | 297 `remove-specifier', it removes *all* specifications! If you want to remove |
| 298 specify a LOCALE of `global'.) | 298 just the `global' specification, make sure to specify a LOCALE of |
| 299 `global'.) | |
| 299 | 300 |
| 300 VALUE can also be a list of instantiators. This means basically, | 301 VALUE can also be a list of instantiators. This means basically, |
| 301 \"try each one in turn until you get one that works\". This allows | 302 \"try each one in turn until you get one that works\". This allows |
| 302 you to give funky instantiators that may only work in some cases, | 303 you to give funky instantiators that may only work in some cases, |
| 303 and provide more normal backups for the other cases. (For example, | 304 and provide more normal backups for the other cases. (For example, |
| 327 Most of the time, you do not need to worry about this argument; | 328 Most of the time, you do not need to worry about this argument; |
| 328 the default behavior of `remove-tag-set-prepend' is usually fine. | 329 the default behavior of `remove-tag-set-prepend' is usually fine. |
| 329 See `copy-specifier' and `add-spec-to-specifier' for a full | 330 See `copy-specifier' and `add-spec-to-specifier' for a full |
| 330 description of what each of these means. | 331 description of what each of these means. |
| 331 | 332 |
| 332 VALUE can actually be anything acceptable to `canonicalize-spec-list'; | 333 \[VALUE can actually be anything acceptable to `canonicalize-spec-list'; |
| 333 this includes, among other things: | 334 this includes, among other things: |
| 334 | 335 |
| 335 -- a cons of a locale and an instantiator (or list of instantiators) | 336 -- a cons of a locale and an instantiator (or list of instantiators) |
| 336 -- a cons of a tag or tag-set and an instantiator (or list of | 337 -- a cons of a tag or tag-set and an instantiator (or list of |
| 337 instantiators) | 338 instantiators) |
| 338 -- a cons of a locale and the previous type of item | 339 -- a cons of a locale and the previous type of item |
| 339 -- a list of one or more of any of the previous types of items | 340 -- a list of one or more of any of the previous types of items |
| 340 | 341 |
| 341 However, in these cases, you cannot give a LOCALE or TAG-SET, | 342 However, this usage is deprecated. Either iterate and call `set-specifier' |
| 342 because they do not make sense. (You will probably get an error if | 343 multiple times, or use the lower-level `add-spec-list-to-specifier'. Also, |
| 343 you try this.) | 344 in these cases, you cannot give a LOCALE or TAG-SET, because they do not |
| 345 make sense. (You will probably get an error if you try this.)] | |
| 344 | 346 |
| 345 Finally, VALUE can itself be a specifier (of the same type as | 347 Finally, VALUE can itself be a specifier (of the same type as |
| 346 SPECIFIER), if you want to copy specifications from one specifier | 348 SPECIFIER), if you want to copy specifications from one specifier |
| 347 to another; this is equivalent to calling `copy-specifier', and | 349 to another; this is equivalent to calling `copy-specifier', and |
| 348 LOCALE, TAG-SET, and HOW-TO-ADD have the same semantics as with | 350 LOCALE, TAG-SET, and HOW-TO-ADD have the same semantics as with |