Mercurial > hg > xemacs-beta

diff lisp/specifier.el @ 771:943eaba38521

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
[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
line wrap: on
line diff
--- a/lisp/specifier.el	Fri Mar 08 13:33:14 2002 +0000
+++ b/lisp/specifier.el	Wed Mar 13 08:54:06 2002 +0000
@@ -290,12 +290,13 @@
 common specifier for that type (`default-toolbar', `default-gutter',
 `current-display-table').
 
-NOTE: It does *not* work to give a VALUE of nil as a way of
-removing the specifications for a locale.  Use `remove-specifier'
-instead. (And keep in mind that, if you omit the LOCALE argument
-to `remove-specifier', it removes *all* specifications!  If you
-want to remove just the `global' specification, make sure to
-specify a LOCALE of `global'.)
+NOTE: It does *not* work to give a VALUE of nil as a way of removing the
+specifications for a locale -- for many specifier types, such as `boolean',
+nil is a perfectly legitimate value to set.  Use `remove-specifier'
+instead. (And keep in mind that, if you omit the LOCALE argument to
+`remove-specifier', it removes *all* specifications!  If you want to remove
+just the `global' specification, make sure to specify a LOCALE of
+`global'.)
 
 VALUE can also be a list of instantiators.  This means basically,
 \"try each one in turn until you get one that works\".  This allows
@@ -329,7 +330,7 @@
 See `copy-specifier' and `add-spec-to-specifier' for a full
 description of what each of these means.
 
-VALUE can actually be anything acceptable to `canonicalize-spec-list';
+\[VALUE can actually be anything acceptable to `canonicalize-spec-list';
 this includes, among other things:
 
 -- a cons of a locale and an instantiator (or list of instantiators)
@@ -338,9 +339,10 @@
 -- a cons of a locale and the previous type of item
 -- a list of one or more of any of the previous types of items
 
-However, in these cases, you cannot give a LOCALE or TAG-SET,
-because they do not make sense. (You will probably get an error if
-you try this.)
+However, this usage is deprecated.  Either iterate and call `set-specifier'
+multiple times, or use the lower-level `add-spec-list-to-specifier'.  Also,
+in these cases, you cannot give a LOCALE or TAG-SET, because they do not
+make sense. (You will probably get an error if you try this.)]
 
 Finally, VALUE can itself be a specifier (of the same type as
 SPECIFIER), if you want to copy specifications from one specifier