Re: Error compiling latest CVS 21.5.b16
This patch fixes the error I saw, and also a subject/verb agreement error in
an earlier paragraph of the file:
*** man/lispref/specifiers.texi.~1~ Sat Jan 24 17:21:57 2004
--- man/lispref/specifiers.texi Sat Jan 24 18:02:40 2004
***************
*** 1102,1108 ****
＠end defun
＠defun specifier-matching-instance specifier matchspec &optional domain default
no-fallback
! This function return an instance for ＠var{specifier} in ＠var{domain}
that matches ＠var{matchspec}. If no instance can be generated for
＠var{domain}, return ＠var{default}.
--- 1102,1108 ----
＠end defun
＠defun specifier-matching-instance specifier matchspec &optional domain default
no-fallback
! This function returns an instance for ＠var{specifier} in ＠var{domain}
that matches ＠var{matchspec}. If no instance can be generated for
＠var{domain}, return ＠var{default}.
***************
*** 1116,1126 ****
For chartable (e.g. display table) specifiers, ＠var{matchspec} should be a
character, and the specification (a chartable) must give a value for
that character in order to be considered. This allows you to specify,
! ＠emphe.g.}, a buffer-local display table that only gives values for particular
characters. All other characters are handled as if the buffer-local
display table is not there. (Chartable specifiers are not yet
implemented.)
!
For font specifiers, ＠var{matchspec} should be a list (＠var{charset}
. ＠var{second-stage-p}), and the specification (a font string) must have
a registry that matches the charset's registry. (This only makes sense
--- 1116,1126 ----
For chartable (e.g. display table) specifiers, ＠var{matchspec} should be a
character, and the specification (a chartable) must give a value for
that character in order to be considered. This allows you to specify,
! ＠emph{e.g.}, a buffer-local display table that only gives values for particular
characters. All other characters are handled as if the buffer-local
display table is not there. (Chartable specifiers are not yet
implemented.)
! ＠item
For font specifiers, ＠var{matchspec} should be a list (＠var{charset}
. ＠var{second-stage-p}), and the specification (a font string) must have
a registry that matches the charset's registry. (This only makes sense
***************
*** 1129,1134 ****
--- 1129,1135 ----
＠var{second-stage-p} means to ignore the font's registry and instead
look at the characters in the font to see if the font can support the
charset. This currently only makes sense under MS Windows.
+ ＠end itemize
＠end defun
＠defun specifier-instance-from-inst-list specifier domain inst-list &optional
default
--
Dr. Robert Delius Royar Associate Professor of English
Morehead State University Morehead, Kentucky
California is a dream in the mind of a New Yorker.
-Nicholson Baker
18:24 up 6:24, 1 user, load averages: 0.25 0.20 0.13