2 @c This is part of the GNU Emacs Lisp Reference Manual.
3 @c Copyright (C) 1990, 1991, 1992, 1993, 1994, 1995, 1998, 1999, 2000, 2001, 2002
4 @c Free Software Foundation, Inc.
5 @c See the file elisp.texi for copying conditions.
6 @setfilename ../info/display
7 @node Display, Calendar, Processes, Top
10 This chapter describes a number of features related to the display
11 that Emacs presents to the user.
14 * Refresh Screen:: Clearing the screen and redrawing everything on it.
15 * Forcing Redisplay:: Forcing redisplay.
16 * Truncation:: Folding or wrapping long text lines.
17 * The Echo Area:: Where messages are displayed.
18 * Invisible Text:: Hiding part of the buffer text.
19 * Selective Display:: Hiding part of the buffer text (the old way).
20 * Overlay Arrow:: Display of an arrow to indicate position.
21 * Temporary Displays:: Displays that go away automatically.
22 * Overlays:: Use overlays to highlight parts of the buffer.
23 * Width:: How wide a character or string is on the screen.
24 * Faces:: A face defines a graphics style for text characters:
26 * Display Property:: Enabling special display features.
27 * Images:: Displaying images in Emacs buffers.
28 * Blinking:: How Emacs shows the matching open parenthesis.
29 * Inverse Video:: Specifying how the screen looks.
30 * Usual Display:: The usual conventions for displaying nonprinting chars.
31 * Display Tables:: How to specify other conventions.
32 * Beeping:: Audible signal to the user.
33 * Window Systems:: Which window system is being used.
37 @section Refreshing the Screen
39 The function @code{redraw-frame} redisplays the entire contents of a
40 given frame (@pxref{Frames}).
43 @defun redraw-frame frame
44 This function clears and redisplays frame @var{frame}.
47 Even more powerful is @code{redraw-display}:
49 @deffn Command redraw-display
50 This function clears and redisplays all visible frames.
53 Processing user input takes absolute priority over redisplay. If you
54 call these functions when input is available, they do nothing
55 immediately, but a full redisplay does happen eventually---after all the
56 input has been processed.
58 Normally, suspending and resuming Emacs also refreshes the screen.
59 Some terminal emulators record separate contents for display-oriented
60 programs such as Emacs and for ordinary sequential display. If you are
61 using such a terminal, you might want to inhibit the redisplay on
64 @defvar no-redraw-on-reenter
65 @cindex suspend (cf. @code{no-redraw-on-reenter})
66 @cindex resume (cf. @code{no-redraw-on-reenter})
67 This variable controls whether Emacs redraws the entire screen after it
68 has been suspended and resumed. Non-@code{nil} means there is no need
69 to redraw, @code{nil} means redrawing is needed. The default is @code{nil}.
72 @node Forcing Redisplay
73 @section Forcing Redisplay
74 @cindex forcing redisplay
76 Emacs redisplay normally stops if input arrives, and does not happen
77 at all if input is available before it starts. Most of the time, this
78 is exactly what you want. However, you can prevent preemption by
79 binding @code{redisplay-dont-pause} to a non-@code{nil} value.
81 @tindex redisplay-dont-pause
82 @defvar redisplay-dont-pause
83 If this variable is non-@code{nil}, pending input does not
84 prevent or halt redisplay; redisplay occurs, and finishes,
85 regardless of whether input is available. This feature is available
89 You can request a display update, but only if no input is pending,
90 with @code{(sit-for 0)}. To force a display update even when input is
94 (let ((redisplay-dont-pause t))
100 @cindex line wrapping
101 @cindex continuation lines
102 @cindex @samp{$} in display
103 @cindex @samp{\} in display
105 When a line of text extends beyond the right edge of a window, the
106 line can either be continued on the next screen line, or truncated to
107 one screen line. The additional screen lines used to display a long
108 text line are called @dfn{continuation} lines. Normally, a @samp{$} in
109 the rightmost column of the window indicates truncation; a @samp{\} on
110 the rightmost column indicates a line that ``wraps'' onto the next line,
111 which is also called @dfn{continuing} the line. (The display table can
112 specify alternative indicators; see @ref{Display Tables}.)
114 @cindex fringes, and line continuation/truncation indicators
115 On a windowed display, the @samp{$} and @samp{\} indicators are
116 replaced with graphics bitmaps displayed on the thin areas right near
117 the window edges, called the @dfn{fringes}.
119 Note that continuation is different from filling; continuation happens
120 on the screen only, not in the buffer contents, and it breaks a line
121 precisely at the right margin, not at a word boundary. @xref{Filling}.
123 @defopt truncate-lines
124 This buffer-local variable controls how Emacs displays lines that extend
125 beyond the right edge of the window. The default is @code{nil}, which
126 specifies continuation. If the value is non-@code{nil}, then these
129 If the variable @code{truncate-partial-width-windows} is non-@code{nil},
130 then truncation is always used for side-by-side windows (within one
131 frame) regardless of the value of @code{truncate-lines}.
134 @defopt default-truncate-lines
135 This variable is the default value for @code{truncate-lines}, for
136 buffers that do not have buffer-local values for it.
139 @defopt truncate-partial-width-windows
140 This variable controls display of lines that extend beyond the right
141 edge of the window, in side-by-side windows (@pxref{Splitting Windows}).
142 If it is non-@code{nil}, these lines are truncated; otherwise,
143 @code{truncate-lines} says what to do with them.
146 When horizontal scrolling (@pxref{Horizontal Scrolling}) is in use in
147 a window, that forces truncation.
149 You can override the glyphs that indicate continuation or truncation
150 using the display table; see @ref{Display Tables}.
152 If your buffer contains @emph{very} long lines, and you use
153 continuation to display them, just thinking about them can make Emacs
154 redisplay slow. The column computation and indentation functions also
155 become slow. Then you might find it advisable to set
156 @code{cache-long-line-scans} to @code{t}.
158 @defvar cache-long-line-scans
159 If this variable is non-@code{nil}, various indentation and motion
160 functions, and Emacs redisplay, cache the results of scanning the
161 buffer, and consult the cache to avoid rescanning regions of the buffer
162 unless they are modified.
164 Turning on the cache slows down processing of short lines somewhat.
166 This variable is automatically buffer-local in every buffer.
170 @section The Echo Area
171 @cindex error display
174 The @dfn{echo area} is used for displaying messages made with the
175 @code{message} primitive, and for echoing keystrokes. It is not the
176 same as the minibuffer, despite the fact that the minibuffer appears
177 (when active) in the same place on the screen as the echo area. The
178 @cite{GNU Emacs Manual} specifies the rules for resolving conflicts
179 between the echo area and the minibuffer for use of that screen space
180 (@pxref{Minibuffer,, The Minibuffer, emacs, The GNU Emacs Manual}).
181 Error messages appear in the echo area; see @ref{Errors}.
183 You can write output in the echo area by using the Lisp printing
184 functions with @code{t} as the stream (@pxref{Output Functions}), or as
187 @defun message string &rest arguments
188 This function displays a message in the echo area. The
189 argument @var{string} is similar to a C language @code{printf} control
190 string. See @code{format} in @ref{String Conversion}, for the details
191 on the conversion specifications. @code{message} returns the
194 In batch mode, @code{message} prints the message text on the standard
195 error stream, followed by a newline.
197 If @var{string}, or strings among the @var{arguments}, have @code{face}
198 text properties, these affect the way the message is displayed.
201 If @var{string} is @code{nil}, @code{message} clears the echo area; if
202 the echo area has been expanded automatically, this brings it back to
203 its normal size. If the minibuffer is active, this brings the
204 minibuffer contents back onto the screen immediately.
206 @vindex message-truncate-lines
207 Normally, displaying a long message resizes the echo area to display
208 the entire message. But if the variable @code{message-truncate-lines}
209 is non-@code{nil}, the echo area does not resize, and the message is
210 truncated to fit it, as in Emacs 20 and before.
214 (message "Minibuffer depth is %d."
216 @print{} Minibuffer depth is 0.
217 @result{} "Minibuffer depth is 0."
221 ---------- Echo Area ----------
222 Minibuffer depth is 0.
223 ---------- Echo Area ----------
227 To automatically display a message in the echo area or in a pop-buffer,
228 depending on its size, use @code{display-message-or-buffer}.
231 @tindex with-temp-message
232 @defmac with-temp-message message &rest body
233 This construct displays a message in the echo area temporarily, during
234 the execution of @var{body}. It displays @var{message}, executes
235 @var{body}, then returns the value of the last body form while restoring
236 the previous echo area contents.
239 @defun message-or-box string &rest arguments
240 This function displays a message like @code{message}, but may display it
241 in a dialog box instead of the echo area. If this function is called in
242 a command that was invoked using the mouse---more precisely, if
243 @code{last-nonmenu-event} (@pxref{Command Loop Info}) is either
244 @code{nil} or a list---then it uses a dialog box or pop-up menu to
245 display the message. Otherwise, it uses the echo area. (This is the
246 same criterion that @code{y-or-n-p} uses to make a similar decision; see
247 @ref{Yes-or-No Queries}.)
249 You can force use of the mouse or of the echo area by binding
250 @code{last-nonmenu-event} to a suitable value around the call.
253 @defun message-box string &rest arguments
254 This function displays a message like @code{message}, but uses a dialog
255 box (or a pop-up menu) whenever that is possible. If it is impossible
256 to use a dialog box or pop-up menu, because the terminal does not
257 support them, then @code{message-box} uses the echo area, like
261 @defun display-message-or-buffer message &optional buffer-name not-this-window frame
262 @tindex display-message-or-buffer
263 This function displays the message @var{message}, which may be either a
264 string or a buffer. If it is shorter than the maximum height of the
265 echo area, as defined by @code{max-mini-window-height}, it is displayed
266 in the echo area, using @code{message}. Otherwise,
267 @code{display-buffer} is used to show it in a pop-up buffer.
269 Returns either the string shown in the echo area, or when a pop-up
270 buffer is used, the window used to display it.
272 If @var{message} is a string, then the optional argument
273 @var{buffer-name} is the name of the buffer used to display it when a
274 pop-up buffer is used, defaulting to @samp{*Message*}. In the case
275 where @var{message} is a string and displayed in the echo area, it is
276 not specified whether the contents are inserted into the buffer anyway.
278 The optional arguments @var{not-this-window} and @var{frame} are as for
279 @code{display-buffer}, and only used if a buffer is displayed.
282 @defun current-message
283 This function returns the message currently being displayed in the
284 echo area, or @code{nil} if there is none.
287 @defvar cursor-in-echo-area
288 This variable controls where the cursor appears when a message is
289 displayed in the echo area. If it is non-@code{nil}, then the cursor
290 appears at the end of the message. Otherwise, the cursor appears at
291 point---not in the echo area at all.
293 The value is normally @code{nil}; Lisp programs bind it to @code{t}
294 for brief periods of time.
297 @defvar echo-area-clear-hook
298 This normal hook is run whenever the echo area is cleared---either by
299 @code{(message nil)} or for any other reason.
302 Almost all the messages displayed in the echo area are also recorded
303 in the @samp{*Messages*} buffer.
305 @defopt message-log-max
306 This variable specifies how many lines to keep in the @samp{*Messages*}
307 buffer. The value @code{t} means there is no limit on how many lines to
308 keep. The value @code{nil} disables message logging entirely. Here's
309 how to display a message and prevent it from being logged:
312 (let (message-log-max)
317 @defvar echo-keystrokes
318 This variable determines how much time should elapse before command
319 characters echo. Its value must be an integer or floating point number,
321 number of seconds to wait before echoing. If the user types a prefix
322 key (such as @kbd{C-x}) and then delays this many seconds before
323 continuing, the prefix key is echoed in the echo area. (Once echoing
324 begins in a key sequence, all subsequent characters in the same key
325 sequence are echoed immediately.)
327 If the value is zero, then command input is not echoed.
331 @section Invisible Text
333 @cindex invisible text
334 You can make characters @dfn{invisible}, so that they do not appear on
335 the screen, with the @code{invisible} property. This can be either a
336 text property (@pxref{Text Properties}) or a property of an overlay
339 In the simplest case, any non-@code{nil} @code{invisible} property makes
340 a character invisible. This is the default case---if you don't alter
341 the default value of @code{buffer-invisibility-spec}, this is how the
342 @code{invisible} property works.
344 More generally, you can use the variable @code{buffer-invisibility-spec}
345 to control which values of the @code{invisible} property make text
346 invisible. This permits you to classify the text into different subsets
347 in advance, by giving them different @code{invisible} values, and
348 subsequently make various subsets visible or invisible by changing the
349 value of @code{buffer-invisibility-spec}.
351 Controlling visibility with @code{buffer-invisibility-spec} is
352 especially useful in a program to display the list of entries in a
353 database. It permits the implementation of convenient filtering
354 commands to view just a part of the entries in the database. Setting
355 this variable is very fast, much faster than scanning all the text in
356 the buffer looking for properties to change.
358 @defvar buffer-invisibility-spec
359 This variable specifies which kinds of @code{invisible} properties
360 actually make a character invisible.
364 A character is invisible if its @code{invisible} property is
365 non-@code{nil}. This is the default.
368 Each element of the list specifies a criterion for invisibility; if a
369 character's @code{invisible} property fits any one of these criteria,
370 the character is invisible. The list can have two kinds of elements:
374 A character is invisible if its @code{invisible} property value
375 is @var{atom} or if it is a list with @var{atom} as a member.
377 @item (@var{atom} . t)
378 A character is invisible if its @code{invisible} property value
379 is @var{atom} or if it is a list with @var{atom} as a member.
380 Moreover, if this character is at the end of a line and is followed
381 by a visible newline, it displays an ellipsis.
386 Two functions are specifically provided for adding elements to
387 @code{buffer-invisibility-spec} and removing elements from it.
389 @defun add-to-invisibility-spec element
390 Add the element @var{element} to @code{buffer-invisibility-spec}
391 (if it is not already present in that list).
394 @defun remove-from-invisibility-spec element
395 Remove the element @var{element} from @code{buffer-invisibility-spec}.
396 This does nothing if @var{element} is not in the list.
399 One convention about the use of @code{buffer-invisibility-spec} is
400 that a major mode should use the mode's own name as an element of
401 @code{buffer-invisibility-spec} and as the value of the @code{invisible}
405 ;; @r{If you want to display an ellipsis:}
406 (add-to-invisibility-spec '(my-symbol . t))
407 ;; @r{If you don't want ellipsis:}
408 (add-to-invisibility-spec 'my-symbol)
410 (overlay-put (make-overlay beginning end)
411 'invisible 'my-symbol)
413 ;; @r{When done with the overlays:}
414 (remove-from-invisibility-spec '(my-symbol . t))
415 ;; @r{Or respectively:}
416 (remove-from-invisibility-spec 'my-symbol)
419 @vindex line-move-ignore-invisible
420 Ordinarily, commands that operate on text or move point do not care
421 whether the text is invisible. The user-level line motion commands
422 explicitly ignore invisible newlines if
423 @code{line-move-ignore-invisible} is non-@code{nil}, but only because
424 they are explicitly programmed to do so.
426 Incremental search can make invisible overlays visible temporarily
427 and/or permanently when a match includes invisible text. To enable
428 this, the overlay should have a non-@code{nil}
429 @code{isearch-open-invisible} property. The property value should be a
430 function to be called with the overlay as an argument. This function
431 should make the overlay visible permanently; it is used when the match
432 overlaps the overlay on exit from the search.
434 During the search, such overlays are made temporarily visible by
435 temporarily modifying their invisible and intangible properties. If you
436 want this to be done differently for a certain overlay, give it an
437 @code{isearch-open-invisible-temporary} property which is a function.
438 The function is called with two arguments: the first is the overlay, and
439 the second is @code{nil} to make the overlay visible, or @code{t} to
440 make it invisible again.
442 @node Selective Display
443 @section Selective Display
444 @cindex selective display
446 @dfn{Selective display} refers to a pair of related features for
447 hiding certain lines on the screen.
449 The first variant, explicit selective display, is designed for use in
450 a Lisp program: it controls which lines are hidden by altering the text.
451 The invisible text feature (@pxref{Invisible Text}) has partially
452 replaced this feature.
454 In the second variant, the choice of lines to hide is made
455 automatically based on indentation. This variant is designed to be a
458 The way you control explicit selective display is by replacing a
459 newline (control-j) with a carriage return (control-m). The text that
460 was formerly a line following that newline is now invisible. Strictly
461 speaking, it is temporarily no longer a line at all, since only newlines
462 can separate lines; it is now part of the previous line.
464 Selective display does not directly affect editing commands. For
465 example, @kbd{C-f} (@code{forward-char}) moves point unhesitatingly into
466 invisible text. However, the replacement of newline characters with
467 carriage return characters affects some editing commands. For example,
468 @code{next-line} skips invisible lines, since it searches only for
469 newlines. Modes that use selective display can also define commands
470 that take account of the newlines, or that make parts of the text
471 visible or invisible.
473 When you write a selectively displayed buffer into a file, all the
474 control-m's are output as newlines. This means that when you next read
475 in the file, it looks OK, with nothing invisible. The selective display
476 effect is seen only within Emacs.
478 @defvar selective-display
479 This buffer-local variable enables selective display. This means that
480 lines, or portions of lines, may be made invisible.
484 If the value of @code{selective-display} is @code{t}, then the character
485 control-m marks the start of invisible text; the control-m, and the rest
486 of the line following it, are not displayed. This is explicit selective
490 If the value of @code{selective-display} is a positive integer, then
491 lines that start with more than that many columns of indentation are not
495 When some portion of a buffer is invisible, the vertical movement
496 commands operate as if that portion did not exist, allowing a single
497 @code{next-line} command to skip any number of invisible lines.
498 However, character movement commands (such as @code{forward-char}) do
499 not skip the invisible portion, and it is possible (if tricky) to insert
500 or delete text in an invisible portion.
502 In the examples below, we show the @emph{display appearance} of the
503 buffer @code{foo}, which changes with the value of
504 @code{selective-display}. The @emph{contents} of the buffer do not
509 (setq selective-display nil)
512 ---------- Buffer: foo ----------
519 ---------- Buffer: foo ----------
523 (setq selective-display 2)
526 ---------- Buffer: foo ----------
531 ---------- Buffer: foo ----------
536 @defvar selective-display-ellipses
537 If this buffer-local variable is non-@code{nil}, then Emacs displays
538 @samp{@dots{}} at the end of a line that is followed by invisible text.
539 This example is a continuation of the previous one.
543 (setq selective-display-ellipses t)
546 ---------- Buffer: foo ----------
551 ---------- Buffer: foo ----------
555 You can use a display table to substitute other text for the ellipsis
556 (@samp{@dots{}}). @xref{Display Tables}.
560 @section The Overlay Arrow
561 @cindex overlay arrow
563 The @dfn{overlay arrow} is useful for directing the user's attention
564 to a particular line in a buffer. For example, in the modes used for
565 interface to debuggers, the overlay arrow indicates the line of code
566 about to be executed.
568 @defvar overlay-arrow-string
569 @cindex fringe, and overlay arrow display
570 This variable holds the string to display to call attention to a
571 particular line, or @code{nil} if the arrow feature is not in use.
572 On a graphical display the contents of the string are ignored; instead a
573 glyph is displayed in the fringe area to the left of the display area.
576 @defvar overlay-arrow-position
577 This variable holds a marker that indicates where to display the overlay
578 arrow. It should point at the beginning of a line. On a non-graphical
579 display the arrow text
580 appears at the beginning of that line, overlaying any text that would
581 otherwise appear. Since the arrow is usually short, and the line
582 usually begins with indentation, normally nothing significant is
585 The overlay string is displayed only in the buffer that this marker
586 points into. Thus, only one buffer can have an overlay arrow at any
588 @c !!! overlay-arrow-position: but the overlay string may remain in the display
589 @c of some other buffer until an update is required. This should be fixed
593 You can do a similar job by creating an overlay with a
594 @code{before-string} property. @xref{Overlay Properties}.
596 @node Temporary Displays
597 @section Temporary Displays
599 Temporary displays are used by Lisp programs to put output into a
600 buffer and then present it to the user for perusal rather than for
601 editing. Many help commands use this feature.
603 @defspec with-output-to-temp-buffer buffer-name forms@dots{}
604 This function executes @var{forms} while arranging to insert any output
605 they print into the buffer named @var{buffer-name}, which is first
606 created if necessary, and put into Help mode. Finally, the buffer is
607 displayed in some window, but not selected.
609 If the @var{forms} do not change the major mode in the output buffer, so
610 that it is still Help mode at the end of their execution, then
611 @code{with-output-to-temp-buffer} makes this buffer read-only at the
612 end, and also scans it for function and variable names to make them into
613 clickable cross-references.
615 The string @var{buffer-name} specifies the temporary buffer, which
616 need not already exist. The argument must be a string, not a buffer.
617 The buffer is erased initially (with no questions asked), and it is
618 marked as unmodified after @code{with-output-to-temp-buffer} exits.
620 @code{with-output-to-temp-buffer} binds @code{standard-output} to the
621 temporary buffer, then it evaluates the forms in @var{forms}. Output
622 using the Lisp output functions within @var{forms} goes by default to
623 that buffer (but screen display and messages in the echo area, although
624 they are ``output'' in the general sense of the word, are not affected).
625 @xref{Output Functions}.
627 Several hooks are available for customizing the behavior
628 of this construct; they are listed below.
630 The value of the last form in @var{forms} is returned.
634 ---------- Buffer: foo ----------
635 This is the contents of foo.
636 ---------- Buffer: foo ----------
640 (with-output-to-temp-buffer "foo"
642 (print standard-output))
643 @result{} #<buffer foo>
645 ---------- Buffer: foo ----------
650 ---------- Buffer: foo ----------
655 @defvar temp-buffer-show-function
656 If this variable is non-@code{nil}, @code{with-output-to-temp-buffer}
657 calls it as a function to do the job of displaying a help buffer. The
658 function gets one argument, which is the buffer it should display.
660 It is a good idea for this function to run @code{temp-buffer-show-hook}
661 just as @code{with-output-to-temp-buffer} normally would, inside of
662 @code{save-selected-window} and with the chosen window and buffer
666 @defvar temp-buffer-setup-hook
667 @tindex temp-buffer-setup-hook
668 This normal hook is run by @code{with-output-to-temp-buffer} before
669 evaluating @var{body}. When the hook runs, the temporary buffer is
670 current. This hook is normally set up with a function to put the
674 @defvar temp-buffer-show-hook
675 This normal hook is run by @code{with-output-to-temp-buffer} after
676 displaying the temporary buffer. When the hook runs, the temporary buffer
677 is current, and the window it was displayed in is selected. This hook
678 is normally set up with a function to make the buffer read only, and
679 find function names and variable names in it, provided the major mode
683 @defun momentary-string-display string position &optional char message
684 This function momentarily displays @var{string} in the current buffer at
685 @var{position}. It has no effect on the undo list or on the buffer's
688 The momentary display remains until the next input event. If the next
689 input event is @var{char}, @code{momentary-string-display} ignores it
690 and returns. Otherwise, that event remains buffered for subsequent use
691 as input. Thus, typing @var{char} will simply remove the string from
692 the display, while typing (say) @kbd{C-f} will remove the string from
693 the display and later (presumably) move point forward. The argument
694 @var{char} is a space by default.
696 The return value of @code{momentary-string-display} is not meaningful.
698 If the string @var{string} does not contain control characters, you can
699 do the same job in a more general way by creating (and then subsequently
700 deleting) an overlay with a @code{before-string} property.
701 @xref{Overlay Properties}.
703 If @var{message} is non-@code{nil}, it is displayed in the echo area
704 while @var{string} is displayed in the buffer. If it is @code{nil}, a
705 default message says to type @var{char} to continue.
707 In this example, point is initially located at the beginning of the
712 ---------- Buffer: foo ----------
713 This is the contents of foo.
715 ---------- Buffer: foo ----------
719 (momentary-string-display
720 "**** Important Message! ****"
722 "Type RET when done reading")
727 ---------- Buffer: foo ----------
728 This is the contents of foo.
729 **** Important Message! ****Second line.
730 ---------- Buffer: foo ----------
732 ---------- Echo Area ----------
733 Type RET when done reading
734 ---------- Echo Area ----------
743 You can use @dfn{overlays} to alter the appearance of a buffer's text on
744 the screen, for the sake of presentation features. An overlay is an
745 object that belongs to a particular buffer, and has a specified
746 beginning and end. It also has properties that you can examine and set;
747 these affect the display of the text within the overlay.
750 * Overlay Properties:: How to read and set properties.
751 What properties do to the screen display.
752 * Managing Overlays:: Creating and moving overlays.
753 * Finding Overlays:: Searching for overlays.
756 @node Overlay Properties
757 @subsection Overlay Properties
759 Overlay properties are like text properties in that the properties that
760 alter how a character is displayed can come from either source. But in
761 most respects they are different. Text properties are considered a part
762 of the text; overlays are specifically considered not to be part of the
763 text. Thus, copying text between various buffers and strings preserves
764 text properties, but does not try to preserve overlays. Changing a
765 buffer's text properties marks the buffer as modified, while moving an
766 overlay or changing its properties does not. Unlike text property
767 changes, overlay changes are not recorded in the buffer's undo list.
768 @xref{Text Properties}, for comparison.
770 These functions are used for reading and writing the properties of an
773 @defun overlay-get overlay prop
774 This function returns the value of property @var{prop} recorded in
775 @var{overlay}, if any. If @var{overlay} does not record any value for
776 that property, but it does have a @code{category} property which is a
777 symbol, that symbol's @var{prop} property is used. Otherwise, the value
781 @defun overlay-put overlay prop value
782 This function sets the value of property @var{prop} recorded in
783 @var{overlay} to @var{value}. It returns @var{value}.
786 See also the function @code{get-char-property} which checks both
787 overlay properties and text properties for a given character.
788 @xref{Examining Properties}.
790 Many overlay properties have special meanings; here is a table
795 @kindex priority @r{(overlay property)}
796 This property's value (which should be a nonnegative number) determines
797 the priority of the overlay. The priority matters when two or more
798 overlays cover the same character and both specify a face for display;
799 the one whose @code{priority} value is larger takes priority over the
800 other, and its face attributes override the face attributes of the lower
803 Currently, all overlays take priority over text properties. Please
804 avoid using negative priority values, as we have not yet decided just
805 what they should mean.
808 @kindex window @r{(overlay property)}
809 If the @code{window} property is non-@code{nil}, then the overlay
810 applies only on that window.
813 @kindex category @r{(overlay property)}
814 If an overlay has a @code{category} property, we call it the
815 @dfn{category} of the overlay. It should be a symbol. The properties
816 of the symbol serve as defaults for the properties of the overlay.
819 @kindex face @r{(overlay property)}
820 This property controls the way text is displayed---for example, which
821 font and which colors. @xref{Faces}, for more information.
823 In the simplest case, the value is a face name. It can also be a list;
824 then each element can be any of these possibilities:
828 A face name (a symbol or string).
831 Starting in Emacs 21, a property list of face attributes. This has the
832 form (@var{keyword} @var{value} @dots{}), where each @var{keyword} is a
833 face attribute name and @var{value} is a meaningful value for that
834 attribute. With this feature, you do not need to create a face each
835 time you want to specify a particular attribute for certain text.
836 @xref{Face Attributes}.
839 A cons cell of the form @code{(foreground-color . @var{color-name})} or
840 @code{(background-color . @var{color-name})}. These elements specify
841 just the foreground color or just the background color.
843 @code{(foreground-color . @var{color-name})} is equivalent to
844 @code{(:foreground @var{color-name})}, and likewise for the background.
848 @kindex mouse-face @r{(overlay property)}
849 This property is used instead of @code{face} when the mouse is within
850 the range of the overlay.
853 @kindex display @r{(overlay property)}
854 This property activates various features that change the
855 way text is displayed. For example, it can make text appear taller
856 or shorter, higher or lower, wider or narrower, or replaced with an image.
857 @xref{Display Property}.
860 @kindex help-echo @r{(text property)}
861 If an overlay has a @code{help-echo} property, then when you move the
862 mouse onto the text in the overlay, Emacs displays a help string in the
863 echo area, or in the tooltip window. For details see @ref{Text
866 @item modification-hooks
867 @kindex modification-hooks @r{(overlay property)}
868 This property's value is a list of functions to be called if any
869 character within the overlay is changed or if text is inserted strictly
872 The hook functions are called both before and after each change.
873 If the functions save the information they receive, and compare notes
874 between calls, they can determine exactly what change has been made
877 When called before a change, each function receives four arguments: the
878 overlay, @code{nil}, and the beginning and end of the text range to be
881 When called after a change, each function receives five arguments: the
882 overlay, @code{t}, the beginning and end of the text range just
883 modified, and the length of the pre-change text replaced by that range.
884 (For an insertion, the pre-change length is zero; for a deletion, that
885 length is the number of characters deleted, and the post-change
886 beginning and end are equal.)
888 @item insert-in-front-hooks
889 @kindex insert-in-front-hooks @r{(overlay property)}
890 This property's value is a list of functions to be called before and
891 after inserting text right at the beginning of the overlay. The calling
892 conventions are the same as for the @code{modification-hooks} functions.
894 @item insert-behind-hooks
895 @kindex insert-behind-hooks @r{(overlay property)}
896 This property's value is a list of functions to be called before and
897 after inserting text right at the end of the overlay. The calling
898 conventions are the same as for the @code{modification-hooks} functions.
901 @kindex invisible @r{(overlay property)}
902 The @code{invisible} property can make the text in the overlay
903 invisible, which means that it does not appear on the screen.
904 @xref{Invisible Text}, for details.
907 @kindex intangible @r{(overlay property)}
908 The @code{intangible} property on an overlay works just like the
909 @code{intangible} text property. @xref{Special Properties}, for details.
911 @item isearch-open-invisible
912 This property tells incremental search how to make an invisible overlay
913 visible, permanently, if the final match overlaps it. @xref{Invisible
916 @item isearch-open-invisible-temporary
917 This property tells incremental search how to make an invisible overlay
918 visible, temporarily, during the search. @xref{Invisible Text}.
921 @kindex before-string @r{(overlay property)}
922 This property's value is a string to add to the display at the beginning
923 of the overlay. The string does not appear in the buffer in any
924 sense---only on the screen.
927 @kindex after-string @r{(overlay property)}
928 This property's value is a string to add to the display at the end of
929 the overlay. The string does not appear in the buffer in any
930 sense---only on the screen.
933 @kindex evaporate @r{(overlay property)}
934 If this property is non-@code{nil}, the overlay is deleted automatically
935 if it ever becomes empty (i.e., if it spans no characters).
938 @cindex keymap of character (and overlays)
939 @kindex local-map @r{(overlay property)}
940 If this property is non-@code{nil}, it specifies a keymap for a portion
941 of the text. The property's value replaces the buffer's local map, when
942 the character after point is within the overlay. @xref{Active Keymaps}.
945 @kindex keymap @r{(overlay property)}
946 The @code{keymap} property is similar to @code{local-map} but overrides the
947 buffer's local map (and the map specified by the @code{local-map}
948 property) rather than replacing it.
951 @node Managing Overlays
952 @subsection Managing Overlays
954 This section describes the functions to create, delete and move
955 overlays, and to examine their contents.
957 @defun make-overlay start end &optional buffer front-advance rear-advance
958 This function creates and returns an overlay that belongs to
959 @var{buffer} and ranges from @var{start} to @var{end}. Both @var{start}
960 and @var{end} must specify buffer positions; they may be integers or
961 markers. If @var{buffer} is omitted, the overlay is created in the
964 The arguments @var{front-advance} and @var{rear-advance} specify the
965 insertion type for the start of the overlay and for the end of the
966 overlay, respectively. @xref{Marker Insertion Types}.
969 @defun overlay-start overlay
970 This function returns the position at which @var{overlay} starts,
974 @defun overlay-end overlay
975 This function returns the position at which @var{overlay} ends,
979 @defun overlay-buffer overlay
980 This function returns the buffer that @var{overlay} belongs to.
983 @defun delete-overlay overlay
984 This function deletes @var{overlay}. The overlay continues to exist as
985 a Lisp object, and its property list is unchanged, but it ceases to be
986 attached to the buffer it belonged to, and ceases to have any effect on
989 A deleted overlay is not permanently disconnected. You can give it a
990 position in a buffer again by calling @code{move-overlay}.
993 @defun move-overlay overlay start end &optional buffer
994 This function moves @var{overlay} to @var{buffer}, and places its bounds
995 at @var{start} and @var{end}. Both arguments @var{start} and @var{end}
996 must specify buffer positions; they may be integers or markers.
998 If @var{buffer} is omitted, @var{overlay} stays in the same buffer it
999 was already associated with; if @var{overlay} was deleted, it goes into
1002 The return value is @var{overlay}.
1004 This is the only valid way to change the endpoints of an overlay. Do
1005 not try modifying the markers in the overlay by hand, as that fails to
1006 update other vital data structures and can cause some overlays to be
1010 Here are some examples:
1013 ;; @r{Create an overlay.}
1014 (setq foo (make-overlay 1 10))
1015 @result{} #<overlay from 1 to 10 in display.texi>
1020 (overlay-buffer foo)
1021 @result{} #<buffer display.texi>
1022 ;; @r{Give it a property we can check later.}
1023 (overlay-put foo 'happy t)
1025 ;; @r{Verify the property is present.}
1026 (overlay-get foo 'happy)
1028 ;; @r{Move the overlay.}
1029 (move-overlay foo 5 20)
1030 @result{} #<overlay from 5 to 20 in display.texi>
1035 ;; @r{Delete the overlay.}
1036 (delete-overlay foo)
1038 ;; @r{Verify it is deleted.}
1040 @result{} #<overlay in no buffer>
1041 ;; @r{A deleted overlay has no position.}
1046 (overlay-buffer foo)
1048 ;; @r{Undelete the overlay.}
1049 (move-overlay foo 1 20)
1050 @result{} #<overlay from 1 to 20 in display.texi>
1051 ;; @r{Verify the results.}
1056 (overlay-buffer foo)
1057 @result{} #<buffer display.texi>
1058 ;; @r{Moving and deleting the overlay does not change its properties.}
1059 (overlay-get foo 'happy)
1063 @node Finding Overlays
1064 @subsection Searching for Overlays
1066 @defun overlays-at pos
1067 This function returns a list of all the overlays that cover the
1068 character at position @var{pos} in the current buffer. The list is in
1069 no particular order. An overlay contains position @var{pos} if it
1070 begins at or before @var{pos}, and ends after @var{pos}.
1072 To illustrate usage, here is a Lisp function that returns a list of the
1073 overlays that specify property @var{prop} for the character at point:
1076 (defun find-overlays-specifying (prop)
1077 (let ((overlays (overlays-at (point)))
1080 (let ((overlay (car overlays)))
1081 (if (overlay-get overlay prop)
1082 (setq found (cons overlay found))))
1083 (setq overlays (cdr overlays)))
1088 @defun overlays-in beg end
1089 This function returns a list of the overlays that overlap the region
1090 @var{beg} through @var{end}. ``Overlap'' means that at least one
1091 character is contained within the overlay and also contained within the
1092 specified region; however, empty overlays are included in the result if
1093 they are located at @var{beg}, or strictly between @var{beg} and @var{end}.
1096 @defun next-overlay-change pos
1097 This function returns the buffer position of the next beginning or end
1098 of an overlay, after @var{pos}.
1101 @defun previous-overlay-change pos
1102 This function returns the buffer position of the previous beginning or
1103 end of an overlay, before @var{pos}.
1106 Here's an easy way to use @code{next-overlay-change} to search for the
1107 next character which gets a non-@code{nil} @code{happy} property from
1108 either its overlays or its text properties (@pxref{Property Search}):
1111 (defun find-overlay-prop (prop)
1113 (while (and (not (eobp))
1114 (not (get-char-property (point) 'happy)))
1115 (goto-char (min (next-overlay-change (point))
1116 (next-single-property-change (point) 'happy))))
1123 Since not all characters have the same width, these functions let you
1124 check the width of a character. @xref{Primitive Indent}, and
1125 @ref{Screen Lines}, for related functions.
1127 @defun char-width char
1128 This function returns the width in columns of the character @var{char},
1129 if it were displayed in the current buffer and the selected window.
1132 @defun string-width string
1133 This function returns the width in columns of the string @var{string},
1134 if it were displayed in the current buffer and the selected window.
1137 @defun truncate-string-to-width string width &optional start-column padding
1138 This function returns the part of @var{string} that fits within
1139 @var{width} columns, as a new string.
1141 If @var{string} does not reach @var{width}, then the result ends where
1142 @var{string} ends. If one multi-column character in @var{string}
1143 extends across the column @var{width}, that character is not included in
1144 the result. Thus, the result can fall short of @var{width} but cannot
1147 The optional argument @var{start-column} specifies the starting column.
1148 If this is non-@code{nil}, then the first @var{start-column} columns of
1149 the string are omitted from the value. If one multi-column character in
1150 @var{string} extends across the column @var{start-column}, that
1151 character is not included.
1153 The optional argument @var{padding}, if non-@code{nil}, is a padding
1154 character added at the beginning and end of the result string, to extend
1155 it to exactly @var{width} columns. The padding character is used at the
1156 end of the result if it falls short of @var{width}. It is also used at
1157 the beginning of the result if one multi-column character in
1158 @var{string} extends across the column @var{start-column}.
1161 (truncate-string-to-width "\tab\t" 12 4)
1163 (truncate-string-to-width "\tab\t" 12 4 ?\ )
1172 A @dfn{face} is a named collection of graphical attributes: font
1173 family, foreground color, background color, optional underlining, and
1174 many others. Faces are used in Emacs to control the style of display of
1175 particular parts of the text or the frame.
1178 Each face has its own @dfn{face number}, which distinguishes faces at
1179 low levels within Emacs. However, for most purposes, you refer to
1180 faces in Lisp programs by their names.
1183 This function returns @code{t} if @var{object} is a face name symbol (or
1184 if it is a vector of the kind used internally to record face data). It
1185 returns @code{nil} otherwise.
1188 Each face name is meaningful for all frames, and by default it has the
1189 same meaning in all frames. But you can arrange to give a particular
1190 face name a special meaning in one frame if you wish.
1193 * Standard Faces:: The faces Emacs normally comes with.
1194 * Defining Faces:: How to define a face with @code{defface}.
1195 * Face Attributes:: What is in a face?
1196 * Attribute Functions:: Functions to examine and set face attributes.
1197 * Merging Faces:: How Emacs combines the faces specified for a character.
1198 * Font Selection:: Finding the best available font for a face.
1199 * Face Functions:: How to define and examine faces.
1200 * Auto Faces:: Hook for automatic face assignment.
1201 * Font Lookup:: Looking up the names of available fonts
1202 and information about them.
1203 * Fontsets:: A fontset is a collection of fonts
1204 that handle a range of character sets.
1207 @node Standard Faces
1208 @subsection Standard Faces
1210 This table lists all the standard faces and their uses. Most of them
1211 are used for displaying certain parts of the frames or certain kinds of
1212 text; you can control how those places look by customizing these faces.
1216 @kindex default @r{(face name)}
1217 This face is used for ordinary text.
1220 @kindex mode-line @r{(face name)}
1221 This face is used for the mode line of the selected window, and for
1222 menu bars when toolkit menus are not used---but only if
1223 @code{mode-line-inverse-video} is non-@code{nil}.
1226 @kindex modeline @r{(face name)}
1227 This is an alias for the @code{mode-line} face, for compatibility with
1230 @item mode-line-inactive
1231 @kindex mode-line-inactive @r{(face name)}
1232 This face is used for mode lines of non-selected windows.
1233 This face inherits from @code{mode-line}, so changes
1234 in that face affect all windows.
1237 @kindex header-line @r{(face name)}
1238 This face is used for the header lines of windows that have them.
1241 This face controls the display of menus, both their colors and their
1242 font. (This works only on certain systems.)
1245 @kindex fringe @r{(face name)}
1246 This face controls the colors of window fringes, the thin areas on
1247 either side that are used to display continuation and truncation glyphs.
1249 @item minibuffer-prompt
1250 @kindex minibuffer-prompt @r{(face name)}
1251 @vindex minibuffer-prompt-properties
1252 This face is used for the text of minibuffer prompts. By default,
1253 Emacs automatically adds this face to the value of
1254 @code{minibuffer-prompt-properties}, which is a list of text
1255 properties used to display the prompt text.
1258 @kindex scroll-bar @r{(face name)}
1259 This face controls the colors for display of scroll bars.
1262 @kindex tool-bar @r{(face name)}
1263 This face is used for display of the tool bar, if any.
1266 @kindex region @r{(face name)}
1267 This face is used for highlighting the region in Transient Mark mode.
1269 @item secondary-selection
1270 @kindex secondary-selection @r{(face name)}
1271 This face is used to show any secondary selection you have made.
1274 @kindex highlight @r{(face name)}
1275 This face is meant to be used for highlighting for various purposes.
1277 @item trailing-whitespace
1278 @kindex trailing-whitespace @r{(face name)}
1279 This face is used to display excess whitespace at the end of a line,
1280 if @code{show-trailing-whitespace} is non-@code{nil}.
1283 In contrast, these faces are provided to change the appearance of text
1284 in specific ways. You can use them on specific text, when you want
1285 the effects they produce.
1289 @kindex bold @r{(face name)}
1290 This face uses a bold font, if possible. It uses the bold variant of
1291 the frame's font, if it has one. It's up to you to choose a default
1292 font that has a bold variant, if you want to use one.
1295 @kindex italic @r{(face name)}
1296 This face uses the italic variant of the frame's font, if it has one.
1299 @kindex bold-italic @r{(face name)}
1300 This face uses the bold italic variant of the frame's font, if it has
1304 @kindex underline @r{(face name)}
1305 This face underlines text.
1308 @kindex fixed-pitch @r{(face name)}
1309 This face forces use of a particular fixed-width font.
1311 @item variable-pitch
1312 @kindex variable-pitch @r{(face name)}
1313 This face forces use of a particular variable-width font. It's
1314 reasonable to customize this to use a different variable-width font, if
1315 you like, but you should not make it a fixed-width font.
1318 @defvar show-trailing-whitespace
1319 @tindex show-trailing-whitespace
1320 If this variable is non-@code{nil}, Emacs uses the
1321 @code{trailing-whitespace} face to display any spaces and tabs at the
1325 @node Defining Faces
1326 @subsection Defining Faces
1328 The way to define a new face is with @code{defface}. This creates a
1329 kind of customization item (@pxref{Customization}) which the user can
1330 customize using the Customization buffer (@pxref{Easy Customization,,,
1331 emacs, The GNU Emacs Manual}).
1333 @defmac defface face spec doc [keyword value]...
1334 This declares @var{face} as a customizable face that defaults according
1335 to @var{spec}. You should not quote the symbol @var{face}. The
1336 argument @var{doc} specifies the face documentation. The keywords you
1337 can use in @code{defface} are the same ones that are meaningful in both
1338 @code{defgroup} and @code{defcustom} (@pxref{Common Keywords}).
1340 When @code{defface} executes, it defines the face according to
1341 @var{spec}, then uses any customizations that were read from the
1342 init file (@pxref{Init File}) to override that specification.
1344 The purpose of @var{spec} is to specify how the face should appear on
1345 different kinds of terminals. It should be an alist whose elements have
1346 the form @code{(@var{display} @var{atts})}. Each element's @sc{car},
1347 @var{display}, specifies a class of terminals. The element's second element,
1348 @var{atts}, is a list of face attributes and their values; it specifies
1349 what the face should look like on that kind of terminal. The possible
1350 attributes are defined in the value of @code{custom-face-attributes}.
1352 The @var{display} part of an element of @var{spec} determines which
1353 frames the element applies to. If more than one element of @var{spec}
1354 matches a given frame, the first matching element is the only one used
1355 for that frame. There are two possibilities for @var{display}:
1359 This element of @var{spec} matches all frames. Therefore, any
1360 subsequent elements of @var{spec} are never used. Normally
1361 @code{t} is used in the last (or only) element of @var{spec}.
1364 If @var{display} is a list, each element should have the form
1365 @code{(@var{characteristic} @var{value}@dots{})}. Here
1366 @var{characteristic} specifies a way of classifying frames, and the
1367 @var{value}s are possible classifications which @var{display} should
1368 apply to. Here are the possible values of @var{characteristic}:
1372 The kind of window system the frame uses---either @code{graphic} (any
1373 graphics-capable display), @code{x}, @code{pc} (for the MS-DOS console),
1374 @code{w32} (for MS Windows 9X/NT), or @code{tty} (a non-graphics-capable
1378 What kinds of colors the frame supports---either @code{color},
1379 @code{grayscale}, or @code{mono}.
1382 The kind of background---either @code{light} or @code{dark}.
1385 Whether or not the frame can display the face attributes given in
1386 @var{value}@dots{} (@pxref{Face Attributes}). See the documentation
1387 for the function @code{display-supports-face-attributes-p} for more
1388 information on exactly how this testing is done. @xref{Display Face
1392 If an element of @var{display} specifies more than one @var{value} for a
1393 given @var{characteristic}, any of those values is acceptable. If
1394 @var{display} has more than one element, each element should specify a
1395 different @var{characteristic}; then @emph{each} characteristic of the
1396 frame must match one of the @var{value}s specified for it in
1401 Here's how the standard face @code{region} is defined:
1406 `((((type tty) (class color))
1407 (:background "blue" :foreground "white"))
1409 (((type tty) (class mono))
1411 (((class color) (background dark))
1412 (:background "blue"))
1413 (((class color) (background light))
1414 (:background "lightblue"))
1415 (t (:background "gray")))
1417 "Basic face for highlighting the region."
1418 :group 'basic-faces)
1422 Internally, @code{defface} uses the symbol property
1423 @code{face-defface-spec} to record the face attributes specified in
1424 @code{defface}, @code{saved-face} for the attributes saved by the user
1425 with the customization buffer, and @code{face-documentation} for the
1426 documentation string.
1428 @defopt frame-background-mode
1429 This option, if non-@code{nil}, specifies the background type to use for
1430 interpreting face definitions. If it is @code{dark}, then Emacs treats
1431 all frames as if they had a dark background, regardless of their actual
1432 background colors. If it is @code{light}, then Emacs treats all frames
1433 as if they had a light background.
1436 @node Face Attributes
1437 @subsection Face Attributes
1438 @cindex face attributes
1440 The effect of using a face is determined by a fixed set of @dfn{face
1441 attributes}. This table lists all the face attributes, and what they
1442 mean. Note that in general, more than one face can be specified for a
1443 given piece of text; when that happens, the attributes of all the faces
1444 are merged to specify how to display the text. @xref{Merging Faces}.
1446 In Emacs 21, any attribute in a face can have the value
1447 @code{unspecified}. This means the face doesn't specify that attribute.
1448 In face merging, when the first face fails to specify a particular
1449 attribute, that means the next face gets a chance. However, the
1450 @code{default} face must specify all attributes.
1452 Some of these font attributes are meaningful only on certain kinds of
1453 displays---if your display cannot handle a certain attribute, the
1454 attribute is ignored. (The attributes @code{:family}, @code{:width},
1455 @code{:height}, @code{:weight}, and @code{:slant} correspond to parts of
1456 an X Logical Font Descriptor.)
1460 Font family name, or fontset name (@pxref{Fontsets}). If you specify a
1461 font family name, the wild-card characters @samp{*} and @samp{?} are
1465 Relative proportionate width, also known as the character set width or
1466 set width. This should be one of the symbols @code{ultra-condensed},
1467 @code{extra-condensed}, @code{condensed}, @code{semi-condensed},
1468 @code{normal}, @code{semi-expanded}, @code{expanded},
1469 @code{extra-expanded}, or @code{ultra-expanded}.
1472 Either the font height, an integer in units of 1/10 point, a floating
1473 point number specifying the amount by which to scale the height of any
1474 underlying face, or a function, which is called with the old height
1475 (from the underlying face), and should return the new height.
1478 Font weight---a symbol from this series (from most dense to most faint):
1479 @code{ultra-bold}, @code{extra-bold}, @code{bold}, @code{semi-bold},
1480 @code{normal}, @code{semi-light}, @code{light}, @code{extra-light},
1481 or @code{ultra-light}.
1483 On a text-only terminal, any weight greater than normal is displayed as
1484 extra bright, and any weight less than normal is displayed as
1485 half-bright (provided the terminal supports the feature).
1488 Font slant---one of the symbols @code{italic}, @code{oblique}, @code{normal},
1489 @code{reverse-italic}, or @code{reverse-oblique}.
1491 On a text-only terminal, slanted text is displayed as half-bright, if
1492 the terminal supports the feature.
1495 Foreground color, a string.
1498 Background color, a string.
1500 @item :inverse-video
1501 Whether or not characters should be displayed in inverse video. The
1502 value should be @code{t} (yes) or @code{nil} (no).
1505 The background stipple, a bitmap.
1507 The value can be a string; that should be the name of a file containing
1508 external-format X bitmap data. The file is found in the directories
1509 listed in the variable @code{x-bitmap-file-path}.
1511 Alternatively, the value can specify the bitmap directly, with a list
1512 of the form @code{(@var{width} @var{height} @var{data})}. Here,
1513 @var{width} and @var{height} specify the size in pixels, and
1514 @var{data} is a string containing the raw bits of the bitmap, row by
1515 row. Each row occupies @math{(@var{width} + 7) / 8} consecutive bytes
1516 in the string (which should be a unibyte string for best results).
1517 This means that each row always occupies at least one whole byte.
1519 If the value is @code{nil}, that means use no stipple pattern.
1521 Normally you do not need to set the stipple attribute, because it is
1522 used automatically to handle certain shades of gray.
1525 Whether or not characters should be underlined, and in what color. If
1526 the value is @code{t}, underlining uses the foreground color of the
1527 face. If the value is a string, underlining uses that color. The
1528 value @code{nil} means do not underline.
1531 Whether or not characters should be overlined, and in what color.
1532 The value is used like that of @code{:underline}.
1534 @item :strike-through
1535 Whether or not characters should be strike-through, and in what
1536 color. The value is used like that of @code{:underline}.
1539 The name of a face from which to inherit attributes, or a list of face
1540 names. Attributes from inherited faces are merged into the face like an
1541 underlying face would be, with higher priority than underlying faces.
1544 Whether or not a box should be drawn around characters, its color, the
1545 width of the box lines, and 3D appearance.
1548 Here are the possible values of the @code{:box} attribute, and what
1556 Draw a box with lines of width 1, in the foreground color.
1559 Draw a box with lines of width 1, in color @var{color}.
1561 @item @code{(:line-width @var{width} :color @var{color} :style @var{style})}
1562 This way you can explicitly specify all aspects of the box. The value
1563 @var{width} specifies the width of the lines to draw; it defaults to 1.
1565 The value @var{color} specifies the color to draw with. The default is
1566 the foreground color of the face for simple boxes, and the background
1567 color of the face for 3D boxes.
1569 The value @var{style} specifies whether to draw a 3D box. If it is
1570 @code{released-button}, the box looks like a 3D button that is not being
1571 pressed. If it is @code{pressed-button}, the box looks like a 3D button
1572 that is being pressed. If it is @code{nil} or omitted, a plain 2D box
1576 The attributes @code{:overline}, @code{:strike-through} and
1577 @code{:box} are new in Emacs 21. The attributes @code{:family},
1578 @code{:height}, @code{:width}, @code{:weight}, @code{:slant} are also
1579 new; previous versions used the following attributes, now semi-obsolete,
1580 to specify some of the same information:
1584 This attribute specifies the font name.
1587 A non-@code{nil} value specifies a bold font.
1590 A non-@code{nil} value specifies an italic font.
1593 For compatibility, you can still set these ``attributes'' in Emacs 21,
1594 even though they are not real face attributes. Here is what that does:
1598 You can specify an X font name as the ``value'' of this ``attribute'';
1599 that sets the @code{:family}, @code{:width}, @code{:height},
1600 @code{:weight}, and @code{:slant} attributes according to the font name.
1602 If the value is a pattern with wildcards, the first font that matches
1603 the pattern is used to set these attributes.
1606 A non-@code{nil} makes the face bold; @code{nil} makes it normal.
1607 This actually works by setting the @code{:weight} attribute.
1610 A non-@code{nil} makes the face italic; @code{nil} makes it normal.
1611 This actually works by setting the @code{:slant} attribute.
1614 @defvar x-bitmap-file-path
1615 This variable specifies a list of directories for searching
1616 for bitmap files, for the @code{:stipple} attribute.
1619 @defun bitmap-spec-p object
1620 This returns @code{t} if @var{object} is a valid bitmap specification,
1621 suitable for use with @code{:stipple} (see above). It returns
1622 @code{nil} otherwise.
1625 @node Attribute Functions
1626 @subsection Face Attribute Functions
1628 You can modify the attributes of an existing face with the following
1629 functions. If you specify @var{frame}, they affect just that frame;
1630 otherwise, they affect all frames as well as the defaults that apply to
1633 @tindex set-face-attribute
1634 @defun set-face-attribute face frame &rest arguments
1635 This function sets one or more attributes of face @var{face}
1636 for frame @var{frame}. If @var{frame} is @code{nil}, it sets
1637 the attribute for all frames, and the defaults for new frames.
1639 The extra arguments @var{arguments} specify the attributes to set, and
1640 the values for them. They should consist of alternating attribute names
1641 (such as @code{:family} or @code{:underline}) and corresponding values.
1645 (set-face-attribute 'foo nil
1652 sets the attributes @code{:width}, @code{:weight} and @code{:underline}
1653 to the corresponding values.
1656 @tindex face-attribute
1657 @defun face-attribute face attribute &optional frame inherit
1658 This returns the value of the @var{attribute} attribute of face
1659 @var{face} on @var{frame}. If @var{frame} is @code{nil},
1660 that means the selected frame (@pxref{Input Focus}).
1662 If @var{frame} is @code{t}, the value is the default for
1663 @var{face} for new frames.
1665 If @var{inherit} is nil, only attributes directly defined by
1666 @var{face} are considered, so the return value may be
1667 @code{unspecified}, or a relative value. If @var{inherit} is non-nil,
1668 @var{face}'s definition of @var{attribute} is merged with the faces
1669 specified by its @code{:inherit} attribute; however the return value
1670 may still be @code{unspecified} or relative. If @var{inherit} is a
1671 face or a list of faces, then the result is further merged with that
1672 face (or faces), until it becomes specified and absolute.
1674 To ensure that the return value is always specified and absolute, use
1675 a value of @code{default} for @var{inherit}; this will resolve any
1676 unspecified or relative values by merging with the @code{default} face
1677 (which is always completely specified).
1682 (face-attribute 'bold :weight)
1687 The functions above did not exist before Emacs 21. For compatibility
1688 with older Emacs versions, you can use the following functions to set
1689 and examine the face attributes which existed in those versions.
1691 @tindex face-attribute-relative-p
1692 @defun face-attribute-relative-p attribute value
1693 This function returns non-@code{nil} if @var{value}, when used as a
1694 the value of the face attribute @var{attribute}, is relative (that is,
1695 if it modifies an underlying or inherited value of @var{attribute}).
1698 @tindex merge-face-attribute
1699 @defun merge-face-attribute attribute value1 value2
1700 If @var{value1} is a relative value for the face attribute
1701 @var{attribute}, returns it merged with the underlying value
1702 @var{value2}; otherwise, if @var{value1} is an absolute value for the
1703 face a attribute @var{attribute}, returns @var{value1} unchanged.
1706 @defun set-face-foreground face color &optional frame
1707 @defunx set-face-background face color &optional frame
1708 These functions set the foreground (or background, respectively) color
1709 of face @var{face} to @var{color}. The argument @var{color} should be a
1710 string, the name of a color.
1712 Certain shades of gray are implemented by stipple patterns on
1713 black-and-white screens.
1716 @defun set-face-stipple face pattern &optional frame
1717 This function sets the background stipple pattern of face @var{face}
1718 to @var{pattern}. The argument @var{pattern} should be the name of a
1719 stipple pattern defined by the X server, or actual bitmap data
1720 (@pxref{Face Attributes}), or @code{nil} meaning don't use stipple.
1722 Normally there is no need to pay attention to stipple patterns, because
1723 they are used automatically to handle certain shades of gray.
1726 @defun set-face-font face font &optional frame
1727 This function sets the font of face @var{face}.
1729 In Emacs 21, this actually sets the attributes @code{:family},
1730 @code{:width}, @code{:height}, @code{:weight}, and @code{:slant}
1731 according to the font name @var{font}.
1733 In Emacs 20, this sets the font attribute. Once you set the font
1734 explicitly, the bold and italic attributes cease to have any effect,
1735 because the precise font that you specified is used.
1738 @defun set-face-bold-p face bold-p &optional frame
1739 This function specifies whether @var{face} should be bold. If
1740 @var{bold-p} is non-@code{nil}, that means yes; @code{nil} means no.
1742 In Emacs 21, this sets the @code{:weight} attribute.
1743 In Emacs 20, it sets the @code{:bold} attribute.
1746 @defun set-face-italic-p face italic-p &optional frame
1747 This function specifies whether @var{face} should be italic. If
1748 @var{italic-p} is non-@code{nil}, that means yes; @code{nil} means no.
1750 In Emacs 21, this sets the @code{:slant} attribute.
1751 In Emacs 20, it sets the @code{:italic} attribute.
1754 @defun set-face-underline-p face underline-p &optional frame
1755 This function sets the underline attribute of face @var{face}.
1756 Non-@code{nil} means do underline; @code{nil} means don't.
1759 @defun invert-face face &optional frame
1760 This function inverts the @code{:inverse-video} attribute of face
1761 @var{face}. If the attribute is @code{nil}, this function sets it to
1762 @code{t}, and vice versa.
1765 These functions examine the attributes of a face. If you don't
1766 specify @var{frame}, they refer to the default data for new frames.
1767 They return the symbol @code{unspecified} if the face doesn't define any
1768 value for that attribute.
1770 @defun face-foreground face &optional frame inherit
1771 @defunx face-background face &optional frame
1772 These functions return the foreground color (or background color,
1773 respectively) of face @var{face}, as a string.
1775 If @var{inherit} is nil, only a color directly defined by the face is
1776 returned. If @var{inherit} is non-nil, any faces specified by its
1777 @code{:inherit} attribute are considered as well, and if @var{inherit}
1778 is a face or a list of faces, then they are also considered, until a
1779 specified color is found. To ensure that the return value is always
1780 specified, use a value of @code{default} for @var{inherit}.
1783 @defun face-stipple face &optional frame inherit
1784 This function returns the name of the background stipple pattern of face
1785 @var{face}, or @code{nil} if it doesn't have one.
1787 If @var{inherit} is nil, only a stipple directly defined by the face
1788 is returned. If @var{inherit} is non-nil, any faces specified by its
1789 @code{:inherit} attribute are considered as well, and if @var{inherit}
1790 is a face or a list of faces, then they are also considered, until a
1791 specified stipple is found. To ensure that the return value is always
1792 specified, use a value of @code{default} for @var{inherit}.
1795 @defun face-font face &optional frame
1796 This function returns the name of the font of face @var{face}.
1799 @defun face-bold-p face &optional frame
1800 This function returns @code{t} if @var{face} is bold---that is, if it is
1801 bolder than normal. It returns @code{nil} otherwise.
1804 @defun face-italic-p face &optional frame
1805 This function returns @code{t} if @var{face} is italic or oblique,
1806 @code{nil} otherwise.
1809 @defun face-underline-p face &optional frame
1810 This function returns the @code{:underline} attribute of face @var{face}.
1813 @defun face-inverse-video-p face &optional frame
1814 This function returns the @code{:inverse-video} attribute of face @var{face}.
1818 @subsection Merging Faces for Display
1820 Here are the ways to specify which faces to use for display of text:
1824 With defaults. The @code{default} face is used as the ultimate
1825 default for all text. (In Emacs 19 and 20, the @code{default}
1826 face is used only when no other face is specified.)
1828 For a mode line or header line, the face @code{modeline} or
1829 @code{header-line} is used just before @code{default}.
1832 With text properties. A character can have a @code{face} property; if
1833 so, the faces and face attributes specified there apply. @xref{Special
1836 If the character has a @code{mouse-face} property, that is used instead
1837 of the @code{face} property when the mouse is ``near enough'' to the
1841 With overlays. An overlay can have @code{face} and @code{mouse-face}
1842 properties too; they apply to all the text covered by the overlay.
1845 With a region that is active. In Transient Mark mode, the region is
1846 highlighted with the face @code{region} (@pxref{Standard Faces}).
1849 With special glyphs. Each glyph can specify a particular face
1850 number. @xref{Glyphs}.
1853 If these various sources together specify more than one face for a
1854 particular character, Emacs merges the attributes of the various faces
1855 specified. The attributes of the faces of special glyphs come first;
1856 then comes the face for region highlighting, if appropriate;
1857 then come attributes of faces from overlays, followed by those from text
1858 properties, and last the default face.
1860 When multiple overlays cover one character, an overlay with higher
1861 priority overrides those with lower priority. @xref{Overlays}.
1863 In Emacs 20, if an attribute such as the font or a color is not
1864 specified in any of the above ways, the frame's own font or color is
1865 used. In newer Emacs versions, this cannot happen, because the
1866 @code{default} face specifies all attributes---in fact, the frame's own
1867 font and colors are synonymous with those of the default face.
1869 @node Font Selection
1870 @subsection Font Selection
1872 @dfn{Selecting a font} means mapping the specified face attributes for
1873 a character to a font that is available on a particular display. The
1874 face attributes, as determined by face merging, specify most of the
1875 font choice, but not all. Part of the choice depends on what character
1878 For multibyte characters, typically each font covers only one
1879 character set. So each character set (@pxref{Character Sets}) specifies
1880 a registry and encoding to use, with the character set's
1881 @code{x-charset-registry} property. Its value is a string containing
1882 the registry and the encoding, with a dash between them:
1885 (plist-get (charset-plist 'latin-iso8859-1)
1886 'x-charset-registry)
1887 @result{} "ISO8859-1"
1890 Unibyte text does not have character sets, so displaying a unibyte
1891 character takes the registry and encoding from the variable
1892 @code{face-default-registry}.
1894 @defvar face-default-registry
1895 This variable specifies which registry and encoding to use in choosing
1896 fonts for unibyte characters. The value is initialized at Emacs startup
1897 time from the font the user specified for Emacs.
1900 If the face specifies a fontset name, that fontset determines a
1901 pattern for fonts of the given charset. If the face specifies a font
1902 family, a font pattern is constructed.
1904 Emacs tries to find an available font for the given face attributes
1905 and character's registry and encoding. If there is a font that matches
1906 exactly, it is used, of course. The hard case is when no available font
1907 exactly fits the specification. Then Emacs looks for one that is
1908 ``close''---one attribute at a time. You can specify the order to
1909 consider the attributes. In the case where a specified font family is
1910 not available, you can specify a set of mappings for alternatives to
1913 @defvar face-font-selection-order
1914 @tindex face-font-selection-order
1915 This variable specifies the order of importance of the face attributes
1916 @code{:width}, @code{:height}, @code{:weight}, and @code{:slant}. The
1917 value should be a list containing those four symbols, in order of
1918 decreasing importance.
1920 Font selection first finds the best available matches for the first
1921 attribute listed; then, among the fonts which are best in that way, it
1922 searches for the best matches in the second attribute, and so on.
1924 The attributes @code{:weight} and @code{:width} have symbolic values in
1925 a range centered around @code{normal}. Matches that are more extreme
1926 (farther from @code{normal}) are somewhat preferred to matches that are
1927 less extreme (closer to @code{normal}); this is designed to ensure that
1928 non-normal faces contrast with normal ones, whenever possible.
1930 The default is @code{(:width :height :weight :slant)}, which means first
1931 find the fonts closest to the specified @code{:width}, then---among the
1932 fonts with that width---find a best match for the specified font height,
1935 One example of a case where this variable makes a difference is when the
1936 default font has no italic equivalent. With the default ordering, the
1937 @code{italic} face will use a non-italic font that is similar to the
1938 default one. But if you put @code{:slant} before @code{:height}, the
1939 @code{italic} face will use an italic font, even if its height is not
1943 @defvar face-font-family-alternatives
1944 @tindex face-font-family-alternatives
1945 This variable lets you specify alternative font families to try, if a
1946 given family is specified and doesn't exist. Each element should have
1950 (@var{family} @var{alternate-families}@dots{})
1953 If @var{family} is specified but not available, Emacs will try the other
1954 families given in @var{alternate-families}, one by one, until it finds a
1955 family that does exist.
1958 @defvar face-font-registry-alternatives
1959 @tindex face-font-registry-alternatives
1960 This variable lets you specify alternative font registries to try, if a
1961 given registry is specified and doesn't exist. Each element should have
1965 (@var{registry} @var{alternate-registries}@dots{})
1968 If @var{registry} is specified but not available, Emacs will try the
1969 other registries given in @var{alternate-registries}, one by one,
1970 until it finds a registry that does exist.
1973 Emacs can make use of scalable fonts, but by default it does not use
1974 them, since the use of too many or too big scalable fonts can crash
1977 @defvar scalable-fonts-allowed
1978 @tindex scalable-fonts-allowed
1979 This variable controls which scalable fonts to use. A value of
1980 @code{nil}, the default, means do not use scalable fonts. @code{t}
1981 means to use any scalable font that seems appropriate for the text.
1983 Otherwise, the value must be a list of regular expressions. Then a
1984 scalable font is enabled for use if its name matches any regular
1985 expression in the list. For example,
1988 (setq scalable-fonts-allowed '("muleindian-2$"))
1992 allows the use of scalable fonts with registry @code{muleindian-2}.
1995 @defun clear-face-cache &optional unload-p
1996 @tindex clear-face-cache
1997 This function clears the face cache for all frames.
1998 If @var{unload-p} is non-@code{nil}, that means to unload
1999 all unused fonts as well.
2002 @node Face Functions
2003 @subsection Functions for Working with Faces
2005 Here are additional functions for creating and working with faces.
2007 @defun make-face name
2008 This function defines a new face named @var{name}, initially with all
2009 attributes @code{nil}. It does nothing if there is already a face named
2014 This function returns a list of all defined face names.
2017 @defun copy-face old-face new-name &optional frame new-frame
2018 This function defines the face @var{new-name} as a copy of the existing
2019 face named @var{old-face}. It creates the face @var{new-name} if that
2020 doesn't already exist.
2022 If the optional argument @var{frame} is given, this function applies
2023 only to that frame. Otherwise it applies to each frame individually,
2024 copying attributes from @var{old-face} in each frame to @var{new-face}
2027 If the optional argument @var{new-frame} is given, then @code{copy-face}
2028 copies the attributes of @var{old-face} in @var{frame} to @var{new-name}
2033 This function returns the face number of face @var{face}.
2036 @defun face-documentation face
2037 This function returns the documentation string of face @var{face}, or
2038 @code{nil} if none was specified for it.
2041 @defun face-equal face1 face2 &optional frame
2042 This returns @code{t} if the faces @var{face1} and @var{face2} have the
2043 same attributes for display.
2046 @defun face-differs-from-default-p face &optional frame
2047 This returns @code{t} if the face @var{face} displays differently from
2048 the default face. A face is considered to be ``the same'' as the
2049 default face if each attribute is either the same as that of the default
2050 face, or unspecified (meaning to inherit from the default).
2054 @subsection Automatic Face Assignment
2055 @cindex automatic face assignment
2056 @cindex faces, automatic choice
2058 @cindex Font-Lock mode
2059 Starting with Emacs 21, a hook is available for automatically
2060 assigning faces to text in the buffer. This hook is used for part of
2061 the implementation of Font-Lock mode.
2063 @tindex fontification-functions
2064 @defvar fontification-functions
2065 This variable holds a list of functions that are called by Emacs
2066 redisplay as needed to assign faces automatically to text in the buffer.
2068 The functions are called in the order listed, with one argument, a
2069 buffer position @var{pos}. Each function should attempt to assign faces
2070 to the text in the current buffer starting at @var{pos}.
2072 Each function should record the faces they assign by setting the
2073 @code{face} property. It should also add a non-@code{nil}
2074 @code{fontified} property for all the text it has assigned faces to.
2075 That property tells redisplay that faces have been assigned to that text
2078 It is probably a good idea for each function to do nothing if the
2079 character after @var{pos} already has a non-@code{nil} @code{fontified}
2080 property, but this is not required. If one function overrides the
2081 assignments made by a previous one, the properties as they are
2082 after the last function finishes are the ones that really matter.
2084 For efficiency, we recommend writing these functions so that they
2085 usually assign faces to around 400 to 600 characters at each call.
2089 @subsection Looking Up Fonts
2091 @defun x-list-fonts pattern &optional face frame maximum
2092 This function returns a list of available font names that match
2093 @var{pattern}. If the optional arguments @var{face} and @var{frame} are
2094 specified, then the list is limited to fonts that are the same size as
2095 @var{face} currently is on @var{frame}.
2097 The argument @var{pattern} should be a string, perhaps with wildcard
2098 characters: the @samp{*} character matches any substring, and the
2099 @samp{?} character matches any single character. Pattern matching
2100 of font names ignores case.
2102 If you specify @var{face} and @var{frame}, @var{face} should be a face name
2103 (a symbol) and @var{frame} should be a frame.
2105 The optional argument @var{maximum} sets a limit on how many fonts to
2106 return. If this is non-@code{nil}, then the return value is truncated
2107 after the first @var{maximum} matching fonts. Specifying a small value
2108 for @var{maximum} can make this function much faster, in cases where
2109 many fonts match the pattern.
2112 These additional functions are available starting in Emacs 21.
2114 @defun x-family-fonts &optional family frame
2115 @tindex x-family-fonts
2116 This function returns a list describing the available fonts for family
2117 @var{family} on @var{frame}. If @var{family} is omitted or @code{nil},
2118 this list applies to all families, and therefore, it contains all
2119 available fonts. Otherwise, @var{family} must be a string; it may
2120 contain the wildcards @samp{?} and @samp{*}.
2122 The list describes the display that @var{frame} is on; if @var{frame} is
2123 omitted or @code{nil}, it applies to the selected frame's display
2124 (@pxref{Input Focus}).
2126 The list contains a vector of the following form for each font:
2129 [@var{family} @var{width} @var{point-size} @var{weight} @var{slant}
2130 @var{fixed-p} @var{full} @var{registry-and-encoding}]
2133 The first five elements correspond to face attributes; if you
2134 specify these attributes for a face, it will use this font.
2136 The last three elements give additional information about the font.
2137 @var{fixed-p} is non-nil if the font is fixed-pitch. @var{full} is the
2138 full name of the font, and @var{registry-and-encoding} is a string
2139 giving the registry and encoding of the font.
2141 The result list is sorted according to the current face font sort order.
2144 @defun x-font-family-list &optional frame
2145 @tindex x-font-family-list
2146 This function returns a list of the font families available for
2147 @var{frame}'s display. If @var{frame} is omitted or @code{nil}, it
2148 describes the selected frame's display (@pxref{Input Focus}).
2150 The value is a list of elements of this form:
2153 (@var{family} . @var{fixed-p})
2157 Here @var{family} is a font family, and @var{fixed-p} is
2158 non-@code{nil} if fonts of that family are fixed-pitch.
2161 @defvar font-list-limit
2162 @tindex font-list-limit
2163 This variable specifies maximum number of fonts to consider in font
2164 matching. The function @code{x-family-fonts} will not return more than
2165 that many fonts, and font selection will consider only that many fonts
2166 when searching a matching font for face attributes. The default is
2171 @subsection Fontsets
2173 A @dfn{fontset} is a list of fonts, each assigned to a range of
2174 character codes. An individual font cannot display the whole range of
2175 characters that Emacs supports, but a fontset can. Fontsets have names,
2176 just as fonts do, and you can use a fontset name in place of a font name
2177 when you specify the ``font'' for a frame or a face. Here is
2178 information about defining a fontset under Lisp program control.
2180 @defun create-fontset-from-fontset-spec fontset-spec &optional style-variant-p noerror
2181 This function defines a new fontset according to the specification
2182 string @var{fontset-spec}. The string should have this format:
2185 @var{fontpattern}, @r{[}@var{charsetname}:@var{fontname}@r{]@dots{}}
2189 Whitespace characters before and after the commas are ignored.
2191 The first part of the string, @var{fontpattern}, should have the form of
2192 a standard X font name, except that the last two fields should be
2193 @samp{fontset-@var{alias}}.
2195 The new fontset has two names, one long and one short. The long name is
2196 @var{fontpattern} in its entirety. The short name is
2197 @samp{fontset-@var{alias}}. You can refer to the fontset by either
2198 name. If a fontset with the same name already exists, an error is
2199 signaled, unless @var{noerror} is non-@code{nil}, in which case this
2200 function does nothing.
2202 If optional argument @var{style-variant-p} is non-@code{nil}, that says
2203 to create bold, italic and bold-italic variants of the fontset as well.
2204 These variant fontsets do not have a short name, only a long one, which
2205 is made by altering @var{fontpattern} to indicate the bold or italic
2208 The specification string also says which fonts to use in the fontset.
2209 See below for the details.
2212 The construct @samp{@var{charset}:@var{font}} specifies which font to
2213 use (in this fontset) for one particular character set. Here,
2214 @var{charset} is the name of a character set, and @var{font} is the font
2215 to use for that character set. You can use this construct any number of
2216 times in the specification string.
2218 For the remaining character sets, those that you don't specify
2219 explicitly, Emacs chooses a font based on @var{fontpattern}: it replaces
2220 @samp{fontset-@var{alias}} with a value that names one character set.
2221 For the @sc{ascii} character set, @samp{fontset-@var{alias}} is replaced
2222 with @samp{ISO8859-1}.
2224 In addition, when several consecutive fields are wildcards, Emacs
2225 collapses them into a single wildcard. This is to prevent use of
2226 auto-scaled fonts. Fonts made by scaling larger fonts are not usable
2227 for editing, and scaling a smaller font is not useful because it is
2228 better to use the smaller font in its own size, which Emacs does.
2230 Thus if @var{fontpattern} is this,
2233 -*-fixed-medium-r-normal-*-24-*-*-*-*-*-fontset-24
2237 the font specification for @sc{ascii} characters would be this:
2240 -*-fixed-medium-r-normal-*-24-*-ISO8859-1
2244 and the font specification for Chinese GB2312 characters would be this:
2247 -*-fixed-medium-r-normal-*-24-*-gb2312*-*
2250 You may not have any Chinese font matching the above font
2251 specification. Most X distributions include only Chinese fonts that
2252 have @samp{song ti} or @samp{fangsong ti} in the @var{family} field. In
2253 such a case, @samp{Fontset-@var{n}} can be specified as below:
2256 Emacs.Fontset-0: -*-fixed-medium-r-normal-*-24-*-*-*-*-*-fontset-24,\
2257 chinese-gb2312:-*-*-medium-r-normal-*-24-*-gb2312*-*
2261 Then, the font specifications for all but Chinese GB2312 characters have
2262 @samp{fixed} in the @var{family} field, and the font specification for
2263 Chinese GB2312 characters has a wild card @samp{*} in the @var{family}
2266 @node Display Property
2267 @section The @code{display} Property
2268 @cindex display specification
2269 @kindex display @r{(text property)}
2271 The @code{display} text property (or overlay property) is used to
2272 insert images into text, and also control other aspects of how text
2273 displays. These features are available starting in Emacs 21. The value
2274 of the @code{display} property should be a display specification, or a
2275 list or vector containing several display specifications. The rest of
2276 this section describes several kinds of display specifications and what
2280 * Specified Space:: Displaying one space with a specified width.
2281 * Other Display Specs:: Displaying an image; magnifying text; moving it
2282 up or down on the page; adjusting the width
2283 of spaces within text.
2284 * Display Margins:: Displaying text or images to the side of the main text.
2285 * Conditional Display:: Making any of the above features conditional
2286 depending on some Lisp expression.
2289 @node Specified Space
2290 @subsection Specified Spaces
2291 @cindex spaces, specified height or width
2292 @cindex specified spaces
2293 @cindex variable-width spaces
2295 To display a space of specified width and/or height, use a display
2296 specification of the form @code{(space . @var{props})}, where
2297 @var{props} is a property list (a list of alternating properties and
2298 values). You can put this property on one or more consecutive
2299 characters; a space of the specified height and width is displayed in
2300 place of @emph{all} of those characters. These are the properties you
2301 can use in @var{props} to specify the weight of the space:
2304 @item :width @var{width}
2305 Specifies that the space width should be @var{width} times the normal
2306 character width. @var{width} can be an integer or floating point
2309 @item :relative-width @var{factor}
2310 Specifies that the width of the stretch should be computed from the
2311 first character in the group of consecutive characters that have the
2312 same @code{display} property. The space width is the width of that
2313 character, multiplied by @var{factor}.
2315 @item :align-to @var{hpos}
2316 Specifies that the space should be wide enough to reach @var{hpos}. The
2317 value @var{hpos} is measured in units of the normal character width. It
2318 may be an interer or a floating point number.
2321 You should use one and only one of the above properties. You can
2322 also specify the height of the space, with other properties:
2325 @item :height @var{height}
2326 Specifies the height of the space, as @var{height},
2327 measured in terms of the normal line height.
2329 @item :relative-height @var{factor}
2330 Specifies the height of the space, multiplying the ordinary height
2331 of the text having this display specification by @var{factor}.
2333 @item :ascent @var{ascent}
2334 Specifies that @var{ascent} percent of the height of the space should be
2335 considered as the ascent of the space---that is, the part above the
2336 baseline. The value of @var{ascent} must be a non-negative number no
2340 Don't use both @code{:height} and @code{:relative-height} together.
2342 @node Other Display Specs
2343 @subsection Other Display Specifications
2346 @item (image . @var{image-props})
2347 This is in fact an image descriptor (@pxref{Images}). When used as a
2348 display specification, it means to display the image instead of the text
2349 that has the display specification.
2351 @item ((margin nil) @var{string})
2353 A display specification of this form means to display @var{string}
2354 instead of the text that has the display specification, at the same
2355 position as that text. This is a special case of marginal display
2356 (@pxref{Display Margins}).
2358 Recursive display specifications are not supported---string display
2359 specifications must not have @code{display} properties themselves.
2361 @item (space-width @var{factor})
2362 This display specification affects all the space characters within the
2363 text that has the specification. It displays all of these spaces
2364 @var{factor} times as wide as normal. The element @var{factor} should
2365 be an integer or float. Characters other than spaces are not affected
2366 at all; in particular, this has no effect on tab characters.
2368 @item (height @var{height})
2369 This display specification makes the text taller or shorter.
2370 Here are the possibilities for @var{height}:
2373 @item @code{(+ @var{n})}
2374 This means to use a font that is @var{n} steps larger. A ``step'' is
2375 defined by the set of available fonts---specifically, those that match
2376 what was otherwise specified for this text, in all attributes except
2377 height. Each size for which a suitable font is available counts as
2378 another step. @var{n} should be an integer.
2380 @item @code{(- @var{n})}
2381 This means to use a font that is @var{n} steps smaller.
2383 @item a number, @var{factor}
2384 A number, @var{factor}, means to use a font that is @var{factor} times
2385 as tall as the default font.
2387 @item a symbol, @var{function}
2388 A symbol is a function to compute the height. It is called with the
2389 current height as argument, and should return the new height to use.
2391 @item anything else, @var{form}
2392 If the @var{height} value doesn't fit the previous possibilities, it is
2393 a form. Emacs evaluates it to get the new height, with the symbol
2394 @code{height} bound to the current specified font height.
2397 @item (raise @var{factor})
2398 This kind of display specification raises or lowers the text
2399 it applies to, relative to the baseline of the line.
2401 @var{factor} must be a number, which is interpreted as a multiple of the
2402 height of the affected text. If it is positive, that means to display
2403 the characters raised. If it is negative, that means to display them
2406 If the text also has a @code{height} display specification, that does
2407 not affect the amount of raising or lowering, which is based on the
2408 faces used for the text.
2411 @node Display Margins
2412 @subsection Displaying in the Margins
2413 @cindex display margins
2414 @cindex margins, display
2416 A buffer can have blank areas called @dfn{display margins} on the left
2417 and on the right. Ordinary text never appears in these areas, but you
2418 can put things into the display margins using the @code{display}
2421 To put text in the left or right display margin of the window, use a
2422 display specification of the form @code{(margin right-margin)} or
2423 @code{(margin left-margin)} on it. To put an image in a display margin,
2424 use that display specification along with the display specification for
2425 the image. Unfortunately, there is currently no way to make
2426 text or images in the margin mouse-sensitive.
2428 If you put such a display specification directly on text in the
2429 buffer, the specified margin display appears @emph{instead of} that
2430 buffer text itself. To put something in the margin @emph{in
2431 association with} certain buffer text without preventing or altering
2432 the display of that text, put a @code{before-string} property on the
2433 text and put the display specification on the contents of the
2436 Before the display margins can display anything, you must give
2437 them a nonzero width. The usual way to do that is to set these
2440 @defvar left-margin-width
2441 @tindex left-margin-width
2442 This variable specifies the width of the left margin.
2443 It is buffer-local in all buffers.
2446 @defvar right-margin-width
2447 @tindex right-margin-width
2448 This variable specifies the width of the right margin.
2449 It is buffer-local in all buffers.
2452 Setting these variables does not immediately affect the window. These
2453 variables are checked when a new buffer is displayed in the window.
2454 Thus, you can make changes take effect by calling
2455 @code{set-window-buffer}.
2457 You can also set the margin widths immediately.
2459 @defun set-window-margins window left &optional right
2460 @tindex set-window-margins
2461 This function specifies the margin widths for window @var{window}.
2462 The argument @var{left} controls the left margin and
2463 @var{right} controls the right margin (default @code{0}).
2466 @defun window-margins &optional window
2467 @tindex window-margins
2468 This function returns the left and right margins of @var{window}
2469 as a cons cell of the form @code{(@var{left} . @var{right})}.
2470 If @var{window} is @code{nil}, the selected window is used.
2473 @node Conditional Display
2474 @subsection Conditional Display Specifications
2475 @cindex conditional display specifications
2477 You can make any display specification conditional. To do that,
2478 package it in another list of the form @code{(when @var{condition} .
2479 @var{spec})}. Then the specification @var{spec} applies only when
2480 @var{condition} evaluates to a non-@code{nil} value. During the
2481 evaluation, @code{object} is bound to the string or buffer having the
2482 conditional @code{display} property. @code{position} and
2483 @code{buffer-position} are bound to the position within @code{object}
2484 and the buffer position where the @code{display} property was found,
2485 respectively. Both positions can be different when @code{object} is a
2490 @cindex images in buffers
2492 To display an image in an Emacs buffer, you must first create an image
2493 descriptor, then use it as a display specifier in the @code{display}
2494 property of text that is displayed (@pxref{Display Property}). Like the
2495 @code{display} property, this feature is available starting in Emacs 21.
2497 Emacs can display a number of different image formats; some of them
2498 are supported only if particular support libraries are installed on your
2499 machine. The supported image formats include XBM, XPM (needing the
2500 libraries @code{libXpm} version 3.4k and @code{libz}), GIF (needing
2501 @code{libungif} 4.1.0), Postscript, PBM, JPEG (needing the
2502 @code{libjpeg} library version v6a), TIFF (needing @code{libtiff} v3.4),
2503 and PNG (needing @code{libpng} 1.0.2).
2505 You specify one of these formats with an image type symbol. The image
2506 type symbols are @code{xbm}, @code{xpm}, @code{gif}, @code{postscript},
2507 @code{pbm}, @code{jpeg}, @code{tiff}, and @code{png}.
2510 This variable contains a list of those image type symbols that are
2511 supported in the current configuration.
2515 * Image Descriptors:: How to specify an image for use in @code{:display}.
2516 * XBM Images:: Special features for XBM format.
2517 * XPM Images:: Special features for XPM format.
2518 * GIF Images:: Special features for GIF format.
2519 * Postscript Images:: Special features for Postscript format.
2520 * Other Image Types:: Various other formats are supported.
2521 * Defining Images:: Convenient ways to define an image for later use.
2522 * Showing Images:: Convenient ways to display an image once it is defined.
2523 * Image Cache:: Internal mechanisms of image display.
2526 @node Image Descriptors
2527 @subsection Image Descriptors
2528 @cindex image descriptor
2530 An image description is a list of the form @code{(image
2531 . @var{props})}, where @var{props} is a property list containing
2532 alternating keyword symbols (symbols whose names start with a colon) and
2533 their values. You can use any Lisp object as a property, but the only
2534 properties that have any special meaning are certain symbols, all of
2537 Every image descriptor must contain the property @code{:type
2538 @var{type}} to specify the format of the image. The value of @var{type}
2539 should be an image type symbol; for example, @code{xpm} for an image in
2542 Here is a list of other properties that are meaningful for all image
2546 @item :file @var{file}
2547 The @code{:file} property specifies to load the image from file
2548 @var{file}. If @var{file} is not an absolute file name, it is expanded
2549 in @code{data-directory}.
2551 @item :data @var{data}
2552 The @code{:data} property specifies the actual contents of the image.
2553 Each image must use either @code{:data} or @code{:file}, but not both.
2554 For most image types, the value of the @code{:data} property should be a
2555 string containing the image data; we recommend using a unibyte string.
2557 Before using @code{:data}, look for further information in the section
2558 below describing the specific image format. For some image types,
2559 @code{:data} may not be supported; for some, it allows other data types;
2560 for some, @code{:data} alone is not enough, so you need to use other
2561 image properties along with @code{:data}.
2563 @item :margin @var{margin}
2564 The @code{:margin} property specifies how many pixels to add as an
2565 extra margin around the image. The value, @var{margin}, must be a a
2566 non-negative number, or a pair @code{(@var{x} . @var{y})} of such
2567 numbers. If it is a pair, @var{x} specifies how many pixels to add
2568 horizontally, and @var{y} specifies how many pixels to add vertically.
2569 If @code{:margin} is not specified, the default is zero.
2571 @item :ascent @var{ascent}
2572 The @code{:ascent} property specifies the amount of the image's
2573 height to use for its ascent---that is, the part above the baseline.
2574 The value, @var{ascent}, must be a number in the range 0 to 100, or
2575 the symbol @code{center}.
2577 If @var{ascent} is a number, that percentage of the image's height is
2578 used for its ascent.
2580 If @var{ascent} is @code{center}, the image is vertically centered
2581 around a centerline which would be the vertical centerline of text drawn
2582 at the position of the image, in the manner specified by the text
2583 properties and overlays that apply to the image.
2585 If this property is omitted, it defaults to 50.
2587 @item :relief @var{relief}
2588 The @code{:relief} property, if non-@code{nil}, adds a shadow rectangle
2589 around the image. The value, @var{relief}, specifies the width of the
2590 shadow lines, in pixels. If @var{relief} is negative, shadows are drawn
2591 so that the image appears as a pressed button; otherwise, it appears as
2592 an unpressed button.
2594 @item :conversion @var{algorithm}
2595 The @code{:conversion} property, if non-@code{nil}, specifies a
2596 conversion algorithm that should be applied to the image before it is
2597 displayed; the value, @var{algorithm}, specifies which algorithm.
2602 Specifies the Laplace edge detection algorithm, which blurs out small
2603 differences in color while highlighting larger differences. People
2604 sometimes consider this useful for displaying the image for a
2605 ``disabled'' button.
2607 @item (edge-detection :matrix @var{matrix} :color-adjust @var{adjust})
2608 Specifies a general edge-detection algorithm. @var{matrix} must be
2609 either a nine-element list or a nine-element vector of numbers. A pixel
2610 at position @math{x/y} in the transformed image is computed from
2611 original pixels around that position. @var{matrix} specifies, for each
2612 pixel in the neighborhood of @math{x/y}, a factor with which that pixel
2613 will influence the transformed pixel; element @math{0} specifies the
2614 factor for the pixel at @math{x-1/y-1}, element @math{1} the factor for
2615 the pixel at @math{x/y-1} etc., as shown below:
2618 $$\pmatrix{x-1/y-1 & x/y-1 & x+1/y-1 \cr
2619 x-1/y & x/y & x+1/y \cr
2620 x-1/y+1& x/y+1 & x+1/y+1 \cr}$$
2625 (x-1/y-1 x/y-1 x+1/y-1
2627 x-1/y+1 x/y+1 x+1/y+1)
2631 The resulting pixel is computed from the color intensity of the color
2632 resulting from summing up the RGB values of surrounding pixels,
2633 multiplied by the specified factors, and dividing that sum by the sum
2634 of the factors' absolute values.
2636 Laplace edge-detection currently uses a matrix of
2639 $$\pmatrix{1 & 0 & 0 \cr
2652 Emboss edge-detection uses a matrix of
2655 $$\pmatrix{ 2 & -1 & 0 \cr
2669 Specifies transforming the image so that it looks ``disabled''.
2672 @item :mask @var{mask}
2673 If @var{mask} is @code{heuristic} or @code{(heuristic @var{bg})}, build
2674 a clipping mask for the image, so that the background of a frame is
2675 visible behind the image. If @var{bg} is not specified, or if @var{bg}
2676 is @code{t}, determine the background color of the image by looking at
2677 the four corners of the image, assuming the most frequently occurring
2678 color from the corners is the background color of the image. Otherwise,
2679 @var{bg} must be a list @code{(@var{red} @var{green} @var{blue})}
2680 specifying the color to assume for the background of the image.
2682 If @var{mask} is nil, remove a mask from the image, if it has one. Images
2683 in some formats include a mask which can be removed by specifying
2687 @defun image-mask-p spec &optional frame
2688 @tindex image-mask-p
2689 This function returns @code{t} if image @var{spec} has a mask bitmap.
2690 @var{frame} is the frame on which the image will be displayed.
2691 @var{frame} @code{nil} or omitted means to use the selected frame
2692 (@pxref{Input Focus}).
2696 @subsection XBM Images
2699 To use XBM format, specify @code{xbm} as the image type. This image
2700 format doesn't require an external library, so images of this type are
2703 Additional image properties supported for the @code{xbm} image type are:
2706 @item :foreground @var{foreground}
2707 The value, @var{foreground}, should be a string specifying the image
2708 foreground color, or @code{nil} for the default color. This color is
2709 used for each pixel in the XBM that is 1. The default is the frame's
2712 @item :background @var{background}
2713 The value, @var{background}, should be a string specifying the image
2714 background color, or @code{nil} for the default color. This color is
2715 used for each pixel in the XBM that is 0. The default is the frame's
2719 If you specify an XBM image using data within Emacs instead of an
2720 external file, use the following three properties:
2723 @item :data @var{data}
2724 The value, @var{data}, specifies the contents of the image.
2725 There are three formats you can use for @var{data}:
2729 A vector of strings or bool-vectors, each specifying one line of the
2730 image. Do specify @code{:height} and @code{:width}.
2733 A string containing the same byte sequence as an XBM file would contain.
2734 You must not specify @code{:height} and @code{:width} in this case,
2735 because omitting them is what indicates the data has the format of an
2736 XBM file. The file contents specify the height and width of the image.
2739 A string or a bool-vector containing the bits of the image (plus perhaps
2740 some extra bits at the end that will not be used). It should contain at
2741 least @var{width} * @code{height} bits. In this case, you must specify
2742 @code{:height} and @code{:width}, both to indicate that the string
2743 contains just the bits rather than a whole XBM file, and to specify the
2747 @item :width @var{width}
2748 The value, @var{width}, specifies the width of the image, in pixels.
2750 @item :height @var{height}
2751 The value, @var{height}, specifies the height of the image, in pixels.
2755 @subsection XPM Images
2758 To use XPM format, specify @code{xpm} as the image type. The
2759 additional image property @code{:color-symbols} is also meaningful with
2760 the @code{xpm} image type:
2763 @item :color-symbols @var{symbols}
2764 The value, @var{symbols}, should be an alist whose elements have the
2765 form @code{(@var{name} . @var{color})}. In each element, @var{name} is
2766 the name of a color as it appears in the image file, and @var{color}
2767 specifies the actual color to use for displaying that name.
2771 @subsection GIF Images
2774 For GIF images, specify image type @code{gif}. Because of the patents
2775 in the US covering the LZW algorithm, the continued use of GIF format is
2776 a problem for the whole Internet; to end this problem, it is a good idea
2777 for everyone, even outside the US, to stop using GIFS right away
2778 (@uref{http://www.burnallgifs.org/}). But if you still want to use
2779 them, Emacs can display them.
2782 @item :index @var{index}
2783 You can use @code{:index} to specify one image from a GIF file that
2784 contains more than one image. This property specifies use of image
2785 number @var{index} from the file. An error is signaled if the GIF file
2786 doesn't contain an image with index @var{index}.
2790 This could be used to implement limited support for animated GIFs.
2791 For example, the following function displays a multi-image GIF file
2792 at point-min in the current buffer, switching between sub-images
2795 (defun show-anim (file max)
2796 "Display multi-image GIF file FILE which contains MAX subimages."
2797 (display-anim (current-buffer) file 0 max t))
2799 (defun display-anim (buffer file idx max first-time)
2802 (let ((img (create-image file nil :image idx)))
2805 (goto-char (point-min))
2806 (unless first-time (delete-char 1))
2808 (run-with-timer 0.1 nil 'display-anim buffer file (1+ idx) max nil)))
2811 @node Postscript Images
2812 @subsection Postscript Images
2813 @cindex Postscript images
2815 To use Postscript for an image, specify image type @code{postscript}.
2816 This works only if you have Ghostscript installed. You must always use
2817 these three properties:
2820 @item :pt-width @var{width}
2821 The value, @var{width}, specifies the width of the image measured in
2822 points (1/72 inch). @var{width} must be an integer.
2824 @item :pt-height @var{height}
2825 The value, @var{height}, specifies the height of the image in points
2826 (1/72 inch). @var{height} must be an integer.
2828 @item :bounding-box @var{box}
2829 The value, @var{box}, must be a list or vector of four integers, which
2830 specifying the bounding box of the Postscript image, analogous to the
2831 @samp{BoundingBox} comment found in Postscript files.
2834 %%BoundingBox: 22 171 567 738
2838 Displaying Postscript images from Lisp data is not currently
2839 implemented, but it may be implemented by the time you read this.
2840 See the @file{etc/NEWS} file to make sure.
2842 @node Other Image Types
2843 @subsection Other Image Types
2846 For PBM images, specify image type @code{pbm}. Color, gray-scale and
2847 monochromatic images are supported. For mono PBM images, two additional
2848 image properties are supported.
2851 @item :foreground @var{foreground}
2852 The value, @var{foreground}, should be a string specifying the image
2853 foreground color, or @code{nil} for the default color. This color is
2854 used for each pixel in the XBM that is 1. The default is the frame's
2857 @item :background @var{background}
2858 The value, @var{background}, should be a string specifying the image
2859 background color, or @code{nil} for the default color. This color is
2860 used for each pixel in the XBM that is 0. The default is the frame's
2864 For JPEG images, specify image type @code{jpeg}.
2866 For TIFF images, specify image type @code{tiff}.
2868 For PNG images, specify image type @code{png}.
2870 @node Defining Images
2871 @subsection Defining Images
2873 The functions @code{create-image}, @code{defimage} and
2874 @code{find-image} provide convenient ways to create image descriptors.
2876 @defun create-image file &optional type &rest props
2877 @tindex create-image
2878 This function creates and returns an image descriptor which uses the
2881 The optional argument @var{type} is a symbol specifying the image type.
2882 If @var{type} is omitted or @code{nil}, @code{create-image} tries to
2883 determine the image type from the file's first few bytes, or else
2884 from the file's name.
2886 The remaining arguments, @var{props}, specify additional image
2887 properties---for example,
2890 (create-image "foo.xpm" 'xpm :heuristic-mask t)
2893 The function returns @code{nil} if images of this type are not
2894 supported. Otherwise it returns an image descriptor.
2897 @defmac defimage symbol specs &optional doc
2899 This macro defines @var{symbol} as an image name. The arguments
2900 @var{specs} is a list which specifies how to display the image.
2901 The third argument, @var{doc}, is an optional documentation string.
2903 Each argument in @var{specs} has the form of a property list, and each
2904 one should specify at least the @code{:type} property and either the
2905 @code{:file} or the @code{:data} property. The value of @code{:type}
2906 should be a symbol specifying the image type, the value of
2907 @code{:file} is the file to load the image from, and the value of
2908 @code{:data} is a string containing the actual image data. Here is an
2912 (defimage test-image
2913 ((:type xpm :file "~/test1.xpm")
2914 (:type xbm :file "~/test1.xbm")))
2917 @code{defimage} tests each argument, one by one, to see if it is
2918 usable---that is, if the type is supported and the file exists. The
2919 first usable argument is used to make an image descriptor which is
2920 stored in @var{symbol}.
2922 If none of the alternatives will work, then @var{symbol} is defined
2926 @defun find-image specs
2928 This function provides a convenient way to find an image satisfying one
2929 of a list of image specifications @var{specs}.
2931 Each specification in @var{specs} is a property list with contents
2932 depending on image type. All specifications must at least contain the
2933 properties @code{:type @var{type}} and either @w{@code{:file @var{file}}}
2934 or @w{@code{:data @var{DATA}}}, where @var{type} is a symbol specifying
2935 the image type, e.g.@: @code{xbm}, @var{file} is the file to load the
2936 image from, and @var{data} is a string containing the actual image data.
2937 The first specification in the list whose @var{type} is supported, and
2938 @var{file} exists, is used to construct the image specification to be
2939 returned. If no specification is satisfied, @code{nil} is returned.
2941 The image is looked for first on @code{load-path} and then in
2942 @code{data-directory}.
2945 @node Showing Images
2946 @subsection Showing Images
2948 You can use an image descriptor by setting up the @code{display}
2949 property yourself, but it is easier to use the functions in this
2952 @defun insert-image image &optional string area
2953 This function inserts @var{image} in the current buffer at point. The
2954 value @var{image} should be an image descriptor; it could be a value
2955 returned by @code{create-image}, or the value of a symbol defined with
2956 @code{defimage}. The argument @var{string} specifies the text to put in
2957 the buffer to hold the image.
2959 The argument @var{area} specifies whether to put the image in a margin.
2960 If it is @code{left-margin}, the image appears in the left margin;
2961 @code{right-margin} specifies the right margin. If @var{area} is
2962 @code{nil} or omitted, the image is displayed at point within the
2965 Internally, this function inserts @var{string} in the buffer, and gives
2966 it a @code{display} property which specifies @var{image}. @xref{Display
2970 @defun put-image image pos &optional string area
2971 This function puts image @var{image} in front of @var{pos} in the
2972 current buffer. The argument @var{pos} should be an integer or a
2973 marker. It specifies the buffer position where the image should appear.
2974 The argument @var{string} specifies the text that should hold the image
2975 as an alternative to the default.
2977 The argument @var{image} must be an image descriptor, perhaps returned
2978 by @code{create-image} or stored by @code{defimage}.
2980 The argument @var{area} specifies whether to put the image in a margin.
2981 If it is @code{left-margin}, the image appears in the left margin;
2982 @code{right-margin} specifies the right margin. If @var{area} is
2983 @code{nil} or omitted, the image is displayed at point within the
2986 Internally, this function creates an overlay, and gives it a
2987 @code{before-string} property containing text that has a @code{display}
2988 property whose value is the image. (Whew!)
2991 @defun remove-images start end &optional buffer
2992 This function removes images in @var{buffer} between positions
2993 @var{start} and @var{end}. If @var{buffer} is omitted or @code{nil},
2994 images are removed from the current buffer.
2996 This removes only images that were put into @var{buffer} the way
2997 @code{put-image} does it, not images that were inserted with
2998 @code{insert-image} or in other ways.
3001 @defun image-size spec &optional pixels frame
3003 This function returns the size of an image as a pair
3004 @w{@code{(@var{width} . @var{height})}}. @var{spec} is an image
3005 specification. @var{pixels} non-nil means return sizes measured in
3006 pixels, otherwise return sizes measured in canonical character units
3007 (fractions of the width/height of the frame's default font).
3008 @var{frame} is the frame on which the image will be displayed.
3009 @var{frame} null or omitted means use the selected frame (@pxref{Input
3014 @subsection Image Cache
3016 Emacs stores images in an image cache when it displays them, so it can
3017 display them again more efficiently. It removes an image from the cache
3018 when it hasn't been displayed for a specified period of time.
3020 When an image is looked up in the cache, its specification is compared
3021 with cached image specifications using @code{equal}. This means that
3022 all images with equal specifications share the same image in the cache.
3024 @defvar image-cache-eviction-delay
3025 @tindex image-cache-eviction-delay
3026 This variable specifies the number of seconds an image can remain in the
3027 cache without being displayed. When an image is not displayed for this
3028 length of time, Emacs removes it from the image cache.
3030 If the value is @code{nil}, Emacs does not remove images from the cache
3031 except when you explicitly clear it. This mode can be useful for
3035 @defun clear-image-cache &optional frame
3036 @tindex clear-image-cache
3037 This function clears the image cache. If @var{frame} is non-@code{nil},
3038 only the cache for that frame is cleared. Otherwise all frames' caches
3043 @section Blinking Parentheses
3044 @cindex parenthesis matching
3046 @cindex balancing parentheses
3047 @cindex close parenthesis
3049 This section describes the mechanism by which Emacs shows a matching
3050 open parenthesis when the user inserts a close parenthesis.
3052 @defvar blink-paren-function
3053 The value of this variable should be a function (of no arguments) to
3054 be called whenever a character with close parenthesis syntax is inserted.
3055 The value of @code{blink-paren-function} may be @code{nil}, in which
3056 case nothing is done.
3059 @defopt blink-matching-paren
3060 If this variable is @code{nil}, then @code{blink-matching-open} does
3064 @defopt blink-matching-paren-distance
3065 This variable specifies the maximum distance to scan for a matching
3066 parenthesis before giving up.
3069 @defopt blink-matching-delay
3070 This variable specifies the number of seconds for the cursor to remain
3071 at the matching parenthesis. A fraction of a second often gives
3072 good results, but the default is 1, which works on all systems.
3075 @deffn Command blink-matching-open
3076 This function is the default value of @code{blink-paren-function}. It
3077 assumes that point follows a character with close parenthesis syntax and
3078 moves the cursor momentarily to the matching opening character. If that
3079 character is not already on the screen, it displays the character's
3080 context in the echo area. To avoid long delays, this function does not
3081 search farther than @code{blink-matching-paren-distance} characters.
3083 Here is an example of calling this function explicitly.
3087 (defun interactive-blink-matching-open ()
3088 @c Do not break this line! -- rms.
3089 @c The first line of a doc string
3090 @c must stand alone.
3091 "Indicate momentarily the start of sexp before point."
3095 (let ((blink-matching-paren-distance
3097 (blink-matching-paren t))
3098 (blink-matching-open)))
3104 @section Inverse Video
3105 @cindex Inverse Video
3107 @defopt inverse-video
3108 @cindex highlighting
3109 This variable controls whether Emacs uses inverse video for all text
3110 on the screen. Non-@code{nil} means yes, @code{nil} means no. The
3111 default is @code{nil}.
3114 @defopt mode-line-inverse-video
3115 This variable controls the use of inverse video for mode lines and menu
3116 bars. If it is non-@code{nil}, then these lines are displayed in
3117 inverse video. Otherwise, these lines are displayed normally, just like
3118 other text. The default is @code{t}.
3120 For window frames, this feature actually applies the face named
3121 @code{mode-line}; that face is normally set up as the inverse of the
3122 default face, unless you change it.
3126 @section Usual Display Conventions
3128 The usual display conventions define how to display each character
3129 code. You can override these conventions by setting up a display table
3130 (@pxref{Display Tables}). Here are the usual display conventions:
3134 Character codes 32 through 126 map to glyph codes 32 through 126.
3135 Normally this means they display as themselves.
3138 Character code 9 is a horizontal tab. It displays as whitespace
3139 up to a position determined by @code{tab-width}.
3142 Character code 10 is a newline.
3145 All other codes in the range 0 through 31, and code 127, display in one
3146 of two ways according to the value of @code{ctl-arrow}. If it is
3147 non-@code{nil}, these codes map to sequences of two glyphs, where the
3148 first glyph is the @sc{ascii} code for @samp{^}. (A display table can
3149 specify a glyph to use instead of @samp{^}.) Otherwise, these codes map
3150 just like the codes in the range 128 to 255.
3152 On MS-DOS terminals, Emacs arranges by default for the character code
3153 127 to be mapped to the glyph code 127, which normally displays as an
3154 empty polygon. This glyph is used to display non-@sc{ascii} characters
3155 that the MS-DOS terminal doesn't support. @xref{MS-DOS and MULE,,,
3156 emacs, The GNU Emacs Manual}.
3159 Character codes 128 through 255 map to sequences of four glyphs, where
3160 the first glyph is the @sc{ascii} code for @samp{\}, and the others are
3161 digit characters representing the character code in octal. (A display
3162 table can specify a glyph to use instead of @samp{\}.)
3165 Multibyte character codes above 256 are displayed as themselves, or as a
3166 question mark or empty box if the terminal cannot display that
3170 The usual display conventions apply even when there is a display
3171 table, for any character whose entry in the active display table is
3172 @code{nil}. Thus, when you set up a display table, you need only
3173 specify the characters for which you want special behavior.
3175 These display rules apply to carriage return (character code 13), when
3176 it appears in the buffer. But that character may not appear in the
3177 buffer where you expect it, if it was eliminated as part of end-of-line
3178 conversion (@pxref{Coding System Basics}).
3180 These variables affect the way certain characters are displayed on the
3181 screen. Since they change the number of columns the characters occupy,
3182 they also affect the indentation functions. These variables also affect
3183 how the mode line is displayed; if you want to force redisplay of the
3184 mode line using the new values, call the function
3185 @code{force-mode-line-update} (@pxref{Mode Line Format}).
3188 @cindex control characters in display
3189 This buffer-local variable controls how control characters are
3190 displayed. If it is non-@code{nil}, they are displayed as a caret
3191 followed by the character: @samp{^A}. If it is @code{nil}, they are
3192 displayed as a backslash followed by three octal digits: @samp{\001}.
3195 @c Following may have overfull hbox.
3196 @defvar default-ctl-arrow
3197 The value of this variable is the default value for @code{ctl-arrow} in
3198 buffers that do not override it. @xref{Default Value}.
3201 @defopt indicate-empty-lines
3202 @tindex indicate-empty-lines
3203 @cindex fringes, and empty line indication
3204 When this is non-@code{nil}, Emacs displays a special glyph in
3205 each empty line at the end of the buffer, on terminals that
3206 support it (window systems).
3210 The value of this variable is the spacing between tab stops used for
3211 displaying tab characters in Emacs buffers. The value is in units of
3212 columns, and the default is 8. Note that this feature is completely
3213 independent of the user-settable tab stops used by the command
3214 @code{tab-to-tab-stop}. @xref{Indent Tabs}.
3217 @node Display Tables
3218 @section Display Tables
3220 @cindex display table
3221 You can use the @dfn{display table} feature to control how all possible
3222 character codes display on the screen. This is useful for displaying
3223 European languages that have letters not in the @sc{ascii} character
3226 The display table maps each character code into a sequence of
3227 @dfn{glyphs}, each glyph being a graphic that takes up one character
3228 position on the screen. You can also define how to display each glyph
3229 on your terminal, using the @dfn{glyph table}.
3231 Display tables affect how the mode line is displayed; if you want to
3232 force redisplay of the mode line using a new display table, call
3233 @code{force-mode-line-update} (@pxref{Mode Line Format}).
3236 * Display Table Format:: What a display table consists of.
3237 * Active Display Table:: How Emacs selects a display table to use.
3238 * Glyphs:: How to define a glyph, and what glyphs mean.
3241 @node Display Table Format
3242 @subsection Display Table Format
3244 A display table is actually a char-table (@pxref{Char-Tables}) with
3245 @code{display-table} as its subtype.
3247 @defun make-display-table
3248 This creates and returns a display table. The table initially has
3249 @code{nil} in all elements.
3252 The ordinary elements of the display table are indexed by character
3253 codes; the element at index @var{c} says how to display the character
3254 code @var{c}. The value should be @code{nil} or a vector of glyph
3255 values (@pxref{Glyphs}). If an element is @code{nil}, it says to
3256 display that character according to the usual display conventions
3257 (@pxref{Usual Display}).
3259 If you use the display table to change the display of newline
3260 characters, the whole buffer will be displayed as one long ``line.''
3262 The display table also has six ``extra slots'' which serve special
3263 purposes. Here is a table of their meanings; @code{nil} in any slot
3264 means to use the default for that slot, as stated below.
3268 The glyph for the end of a truncated screen line (the default for this
3269 is @samp{$}). @xref{Glyphs}. Newer Emacs versions, on some platforms,
3270 display arrows to indicate truncation---the display table has no effect
3271 in these situations.
3273 The glyph for the end of a continued line (the default is @samp{\}).
3274 Newer Emacs versions, on some platforms, display curved arrows to
3275 indicate truncation---the display table has no effect in these
3278 The glyph for indicating a character displayed as an octal character
3279 code (the default is @samp{\}).
3281 The glyph for indicating a control character (the default is @samp{^}).
3283 A vector of glyphs for indicating the presence of invisible lines (the
3284 default is @samp{...}). @xref{Selective Display}.
3286 The glyph used to draw the border between side-by-side windows (the
3287 default is @samp{|}). @xref{Splitting Windows}. This takes effect only
3288 when there are no scroll bars; if scroll bars are supported and in use,
3289 a scroll bar separates the two windows.
3292 For example, here is how to construct a display table that mimics the
3293 effect of setting @code{ctl-arrow} to a non-@code{nil} value:
3296 (setq disptab (make-display-table))
3299 (or (= i ?\t) (= i ?\n)
3300 (aset disptab i (vector ?^ (+ i 64))))
3302 (aset disptab 127 (vector ?^ ??)))
3305 @defun display-table-slot display-table slot
3306 This function returns the value of the extra slot @var{slot} of
3307 @var{display-table}. The argument @var{slot} may be a number from 0 to
3308 5 inclusive, or a slot name (symbol). Valid symbols are
3309 @code{truncation}, @code{wrap}, @code{escape}, @code{control},
3310 @code{selective-display}, and @code{vertical-border}.
3313 @defun set-display-table-slot display-table slot value
3314 This function stores @var{value} in the extra slot @var{slot} of
3315 @var{display-table}. The argument @var{slot} may be a number from 0 to
3316 5 inclusive, or a slot name (symbol). Valid symbols are
3317 @code{truncation}, @code{wrap}, @code{escape}, @code{control},
3318 @code{selective-display}, and @code{vertical-border}.
3321 @defun describe-display-table display-table
3322 @tindex describe-display-table
3323 This function displays a description of the display table
3324 @var{display-table} in a help buffer.
3327 @deffn Command describe-current-display-table
3328 @tindex describe-current-display-table
3329 This command displays a description of the current display table in a
3333 @node Active Display Table
3334 @subsection Active Display Table
3335 @cindex active display table
3337 Each window can specify a display table, and so can each buffer. When
3338 a buffer @var{b} is displayed in window @var{w}, display uses the
3339 display table for window @var{w} if it has one; otherwise, the display
3340 table for buffer @var{b} if it has one; otherwise, the standard display
3341 table if any. The display table chosen is called the @dfn{active}
3344 @defun window-display-table window
3345 This function returns @var{window}'s display table, or @code{nil}
3346 if @var{window} does not have an assigned display table.
3349 @defun set-window-display-table window table
3350 This function sets the display table of @var{window} to @var{table}.
3351 The argument @var{table} should be either a display table or
3355 @defvar buffer-display-table
3356 This variable is automatically buffer-local in all buffers; its value in
3357 a particular buffer specifies the display table for that buffer. If it
3358 is @code{nil}, that means the buffer does not have an assigned display
3362 @defvar standard-display-table
3363 This variable's value is the default display table, used whenever a
3364 window has no display table and neither does the buffer displayed in
3365 that window. This variable is @code{nil} by default.
3368 If there is no display table to use for a particular window---that is,
3369 if the window specifies none, its buffer specifies none, and
3370 @code{standard-display-table} is @code{nil}---then Emacs uses the usual
3371 display conventions for all character codes in that window. @xref{Usual
3374 A number of functions for changing the standard display table
3375 are defined in the library @file{disp-table}.
3381 A @dfn{glyph} is a generalization of a character; it stands for an
3382 image that takes up a single character position on the screen. Glyphs
3383 are represented in Lisp as integers, just as characters are. Normally
3384 Emacs finds glyphs in the display table (@pxref{Display Tables}).
3386 A glyph can be @dfn{simple} or it can be defined by the @dfn{glyph
3387 table}. A simple glyph is just a way of specifying a character and a
3388 face to output it in. The glyph code for a simple glyph, mod 524288,
3389 is the character to output, and the glyph code divided by 524288
3390 specifies the face number (@pxref{Face Functions}) to use while
3391 outputting it. (524288 is
3400 On character terminals, you can set up a @dfn{glyph table} to define
3401 the meaning of glyph codes. The glyph codes is the value of the
3402 variable @code{glyph-table}.
3405 The value of this variable is the current glyph table. It should be a
3406 vector; the @var{g}th element defines glyph code @var{g}.
3408 If a glyph code is greater than or equal to the length of the glyph
3409 table, that code is automatically simple. If the value of
3410 @code{glyph-table} is @code{nil} instead of a vector, then all glyphs
3411 are simple. The glyph table is not used on graphical displays, only
3412 on character terminals. On graphical displays, all glyphs are simple.
3415 Here are the possible types of elements in the glyph table:
3419 Send the characters in @var{string} to the terminal to output
3420 this glyph. This alternative is available on character terminals,
3421 but not under a window system.
3424 Define this glyph code as an alias for glyph code @var{integer}. You
3425 can use an alias to specify a face code for the glyph and use a small
3429 This glyph is simple.
3432 @defun create-glyph string
3433 @tindex create-glyph
3434 This function returns a newly-allocated glyph code which is set up to
3435 display by sending @var{string} to the terminal.
3443 This section describes how to make Emacs ring the bell (or blink the
3444 screen) to attract the user's attention. Be conservative about how
3445 often you do this; frequent bells can become irritating. Also be
3446 careful not to use just beeping when signaling an error is more
3447 appropriate. (@xref{Errors}.)
3449 @defun ding &optional do-not-terminate
3450 @cindex keyboard macro termination
3451 This function beeps, or flashes the screen (see @code{visible-bell} below).
3452 It also terminates any keyboard macro currently executing unless
3453 @var{do-not-terminate} is non-@code{nil}.
3456 @defun beep &optional do-not-terminate
3457 This is a synonym for @code{ding}.
3460 @defopt visible-bell
3461 This variable determines whether Emacs should flash the screen to
3462 represent a bell. Non-@code{nil} means yes, @code{nil} means no. This
3463 is effective on a window system, and on a character-only terminal
3464 provided the terminal's Termcap entry defines the visible bell
3465 capability (@samp{vb}).
3468 @defvar ring-bell-function
3469 If this is non-@code{nil}, it specifies how Emacs should ``ring the
3470 bell.'' Its value should be a function of no arguments. If this is
3471 non-@code{nil}, it takes precedence over the @code{visible-bell}
3475 @node Window Systems
3476 @section Window Systems
3478 Emacs works with several window systems, most notably the X Window
3479 System. Both Emacs and X use the term ``window'', but use it
3480 differently. An Emacs frame is a single window as far as X is
3481 concerned; the individual Emacs windows are not known to X at all.
3483 @defvar window-system
3484 This variable tells Lisp programs what window system Emacs is running
3485 under. The possible values are
3489 @cindex X Window System
3490 Emacs is displaying using X.
3492 Emacs is displaying using MS-DOS.
3494 Emacs is displaying using Windows.
3496 Emacs is displaying using a Macintosh.
3498 Emacs is using a character-based terminal.
3502 @defvar window-setup-hook
3503 This variable is a normal hook which Emacs runs after handling the
3504 initialization files. Emacs runs this hook after it has completed
3505 loading your init file, the default initialization file (if
3506 any), and the terminal-specific Lisp code, and running the hook
3507 @code{term-setup-hook}.
3509 This hook is used for internal purposes: setting up communication with
3510 the window system, and creating the initial window. Users should not