@findex customize
@cindex customization buffer
A convenient way to find the user option variables that you want to
-change, and then change them, is with @kbd{M-x customize}. This command
+change, and then change them, is with @kbd{M-x customize} (or use a
+keyboard shortcut, @kbd{C-h C}. This command
creates a @dfn{customization buffer} with which you can browse through
the Emacs user options in a logically organized structure, then edit and
set their values. You can also use the customization buffer to save
@dfn{groups} to help you find them. Groups are collected into bigger
groups, all the way up to a master group called @code{Emacs}.
- @kbd{M-x customize} creates a customization buffer that shows the
-top-level @code{Emacs} group and the second-level groups immediately
+ @kbd{M-x customize} (or @kbd{C-h C}) creates a customization buffer that
+shows the top-level @code{Emacs} group and the second-level groups immediately
under it. It looks like this, in part:
@smallexample
attribute by invoking that field. When the attribute is enabled, you
can change the attribute value in the usual ways.
+@xref{Faces}, for description of how @code{face-frob-from-locale-first}
+variable affects changing @samp{Bold} and @samp{Italic} attributes.
+
@c Is this true for XEmacs?
@c On a black-and-white display, the colors you can use for the
@c background are @samp{black}, @samp{white}, @samp{gray}, @samp{gray1},
list. That is inappropriate. Whether you use Auto Fill mode or not is
a matter of personal taste, not a matter of the contents of particular
files. If you want to use Auto Fill, set up major mode hooks with your
-file file to turn it on (when appropriate) for you alone
+init file to turn it on (when appropriate) for you alone
(@pxref{Init File}). Don't try to use a local variable list that would
impose your taste on everyone working with the file.
@code{minibuffer-local-must-match-map} is for strict completion and
for cautious completion.
@item
-@code{repeat-complex-command-map} is for use in @kbd{C-x @key{ESC}}.
+@code{repeat-complex-command-map} is for use in @kbd{C-x @key{ESC} @key{ESC}}.
@item
@code{isearch-mode-map} contains the bindings of the special keys which
are bound in the pseudo-mode entered with @kbd{C-s} and @kbd{C-r}.
table of syntactic classes, with the characters that specify them.
@table @samp
-@item @w{ }
-The class of whitespace characters.
+@item @w{-}
+The class of whitespace characters. Please don't use the formerly
+advertised @w{ }, which is not supported by GNU Emacs.
@item w
The class of word-constituent characters.
@item _
Change whether the given @var{face} is underlined.
@end table
-@findex make-face-bold
-@findex make-face-bold-italic
-@findex make-face-italic
-@findex make-face-unbold
-@findex make-face-unitalic
@findex make-face-larger
@findex make-face-smaller
@var{frame} to specify which frame is affected; otherwise, all frames
are affected.
+@findex make-face-bold
+@findex make-face-bold-italic
+@findex make-face-italic
+@findex make-face-unbold
+@findex make-face-unitalic
+@vindex face-frob-from-locale-first
+The work of @code{make-face-bold}, @code{make-face-bold-italic},
+@code{make-face-italic}, @code{make-face-unbold},
+@code{make-face-unitalic} functions is affected by
+@code{face-frob-from-locale-first} variable. If it is @code{nil}, those
+functions first try to manipulate device specific data like X font names
+to obtain the desired font face specification. This may be unsuitable
+in environments using different font face specifications for different
+frames, non-Mule environments in particular.
+
+If the variable is non-@code{nil}, those functions first try to figure
+out whether the face font is the same as one of predefined faces:
+@code{default}, @code{bold}, @code{italic}, @code{bold-italic}. If it
+is the same, then the new face font specification is set to be the same
+as that of a corresponding predefined face. Thus if the predefined face
+is set up properly for different frames, the same will hold for the face
+being changed by the functions. This is the behavior one might desire
+in non-Mule environments mentioned above: face being changed still looks
+right in all frames.
+
+How predefined faces might be set up for different frames in such an
+environments is described in @ref{Face Resources}.
+
@findex set-face-background
You can set the background color of the specified @var{face} with the
function @code{set-face-background}. The argument @code{color} should
Starting with XEmacs 21, XEmacs uses the class @samp{XEmacs} if it finds
any XEmacs resources in the resource database when the X connection is
initialized. Otherwise, it will use the class @samp{Emacs} for
-backwards compatibility. The variable @var{x-emacs-application-class}
+backwards compatibility. The variable @code{x-emacs-application-class}
may be consulted to determine the application class being used.
The examples in this section assume the application class is @samp{Emacs}.
colors: It uses whatever resources are appropriate to the type of widget
which is used to implement it.
-If Emacs was compiled to use only the Motif-lookalike menu widgets, then one
-way to specify the font of the menubar would be
+If Emacs was compiled to use only the Lucid Motif-lookalike menu widgets,
+then one way to specify the font of the menubar would be
@example
Emacs*menubar*font: *-courier-medium-r-*-*-*-120-*-*-*-*-*-*
@end example
+If both the Lucid Motif-lookalike menu widgets and X Font Sets are
+configured to allow multilingual menubars, then one uses
+
+@example
+*menubar*FontSet: -*-helvetica-bold-r-*-*-*-120-*-*-*-*-iso8859-*, \
+ -*-*-*-*-*-*-*-120-*-jisx0208.1983-0
+@end example
+
+That would specify fonts for a Japanese menubar. Specifying only one
+XLFD is acceptable; specifying more than one for a given registry
+(language) is also allowed. When X Font Sets are configured, some .font
+resources (eg, menubars) are ignored in favor of the corresponding
+.fontSet resources.
+
If the Motif library is being used, then one would have to use
@example
projects / chise / xemacs-chise.git.1 / blobdiff