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,
4 @c 2002, 2005 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 * Warnings:: Displaying warning messages for the user.
19 * Progress:: Informing user about progress of a long operation.
20 * Invisible Text:: Hiding part of the buffer text.
21 * Selective Display:: Hiding part of the buffer text (the old way).
22 * Overlay Arrow:: Display of an arrow to indicate position.
23 * Temporary Displays:: Displays that go away automatically.
24 * Overlays:: Use overlays to highlight parts of the buffer.
25 * Width:: How wide a character or string is on the screen.
26 * Line Height:: Controlling the height of lines.
27 * Faces:: A face defines a graphics style for text characters:
29 * Fringes:: Controlling window fringes.
30 * Fringe Bitmaps:: Displaying bitmaps in the window fringes.
31 * Customizing Bitmaps:: Specifying your own bitmaps to use in the fringes.
32 * Scroll Bars:: Controlling vertical scroll bars.
33 * Pointer Shape:: Controlling the mouse pointer shape.
34 * Display Property:: Enabling special display features.
35 * Images:: Displaying images in Emacs buffers.
36 * Buttons:: Adding clickable buttons to Emacs buffers.
37 * Blinking:: How Emacs shows the matching open parenthesis.
38 * Inverse Video:: Specifying how the screen looks.
39 * Usual Display:: The usual conventions for displaying nonprinting chars.
40 * Display Tables:: How to specify other conventions.
41 * Beeping:: Audible signal to the user.
42 * Window Systems:: Which window system is being used.
46 @section Refreshing the Screen
48 The function @code{redraw-frame} redisplays the entire contents of a
49 given frame (@pxref{Frames}).
52 @defun redraw-frame frame
53 This function clears and redisplays frame @var{frame}.
56 Even more powerful is @code{redraw-display}:
58 @deffn Command redraw-display
59 This function clears and redisplays all visible frames.
62 This function forces certain windows to be redisplayed
63 but does not clear them.
65 @defun force-window-update object
66 This function forces redisplay of some or all windows. If
67 @var{object} is a window, it forces redisplay of that window. If
68 @var{object} is a buffer or buffer name, it forces redisplay of all
69 windows displaying that buffer. If @var{object} is @code{nil}, it
70 forces redisplay of all windows.
73 Processing user input takes absolute priority over redisplay. If you
74 call these functions when input is available, they do nothing
75 immediately, but a full redisplay does happen eventually---after all the
76 input has been processed.
78 Normally, suspending and resuming Emacs also refreshes the screen.
79 Some terminal emulators record separate contents for display-oriented
80 programs such as Emacs and for ordinary sequential display. If you are
81 using such a terminal, you might want to inhibit the redisplay on
84 @defvar no-redraw-on-reenter
85 @cindex suspend (cf. @code{no-redraw-on-reenter})
86 @cindex resume (cf. @code{no-redraw-on-reenter})
87 This variable controls whether Emacs redraws the entire screen after it
88 has been suspended and resumed. Non-@code{nil} means there is no need
89 to redraw, @code{nil} means redrawing is needed. The default is @code{nil}.
92 @node Forcing Redisplay
93 @section Forcing Redisplay
94 @cindex forcing redisplay
96 Emacs redisplay normally stops if input arrives, and does not happen
97 at all if input is available before it starts. Most of the time, this
98 is exactly what you want. However, you can prevent preemption by
99 binding @code{redisplay-dont-pause} to a non-@code{nil} value.
101 @tindex redisplay-dont-pause
102 @defvar redisplay-dont-pause
103 If this variable is non-@code{nil}, pending input does not
104 prevent or halt redisplay; redisplay occurs, and finishes,
105 regardless of whether input is available. This feature is available
109 You can request a display update, but only if no input is pending,
110 with @code{(sit-for 0)}. To force a display update even when input is
114 (let ((redisplay-dont-pause t))
120 @cindex line wrapping
121 @cindex continuation lines
122 @cindex @samp{$} in display
123 @cindex @samp{\} in display
125 When a line of text extends beyond the right edge of a window, the
126 line can either be continued on the next screen line, or truncated to
127 one screen line. The additional screen lines used to display a long
128 text line are called @dfn{continuation} lines. Normally, a @samp{$} in
129 the rightmost column of the window indicates truncation; a @samp{\} on
130 the rightmost column indicates a line that ``wraps'' onto the next line,
131 which is also called @dfn{continuing} the line. (The display table can
132 specify alternative indicators; see @ref{Display Tables}.)
134 On a windowed display, the @samp{$} and @samp{\} indicators are
135 replaced with graphics bitmaps displayed in the window fringes
138 Note that continuation is different from filling; continuation happens
139 on the screen only, not in the buffer contents, and it breaks a line
140 precisely at the right margin, not at a word boundary. @xref{Filling}.
142 @defopt truncate-lines
143 This buffer-local variable controls how Emacs displays lines that extend
144 beyond the right edge of the window. The default is @code{nil}, which
145 specifies continuation. If the value is non-@code{nil}, then these
148 If the variable @code{truncate-partial-width-windows} is non-@code{nil},
149 then truncation is always used for side-by-side windows (within one
150 frame) regardless of the value of @code{truncate-lines}.
153 @defopt default-truncate-lines
154 This variable is the default value for @code{truncate-lines}, for
155 buffers that do not have buffer-local values for it.
158 @defopt truncate-partial-width-windows
159 This variable controls display of lines that extend beyond the right
160 edge of the window, in side-by-side windows (@pxref{Splitting Windows}).
161 If it is non-@code{nil}, these lines are truncated; otherwise,
162 @code{truncate-lines} says what to do with them.
165 When horizontal scrolling (@pxref{Horizontal Scrolling}) is in use in
166 a window, that forces truncation.
168 You can override the glyphs that indicate continuation or truncation
169 using the display table; see @ref{Display Tables}.
171 If your buffer contains @emph{very} long lines, and you use
172 continuation to display them, just thinking about them can make Emacs
173 redisplay slow. The column computation and indentation functions also
174 become slow. Then you might find it advisable to set
175 @code{cache-long-line-scans} to @code{t}.
177 @defvar cache-long-line-scans
178 If this variable is non-@code{nil}, various indentation and motion
179 functions, and Emacs redisplay, cache the results of scanning the
180 buffer, and consult the cache to avoid rescanning regions of the buffer
181 unless they are modified.
183 Turning on the cache slows down processing of short lines somewhat.
185 This variable is automatically buffer-local in every buffer.
189 @section The Echo Area
190 @cindex error display
193 The @dfn{echo area} is used for displaying messages made with the
194 @code{message} primitive, and for echoing keystrokes. It is not the
195 same as the minibuffer, despite the fact that the minibuffer appears
196 (when active) in the same place on the screen as the echo area. The
197 @cite{GNU Emacs Manual} specifies the rules for resolving conflicts
198 between the echo area and the minibuffer for use of that screen space
199 (@pxref{Minibuffer,, The Minibuffer, emacs, The GNU Emacs Manual}).
200 Error messages appear in the echo area; see @ref{Errors}.
202 You can write output in the echo area by using the Lisp printing
203 functions with @code{t} as the stream (@pxref{Output Functions}), or as
206 @defun message string &rest arguments
207 This function displays a message in the echo area. The
208 argument @var{string} is similar to a C language @code{printf} control
209 string. See @code{format} in @ref{String Conversion}, for the details
210 on the conversion specifications. @code{message} returns the
213 In batch mode, @code{message} prints the message text on the standard
214 error stream, followed by a newline.
216 If @var{string}, or strings among the @var{arguments}, have @code{face}
217 text properties, these affect the way the message is displayed.
220 If @var{string} is @code{nil}, @code{message} clears the echo area; if
221 the echo area has been expanded automatically, this brings it back to
222 its normal size. If the minibuffer is active, this brings the
223 minibuffer contents back onto the screen immediately.
225 @vindex message-truncate-lines
226 Normally, displaying a long message resizes the echo area to display
227 the entire message. But if the variable @code{message-truncate-lines}
228 is non-@code{nil}, the echo area does not resize, and the message is
229 truncated to fit it, as in Emacs 20 and before.
233 (message "Minibuffer depth is %d."
235 @print{} Minibuffer depth is 0.
236 @result{} "Minibuffer depth is 0."
240 ---------- Echo Area ----------
241 Minibuffer depth is 0.
242 ---------- Echo Area ----------
246 To automatically display a message in the echo area or in a pop-buffer,
247 depending on its size, use @code{display-message-or-buffer}.
250 @tindex with-temp-message
251 @defmac with-temp-message message &rest body
252 This construct displays a message in the echo area temporarily, during
253 the execution of @var{body}. It displays @var{message}, executes
254 @var{body}, then returns the value of the last body form while restoring
255 the previous echo area contents.
258 @defun message-or-box string &rest arguments
259 This function displays a message like @code{message}, but may display it
260 in a dialog box instead of the echo area. If this function is called in
261 a command that was invoked using the mouse---more precisely, if
262 @code{last-nonmenu-event} (@pxref{Command Loop Info}) is either
263 @code{nil} or a list---then it uses a dialog box or pop-up menu to
264 display the message. Otherwise, it uses the echo area. (This is the
265 same criterion that @code{y-or-n-p} uses to make a similar decision; see
266 @ref{Yes-or-No Queries}.)
268 You can force use of the mouse or of the echo area by binding
269 @code{last-nonmenu-event} to a suitable value around the call.
272 @defun message-box string &rest arguments
273 This function displays a message like @code{message}, but uses a dialog
274 box (or a pop-up menu) whenever that is possible. If it is impossible
275 to use a dialog box or pop-up menu, because the terminal does not
276 support them, then @code{message-box} uses the echo area, like
280 @defun display-message-or-buffer message &optional buffer-name not-this-window frame
281 @tindex display-message-or-buffer
282 This function displays the message @var{message}, which may be either a
283 string or a buffer. If it is shorter than the maximum height of the
284 echo area, as defined by @code{max-mini-window-height}, it is displayed
285 in the echo area, using @code{message}. Otherwise,
286 @code{display-buffer} is used to show it in a pop-up buffer.
288 Returns either the string shown in the echo area, or when a pop-up
289 buffer is used, the window used to display it.
291 If @var{message} is a string, then the optional argument
292 @var{buffer-name} is the name of the buffer used to display it when a
293 pop-up buffer is used, defaulting to @samp{*Message*}. In the case
294 where @var{message} is a string and displayed in the echo area, it is
295 not specified whether the contents are inserted into the buffer anyway.
297 The optional arguments @var{not-this-window} and @var{frame} are as for
298 @code{display-buffer}, and only used if a buffer is displayed.
301 @defun current-message
302 This function returns the message currently being displayed in the
303 echo area, or @code{nil} if there is none.
306 @defvar cursor-in-echo-area
307 This variable controls where the cursor appears when a message is
308 displayed in the echo area. If it is non-@code{nil}, then the cursor
309 appears at the end of the message. Otherwise, the cursor appears at
310 point---not in the echo area at all.
312 The value is normally @code{nil}; Lisp programs bind it to @code{t}
313 for brief periods of time.
316 @defvar echo-area-clear-hook
317 This normal hook is run whenever the echo area is cleared---either by
318 @code{(message nil)} or for any other reason.
321 Almost all the messages displayed in the echo area are also recorded
322 in the @samp{*Messages*} buffer.
324 @defopt message-log-max
325 This variable specifies how many lines to keep in the @samp{*Messages*}
326 buffer. The value @code{t} means there is no limit on how many lines to
327 keep. The value @code{nil} disables message logging entirely. Here's
328 how to display a message and prevent it from being logged:
331 (let (message-log-max)
336 @defvar echo-keystrokes
337 This variable determines how much time should elapse before command
338 characters echo. Its value must be an integer or floating point number,
340 number of seconds to wait before echoing. If the user types a prefix
341 key (such as @kbd{C-x}) and then delays this many seconds before
342 continuing, the prefix key is echoed in the echo area. (Once echoing
343 begins in a key sequence, all subsequent characters in the same key
344 sequence are echoed immediately.)
346 If the value is zero, then command input is not echoed.
350 @section Reporting Warnings
353 @dfn{Warnings} are a facility for a program to inform the user of a
354 possible problem, but continue running.
357 * Warning Basics:: Warnings concepts and functions to report them.
358 * Warning Variables:: Variables programs bind to customize their warnings.
359 * Warning Options:: Variables users set to control display of warnings.
363 @subsection Warning Basics
364 @cindex severity level
366 Every warning has a textual message, which explains the problem for
367 the user, and a @dfn{severity level} which is a symbol. Here are the
368 possible severity levels, in order of decreasing severity, and their
373 A problem that will seriously impair Emacs operation soon
374 if you do not attend to it promptly.
376 A report of data or circumstances that are inherently wrong.
378 A report of data or circumstances that are not inherently wrong, but
379 raise suspicion of a possible problem.
381 A report of information that may be useful if you are debugging.
384 When your program encounters invalid input data, it can either
385 signal a Lisp error by calling @code{error} or @code{signal} or report
386 a warning with severity @code{:error}. Signaling a Lisp error is the
387 easiest thing to do, but it means the program cannot continue
388 processing. If you want to take the trouble to implement a way to
389 continue processing despite the bad data, then reporting a warning of
390 severity @code{:error} is the right way to inform the user of the
391 problem. For instance, the Emacs Lisp byte compiler can report an
392 error that way and continue compiling other functions. (If the
393 program signals a Lisp error and then handles it with
394 @code{condition-case}, the user won't see the error message; it could
395 show the message to the user by reporting it as a warning.)
398 Each warning has a @dfn{warning type} to classify it. The type is a
399 list of symbols. The first symbol should be the custom group that you
400 use for the program's user options. For example, byte compiler
401 warnings use the warning type @code{(bytecomp)}. You can also
402 subcategorize the warnings, if you wish, by using more symbols in the
405 @defun display-warning type message &optional level buffer-name
406 This function reports a warning, using @var{message} as the message
407 and @var{type} as the warning type. @var{level} should be the
408 severity level, with @code{:warning} being the default.
410 @var{buffer-name}, if non-@code{nil}, specifies the name of the buffer
411 for logging the warning. By default, it is @samp{*Warnings*}.
414 @defun lwarn type level message &rest args
415 This function reports a warning using the value of @code{(format
416 @var{message} @var{args}...)} as the message. In other respects it is
417 equivalent to @code{display-warning}.
420 @defun warn message &rest args
421 This function reports a warning using the value of @code{(format
422 @var{message} @var{args}...)} as the message, @code{(emacs)} as the
423 type, and @code{:warning} as the severity level. It exists for
424 compatibility only; we recommend not using it, because you should
425 specify a specific warning type.
428 @node Warning Variables
429 @subsection Warning Variables
431 Programs can customize how their warnings appear by binding
432 the variables described in this section.
434 @defvar warning-levels
435 This list defines the meaning and severity order of the warning
436 severity levels. Each element defines one severity level,
437 and they are arranged in order of decreasing severity.
439 Each element has the form @code{(@var{level} @var{string}
440 @var{function})}, where @var{level} is the severity level it defines.
441 @var{string} specifies the textual description of this level.
442 @var{string} should use @samp{%s} to specify where to put the warning
443 type information, or it can omit the @samp{%s} so as not to include
446 The optional @var{function}, if non-@code{nil}, is a function to call
447 with no arguments, to get the user's attention.
449 Normally you should not change the value of this variable.
452 @defvar warning-prefix-function
453 If non-@code{nil}, the value is a function to generate prefix text for
454 warnings. Programs can bind the variable to a suitable function.
455 @code{display-warning} calls this function with the warnings buffer
456 current, and the function can insert text in it. That text becomes
457 the beginning of the warning message.
459 The function is called with two arguments, the severity level and its
460 entry in @code{warning-levels}. It should return a list to use as the
461 entry (this value need not be an actual member of
462 @code{warning-levels}). By constructing this value, the function can
463 change the severity of the warning, or specify different handling for
464 a given severity level.
466 If the variable's value is @code{nil} then there is no function
470 @defvar warning-series
471 Programs can bind this variable to @code{t} to say that the next
472 warning should begin a series. When several warnings form a series,
473 that means to leave point on the first warning of the series, rather
474 than keep moving it for each warning so that it appears on the last one.
475 The series ends when the local binding is unbound and
476 @code{warning-series} becomes @code{nil} again.
478 The value can also be a symbol with a function definition. That is
479 equivalent to @code{t}, except that the next warning will also call
480 the function with no arguments with the warnings buffer current. The
481 function can insert text which will serve as a header for the series
484 Once a series has begun, the value is a marker which points to the
485 buffer position in the warnings buffer of the start of the series.
487 The variable's normal value is @code{nil}, which means to handle
488 each warning separately.
491 @defvar warning-fill-prefix
492 When this variable is non-@code{nil}, it specifies a fill prefix to
493 use for filling each warning's text.
496 @defvar warning-type-format
497 This variable specifies the format for displaying the warning type
498 in the warning message. The result of formatting the type this way
499 gets included in the message under the control of the string in the
500 entry in @code{warning-levels}. The default value is @code{" (%s)"}.
501 If you bind it to @code{""} then the warning type won't appear at
505 @node Warning Options
506 @subsection Warning Options
508 These variables are used by users to control what happens
509 when a Lisp program reports a warning.
511 @defopt warning-minimum-level
512 This user option specifies the minimum severity level that should be
513 shown immediately to the user. The default is @code{:warning}, which
514 means to immediately display all warnings except @code{:debug}
518 @defopt warning-minimum-log-level
519 This user option specifies the minimum severity level that should be
520 logged in the warnings buffer. The default is @code{:warning}, which
521 means to log all warnings except @code{:debug} warnings.
524 @defopt warning-suppress-types
525 This list specifies which warning types should not be displayed
526 immediately for the user. Each element of the list should be a list
527 of symbols. If its elements match the first elements in a warning
528 type, then that warning is not displayed immediately.
531 @defopt warning-suppress-log-types
532 This list specifies which warning types should not be logged in the
533 warnings buffer. Each element of the list should be a list of
534 symbols. If it matches the first few elements in a warning type, then
535 that warning is not logged.
539 @section Reporting Operation Progress
540 @cindex progress reporting
542 When an operation can take a while to finish, you should inform the
543 user about the progress it makes. This way the user can estimate
544 remaining time and clearly see that Emacs is busy working, not hung.
546 Functions listed in this section provide simple and efficient way of
547 reporting operation progress. Here is a working example that does
551 (let ((progress-reporter
552 (make-progress-reporter "Collecting some mana for Emacs..."
556 (progress-reporter-update progress-reporter k))
557 (progress-reporter-done progress-reporter))
560 @defun make-progress-reporter message min-value max-value &optional current-value min-change min-time
561 This function creates a progress reporter---the object you will use as
562 an argument for all other functions listed here. The idea is to
563 precompute as much data as possible to make progress reporting very
566 The @var{message} will be displayed in the echo area, followed by
567 progress percentage. @var{message} is treated as a simple string. If
568 you need it to depend on a filename, for instance, use @code{format}
569 before calling this function.
571 @var{min-value} and @var{max-value} arguments stand for starting and
572 final states of your operation. For instance, if you scan a buffer,
573 they should be the results of @code{point-min} and @code{point-max}
574 correspondingly. It is required that @var{max-value} is greater than
575 @var{min-value}. If you create progress reporter when some part of
576 the operation has already been completed, then specify
577 @var{current-value} argument. But normally you should omit it or set
578 it to @code{nil}---it will default to @var{min-value} then.
580 Remaining arguments control the rate of echo area updates. Progress
581 reporter will wait for at least @var{min-change} more percents of the
582 operation to be completed before printing next message.
583 @var{min-time} specifies the minimum time in seconds to pass between
584 successive prints. It can be fractional. Depending on Emacs and
585 system capabilities, progress reporter may or may not respect this
586 last argument or do it with varying precision. Default value for
587 @var{min-change} is 1 (one percent), for @var{min-time}---0.2
590 This function calls @code{progress-reporter-update}, so the first
591 message is printed immediately.
594 @defun progress-reporter-update reporter value
595 This function does the main work of reporting progress of your
596 operation. It print the message of @var{reporter} followed by
597 progress percentage determined by @var{value}. If percentage is zero,
598 then it is not printed at all.
600 @var{reporter} must be the result of a call to
601 @code{make-progress-reporter}. @var{value} specifies the current
602 state of your operation and must be between @var{min-value} and
603 @var{max-value} (inclusive) as passed to
604 @code{make-progress-reporter}. For instance, if you scan a buffer,
605 then @var{value} should be the result of a call to @code{point}.
607 This function respects @var{min-change} and @var{min-time} as passed
608 to @code{make-progress-reporter} and so does not output new messages
609 on every invocation. It is thus very fast and normally you should not
610 try to reduce the number of calls to it: resulting overhead will most
611 likely negate your effort.
614 @defun progress-reporter-force-update reporter value &optional new-message
615 This function is similar to @code{progress-reporter-update} except
616 that it prints a message in the echo area unconditionally.
618 The first two arguments have the same meaning as for
619 @code{progress-reporter-update}. Optional @var{new-message} allows
620 you to change the message of the @var{reporter}. Since this functions
621 always updates the echo area, such a change will be immediately
622 presented to the user.
625 @defun progress-reporter-done reporter
626 This function should be called when the operation is finished. It
627 prints the message of @var{reporter} followed by word ``done'' in the
630 You should always call this function and not hope for
631 @code{progress-reporter-update} to print ``100%.'' Firstly, it may
632 never print it, there are many good reasons for this not to happen.
633 Secondly, ``done'' is more explicit.
636 @defmac dotimes-with-progress-reporter (var count [result]) message body...
637 This is a convenience macro that works the same way as @code{dotimes}
638 does, but also reports loop progress using the functions described
639 above. It allows you to save some typing.
641 You can rewrite the example in the beginning of this node using
645 (dotimes-with-progress-reporter
647 "Collecting some mana for Emacs..."
653 @section Invisible Text
655 @cindex invisible text
656 You can make characters @dfn{invisible}, so that they do not appear on
657 the screen, with the @code{invisible} property. This can be either a
658 text property (@pxref{Text Properties}) or a property of an overlay
661 In the simplest case, any non-@code{nil} @code{invisible} property makes
662 a character invisible. This is the default case---if you don't alter
663 the default value of @code{buffer-invisibility-spec}, this is how the
664 @code{invisible} property works. You should normally use @code{t}
665 as the value of the @code{invisible} property if you don't plan
666 to set @code{buffer-invisibility-spec} yourself.
668 More generally, you can use the variable @code{buffer-invisibility-spec}
669 to control which values of the @code{invisible} property make text
670 invisible. This permits you to classify the text into different subsets
671 in advance, by giving them different @code{invisible} values, and
672 subsequently make various subsets visible or invisible by changing the
673 value of @code{buffer-invisibility-spec}.
675 Controlling visibility with @code{buffer-invisibility-spec} is
676 especially useful in a program to display the list of entries in a
677 database. It permits the implementation of convenient filtering
678 commands to view just a part of the entries in the database. Setting
679 this variable is very fast, much faster than scanning all the text in
680 the buffer looking for properties to change.
682 @defvar buffer-invisibility-spec
683 This variable specifies which kinds of @code{invisible} properties
684 actually make a character invisible. Setting this variable makes it
689 A character is invisible if its @code{invisible} property is
690 non-@code{nil}. This is the default.
693 Each element of the list specifies a criterion for invisibility; if a
694 character's @code{invisible} property fits any one of these criteria,
695 the character is invisible. The list can have two kinds of elements:
699 A character is invisible if its @code{invisible} property value
700 is @var{atom} or if it is a list with @var{atom} as a member.
702 @item (@var{atom} . t)
703 A character is invisible if its @code{invisible} property value
704 is @var{atom} or if it is a list with @var{atom} as a member.
705 Moreover, if this character is at the end of a line and is followed
706 by a visible newline, it displays an ellipsis.
711 Two functions are specifically provided for adding elements to
712 @code{buffer-invisibility-spec} and removing elements from it.
714 @defun add-to-invisibility-spec element
715 This function adds the element @var{element} to
716 @code{buffer-invisibility-spec} (if it is not already present in that
717 list). If @code{buffer-invisibility-spec} was @code{t}, it changes to
718 a list, @code{(t)}, so that text whose @code{invisible} property
719 is @code{t} remains invisible.
722 @defun remove-from-invisibility-spec element
723 This removes the element @var{element} from
724 @code{buffer-invisibility-spec}. This does nothing if @var{element}
728 A convention for use of @code{buffer-invisibility-spec} is that a
729 major mode should use the mode's own name as an element of
730 @code{buffer-invisibility-spec} and as the value of the
731 @code{invisible} property:
734 ;; @r{If you want to display an ellipsis:}
735 (add-to-invisibility-spec '(my-symbol . t))
736 ;; @r{If you don't want ellipsis:}
737 (add-to-invisibility-spec 'my-symbol)
739 (overlay-put (make-overlay beginning end)
740 'invisible 'my-symbol)
742 ;; @r{When done with the overlays:}
743 (remove-from-invisibility-spec '(my-symbol . t))
744 ;; @r{Or respectively:}
745 (remove-from-invisibility-spec 'my-symbol)
748 @vindex line-move-ignore-invisible
749 Ordinarily, functions that operate on text or move point do not care
750 whether the text is invisible. The user-level line motion commands
751 explicitly ignore invisible newlines if
752 @code{line-move-ignore-invisible} is non-@code{nil}, but only because
753 they are explicitly programmed to do so.
755 However, if a command ends with point inside or immediately after
756 invisible text, the main editing loop moves point further forward or
757 further backward (in the same direction that the command already moved
758 it) until that condition is no longer true. Thus, if the command
759 moved point back into an invisible range, Emacs moves point back to
760 the beginning of that range, following the previous visible character.
761 If the command moved point forward into an invisible range, Emacs
762 moves point forward past the first visible character that follows the
765 Incremental search can make invisible overlays visible temporarily
766 and/or permanently when a match includes invisible text. To enable
767 this, the overlay should have a non-@code{nil}
768 @code{isearch-open-invisible} property. The property value should be a
769 function to be called with the overlay as an argument. This function
770 should make the overlay visible permanently; it is used when the match
771 overlaps the overlay on exit from the search.
773 During the search, such overlays are made temporarily visible by
774 temporarily modifying their invisible and intangible properties. If you
775 want this to be done differently for a certain overlay, give it an
776 @code{isearch-open-invisible-temporary} property which is a function.
777 The function is called with two arguments: the first is the overlay, and
778 the second is @code{nil} to make the overlay visible, or @code{t} to
779 make it invisible again.
781 @node Selective Display
782 @section Selective Display
783 @cindex selective display
785 @dfn{Selective display} refers to a pair of related features for
786 hiding certain lines on the screen.
788 The first variant, explicit selective display, is designed for use in
789 a Lisp program: it controls which lines are hidden by altering the text.
790 The invisible text feature (@pxref{Invisible Text}) has partially
791 replaced this feature.
793 In the second variant, the choice of lines to hide is made
794 automatically based on indentation. This variant is designed to be a
797 The way you control explicit selective display is by replacing a
798 newline (control-j) with a carriage return (control-m). The text that
799 was formerly a line following that newline is now invisible. Strictly
800 speaking, it is temporarily no longer a line at all, since only newlines
801 can separate lines; it is now part of the previous line.
803 Selective display does not directly affect editing commands. For
804 example, @kbd{C-f} (@code{forward-char}) moves point unhesitatingly into
805 invisible text. However, the replacement of newline characters with
806 carriage return characters affects some editing commands. For example,
807 @code{next-line} skips invisible lines, since it searches only for
808 newlines. Modes that use selective display can also define commands
809 that take account of the newlines, or that make parts of the text
810 visible or invisible.
812 When you write a selectively displayed buffer into a file, all the
813 control-m's are output as newlines. This means that when you next read
814 in the file, it looks OK, with nothing invisible. The selective display
815 effect is seen only within Emacs.
817 @defvar selective-display
818 This buffer-local variable enables selective display. This means that
819 lines, or portions of lines, may be made invisible.
823 If the value of @code{selective-display} is @code{t}, then the character
824 control-m marks the start of invisible text; the control-m, and the rest
825 of the line following it, are not displayed. This is explicit selective
829 If the value of @code{selective-display} is a positive integer, then
830 lines that start with more than that many columns of indentation are not
834 When some portion of a buffer is invisible, the vertical movement
835 commands operate as if that portion did not exist, allowing a single
836 @code{next-line} command to skip any number of invisible lines.
837 However, character movement commands (such as @code{forward-char}) do
838 not skip the invisible portion, and it is possible (if tricky) to insert
839 or delete text in an invisible portion.
841 In the examples below, we show the @emph{display appearance} of the
842 buffer @code{foo}, which changes with the value of
843 @code{selective-display}. The @emph{contents} of the buffer do not
848 (setq selective-display nil)
851 ---------- Buffer: foo ----------
858 ---------- Buffer: foo ----------
862 (setq selective-display 2)
865 ---------- Buffer: foo ----------
870 ---------- Buffer: foo ----------
875 @defvar selective-display-ellipses
876 If this buffer-local variable is non-@code{nil}, then Emacs displays
877 @samp{@dots{}} at the end of a line that is followed by invisible text.
878 This example is a continuation of the previous one.
882 (setq selective-display-ellipses t)
885 ---------- Buffer: foo ----------
890 ---------- Buffer: foo ----------
894 You can use a display table to substitute other text for the ellipsis
895 (@samp{@dots{}}). @xref{Display Tables}.
899 @section The Overlay Arrow
900 @cindex overlay arrow
902 The @dfn{overlay arrow} is useful for directing the user's attention
903 to a particular line in a buffer. For example, in the modes used for
904 interface to debuggers, the overlay arrow indicates the line of code
905 about to be executed.
907 @defvar overlay-arrow-string
908 This variable holds the string to display to call attention to a
909 particular line, or @code{nil} if the arrow feature is not in use.
910 On a graphical display the contents of the string are ignored; instead a
911 glyph is displayed in the fringe area to the left of the display area.
914 @defvar overlay-arrow-position
915 This variable holds a marker that indicates where to display the overlay
916 arrow. It should point at the beginning of a line. On a non-graphical
917 display the arrow text
918 appears at the beginning of that line, overlaying any text that would
919 otherwise appear. Since the arrow is usually short, and the line
920 usually begins with indentation, normally nothing significant is
923 The overlay string is displayed only in the buffer that this marker
924 points into. Thus, only one buffer can have an overlay arrow at any
926 @c !!! overlay-arrow-position: but the overlay string may remain in the display
927 @c of some other buffer until an update is required. This should be fixed
931 You can do a similar job by creating an overlay with a
932 @code{before-string} property. @xref{Overlay Properties}.
934 @node Temporary Displays
935 @section Temporary Displays
937 Temporary displays are used by Lisp programs to put output into a
938 buffer and then present it to the user for perusal rather than for
939 editing. Many help commands use this feature.
941 @defspec with-output-to-temp-buffer buffer-name forms@dots{}
942 This function executes @var{forms} while arranging to insert any output
943 they print into the buffer named @var{buffer-name}, which is first
944 created if necessary, and put into Help mode. Finally, the buffer is
945 displayed in some window, but not selected.
947 If the @var{forms} do not change the major mode in the output buffer,
948 so that it is still Help mode at the end of their execution, then
949 @code{with-output-to-temp-buffer} makes this buffer read-only at the
950 end, and also scans it for function and variable names to make them
951 into clickable cross-references. @xref{Docstring hyperlinks, , Tips
952 for Documentation Strings}, in particular the item on hyperlinks in
953 documentation strings, for more details.
955 The string @var{buffer-name} specifies the temporary buffer, which
956 need not already exist. The argument must be a string, not a buffer.
957 The buffer is erased initially (with no questions asked), and it is
958 marked as unmodified after @code{with-output-to-temp-buffer} exits.
960 @code{with-output-to-temp-buffer} binds @code{standard-output} to the
961 temporary buffer, then it evaluates the forms in @var{forms}. Output
962 using the Lisp output functions within @var{forms} goes by default to
963 that buffer (but screen display and messages in the echo area, although
964 they are ``output'' in the general sense of the word, are not affected).
965 @xref{Output Functions}.
967 Several hooks are available for customizing the behavior
968 of this construct; they are listed below.
970 The value of the last form in @var{forms} is returned.
974 ---------- Buffer: foo ----------
975 This is the contents of foo.
976 ---------- Buffer: foo ----------
980 (with-output-to-temp-buffer "foo"
982 (print standard-output))
983 @result{} #<buffer foo>
985 ---------- Buffer: foo ----------
990 ---------- Buffer: foo ----------
995 @defvar temp-buffer-show-function
996 If this variable is non-@code{nil}, @code{with-output-to-temp-buffer}
997 calls it as a function to do the job of displaying a help buffer. The
998 function gets one argument, which is the buffer it should display.
1000 It is a good idea for this function to run @code{temp-buffer-show-hook}
1001 just as @code{with-output-to-temp-buffer} normally would, inside of
1002 @code{save-selected-window} and with the chosen window and buffer
1006 @defvar temp-buffer-setup-hook
1007 @tindex temp-buffer-setup-hook
1008 This normal hook is run by @code{with-output-to-temp-buffer} before
1009 evaluating @var{body}. When the hook runs, the temporary buffer is
1010 current. This hook is normally set up with a function to put the
1011 buffer in Help mode.
1014 @defvar temp-buffer-show-hook
1015 This normal hook is run by @code{with-output-to-temp-buffer} after
1016 displaying the temporary buffer. When the hook runs, the temporary buffer
1017 is current, and the window it was displayed in is selected. This hook
1018 is normally set up with a function to make the buffer read only, and
1019 find function names and variable names in it, provided the major mode
1023 @defun momentary-string-display string position &optional char message
1024 This function momentarily displays @var{string} in the current buffer at
1025 @var{position}. It has no effect on the undo list or on the buffer's
1026 modification status.
1028 The momentary display remains until the next input event. If the next
1029 input event is @var{char}, @code{momentary-string-display} ignores it
1030 and returns. Otherwise, that event remains buffered for subsequent use
1031 as input. Thus, typing @var{char} will simply remove the string from
1032 the display, while typing (say) @kbd{C-f} will remove the string from
1033 the display and later (presumably) move point forward. The argument
1034 @var{char} is a space by default.
1036 The return value of @code{momentary-string-display} is not meaningful.
1038 If the string @var{string} does not contain control characters, you can
1039 do the same job in a more general way by creating (and then subsequently
1040 deleting) an overlay with a @code{before-string} property.
1041 @xref{Overlay Properties}.
1043 If @var{message} is non-@code{nil}, it is displayed in the echo area
1044 while @var{string} is displayed in the buffer. If it is @code{nil}, a
1045 default message says to type @var{char} to continue.
1047 In this example, point is initially located at the beginning of the
1052 ---------- Buffer: foo ----------
1053 This is the contents of foo.
1054 @point{}Second line.
1055 ---------- Buffer: foo ----------
1059 (momentary-string-display
1060 "**** Important Message! ****"
1062 "Type RET when done reading")
1067 ---------- Buffer: foo ----------
1068 This is the contents of foo.
1069 **** Important Message! ****Second line.
1070 ---------- Buffer: foo ----------
1072 ---------- Echo Area ----------
1073 Type RET when done reading
1074 ---------- Echo Area ----------
1083 You can use @dfn{overlays} to alter the appearance of a buffer's text on
1084 the screen, for the sake of presentation features. An overlay is an
1085 object that belongs to a particular buffer, and has a specified
1086 beginning and end. It also has properties that you can examine and set;
1087 these affect the display of the text within the overlay.
1089 An overlays uses markers to record its beginning and end; thus,
1090 editing the text of the buffer adjusts the beginning and end of each
1091 overlay so that it stays with the text. When you create the overlay,
1092 you can specify whether text inserted at the beginning should be
1093 inside the overlay or outside, and likewise for the end of the overlay.
1096 * Overlay Properties:: How to read and set properties.
1097 What properties do to the screen display.
1098 * Managing Overlays:: Creating and moving overlays.
1099 * Finding Overlays:: Searching for overlays.
1102 @node Overlay Properties
1103 @subsection Overlay Properties
1105 Overlay properties are like text properties in that the properties that
1106 alter how a character is displayed can come from either source. But in
1107 most respects they are different. Text properties are considered a part
1108 of the text; overlays are specifically considered not to be part of the
1109 text. Thus, copying text between various buffers and strings preserves
1110 text properties, but does not try to preserve overlays. Changing a
1111 buffer's text properties marks the buffer as modified, while moving an
1112 overlay or changing its properties does not. Unlike text property
1113 changes, overlay changes are not recorded in the buffer's undo list.
1114 @xref{Text Properties}, for comparison.
1116 These functions are used for reading and writing the properties of an
1119 @defun overlay-get overlay prop
1120 This function returns the value of property @var{prop} recorded in
1121 @var{overlay}, if any. If @var{overlay} does not record any value for
1122 that property, but it does have a @code{category} property which is a
1123 symbol, that symbol's @var{prop} property is used. Otherwise, the value
1127 @defun overlay-put overlay prop value
1128 This function sets the value of property @var{prop} recorded in
1129 @var{overlay} to @var{value}. It returns @var{value}.
1132 @defun overlay-properties overlay
1133 This returns a copy of the property list of @var{overlay}.
1136 See also the function @code{get-char-property} which checks both
1137 overlay properties and text properties for a given character.
1138 @xref{Examining Properties}.
1140 Many overlay properties have special meanings; here is a table
1145 @kindex priority @r{(overlay property)}
1146 This property's value (which should be a nonnegative integer number)
1147 determines the priority of the overlay. The priority matters when two
1148 or more overlays cover the same character and both specify the same
1149 property; the one whose @code{priority} value is larger takes priority
1150 over the other. For the @code{face} property, the higher priority
1151 value does not completely replace the other; instead, its face
1152 attributes override the face attributes of the lower priority
1153 @code{face} property.
1155 Currently, all overlays take priority over text properties. Please
1156 avoid using negative priority values, as we have not yet decided just
1157 what they should mean.
1160 @kindex window @r{(overlay property)}
1161 If the @code{window} property is non-@code{nil}, then the overlay
1162 applies only on that window.
1165 @kindex category @r{(overlay property)}
1166 If an overlay has a @code{category} property, we call it the
1167 @dfn{category} of the overlay. It should be a symbol. The properties
1168 of the symbol serve as defaults for the properties of the overlay.
1171 @kindex face @r{(overlay property)}
1172 This property controls the way text is displayed---for example, which
1173 font and which colors. @xref{Faces}, for more information.
1175 In the simplest case, the value is a face name. It can also be a list;
1176 then each element can be any of these possibilities:
1180 A face name (a symbol or string).
1183 Starting in Emacs 21, a property list of face attributes. This has the
1184 form (@var{keyword} @var{value} @dots{}), where each @var{keyword} is a
1185 face attribute name and @var{value} is a meaningful value for that
1186 attribute. With this feature, you do not need to create a face each
1187 time you want to specify a particular attribute for certain text.
1188 @xref{Face Attributes}.
1191 A cons cell of the form @code{(foreground-color . @var{color-name})} or
1192 @code{(background-color . @var{color-name})}. These elements specify
1193 just the foreground color or just the background color.
1195 @code{(foreground-color . @var{color-name})} is equivalent to
1196 @code{(:foreground @var{color-name})}, and likewise for the background.
1200 @kindex mouse-face @r{(overlay property)}
1201 This property is used instead of @code{face} when the mouse is within
1202 the range of the overlay.
1205 @kindex display @r{(overlay property)}
1206 This property activates various features that change the
1207 way text is displayed. For example, it can make text appear taller
1208 or shorter, higher or lower, wider or narrower, or replaced with an image.
1209 @xref{Display Property}.
1212 @kindex help-echo @r{(overlay property)}
1213 If an overlay has a @code{help-echo} property, then when you move the
1214 mouse onto the text in the overlay, Emacs displays a help string in the
1215 echo area, or in the tooltip window. For details see @ref{Text
1218 @item modification-hooks
1219 @kindex modification-hooks @r{(overlay property)}
1220 This property's value is a list of functions to be called if any
1221 character within the overlay is changed or if text is inserted strictly
1224 The hook functions are called both before and after each change.
1225 If the functions save the information they receive, and compare notes
1226 between calls, they can determine exactly what change has been made
1229 When called before a change, each function receives four arguments: the
1230 overlay, @code{nil}, and the beginning and end of the text range to be
1233 When called after a change, each function receives five arguments: the
1234 overlay, @code{t}, the beginning and end of the text range just
1235 modified, and the length of the pre-change text replaced by that range.
1236 (For an insertion, the pre-change length is zero; for a deletion, that
1237 length is the number of characters deleted, and the post-change
1238 beginning and end are equal.)
1240 @item insert-in-front-hooks
1241 @kindex insert-in-front-hooks @r{(overlay property)}
1242 This property's value is a list of functions to be called before and
1243 after inserting text right at the beginning of the overlay. The calling
1244 conventions are the same as for the @code{modification-hooks} functions.
1246 @item insert-behind-hooks
1247 @kindex insert-behind-hooks @r{(overlay property)}
1248 This property's value is a list of functions to be called before and
1249 after inserting text right at the end of the overlay. The calling
1250 conventions are the same as for the @code{modification-hooks} functions.
1253 @kindex invisible @r{(overlay property)}
1254 The @code{invisible} property can make the text in the overlay
1255 invisible, which means that it does not appear on the screen.
1256 @xref{Invisible Text}, for details.
1259 @kindex intangible @r{(overlay property)}
1260 The @code{intangible} property on an overlay works just like the
1261 @code{intangible} text property. @xref{Special Properties}, for details.
1263 @item isearch-open-invisible
1264 This property tells incremental search how to make an invisible overlay
1265 visible, permanently, if the final match overlaps it. @xref{Invisible
1268 @item isearch-open-invisible-temporary
1269 This property tells incremental search how to make an invisible overlay
1270 visible, temporarily, during the search. @xref{Invisible Text}.
1273 @kindex before-string @r{(overlay property)}
1274 This property's value is a string to add to the display at the beginning
1275 of the overlay. The string does not appear in the buffer in any
1276 sense---only on the screen.
1279 @kindex after-string @r{(overlay property)}
1280 This property's value is a string to add to the display at the end of
1281 the overlay. The string does not appear in the buffer in any
1282 sense---only on the screen.
1285 @kindex evaporate @r{(overlay property)}
1286 If this property is non-@code{nil}, the overlay is deleted automatically
1287 if it becomes empty (i.e., if its length becomes zero). If you give
1288 an empty overlay a non-@code{nil} @code{evaporate} property, that deletes
1292 @cindex keymap of character (and overlays)
1293 @kindex local-map @r{(overlay property)}
1294 If this property is non-@code{nil}, it specifies a keymap for a portion
1295 of the text. The property's value replaces the buffer's local map, when
1296 the character after point is within the overlay. @xref{Active Keymaps}.
1299 @kindex keymap @r{(overlay property)}
1300 The @code{keymap} property is similar to @code{local-map} but overrides the
1301 buffer's local map (and the map specified by the @code{local-map}
1302 property) rather than replacing it.
1305 @node Managing Overlays
1306 @subsection Managing Overlays
1308 This section describes the functions to create, delete and move
1309 overlays, and to examine their contents.
1311 @defun overlayp object
1312 This function returns @code{t} if @var{object} is an overlay.
1315 @defun make-overlay start end &optional buffer front-advance rear-advance
1316 This function creates and returns an overlay that belongs to
1317 @var{buffer} and ranges from @var{start} to @var{end}. Both @var{start}
1318 and @var{end} must specify buffer positions; they may be integers or
1319 markers. If @var{buffer} is omitted, the overlay is created in the
1322 The arguments @var{front-advance} and @var{rear-advance} specify the
1323 insertion type for the start of the overlay and for the end of the
1324 overlay, respectively. @xref{Marker Insertion Types}. If
1325 @var{front-advance} is non-@code{nil}, text inserted at the beginning
1326 of the overlay is excluded from the overlay. If @var{read-advance} is
1327 non-@code{nil}, text inserted at the beginning of the overlay is
1328 included in the overlay.
1331 @defun overlay-start overlay
1332 This function returns the position at which @var{overlay} starts,
1336 @defun overlay-end overlay
1337 This function returns the position at which @var{overlay} ends,
1341 @defun overlay-buffer overlay
1342 This function returns the buffer that @var{overlay} belongs to. It
1343 returns @code{nil}, if @var{overlay} has been deleted.
1346 @defun delete-overlay overlay
1347 This function deletes @var{overlay}. The overlay continues to exist as
1348 a Lisp object, and its property list is unchanged, but it ceases to be
1349 attached to the buffer it belonged to, and ceases to have any effect on
1352 A deleted overlay is not permanently disconnected. You can give it a
1353 position in a buffer again by calling @code{move-overlay}.
1356 @defun move-overlay overlay start end &optional buffer
1357 This function moves @var{overlay} to @var{buffer}, and places its bounds
1358 at @var{start} and @var{end}. Both arguments @var{start} and @var{end}
1359 must specify buffer positions; they may be integers or markers.
1361 If @var{buffer} is omitted, @var{overlay} stays in the same buffer it
1362 was already associated with; if @var{overlay} was deleted, it goes into
1365 The return value is @var{overlay}.
1367 This is the only valid way to change the endpoints of an overlay. Do
1368 not try modifying the markers in the overlay by hand, as that fails to
1369 update other vital data structures and can cause some overlays to be
1373 Here are some examples:
1376 ;; @r{Create an overlay.}
1377 (setq foo (make-overlay 1 10))
1378 @result{} #<overlay from 1 to 10 in display.texi>
1383 (overlay-buffer foo)
1384 @result{} #<buffer display.texi>
1385 ;; @r{Give it a property we can check later.}
1386 (overlay-put foo 'happy t)
1388 ;; @r{Verify the property is present.}
1389 (overlay-get foo 'happy)
1391 ;; @r{Move the overlay.}
1392 (move-overlay foo 5 20)
1393 @result{} #<overlay from 5 to 20 in display.texi>
1398 ;; @r{Delete the overlay.}
1399 (delete-overlay foo)
1401 ;; @r{Verify it is deleted.}
1403 @result{} #<overlay in no buffer>
1404 ;; @r{A deleted overlay has no position.}
1409 (overlay-buffer foo)
1411 ;; @r{Undelete the overlay.}
1412 (move-overlay foo 1 20)
1413 @result{} #<overlay from 1 to 20 in display.texi>
1414 ;; @r{Verify the results.}
1419 (overlay-buffer foo)
1420 @result{} #<buffer display.texi>
1421 ;; @r{Moving and deleting the overlay does not change its properties.}
1422 (overlay-get foo 'happy)
1426 @node Finding Overlays
1427 @subsection Searching for Overlays
1429 @defun overlays-at pos
1430 This function returns a list of all the overlays that cover the
1431 character at position @var{pos} in the current buffer. The list is in
1432 no particular order. An overlay contains position @var{pos} if it
1433 begins at or before @var{pos}, and ends after @var{pos}.
1435 To illustrate usage, here is a Lisp function that returns a list of the
1436 overlays that specify property @var{prop} for the character at point:
1439 (defun find-overlays-specifying (prop)
1440 (let ((overlays (overlays-at (point)))
1443 (let ((overlay (car overlays)))
1444 (if (overlay-get overlay prop)
1445 (setq found (cons overlay found))))
1446 (setq overlays (cdr overlays)))
1451 @defun overlays-in beg end
1452 This function returns a list of the overlays that overlap the region
1453 @var{beg} through @var{end}. ``Overlap'' means that at least one
1454 character is contained within the overlay and also contained within the
1455 specified region; however, empty overlays are included in the result if
1456 they are located at @var{beg}, or strictly between @var{beg} and @var{end}.
1459 @defun next-overlay-change pos
1460 This function returns the buffer position of the next beginning or end
1461 of an overlay, after @var{pos}.
1464 @defun previous-overlay-change pos
1465 This function returns the buffer position of the previous beginning or
1466 end of an overlay, before @var{pos}.
1469 Here's an easy way to use @code{next-overlay-change} to search for the
1470 next character which gets a non-@code{nil} @code{happy} property from
1471 either its overlays or its text properties (@pxref{Property Search}):
1474 (defun find-overlay-prop (prop)
1476 (while (and (not (eobp))
1477 (not (get-char-property (point) 'happy)))
1478 (goto-char (min (next-overlay-change (point))
1479 (next-single-property-change (point) 'happy))))
1486 Since not all characters have the same width, these functions let you
1487 check the width of a character. @xref{Primitive Indent}, and
1488 @ref{Screen Lines}, for related functions.
1490 @defun char-width char
1491 This function returns the width in columns of the character @var{char},
1492 if it were displayed in the current buffer and the selected window.
1495 @defun string-width string
1496 This function returns the width in columns of the string @var{string},
1497 if it were displayed in the current buffer and the selected window.
1500 @defun truncate-string-to-width string width &optional start-column padding
1501 This function returns the part of @var{string} that fits within
1502 @var{width} columns, as a new string.
1504 If @var{string} does not reach @var{width}, then the result ends where
1505 @var{string} ends. If one multi-column character in @var{string}
1506 extends across the column @var{width}, that character is not included in
1507 the result. Thus, the result can fall short of @var{width} but cannot
1510 The optional argument @var{start-column} specifies the starting column.
1511 If this is non-@code{nil}, then the first @var{start-column} columns of
1512 the string are omitted from the value. If one multi-column character in
1513 @var{string} extends across the column @var{start-column}, that
1514 character is not included.
1516 The optional argument @var{padding}, if non-@code{nil}, is a padding
1517 character added at the beginning and end of the result string, to extend
1518 it to exactly @var{width} columns. The padding character is used at the
1519 end of the result if it falls short of @var{width}. It is also used at
1520 the beginning of the result if one multi-column character in
1521 @var{string} extends across the column @var{start-column}.
1524 (truncate-string-to-width "\tab\t" 12 4)
1526 (truncate-string-to-width "\tab\t" 12 4 ?\s)
1532 @section Line Height
1535 The total height of each display line consists of the height of the
1536 contents of the line, and additional vertical line spacing below the
1539 The height of the line contents is normally determined from the
1540 maximum height of any character or image on that display line,
1541 including the final newline if there is one. (A line that is
1542 continued doesn't include a final newline.) In the most common case,
1543 the line height equals the height of the default frame font.
1545 There are several ways to explicitly control or change the line
1546 height, either by specifying an absolute height for the display line,
1547 or by adding additional vertical space below one or all lines.
1549 @kindex line-height @r{(text property)}
1550 A newline can have a @code{line-height} text or overlay property
1551 that controls the total height of the display line ending in that
1554 If the property value is a list @code{(@var{height} @var{total})},
1555 then @var{height} is used as the actual property value for the
1556 @code{line-height}, and @var{total} specifies the total displayed
1557 height of the line, so the line spacing added below the line equals
1558 the @var{total} height minus the actual line height. In this case,
1559 the other ways to specify the line spacing are ignored.
1561 If the property value is @code{t}, the displayed height of the
1562 line is exactly what its contents demand; no line-spacing is added.
1563 This case is useful for tiling small images or image slices without
1564 adding blank areas between the images.
1566 If the property value is not @code{t}, it is a height spec. A height
1567 spec stands for a numeric height value; this heigh spec specifies the
1568 actual line height, @var{line-height}. There are several ways to
1569 write a height spec; here's how each of them translates into a numeric
1574 If the height spec is a positive integer, the height value is that integer.
1576 If the height spec is a float, @var{float}, the numeric height value
1577 is @var{float} times the frame's default line height.
1578 @item (@var{face} . @var{ratio})
1579 If the height spec is a cons of the format shown, the numeric height
1580 is @var{ratio} times the height of face @var{face}. @var{ratio} can
1581 be any type of number, or @code{nil} which means a ratio of 1.
1582 If @var{face} is @code{t}, it refers to the current face.
1583 @item (@code{nil} . @var{ratio})
1584 If the height spec is a cons of the format shown, the numeric height
1585 is @var{ratio} times the height of the contents of the line.
1588 Thus, any valid non-@code{t} property value specifies a height in pixels,
1589 @var{line-height}, one way or another. If the line contents' height
1590 is less than @var{line-height}, Emacs adds extra vertical space above
1591 the line to achieve the total height @var{line-height}. Otherwise,
1592 @var{line-height} has no effect.
1594 If you don't specify the @code{line-height} propery, the line's
1595 height consists of the contents' height plus the line spacing.
1596 There are several ways to specify the line spacing for different
1597 parts of Emacs text.
1599 @vindex default-line-spacing
1600 You can specify the line spacing for all lines in a frame with the
1601 @code{line-spacing} frame parameter, @xref{Window Frame Parameters}.
1602 However, if the variable @code{default-line-spacing} is
1603 non-@code{nil}, it overrides the frame's @code{line-spacing}
1604 parameter. An integer value specifies the number of pixels put below
1605 lines on window systems. A floating point number specifies the
1606 spacing relative to the frame's default line height.
1608 @vindex line-spacing
1609 You can specify the line spacing for all lines in a buffer via the
1610 buffer-local @code{line-spacing} variable. An integer value specifies
1611 the number of pixels put below lines on window systems. A floating
1612 point number specifies the spacing relative to the default frame line
1613 height. This overrides line spacings specified for the frame.
1615 @kindex line-spacing @r{(text property)}
1616 Finally, a newline can have a @code{line-spacing} text or overlay
1617 property that controls the height of the display line ending with that
1618 newline. The property value overrides the default frame line spacing
1619 and the buffer local @code{line-spacing} variable.
1621 One way or another, these mechanisms specify a Lisp value for the
1622 spacing of each line. The value is a height spec, and it translates
1623 into a Lisp value as described above. However, in this case the
1624 numeric height value specifies the line spacing, rather than the line
1631 A @dfn{face} is a named collection of graphical attributes: font
1632 family, foreground color, background color, optional underlining, and
1633 many others. Faces are used in Emacs to control the style of display of
1634 particular parts of the text or the frame.
1637 Each face has its own @dfn{face number}, which distinguishes faces at
1638 low levels within Emacs. However, for most purposes, you refer to
1639 faces in Lisp programs by their names.
1642 This function returns @code{t} if @var{object} is a face name symbol (or
1643 if it is a vector of the kind used internally to record face data). It
1644 returns @code{nil} otherwise.
1647 Each face name is meaningful for all frames, and by default it has the
1648 same meaning in all frames. But you can arrange to give a particular
1649 face name a special meaning in one frame if you wish.
1652 * Standard Faces:: The faces Emacs normally comes with.
1653 * Defining Faces:: How to define a face with @code{defface}.
1654 * Face Attributes:: What is in a face?
1655 * Attribute Functions:: Functions to examine and set face attributes.
1656 * Displaying Faces:: How Emacs combines the faces specified for a character.
1657 * Font Selection:: Finding the best available font for a face.
1658 * Face Functions:: How to define and examine faces.
1659 * Auto Faces:: Hook for automatic face assignment.
1660 * Font Lookup:: Looking up the names of available fonts
1661 and information about them.
1662 * Fontsets:: A fontset is a collection of fonts
1663 that handle a range of character sets.
1666 @node Standard Faces
1667 @subsection Standard Faces
1669 This table lists all the standard faces and their uses. Most of them
1670 are used for displaying certain parts of the frames or certain kinds of
1671 text; you can control how those places look by customizing these faces.
1675 @kindex default @r{(face name)}
1676 This face is used for ordinary text.
1679 @kindex mode-line @r{(face name)}
1680 This face is used for the mode line of the selected window, and for
1681 menu bars when toolkit menus are not used---but only if
1682 @code{mode-line-inverse-video} is non-@code{nil}.
1685 @kindex modeline @r{(face name)}
1686 This is an alias for the @code{mode-line} face, for compatibility with
1689 @item mode-line-inactive
1690 @kindex mode-line-inactive @r{(face name)}
1691 This face is used for mode lines of non-selected windows.
1692 This face inherits from @code{mode-line}, so changes
1693 in that face affect all windows.
1696 @kindex header-line @r{(face name)}
1697 This face is used for the header lines of windows that have them.
1700 This face controls the display of menus, both their colors and their
1701 font. (This works only on certain systems.)
1704 @kindex fringe @r{(face name)}
1705 This face controls the default colors of window fringes, the thin areas on
1706 either side that are used to display continuation and truncation glyphs.
1708 @item minibuffer-prompt
1709 @kindex minibuffer-prompt @r{(face name)}
1710 @vindex minibuffer-prompt-properties
1711 This face is used for the text of minibuffer prompts. By default,
1712 Emacs automatically adds this face to the value of
1713 @code{minibuffer-prompt-properties}, which is a list of text
1714 properties used to display the prompt text.
1717 @kindex scroll-bar @r{(face name)}
1718 This face controls the colors for display of scroll bars.
1721 @kindex tool-bar @r{(face name)}
1722 This face is used for display of the tool bar, if any.
1725 @kindex region @r{(face name)}
1726 This face is used for highlighting the region in Transient Mark mode.
1728 @item secondary-selection
1729 @kindex secondary-selection @r{(face name)}
1730 This face is used to show any secondary selection you have made.
1733 @kindex highlight @r{(face name)}
1734 This face is meant to be used for highlighting for various purposes.
1736 @item trailing-whitespace
1737 @kindex trailing-whitespace @r{(face name)}
1738 This face is used to display excess whitespace at the end of a line,
1739 if @code{show-trailing-whitespace} is non-@code{nil}.
1742 In contrast, these faces are provided to change the appearance of text
1743 in specific ways. You can use them on specific text, when you want
1744 the effects they produce.
1748 @kindex bold @r{(face name)}
1749 This face uses a bold font, if possible. It uses the bold variant of
1750 the frame's font, if it has one. It's up to you to choose a default
1751 font that has a bold variant, if you want to use one.
1754 @kindex italic @r{(face name)}
1755 This face uses the italic variant of the frame's font, if it has one.
1758 @kindex bold-italic @r{(face name)}
1759 This face uses the bold italic variant of the frame's font, if it has
1763 @kindex underline @r{(face name)}
1764 This face underlines text.
1767 @kindex fixed-pitch @r{(face name)}
1768 This face forces use of a particular fixed-width font.
1770 @item variable-pitch
1771 @kindex variable-pitch @r{(face name)}
1772 This face forces use of a particular variable-width font. It's
1773 reasonable to customize this to use a different variable-width font, if
1774 you like, but you should not make it a fixed-width font.
1777 @defvar show-trailing-whitespace
1778 @tindex show-trailing-whitespace
1779 If this variable is non-@code{nil}, Emacs uses the
1780 @code{trailing-whitespace} face to display any spaces and tabs at the
1784 @node Defining Faces
1785 @subsection Defining Faces
1787 The way to define a new face is with @code{defface}. This creates a
1788 kind of customization item (@pxref{Customization}) which the user can
1789 customize using the Customization buffer (@pxref{Easy Customization,,,
1790 emacs, The GNU Emacs Manual}).
1792 @defmac defface face spec doc [keyword value]...
1793 This declares @var{face} as a customizable face that defaults according
1794 to @var{spec}. You should not quote the symbol @var{face}. The
1795 argument @var{doc} specifies the face documentation. The keywords you
1796 can use in @code{defface} are the same ones that are meaningful in both
1797 @code{defgroup} and @code{defcustom} (@pxref{Common Keywords}).
1799 When @code{defface} executes, it defines the face according to
1800 @var{spec}, then uses any customizations that were read from the
1801 init file (@pxref{Init File}) to override that specification.
1803 The purpose of @var{spec} is to specify how the face should appear on
1804 different kinds of terminals. It should be an alist whose elements have
1805 the form @code{(@var{display} @var{atts})}. Each element's @sc{car},
1806 @var{display}, specifies a class of terminals. The element's second element,
1807 @var{atts}, is a list of face attributes and their values; it specifies
1808 what the face should look like on that kind of terminal. The possible
1809 attributes are defined in the value of @code{custom-face-attributes}.
1811 The @var{display} part of an element of @var{spec} determines which
1812 frames the element applies to. If more than one element of @var{spec}
1813 matches a given frame, the first matching element is the only one used
1814 for that frame. There are two possibilities for @var{display}:
1818 This element of @var{spec} matches all frames. Therefore, any
1819 subsequent elements of @var{spec} are never used. Normally
1820 @code{t} is used in the last (or only) element of @var{spec}.
1823 If @var{display} is a list, each element should have the form
1824 @code{(@var{characteristic} @var{value}@dots{})}. Here
1825 @var{characteristic} specifies a way of classifying frames, and the
1826 @var{value}s are possible classifications which @var{display} should
1827 apply to. Here are the possible values of @var{characteristic}:
1831 The kind of window system the frame uses---either @code{graphic} (any
1832 graphics-capable display), @code{x}, @code{pc} (for the MS-DOS console),
1833 @code{w32} (for MS Windows 9X/NT), or @code{tty} (a non-graphics-capable
1837 What kinds of colors the frame supports---either @code{color},
1838 @code{grayscale}, or @code{mono}.
1841 The kind of background---either @code{light} or @code{dark}.
1844 An integer that represents the minimum number of colors the frame should
1845 support, it is compared with the result of @code{display-color-cells}.
1848 Whether or not the frame can display the face attributes given in
1849 @var{value}@dots{} (@pxref{Face Attributes}). See the documentation
1850 for the function @code{display-supports-face-attributes-p} for more
1851 information on exactly how this testing is done. @xref{Display Face
1855 If an element of @var{display} specifies more than one @var{value} for a
1856 given @var{characteristic}, any of those values is acceptable. If
1857 @var{display} has more than one element, each element should specify a
1858 different @var{characteristic}; then @emph{each} characteristic of the
1859 frame must match one of the @var{value}s specified for it in
1864 Here's how the standard face @code{region} is defined:
1868 '((((class color) (min-colors 88) (background dark))
1869 :background "blue3")
1871 (((class color) (min-colors 88) (background light))
1872 :background "lightgoldenrod2")
1873 (((class color) (min-colors 16) (background dark))
1874 :background "blue3")
1875 (((class color) (min-colors 16) (background light))
1876 :background "lightgoldenrod2")
1877 (((class color) (min-colors 8))
1878 :background "blue" :foreground "white")
1879 (((type tty) (class mono))
1881 (t :background "gray"))
1883 "Basic face for highlighting the region."
1884 :group 'basic-faces)
1888 Internally, @code{defface} uses the symbol property
1889 @code{face-defface-spec} to record the face attributes specified in
1890 @code{defface}, @code{saved-face} for the attributes saved by the user
1891 with the customization buffer, and @code{face-documentation} for the
1892 documentation string.
1894 @defopt frame-background-mode
1895 This option, if non-@code{nil}, specifies the background type to use for
1896 interpreting face definitions. If it is @code{dark}, then Emacs treats
1897 all frames as if they had a dark background, regardless of their actual
1898 background colors. If it is @code{light}, then Emacs treats all frames
1899 as if they had a light background.
1902 @node Face Attributes
1903 @subsection Face Attributes
1904 @cindex face attributes
1906 The effect of using a face is determined by a fixed set of @dfn{face
1907 attributes}. This table lists all the face attributes, and what they
1908 mean. Note that in general, more than one face can be specified for a
1909 given piece of text; when that happens, the attributes of all the faces
1910 are merged to specify how to display the text. @xref{Displaying Faces}.
1912 In Emacs 21, any attribute in a face can have the value
1913 @code{unspecified}. This means the face doesn't specify that attribute.
1914 In face merging, when the first face fails to specify a particular
1915 attribute, that means the next face gets a chance. However, the
1916 @code{default} face must specify all attributes.
1918 Some of these font attributes are meaningful only on certain kinds of
1919 displays---if your display cannot handle a certain attribute, the
1920 attribute is ignored. (The attributes @code{:family}, @code{:width},
1921 @code{:height}, @code{:weight}, and @code{:slant} correspond to parts of
1922 an X Logical Font Descriptor.)
1926 Font family name, or fontset name (@pxref{Fontsets}). If you specify a
1927 font family name, the wild-card characters @samp{*} and @samp{?} are
1931 Relative proportionate width, also known as the character set width or
1932 set width. This should be one of the symbols @code{ultra-condensed},
1933 @code{extra-condensed}, @code{condensed}, @code{semi-condensed},
1934 @code{normal}, @code{semi-expanded}, @code{expanded},
1935 @code{extra-expanded}, or @code{ultra-expanded}.
1938 Either the font height, an integer in units of 1/10 point, a floating
1939 point number specifying the amount by which to scale the height of any
1940 underlying face, or a function, which is called with the old height
1941 (from the underlying face), and should return the new height.
1944 Font weight---a symbol from this series (from most dense to most faint):
1945 @code{ultra-bold}, @code{extra-bold}, @code{bold}, @code{semi-bold},
1946 @code{normal}, @code{semi-light}, @code{light}, @code{extra-light},
1947 or @code{ultra-light}.
1949 On a text-only terminal, any weight greater than normal is displayed as
1950 extra bright, and any weight less than normal is displayed as
1951 half-bright (provided the terminal supports the feature).
1954 Font slant---one of the symbols @code{italic}, @code{oblique}, @code{normal},
1955 @code{reverse-italic}, or @code{reverse-oblique}.
1957 On a text-only terminal, slanted text is displayed as half-bright, if
1958 the terminal supports the feature.
1961 Foreground color, a string. The value can be a system-defined color
1962 name, or a hexadecimal color specification of the form
1963 @samp{#@var{rr}@var{gg}@var{bb}}. (@samp{#000000} is black,
1964 @samp{#ff0000} is red, @samp{#00ff00} is green, @samp{#0000ff} is
1965 blue, and @samp{#ffffff} is white.)
1968 Background color, a string, like the foreground color.
1970 @item :inverse-video
1971 Whether or not characters should be displayed in inverse video. The
1972 value should be @code{t} (yes) or @code{nil} (no).
1975 The background stipple, a bitmap.
1977 The value can be a string; that should be the name of a file containing
1978 external-format X bitmap data. The file is found in the directories
1979 listed in the variable @code{x-bitmap-file-path}.
1981 Alternatively, the value can specify the bitmap directly, with a list
1982 of the form @code{(@var{width} @var{height} @var{data})}. Here,
1983 @var{width} and @var{height} specify the size in pixels, and
1984 @var{data} is a string containing the raw bits of the bitmap, row by
1985 row. Each row occupies @math{(@var{width} + 7) / 8} consecutive bytes
1986 in the string (which should be a unibyte string for best results).
1987 This means that each row always occupies at least one whole byte.
1989 If the value is @code{nil}, that means use no stipple pattern.
1991 Normally you do not need to set the stipple attribute, because it is
1992 used automatically to handle certain shades of gray.
1995 Whether or not characters should be underlined, and in what color. If
1996 the value is @code{t}, underlining uses the foreground color of the
1997 face. If the value is a string, underlining uses that color. The
1998 value @code{nil} means do not underline.
2001 Whether or not characters should be overlined, and in what color.
2002 The value is used like that of @code{:underline}.
2004 @item :strike-through
2005 Whether or not characters should be strike-through, and in what
2006 color. The value is used like that of @code{:underline}.
2009 The name of a face from which to inherit attributes, or a list of face
2010 names. Attributes from inherited faces are merged into the face like an
2011 underlying face would be, with higher priority than underlying faces.
2014 Whether or not a box should be drawn around characters, its color, the
2015 width of the box lines, and 3D appearance.
2018 Here are the possible values of the @code{:box} attribute, and what
2026 Draw a box with lines of width 1, in the foreground color.
2029 Draw a box with lines of width 1, in color @var{color}.
2031 @item @code{(:line-width @var{width} :color @var{color} :style @var{style})}
2032 This way you can explicitly specify all aspects of the box. The value
2033 @var{width} specifies the width of the lines to draw; it defaults to 1.
2035 The value @var{color} specifies the color to draw with. The default is
2036 the foreground color of the face for simple boxes, and the background
2037 color of the face for 3D boxes.
2039 The value @var{style} specifies whether to draw a 3D box. If it is
2040 @code{released-button}, the box looks like a 3D button that is not being
2041 pressed. If it is @code{pressed-button}, the box looks like a 3D button
2042 that is being pressed. If it is @code{nil} or omitted, a plain 2D box
2046 The attributes @code{:overline}, @code{:strike-through} and
2047 @code{:box} are new in Emacs 21. The attributes @code{:family},
2048 @code{:height}, @code{:width}, @code{:weight}, @code{:slant} are also
2049 new; previous versions used the following attributes, now semi-obsolete,
2050 to specify some of the same information:
2054 This attribute specifies the font name.
2057 A non-@code{nil} value specifies a bold font.
2060 A non-@code{nil} value specifies an italic font.
2063 For compatibility, you can still set these ``attributes'' in Emacs 21,
2064 even though they are not real face attributes. Here is what that does:
2068 You can specify an X font name as the ``value'' of this ``attribute'';
2069 that sets the @code{:family}, @code{:width}, @code{:height},
2070 @code{:weight}, and @code{:slant} attributes according to the font name.
2072 If the value is a pattern with wildcards, the first font that matches
2073 the pattern is used to set these attributes.
2076 A non-@code{nil} makes the face bold; @code{nil} makes it normal.
2077 This actually works by setting the @code{:weight} attribute.
2080 A non-@code{nil} makes the face italic; @code{nil} makes it normal.
2081 This actually works by setting the @code{:slant} attribute.
2084 @defvar x-bitmap-file-path
2085 This variable specifies a list of directories for searching
2086 for bitmap files, for the @code{:stipple} attribute.
2089 @defun bitmap-spec-p object
2090 This returns @code{t} if @var{object} is a valid bitmap specification,
2091 suitable for use with @code{:stipple} (see above). It returns
2092 @code{nil} otherwise.
2095 @node Attribute Functions
2096 @subsection Face Attribute Functions
2098 You can modify the attributes of an existing face with the following
2099 functions. If you specify @var{frame}, they affect just that frame;
2100 otherwise, they affect all frames as well as the defaults that apply to
2103 @tindex set-face-attribute
2104 @defun set-face-attribute face frame &rest arguments
2105 This function sets one or more attributes of face @var{face}
2106 for frame @var{frame}. If @var{frame} is @code{nil}, it sets
2107 the attribute for all frames, and the defaults for new frames.
2109 The extra arguments @var{arguments} specify the attributes to set, and
2110 the values for them. They should consist of alternating attribute names
2111 (such as @code{:family} or @code{:underline}) and corresponding values.
2115 (set-face-attribute 'foo nil
2122 sets the attributes @code{:width}, @code{:weight} and @code{:underline}
2123 to the corresponding values.
2126 @tindex face-attribute
2127 @defun face-attribute face attribute &optional frame inherit
2128 This returns the value of the @var{attribute} attribute of face
2129 @var{face} on @var{frame}. If @var{frame} is @code{nil},
2130 that means the selected frame (@pxref{Input Focus}).
2132 If @var{frame} is @code{t}, the value is the default for
2133 @var{face} for new frames.
2135 If @var{inherit} is @code{nil}, only attributes directly defined by
2136 @var{face} are considered, so the return value may be
2137 @code{unspecified}, or a relative value. If @var{inherit} is
2138 non-@code{nil}, @var{face}'s definition of @var{attribute} is merged
2139 with the faces specified by its @code{:inherit} attribute; however the
2140 return value may still be @code{unspecified} or relative. If
2141 @var{inherit} is a face or a list of faces, then the result is further
2142 merged with that face (or faces), until it becomes specified and
2145 To ensure that the return value is always specified and absolute, use
2146 a value of @code{default} for @var{inherit}; this will resolve any
2147 unspecified or relative values by merging with the @code{default} face
2148 (which is always completely specified).
2153 (face-attribute 'bold :weight)
2158 The functions above did not exist before Emacs 21. For compatibility
2159 with older Emacs versions, you can use the following functions to set
2160 and examine the face attributes which existed in those versions.
2162 @tindex face-attribute-relative-p
2163 @defun face-attribute-relative-p attribute value
2164 This function returns non-@code{nil} if @var{value}, when used as
2165 the value of the face attribute @var{attribute}, is relative (that is,
2166 if it modifies an underlying or inherited value of @var{attribute}).
2169 @tindex merge-face-attribute
2170 @defun merge-face-attribute attribute value1 value2
2171 If @var{value1} is a relative value for the face attribute
2172 @var{attribute}, returns it merged with the underlying value
2173 @var{value2}; otherwise, if @var{value1} is an absolute value for the
2174 face attribute @var{attribute}, returns @var{value1} unchanged.
2177 @defun set-face-foreground face color &optional frame
2178 @defunx set-face-background face color &optional frame
2179 These functions set the foreground (or background, respectively) color
2180 of face @var{face} to @var{color}. The argument @var{color} should be a
2181 string, the name of a color.
2183 Certain shades of gray are implemented by stipple patterns on
2184 black-and-white screens.
2187 @defun set-face-stipple face pattern &optional frame
2188 This function sets the background stipple pattern of face @var{face}
2189 to @var{pattern}. The argument @var{pattern} should be the name of a
2190 stipple pattern defined by the X server, or actual bitmap data
2191 (@pxref{Face Attributes}), or @code{nil} meaning don't use stipple.
2193 Normally there is no need to pay attention to stipple patterns, because
2194 they are used automatically to handle certain shades of gray.
2197 @defun set-face-font face font &optional frame
2198 This function sets the font of face @var{face}.
2200 In Emacs 21, this actually sets the attributes @code{:family},
2201 @code{:width}, @code{:height}, @code{:weight}, and @code{:slant}
2202 according to the font name @var{font}.
2204 In Emacs 20, this sets the font attribute. Once you set the font
2205 explicitly, the bold and italic attributes cease to have any effect,
2206 because the precise font that you specified is used.
2209 @defun set-face-bold-p face bold-p &optional frame
2210 This function specifies whether @var{face} should be bold. If
2211 @var{bold-p} is non-@code{nil}, that means yes; @code{nil} means no.
2213 In Emacs 21, this sets the @code{:weight} attribute.
2214 In Emacs 20, it sets the @code{:bold} attribute.
2217 @defun set-face-italic-p face italic-p &optional frame
2218 This function specifies whether @var{face} should be italic. If
2219 @var{italic-p} is non-@code{nil}, that means yes; @code{nil} means no.
2221 In Emacs 21, this sets the @code{:slant} attribute.
2222 In Emacs 20, it sets the @code{:italic} attribute.
2225 @defun set-face-underline-p face underline-p &optional frame
2226 This function sets the underline attribute of face @var{face}.
2227 Non-@code{nil} means do underline; @code{nil} means don't.
2230 @defun invert-face face &optional frame
2231 This function inverts the @code{:inverse-video} attribute of face
2232 @var{face}. If the attribute is @code{nil}, this function sets it to
2233 @code{t}, and vice versa.
2236 These functions examine the attributes of a face. If you don't
2237 specify @var{frame}, they refer to the default data for new frames.
2238 They return the symbol @code{unspecified} if the face doesn't define any
2239 value for that attribute.
2241 @defun face-foreground face &optional frame inherit
2242 @defunx face-background face &optional frame
2243 These functions return the foreground color (or background color,
2244 respectively) of face @var{face}, as a string.
2246 If @var{inherit} is @code{nil}, only a color directly defined by the face is
2247 returned. If @var{inherit} is non-@code{nil}, any faces specified by its
2248 @code{:inherit} attribute are considered as well, and if @var{inherit}
2249 is a face or a list of faces, then they are also considered, until a
2250 specified color is found. To ensure that the return value is always
2251 specified, use a value of @code{default} for @var{inherit}.
2254 @defun face-stipple face &optional frame inherit
2255 This function returns the name of the background stipple pattern of face
2256 @var{face}, or @code{nil} if it doesn't have one.
2258 If @var{inherit} is @code{nil}, only a stipple directly defined by the
2259 face is returned. If @var{inherit} is non-@code{nil}, any faces
2260 specified by its @code{:inherit} attribute are considered as well, and
2261 if @var{inherit} is a face or a list of faces, then they are also
2262 considered, until a specified stipple is found. To ensure that the
2263 return value is always specified, use a value of @code{default} for
2267 @defun face-font face &optional frame
2268 This function returns the name of the font of face @var{face}.
2271 @defun face-bold-p face &optional frame
2272 This function returns @code{t} if @var{face} is bold---that is, if it is
2273 bolder than normal. It returns @code{nil} otherwise.
2276 @defun face-italic-p face &optional frame
2277 This function returns @code{t} if @var{face} is italic or oblique,
2278 @code{nil} otherwise.
2281 @defun face-underline-p face &optional frame
2282 This function returns the @code{:underline} attribute of face @var{face}.
2285 @defun face-inverse-video-p face &optional frame
2286 This function returns the @code{:inverse-video} attribute of face @var{face}.
2289 @node Displaying Faces
2290 @subsection Displaying Faces
2292 Here are the ways to specify which faces to use for display of text:
2296 With defaults. The @code{default} face is used as the ultimate
2297 default for all text. (In Emacs 19 and 20, the @code{default}
2298 face is used only when no other face is specified.)
2300 For a mode line or header line, the face @code{modeline} or
2301 @code{header-line} is used just before @code{default}.
2304 With text properties. A character can have a @code{face} property; if
2305 so, the faces and face attributes specified there apply. @xref{Special
2308 If the character has a @code{mouse-face} property, that is used instead
2309 of the @code{face} property when the mouse is ``near enough'' to the
2313 With overlays. An overlay can have @code{face} and @code{mouse-face}
2314 properties too; they apply to all the text covered by the overlay.
2317 With a region that is active. In Transient Mark mode, the region is
2318 highlighted with the face @code{region} (@pxref{Standard Faces}).
2321 With special glyphs. Each glyph can specify a particular face
2322 number. @xref{Glyphs}.
2325 If these various sources together specify more than one face for a
2326 particular character, Emacs merges the attributes of the various faces
2327 specified. The attributes of the faces of special glyphs come first;
2328 then comes the face for region highlighting, if appropriate;
2329 then come attributes of faces from overlays, followed by those from text
2330 properties, and last the default face.
2332 When multiple overlays cover one character, an overlay with higher
2333 priority overrides those with lower priority. @xref{Overlays}.
2335 In Emacs 20, if an attribute such as the font or a color is not
2336 specified in any of the above ways, the frame's own font or color is
2337 used. In newer Emacs versions, this cannot happen, because the
2338 @code{default} face specifies all attributes---in fact, the frame's own
2339 font and colors are synonymous with those of the default face.
2341 @node Font Selection
2342 @subsection Font Selection
2344 @dfn{Selecting a font} means mapping the specified face attributes for
2345 a character to a font that is available on a particular display. The
2346 face attributes, as determined by face merging, specify most of the
2347 font choice, but not all. Part of the choice depends on what character
2350 If the face specifies a fontset name, that fontset determines a
2351 pattern for fonts of the given charset. If the face specifies a font
2352 family, a font pattern is constructed.
2354 Emacs tries to find an available font for the given face attributes
2355 and character's registry and encoding. If there is a font that matches
2356 exactly, it is used, of course. The hard case is when no available font
2357 exactly fits the specification. Then Emacs looks for one that is
2358 ``close''---one attribute at a time. You can specify the order to
2359 consider the attributes. In the case where a specified font family is
2360 not available, you can specify a set of mappings for alternatives to
2363 @defvar face-font-selection-order
2364 @tindex face-font-selection-order
2365 This variable specifies the order of importance of the face attributes
2366 @code{:width}, @code{:height}, @code{:weight}, and @code{:slant}. The
2367 value should be a list containing those four symbols, in order of
2368 decreasing importance.
2370 Font selection first finds the best available matches for the first
2371 attribute listed; then, among the fonts which are best in that way, it
2372 searches for the best matches in the second attribute, and so on.
2374 The attributes @code{:weight} and @code{:width} have symbolic values in
2375 a range centered around @code{normal}. Matches that are more extreme
2376 (farther from @code{normal}) are somewhat preferred to matches that are
2377 less extreme (closer to @code{normal}); this is designed to ensure that
2378 non-normal faces contrast with normal ones, whenever possible.
2380 The default is @code{(:width :height :weight :slant)}, which means first
2381 find the fonts closest to the specified @code{:width}, then---among the
2382 fonts with that width---find a best match for the specified font height,
2385 One example of a case where this variable makes a difference is when the
2386 default font has no italic equivalent. With the default ordering, the
2387 @code{italic} face will use a non-italic font that is similar to the
2388 default one. But if you put @code{:slant} before @code{:height}, the
2389 @code{italic} face will use an italic font, even if its height is not
2393 @defvar face-font-family-alternatives
2394 @tindex face-font-family-alternatives
2395 This variable lets you specify alternative font families to try, if a
2396 given family is specified and doesn't exist. Each element should have
2400 (@var{family} @var{alternate-families}@dots{})
2403 If @var{family} is specified but not available, Emacs will try the other
2404 families given in @var{alternate-families}, one by one, until it finds a
2405 family that does exist.
2408 @defvar face-font-registry-alternatives
2409 @tindex face-font-registry-alternatives
2410 This variable lets you specify alternative font registries to try, if a
2411 given registry is specified and doesn't exist. Each element should have
2415 (@var{registry} @var{alternate-registries}@dots{})
2418 If @var{registry} is specified but not available, Emacs will try the
2419 other registries given in @var{alternate-registries}, one by one,
2420 until it finds a registry that does exist.
2423 Emacs can make use of scalable fonts, but by default it does not use
2424 them, since the use of too many or too big scalable fonts can crash
2427 @defvar scalable-fonts-allowed
2428 @tindex scalable-fonts-allowed
2429 This variable controls which scalable fonts to use. A value of
2430 @code{nil}, the default, means do not use scalable fonts. @code{t}
2431 means to use any scalable font that seems appropriate for the text.
2433 Otherwise, the value must be a list of regular expressions. Then a
2434 scalable font is enabled for use if its name matches any regular
2435 expression in the list. For example,
2438 (setq scalable-fonts-allowed '("muleindian-2$"))
2442 allows the use of scalable fonts with registry @code{muleindian-2}.
2445 @defun clear-face-cache &optional unload-p
2446 @tindex clear-face-cache
2447 This function clears the face cache for all frames.
2448 If @var{unload-p} is non-@code{nil}, that means to unload
2449 all unused fonts as well.
2452 @defvar face-font-rescale-alist
2453 This variable specifies scaling for certain faces. Its value should
2454 be a list of elements of the form
2457 (@var{fontname-regexp} . @var{scale-factor})
2460 If @var{fontname-regexp} matches the font name that is about to be
2461 used, this says to choose a larger similar font according to the
2462 factor @var{scale-factor}. You would use this feature to normalize
2463 the font size if certain fonts are bigger or smaller than their
2464 nominal heights and widths would suggest.
2467 @node Face Functions
2468 @subsection Functions for Working with Faces
2470 Here are additional functions for creating and working with faces.
2472 @defun make-face name
2473 This function defines a new face named @var{name}, initially with all
2474 attributes @code{nil}. It does nothing if there is already a face named
2479 This function returns a list of all defined face names.
2482 @defun copy-face old-face new-name &optional frame new-frame
2483 This function defines the face @var{new-name} as a copy of the existing
2484 face named @var{old-face}. It creates the face @var{new-name} if that
2485 doesn't already exist.
2487 If the optional argument @var{frame} is given, this function applies
2488 only to that frame. Otherwise it applies to each frame individually,
2489 copying attributes from @var{old-face} in each frame to @var{new-face}
2492 If the optional argument @var{new-frame} is given, then @code{copy-face}
2493 copies the attributes of @var{old-face} in @var{frame} to @var{new-name}
2498 This function returns the face number of face @var{face}.
2501 @defun face-documentation face
2502 This function returns the documentation string of face @var{face}, or
2503 @code{nil} if none was specified for it.
2506 @defun face-equal face1 face2 &optional frame
2507 This returns @code{t} if the faces @var{face1} and @var{face2} have the
2508 same attributes for display.
2511 @defun face-differs-from-default-p face &optional frame
2512 This returns non-@code{nil} if the face @var{face} displays
2513 differently from the default face.
2517 @subsection Automatic Face Assignment
2518 @cindex automatic face assignment
2519 @cindex faces, automatic choice
2521 @cindex Font-Lock mode
2522 Starting with Emacs 21, a hook is available for automatically
2523 assigning faces to text in the buffer. This hook is used for part of
2524 the implementation of Font-Lock mode.
2526 @tindex fontification-functions
2527 @defvar fontification-functions
2528 This variable holds a list of functions that are called by Emacs
2529 redisplay as needed to assign faces automatically to text in the buffer.
2531 The functions are called in the order listed, with one argument, a
2532 buffer position @var{pos}. Each function should attempt to assign faces
2533 to the text in the current buffer starting at @var{pos}.
2535 Each function should record the faces they assign by setting the
2536 @code{face} property. It should also add a non-@code{nil}
2537 @code{fontified} property for all the text it has assigned faces to.
2538 That property tells redisplay that faces have been assigned to that text
2541 It is probably a good idea for each function to do nothing if the
2542 character after @var{pos} already has a non-@code{nil} @code{fontified}
2543 property, but this is not required. If one function overrides the
2544 assignments made by a previous one, the properties as they are
2545 after the last function finishes are the ones that really matter.
2547 For efficiency, we recommend writing these functions so that they
2548 usually assign faces to around 400 to 600 characters at each call.
2552 @subsection Looking Up Fonts
2554 @defun x-list-fonts pattern &optional face frame maximum
2555 This function returns a list of available font names that match
2556 @var{pattern}. If the optional arguments @var{face} and @var{frame} are
2557 specified, then the list is limited to fonts that are the same size as
2558 @var{face} currently is on @var{frame}.
2560 The argument @var{pattern} should be a string, perhaps with wildcard
2561 characters: the @samp{*} character matches any substring, and the
2562 @samp{?} character matches any single character. Pattern matching
2563 of font names ignores case.
2565 If you specify @var{face} and @var{frame}, @var{face} should be a face name
2566 (a symbol) and @var{frame} should be a frame.
2568 The optional argument @var{maximum} sets a limit on how many fonts to
2569 return. If this is non-@code{nil}, then the return value is truncated
2570 after the first @var{maximum} matching fonts. Specifying a small value
2571 for @var{maximum} can make this function much faster, in cases where
2572 many fonts match the pattern.
2575 These additional functions are available starting in Emacs 21.
2577 @defun x-family-fonts &optional family frame
2578 @tindex x-family-fonts
2579 This function returns a list describing the available fonts for family
2580 @var{family} on @var{frame}. If @var{family} is omitted or @code{nil},
2581 this list applies to all families, and therefore, it contains all
2582 available fonts. Otherwise, @var{family} must be a string; it may
2583 contain the wildcards @samp{?} and @samp{*}.
2585 The list describes the display that @var{frame} is on; if @var{frame} is
2586 omitted or @code{nil}, it applies to the selected frame's display
2587 (@pxref{Input Focus}).
2589 The list contains a vector of the following form for each font:
2592 [@var{family} @var{width} @var{point-size} @var{weight} @var{slant}
2593 @var{fixed-p} @var{full} @var{registry-and-encoding}]
2596 The first five elements correspond to face attributes; if you
2597 specify these attributes for a face, it will use this font.
2599 The last three elements give additional information about the font.
2600 @var{fixed-p} is non-@code{nil} if the font is fixed-pitch.
2601 @var{full} is the full name of the font, and
2602 @var{registry-and-encoding} is a string giving the registry and
2603 encoding of the font.
2605 The result list is sorted according to the current face font sort order.
2608 @defun x-font-family-list &optional frame
2609 @tindex x-font-family-list
2610 This function returns a list of the font families available for
2611 @var{frame}'s display. If @var{frame} is omitted or @code{nil}, it
2612 describes the selected frame's display (@pxref{Input Focus}).
2614 The value is a list of elements of this form:
2617 (@var{family} . @var{fixed-p})
2621 Here @var{family} is a font family, and @var{fixed-p} is
2622 non-@code{nil} if fonts of that family are fixed-pitch.
2625 @defvar font-list-limit
2626 @tindex font-list-limit
2627 This variable specifies maximum number of fonts to consider in font
2628 matching. The function @code{x-family-fonts} will not return more than
2629 that many fonts, and font selection will consider only that many fonts
2630 when searching a matching font for face attributes. The default is
2635 @subsection Fontsets
2637 A @dfn{fontset} is a list of fonts, each assigned to a range of
2638 character codes. An individual font cannot display the whole range of
2639 characters that Emacs supports, but a fontset can. Fontsets have names,
2640 just as fonts do, and you can use a fontset name in place of a font name
2641 when you specify the ``font'' for a frame or a face. Here is
2642 information about defining a fontset under Lisp program control.
2644 @defun create-fontset-from-fontset-spec fontset-spec &optional style-variant-p noerror
2645 This function defines a new fontset according to the specification
2646 string @var{fontset-spec}. The string should have this format:
2649 @var{fontpattern}, @r{[}@var{charsetname}:@var{fontname}@r{]@dots{}}
2653 Whitespace characters before and after the commas are ignored.
2655 The first part of the string, @var{fontpattern}, should have the form of
2656 a standard X font name, except that the last two fields should be
2657 @samp{fontset-@var{alias}}.
2659 The new fontset has two names, one long and one short. The long name is
2660 @var{fontpattern} in its entirety. The short name is
2661 @samp{fontset-@var{alias}}. You can refer to the fontset by either
2662 name. If a fontset with the same name already exists, an error is
2663 signaled, unless @var{noerror} is non-@code{nil}, in which case this
2664 function does nothing.
2666 If optional argument @var{style-variant-p} is non-@code{nil}, that says
2667 to create bold, italic and bold-italic variants of the fontset as well.
2668 These variant fontsets do not have a short name, only a long one, which
2669 is made by altering @var{fontpattern} to indicate the bold or italic
2672 The specification string also says which fonts to use in the fontset.
2673 See below for the details.
2676 The construct @samp{@var{charset}:@var{font}} specifies which font to
2677 use (in this fontset) for one particular character set. Here,
2678 @var{charset} is the name of a character set, and @var{font} is the font
2679 to use for that character set. You can use this construct any number of
2680 times in the specification string.
2682 For the remaining character sets, those that you don't specify
2683 explicitly, Emacs chooses a font based on @var{fontpattern}: it replaces
2684 @samp{fontset-@var{alias}} with a value that names one character set.
2685 For the @acronym{ASCII} character set, @samp{fontset-@var{alias}} is replaced
2686 with @samp{ISO8859-1}.
2688 In addition, when several consecutive fields are wildcards, Emacs
2689 collapses them into a single wildcard. This is to prevent use of
2690 auto-scaled fonts. Fonts made by scaling larger fonts are not usable
2691 for editing, and scaling a smaller font is not useful because it is
2692 better to use the smaller font in its own size, which Emacs does.
2694 Thus if @var{fontpattern} is this,
2697 -*-fixed-medium-r-normal-*-24-*-*-*-*-*-fontset-24
2701 the font specification for @acronym{ASCII} characters would be this:
2704 -*-fixed-medium-r-normal-*-24-*-ISO8859-1
2708 and the font specification for Chinese GB2312 characters would be this:
2711 -*-fixed-medium-r-normal-*-24-*-gb2312*-*
2714 You may not have any Chinese font matching the above font
2715 specification. Most X distributions include only Chinese fonts that
2716 have @samp{song ti} or @samp{fangsong ti} in the @var{family} field. In
2717 such a case, @samp{Fontset-@var{n}} can be specified as below:
2720 Emacs.Fontset-0: -*-fixed-medium-r-normal-*-24-*-*-*-*-*-fontset-24,\
2721 chinese-gb2312:-*-*-medium-r-normal-*-24-*-gb2312*-*
2725 Then, the font specifications for all but Chinese GB2312 characters have
2726 @samp{fixed} in the @var{family} field, and the font specification for
2727 Chinese GB2312 characters has a wild card @samp{*} in the @var{family}
2730 @defun set-fontset-font name character fontname &optional frame
2731 This function modifies the existing fontset @var{name} to
2732 use the font name @var{fontname} for the character @var{character}.
2734 If @var{name} is @code{nil}, this function modifies the default
2735 fontset, whose short name is @samp{fontset-default}.
2737 @var{character} may be a cons; @code{(@var{from} . @var{to})}, where
2738 @var{from} and @var{to} are non-generic characters. In that case, use
2739 @var{fontname} for all characters in the range @var{from} and @var{to}
2742 @var{character} may be a charset. In that case, use
2743 @var{fontname} for all character in the charsets.
2745 @var{fontname} may be a cons; @code{(@var{family} . @var{registry})},
2746 where @var{family} is a family name of a font (possibly including a
2747 foundry name at the head), @var{registry} is a registry name of a font
2748 (possibly including an encoding name at the tail).
2750 For instance, this changes the default fontset to use a font of which
2751 registry name is @samp{JISX0208.1983} for all characters belonging to
2752 the charset @code{japanese-jisx0208}.
2755 (set-fontset-font nil 'japanese-jisx0208 '(nil . "JISX0208.1983"))
2760 @defun char-displayable-p char
2761 This function returns @code{t} if Emacs ought to be able to display
2762 @var{char}. More precisely, if the selected frame's fontset has a
2763 font to display the character set that @var{char} belongs to.
2765 Fontsets can specify a font on a per-character basis; when the fontset
2766 does that, this function's value may not be accurate.
2773 The @dfn{fringes} of a window are thin vertical strips down the
2774 sides that are used for displaying bitmaps that indicate truncation,
2775 continuation, horizontal scrolling, and the overlay arrow. The
2776 fringes normally appear between the display margins and the window
2777 text, but you can put them outside the display margins for a specific
2778 buffer by setting @code{fringes-outside-margins} buffer-locally to a
2779 non-@code{nil} value.
2781 @defvar fringes-outside-margins
2782 If the value is non-@code{nil}, the frames appear outside
2783 the display margins.
2786 @defvar left-fringe-width
2787 This variable, if non-@code{nil}, specifies the width of the left
2791 @defvar right-fringe-width
2792 This variable, if non-@code{nil}, specifies the width of the right
2796 The values of these variables take effect when you display the
2797 buffer in a window. If you change them while the buffer is visible,
2798 you can call @code{set-window-buffer} to display it once again in the
2799 same window, to make the changes take effect.
2801 @defun set-window-fringes window left &optional right outside-margins
2802 This function sets the fringe widths of window @var{window}.
2803 If @var{window} is @code{nil}, the selected window is used.
2805 The argument @var{left} specifies the width in pixels of the left
2806 fringe, and likewise @var{right} for the right fringe. A value of
2807 @code{nil} for either one stands for the default width. If
2808 @var{outside-margins} is non-@code{nil}, that specifies that fringes
2809 should appear outside of the display margins.
2812 @defun window-fringes &optional window
2813 This function returns information about the fringes of a window
2814 @var{window}. If @var{window} is omitted or @code{nil}, the selected
2815 window is used. The value has the form @code{(@var{left-width}
2816 @var{right-width} @var{frames-outside-margins})}.
2819 @defvar overflow-newline-into-fringe
2820 If this is non-@code{nil}, lines exactly as wide as the window (not
2821 counting the final newline character) are not continued. Instead,
2822 when point is at the end of the line, the cursor appears in the right
2826 @node Fringe Bitmaps
2827 @section Fringe Bitmaps
2828 @cindex fringe bitmaps
2829 @cindex bitmaps, fringe
2831 The @dfn{fringe bitmaps} are tiny icons Emacs displays in the window
2832 fringe (on a graphic display) to indicate truncated or continued
2833 lines, buffer boundaries, overlay arrow, etc. The fringe bitmaps are
2834 shared by all frames and windows. You can redefine the built-in
2835 fringe bitmaps, and you can define new fringe bitmaps.
2837 The way to display a bitmap in the left or right fringes for a given
2838 line in a window is by specifying the @code{display} property for one
2839 of the characters that appears in it. Use a display specification of
2840 the form @code{(left-fringe @var{bitmap} [@var{face}])} or
2841 @code{(right-fringe @var{bitmap} [@var{face}])} (@pxref{Display
2842 Property}). Here, @var{bitmap} is a symbol identifying the bitmap
2843 you want, and @var{face} (which is optional) is the name of the face
2844 whose colors should be used for displaying the bitmap.
2846 These are the symbols identify the standard fringe bitmaps.
2847 Evaluate @code{(require 'fringe)} to define them. Fringe bitmap
2848 symbols have their own name space.
2851 @item Truncation and continuation line bitmaps:
2852 @code{left-truncation}, @code{right-truncation},
2853 @code{continued-line}, @code{continuation-line}.
2855 @item Buffer indication bitmaps:
2856 @code{up-arrow}, @code{down-arrow},
2857 @code{top-left-angle}, @code{top-right-angle},
2858 @code{bottom-left-angle}, @code{bottom-right-angle},
2859 @code{left-bracket}, @code{right-bracket}.
2861 @item Empty line indication bitmap:
2864 @item Overlay arrow bitmap:
2865 @code{overlay-arrow}.
2867 @item Bitmaps for displaying the cursor in right fringe:
2868 @code{filled-box-cursor}, @code{hollow-box-cursor}, @code{hollow-square},
2869 @code{bar-cursor}, @code{hbar-cursor}.
2872 @defun fringe-bitmaps-at-pos &optional pos window
2873 This function returns the fringe bitmaps of the display line
2874 containing position @var{pos} in window @var{window}. The return
2875 value has the form @code{(@var{left} @var{right} @var{ov})}, where @var{left}
2876 is the symbol for the fringe bitmap in the left fringe (or @code{nil}
2877 if no bitmap), @var{right} is similar for the right fringe, and @var{ov}
2878 is non-@code{nil} if there is an overlay arrow in the left fringe.
2880 The value is @code{nil} if @var{pos} is not visible in @var{window}.
2881 If @var{window} is @code{nil}, that stands for the selected window.
2882 If @var{pos} is @code{nil}, that stands for the value of point in
2886 @node Customizing Bitmaps
2887 @section Customizing Fringe Bitmaps
2889 @defun define-fringe-bitmap bitmap bits &optional height width align
2890 This function defines the symbol @var{bitmap} as a new fringe bitmap,
2891 or replaces an existing bitmap with that name.
2893 The argument @var{bits} specifies the image to use. It should be
2894 either a string or a vector of integers, where each element (an
2895 integer) corresponds to one row of the bitmap. Each bit of an integer
2896 corresponds to one pixel of the bitmap, where the low bit corresponds
2897 to the rightmost pixel of the bitmap.
2899 The height is normally the length of @var{bits}. However, you
2900 can specify a different height with non-@code{nil} @var{height}. The width
2901 is normally 8, but you can specify a different width with non-@code{nil}
2902 @var{width}. The width must be an integer between 1 and 16.
2904 The argument @var{align} specifies the positioning of the bitmap
2905 relative to the range of rows where it is used; the default is to
2906 center the bitmap. The allowed values are @code{top}, @code{center},
2909 The @var{align} argument may also be a list @code{(@var{align}
2910 @var{periodic})} where @var{align} is interpreted as described above.
2911 If @var{periodic} is non-@code{nil}, it specifies that the rows in
2912 @code{bits} should be repeated enough times to reach the specified
2915 The return value on success is an integer identifying the new bitmap.
2916 You should save that integer in a variable so it can be used to select
2919 This function signals an error if there are no more free bitmap slots.
2922 @defun destroy-fringe-bitmap bitmap
2923 This function destroy the fringe bitmap identified by @var{bitmap}.
2924 If @var{bitmap} identifies a standard fringe bitmap, it actually
2925 restores the standard definition of that bitmap, instead of
2926 eliminating it entirely.
2929 @defun set-fringe-bitmap-face bitmap &optional face
2930 This sets the face for the fringe bitmap @var{bitmap} to @var{face}.
2931 If @var{face} is @code{nil}, it selects the @code{fringe} face. The
2932 bitmap's face controls the color to draw it in.
2934 The face you use here should be derived from @code{fringe}, and should
2935 specify only the foreground color.
2939 @section Scroll Bars
2941 Normally the frame parameter @code{vertical-scroll-bars} controls
2942 whether the windows in the frame have vertical scroll bars. A
2943 non-@code{nil} parameter value means they do. The frame parameter
2944 @code{scroll-bar-width} specifies how wide they are (@code{nil}
2945 meaning the default). @xref{Window Frame Parameters}.
2947 @vindex vertical-scroll-bar
2948 You can enable or disable scroll bars for a particular buffer,
2949 by setting the variable @code{vertical-scroll-bar}. This variable
2950 automatically becomes buffer-local when set. The possible values are
2951 @code{left}, @code{right}, @code{t}, which means to use the
2952 frame's default, and @code{nil} for no scroll bar.
2954 You can also control this for individual windows. Call the function
2955 @code{set-window-scroll-bars} to specify what to do for a specific window:
2957 @defun set-window-scroll-bars window width &optional vertical-type horizontal-type
2958 This function sets the width and type of scroll bars for window
2961 @var{width} specifies the scroll bar width in pixels (@code{nil} means
2962 use the width specified for the frame). @var{vertical-type} specifies
2963 whether to have a vertical scroll bar and, if so, where. The possible
2964 values are @code{left}, @code{right} and @code{nil}, just like the
2965 values of the @code{vertical-scroll-bars} frame parameter.
2967 The argument @var{horizontal-type} is meant to specify whether and
2968 where to have horizontal scroll bars, but since they are not
2969 implemented, it has no effect. If @var{window} is @code{nil}, the
2970 selected window is used.
2973 @defun window-scroll-bars &optional window
2974 Report the width and type of scroll bars specified for @var{window}.
2975 If @var{window} is omitted or @code{nil}, the selected window is used.
2976 The value is a list of the form @code{(@var{width}
2977 @var{cols} @var{vertical-type} @var{horizontal-type})}. The value
2978 @var{width} is the value that was specified for the width (which may
2979 be @code{nil}); @var{cols} is the number of columns that the scroll
2980 bar actually occupies.
2982 @var{horizontal-type} is not actually meaningful.
2985 If you don't specify these values for a window with
2986 @code{set-window-scroll-bars}, the buffer-local variables
2987 @code{scroll-bar-mode} and @code{scroll-bar-width} in the buffer being
2988 displayed control the window's vertical scroll bars. The function
2989 @code{set-window-buffer} examines these variables. If you change them
2990 in a buffer that is already visible in a window, you can make the
2991 window take note of the new values by calling @code{set-window-buffer}
2992 specifying the same buffer that is already displayed.
2994 @defvar scroll-bar-mode
2995 This variable, always local in all buffers, controls whether and where
2996 to put scroll bars in windows displaying the buffer. The possible values
2997 are @code{nil} for no scroll bar, @code{left} to put a scroll bar on
2998 the left, and @code{right} to put a scroll bar on the right.
3001 @defvar scroll-bar-width
3002 This variable, always local in all buffers, specifies the width of the
3003 buffer's scroll bars, measured in pixels. A value of @code{nil} means
3004 to use the value specified by the frame.
3008 @section Pointer Shape
3010 Normally, the mouse pointer has the @code{text} shape over text and
3011 the @code{arrow} shape over window areas which do not correspond to
3012 any buffer text. You can specify the mouse pointer shape over text or
3013 images via the @code{pointer} text property, and for images with the
3014 @code{:pointer} and @code{:map} image properties.
3016 The available pointer shapes are: @code{text} (or @code{nil}),
3017 @code{arrow}, @code{hand}, @code{vdrag}, @code{hdrag},
3018 @code{modeline}, and @code{hourglass}.
3020 @defvar void-text-area-pointer
3021 @tindex void-text-area-pointer
3022 This variable specifies the mouse pointer shape in void text areas,
3023 i.e. the areas after the end of a line or below the last line in the
3024 buffer. The default is to use the @code{arrow} (non-text) pointer.
3027 @node Display Property
3028 @section The @code{display} Property
3029 @cindex display specification
3030 @kindex display @r{(text property)}
3032 The @code{display} text property (or overlay property) is used to
3033 insert images into text, and also control other aspects of how text
3034 displays. These features are available starting in Emacs 21. The value
3035 of the @code{display} property should be a display specification, or a
3036 list or vector containing several display specifications. The rest of
3037 this section describes several kinds of display specifications and what
3041 * Specified Space:: Displaying one space with a specified width.
3042 * Pixel Specification:: Specifying space width or height in pixels.
3043 * Other Display Specs:: Displaying an image; magnifying text; moving it
3044 up or down on the page; adjusting the width
3045 of spaces within text.
3046 * Display Margins:: Displaying text or images to the side of the main text.
3047 * Conditional Display:: Making any of the above features conditional
3048 depending on some Lisp expression.
3051 @node Specified Space
3052 @subsection Specified Spaces
3053 @cindex spaces, specified height or width
3054 @cindex specified spaces
3055 @cindex variable-width spaces
3057 To display a space of specified width and/or height, use a display
3058 specification of the form @code{(space . @var{props})}, where
3059 @var{props} is a property list (a list of alternating properties and
3060 values). You can put this property on one or more consecutive
3061 characters; a space of the specified height and width is displayed in
3062 place of @emph{all} of those characters. These are the properties you
3063 can use in @var{props} to specify the weight of the space:
3066 @item :width @var{width}
3067 If @var{width} is an integer or floating point number, it specifies
3068 that the space width should be @var{width} times the normal character
3069 width. @var{width} can also be a @dfn{pixel width} specification
3070 (@pxref{Pixel Specification}).
3072 @item :relative-width @var{factor}
3073 Specifies that the width of the stretch should be computed from the
3074 first character in the group of consecutive characters that have the
3075 same @code{display} property. The space width is the width of that
3076 character, multiplied by @var{factor}.
3078 @item :align-to @var{hpos}
3079 Specifies that the space should be wide enough to reach @var{hpos}.
3080 If @var{hpos} is a number, it is measured in units of the normal
3081 character width. @var{hpos} can also be a @dfn{pixel width}
3082 specification (@pxref{Pixel Specification}).
3085 You should use one and only one of the above properties. You can
3086 also specify the height of the space, with these properties:
3089 @item :height @var{height}
3090 Specifies the height of the space.
3091 If @var{height} is an integer or floating point number, it specifies
3092 that the space height should be @var{height} times the normal character
3093 height. The @var{height} may also be a @dfn{pixel height} specification
3094 (@pxref{Pixel Specification}).
3096 @item :relative-height @var{factor}
3097 Specifies the height of the space, multiplying the ordinary height
3098 of the text having this display specification by @var{factor}.
3100 @item :ascent @var{ascent}
3101 If the value of @var{ascent} is a non-negative number no greater than
3102 100, it specifies that @var{ascent} percent of the height of the space
3103 should be considered as the ascent of the space---that is, the part
3104 above the baseline. The ascent may also be specified in pixel units
3105 with a @dfn{pixel ascent} specification (@pxref{Pixel Specification}).
3109 Don't use both @code{:height} and @code{:relative-height} together.
3111 The @code{:height} and @code{:align-to} properties are supported on
3112 non-graphic terminals, but the other space properties in this section
3115 @node Pixel Specification
3116 @subsection Pixel Specification for Spaces
3117 @cindex spaces, pixel specification
3119 The value of the @code{:width}, @code{:align-to}, @code{:height},
3120 and @code{:ascent} properties can be a special kind of expression that
3121 is evaluated during redisplay. The result of the evaluation is used
3122 as an absolute number of pixels.
3124 The following expressions are supported:
3128 @var{expr} ::= @var{num} | (@var{num}) | @var{unit} | @var{elem} | @var{pos} | @var{image} | @var{form}
3129 @var{num} ::= @var{integer} | @var{float} | @var{symbol}
3130 @var{unit} ::= in | mm | cm | width | height
3131 @var{elem} ::= left-fringe | right-fringe | left-margin | right-margin
3133 @var{pos} ::= left | center | right
3134 @var{form} ::= (@var{num} . @var{expr}) | (@var{op} @var{expr} ...)
3139 The form @var{num} specifies a fraction of the default frame font
3140 height or width. The form @code{(@var{num})} specifies an absolute
3141 number of pixels. If @var{num} is a symbol, @var{symbol}, its
3142 buffer-local variable binding is used.
3144 The @code{in}, @code{mm}, and @code{cm} units specify the number of
3145 pixels per inch, millimeter, and centimeter, respectively. The
3146 @code{width} and @code{height} units correspond to the default width
3147 and height of the current face. An image specification @code{image}
3148 corresponds to the width or height of the image.
3150 The @code{left-fringe}, @code{right-fringe}, @code{left-margin},
3151 @code{right-margin}, @code{scroll-bar}, and @code{text} elements
3152 specify to the width of the corresponding area of the window.
3154 The @code{left}, @code{center}, and @code{right} positions can be
3155 used with @code{:align-to} to specify a position relative to the left
3156 edge, center, or right edge of the text area.
3158 Any of the above window elements (except @code{text}) can also be
3159 used with @code{:align-to} to specify that the position is relative to
3160 the left edge of the given area. Once the base offset for a relative
3161 position has been set (by the first occurrence of one of these
3162 symbols), further occurrences of these symbols are interpreted as the
3163 width of the specified area. For example, to align to the center of
3164 the left-margin, use
3167 :align-to (+ left-margin (0.5 . left-margin))
3170 If no specific base offset is set for alignment, it is always relative
3171 to the left edge of the text area. For example, @samp{:align-to 0} in a
3172 header-line aligns with the first text column in the text area.
3174 A value of the form @code{(@var{num} . @var{expr})} stands
3175 multiplying the values of @var{num} and @var{expr}. For example,
3176 @code{(2 . in)} specifies a width of 2 inches, while @code{(0.5 .
3177 @var{image})} specifies half the width (or height) of the specified image.
3179 The form @code{(+ @var{expr} ...)} adds up the value of the
3180 expressions. The form @code{(- @var{expr} ...)} negates or subtracts
3181 the value of the expressions.
3183 @node Other Display Specs
3184 @subsection Other Display Specifications
3186 Here are the other sorts of display specifications that you can use
3187 in the @code{display} text property.
3190 @item (image . @var{image-props})
3191 This is in fact an image descriptor (@pxref{Images}). When used as a
3192 display specification, it means to display the image instead of the text
3193 that has the display specification.
3195 @item (slice @var{x} @var{y} @var{width} @var{height})
3196 This specification together with @code{image} specifies a @dfn{slice}
3197 (a partial area) of the image to display. The elements @var{y} and
3198 @var{x} specify the top left corner of the slice, within the image;
3199 @var{width} and @var{height} specify the width and height of the
3200 slice. Integer values are numbers of pixels. A floating point number
3201 in the range 0.0--1.0 stands for that fraction of the width or height
3202 of the entire image.
3204 @item ((margin nil) @var{string})
3206 A display specification of this form means to display @var{string}
3207 instead of the text that has the display specification, at the same
3208 position as that text. This is a special case of marginal display
3209 (@pxref{Display Margins}).
3211 Recursive display specifications are not supported---string display
3212 specifications must not have @code{display} properties themselves.
3214 @item (space-width @var{factor})
3215 This display specification affects all the space characters within the
3216 text that has the specification. It displays all of these spaces
3217 @var{factor} times as wide as normal. The element @var{factor} should
3218 be an integer or float. Characters other than spaces are not affected
3219 at all; in particular, this has no effect on tab characters.
3221 @item (height @var{height})
3222 This display specification makes the text taller or shorter.
3223 Here are the possibilities for @var{height}:
3226 @item @code{(+ @var{n})}
3227 This means to use a font that is @var{n} steps larger. A ``step'' is
3228 defined by the set of available fonts---specifically, those that match
3229 what was otherwise specified for this text, in all attributes except
3230 height. Each size for which a suitable font is available counts as
3231 another step. @var{n} should be an integer.
3233 @item @code{(- @var{n})}
3234 This means to use a font that is @var{n} steps smaller.
3236 @item a number, @var{factor}
3237 A number, @var{factor}, means to use a font that is @var{factor} times
3238 as tall as the default font.
3240 @item a symbol, @var{function}
3241 A symbol is a function to compute the height. It is called with the
3242 current height as argument, and should return the new height to use.
3244 @item anything else, @var{form}
3245 If the @var{height} value doesn't fit the previous possibilities, it is
3246 a form. Emacs evaluates it to get the new height, with the symbol
3247 @code{height} bound to the current specified font height.
3250 @item (raise @var{factor})
3251 This kind of display specification raises or lowers the text
3252 it applies to, relative to the baseline of the line.
3254 @var{factor} must be a number, which is interpreted as a multiple of the
3255 height of the affected text. If it is positive, that means to display
3256 the characters raised. If it is negative, that means to display them
3259 If the text also has a @code{height} display specification, that does
3260 not affect the amount of raising or lowering, which is based on the
3261 faces used for the text.
3264 @node Display Margins
3265 @subsection Displaying in the Margins
3266 @cindex display margins
3267 @cindex margins, display
3269 A buffer can have blank areas called @dfn{display margins} on the left
3270 and on the right. Ordinary text never appears in these areas, but you
3271 can put things into the display margins using the @code{display}
3274 To put text in the left or right display margin of the window, use a
3275 display specification of the form @code{(margin right-margin)} or
3276 @code{(margin left-margin)} on it. To put an image in a display margin,
3277 use that display specification along with the display specification for
3278 the image. Unfortunately, there is currently no way to make
3279 text or images in the margin mouse-sensitive.
3281 If you put such a display specification directly on text in the
3282 buffer, the specified margin display appears @emph{instead of} that
3283 buffer text itself. To put something in the margin @emph{in
3284 association with} certain buffer text without preventing or altering
3285 the display of that text, put a @code{before-string} property on the
3286 text and put the display specification on the contents of the
3289 Before the display margins can display anything, you must give
3290 them a nonzero width. The usual way to do that is to set these
3293 @defvar left-margin-width
3294 @tindex left-margin-width
3295 This variable specifies the width of the left margin.
3296 It is buffer-local in all buffers.
3299 @defvar right-margin-width
3300 @tindex right-margin-width
3301 This variable specifies the width of the right margin.
3302 It is buffer-local in all buffers.
3305 Setting these variables does not immediately affect the window. These
3306 variables are checked when a new buffer is displayed in the window.
3307 Thus, you can make changes take effect by calling
3308 @code{set-window-buffer}.
3310 You can also set the margin widths immediately.
3312 @defun set-window-margins window left &optional right
3313 @tindex set-window-margins
3314 This function specifies the margin widths for window @var{window}.
3315 The argument @var{left} controls the left margin and
3316 @var{right} controls the right margin (default @code{0}).
3319 @defun window-margins &optional window
3320 @tindex window-margins
3321 This function returns the left and right margins of @var{window}
3322 as a cons cell of the form @code{(@var{left} . @var{right})}.
3323 If @var{window} is @code{nil}, the selected window is used.
3326 @node Conditional Display
3327 @subsection Conditional Display Specifications
3328 @cindex conditional display specifications
3330 You can make any display specification conditional. To do that,
3331 package it in another list of the form @code{(when @var{condition} .
3332 @var{spec})}. Then the specification @var{spec} applies only when
3333 @var{condition} evaluates to a non-@code{nil} value. During the
3334 evaluation, @code{object} is bound to the string or buffer having the
3335 conditional @code{display} property. @code{position} and
3336 @code{buffer-position} are bound to the position within @code{object}
3337 and the buffer position where the @code{display} property was found,
3338 respectively. Both positions can be different when @code{object} is a
3343 @cindex images in buffers
3345 To display an image in an Emacs buffer, you must first create an image
3346 descriptor, then use it as a display specifier in the @code{display}
3347 property of text that is displayed (@pxref{Display Property}). Like the
3348 @code{display} property, this feature is available starting in Emacs 21.
3350 Emacs can display a number of different image formats; some of them
3351 are supported only if particular support libraries are installed on
3352 your machine. In some environments, Emacs allows loading image
3353 libraries on demand; if so, the variable @code{image-library-alist}
3354 can be used to modify the set of known names for these dynamic
3355 libraries (though it is not possible to add new image formats).
3357 The supported image formats include XBM, XPM (needing the
3358 libraries @code{libXpm} version 3.4k and @code{libz}), GIF (needing
3359 @code{libungif} 4.1.0), Postscript, PBM, JPEG (needing the
3360 @code{libjpeg} library version v6a), TIFF (needing @code{libtiff} v3.4),
3361 and PNG (needing @code{libpng} 1.0.2).
3363 You specify one of these formats with an image type symbol. The image
3364 type symbols are @code{xbm}, @code{xpm}, @code{gif}, @code{postscript},
3365 @code{pbm}, @code{jpeg}, @code{tiff}, and @code{png}.
3368 This variable contains a list of those image type symbols that are
3369 potentially supported in the current configuration.
3370 @emph{Potentially} here means that Emacs knows about the image types,
3371 not necessarily that they can be loaded (they could depend on
3372 unavailable dynamic libraries, for example).
3374 To know which image types are really available, use
3375 @code{image-type-available-p}.
3378 @defvar image-library-alist
3379 This in an alist of image types vs external libraries needed to
3382 Each element is a list @code{(@var{image-type} @var{library}...)},
3383 where the car is a supported image format from @code{image-types}, and
3384 the rest are strings giving alternate filenames for the corresponding
3385 external libraries to load.
3387 Emacs tries to load the libraries in the order they appear on the
3388 list; if none is loaded, the running session of Emacs won't support
3389 the image type. @code{pbm} and @code{xbm} don't need to be listed;
3390 they're always supported.
3392 This variable is ignored if the image libraries are statically linked
3396 @defun image-type-available-p type
3397 @findex image-type-available-p
3399 This function returns non-@code{nil} if image type @var{type} is
3400 available, i.e., if images of this type can be loaded and displayed in
3401 Emacs. @var{type} should be one of the types contained in
3404 For image types whose support libraries are statically linked, this
3405 function always returns @code{t}; for other image types, it returns
3406 @code{t} if the dynamic library could be loaded, @code{nil} otherwise.
3410 * Image Descriptors:: How to specify an image for use in @code{:display}.
3411 * XBM Images:: Special features for XBM format.
3412 * XPM Images:: Special features for XPM format.
3413 * GIF Images:: Special features for GIF format.
3414 * Postscript Images:: Special features for Postscript format.
3415 * Other Image Types:: Various other formats are supported.
3416 * Defining Images:: Convenient ways to define an image for later use.
3417 * Showing Images:: Convenient ways to display an image once it is defined.
3418 * Image Cache:: Internal mechanisms of image display.
3421 @node Image Descriptors
3422 @subsection Image Descriptors
3423 @cindex image descriptor
3425 An image description is a list of the form @code{(image
3426 . @var{props})}, where @var{props} is a property list containing
3427 alternating keyword symbols (symbols whose names start with a colon) and
3428 their values. You can use any Lisp object as a property, but the only
3429 properties that have any special meaning are certain symbols, all of
3432 Every image descriptor must contain the property @code{:type
3433 @var{type}} to specify the format of the image. The value of @var{type}
3434 should be an image type symbol; for example, @code{xpm} for an image in
3437 Here is a list of other properties that are meaningful for all image
3441 @item :file @var{file}
3442 The @code{:file} property specifies to load the image from file
3443 @var{file}. If @var{file} is not an absolute file name, it is expanded
3444 in @code{data-directory}.
3446 @item :data @var{data}
3447 The @code{:data} property specifies the actual contents of the image.
3448 Each image must use either @code{:data} or @code{:file}, but not both.
3449 For most image types, the value of the @code{:data} property should be a
3450 string containing the image data; we recommend using a unibyte string.
3452 Before using @code{:data}, look for further information in the section
3453 below describing the specific image format. For some image types,
3454 @code{:data} may not be supported; for some, it allows other data types;
3455 for some, @code{:data} alone is not enough, so you need to use other
3456 image properties along with @code{:data}.
3458 @item :margin @var{margin}
3459 The @code{:margin} property specifies how many pixels to add as an
3460 extra margin around the image. The value, @var{margin}, must be a
3461 non-negative number, or a pair @code{(@var{x} . @var{y})} of such
3462 numbers. If it is a pair, @var{x} specifies how many pixels to add
3463 horizontally, and @var{y} specifies how many pixels to add vertically.
3464 If @code{:margin} is not specified, the default is zero.
3466 @item :ascent @var{ascent}
3467 The @code{:ascent} property specifies the amount of the image's
3468 height to use for its ascent---that is, the part above the baseline.
3469 The value, @var{ascent}, must be a number in the range 0 to 100, or
3470 the symbol @code{center}.
3472 If @var{ascent} is a number, that percentage of the image's height is
3473 used for its ascent.
3475 If @var{ascent} is @code{center}, the image is vertically centered
3476 around a centerline which would be the vertical centerline of text drawn
3477 at the position of the image, in the manner specified by the text
3478 properties and overlays that apply to the image.
3480 If this property is omitted, it defaults to 50.
3482 @item :relief @var{relief}
3483 The @code{:relief} property, if non-@code{nil}, adds a shadow rectangle
3484 around the image. The value, @var{relief}, specifies the width of the
3485 shadow lines, in pixels. If @var{relief} is negative, shadows are drawn
3486 so that the image appears as a pressed button; otherwise, it appears as
3487 an unpressed button.
3489 @item :conversion @var{algorithm}
3490 The @code{:conversion} property, if non-@code{nil}, specifies a
3491 conversion algorithm that should be applied to the image before it is
3492 displayed; the value, @var{algorithm}, specifies which algorithm.
3497 Specifies the Laplace edge detection algorithm, which blurs out small
3498 differences in color while highlighting larger differences. People
3499 sometimes consider this useful for displaying the image for a
3500 ``disabled'' button.
3502 @item (edge-detection :matrix @var{matrix} :color-adjust @var{adjust})
3503 Specifies a general edge-detection algorithm. @var{matrix} must be
3504 either a nine-element list or a nine-element vector of numbers. A pixel
3505 at position @math{x/y} in the transformed image is computed from
3506 original pixels around that position. @var{matrix} specifies, for each
3507 pixel in the neighborhood of @math{x/y}, a factor with which that pixel
3508 will influence the transformed pixel; element @math{0} specifies the
3509 factor for the pixel at @math{x-1/y-1}, element @math{1} the factor for
3510 the pixel at @math{x/y-1} etc., as shown below:
3513 $$\pmatrix{x-1/y-1 & x/y-1 & x+1/y-1 \cr
3514 x-1/y & x/y & x+1/y \cr
3515 x-1/y+1& x/y+1 & x+1/y+1 \cr}$$
3520 (x-1/y-1 x/y-1 x+1/y-1
3522 x-1/y+1 x/y+1 x+1/y+1)
3526 The resulting pixel is computed from the color intensity of the color
3527 resulting from summing up the RGB values of surrounding pixels,
3528 multiplied by the specified factors, and dividing that sum by the sum
3529 of the factors' absolute values.
3531 Laplace edge-detection currently uses a matrix of
3534 $$\pmatrix{1 & 0 & 0 \cr
3547 Emboss edge-detection uses a matrix of
3550 $$\pmatrix{ 2 & -1 & 0 \cr
3564 Specifies transforming the image so that it looks ``disabled''.
3567 @item :mask @var{mask}
3568 If @var{mask} is @code{heuristic} or @code{(heuristic @var{bg})}, build
3569 a clipping mask for the image, so that the background of a frame is
3570 visible behind the image. If @var{bg} is not specified, or if @var{bg}
3571 is @code{t}, determine the background color of the image by looking at
3572 the four corners of the image, assuming the most frequently occurring
3573 color from the corners is the background color of the image. Otherwise,
3574 @var{bg} must be a list @code{(@var{red} @var{green} @var{blue})}
3575 specifying the color to assume for the background of the image.
3577 If @var{mask} is @code{nil}, remove a mask from the image, if it has
3578 one. Images in some formats include a mask which can be removed by
3579 specifying @code{:mask nil}.
3581 @item :pointer @var{shape}
3582 This specifies the pointer shape when the mouse pointer is over this
3583 image. @xref{Pointer Shape}, for available pointer shapes.
3585 @item :map @var{map}
3586 This associates an image map of @dfn{hot spots} with this image.
3588 An image map is an alist where each element has the format
3589 @code{(@var{area} @var{id} @var{plist})}. An @var{area} is specified
3590 as either a rectangle, a circle, or a polygon.
3592 A rectangle is a cons
3593 @code{(rect . ((@var{x0} . @var{y0}) . (@var{x1} . @var{y1})))}
3594 which specifies the pixel coordinates of the upper left and bottom right
3595 corners of the rectangle area.
3598 @code{(circle . ((@var{x0} . @var{y0}) . @var{r}))}
3599 which specifies the center and the radius of the circle; @var{r} may
3600 be a float or integer.
3603 @code{(poly . [@var{x0} @var{y0} @var{x1} @var{y1} ...])}
3604 where each pair in the vector describes one corner in the polygon.
3606 When the mouse pointer is above a hot-spot area of an image, the
3607 @var{plist} of that hot-spot is consulted; if it contains a @code{help-echo}
3608 property it defines a tool-tip for the hot-spot, and if it contains
3609 a @code{pointer} property, it defines the shape of the mouse cursor when
3610 it is over the hot-spot.
3611 @xref{Pointer Shape}, for available pointer shapes.
3613 When you click the mouse when the mouse pointer is over a hot-spot, an
3614 event is composed by combining the @var{id} of the hot-spot with the
3615 mouse event; for instance, @code{[area4 mouse-1]} if the hot-spot's
3616 @var{id} is @code{area4}.
3619 @defun image-mask-p spec &optional frame
3620 @tindex image-mask-p
3621 This function returns @code{t} if image @var{spec} has a mask bitmap.
3622 @var{frame} is the frame on which the image will be displayed.
3623 @var{frame} @code{nil} or omitted means to use the selected frame
3624 (@pxref{Input Focus}).
3628 @subsection XBM Images
3631 To use XBM format, specify @code{xbm} as the image type. This image
3632 format doesn't require an external library, so images of this type are
3635 Additional image properties supported for the @code{xbm} image type are:
3638 @item :foreground @var{foreground}
3639 The value, @var{foreground}, should be a string specifying the image
3640 foreground color, or @code{nil} for the default color. This color is
3641 used for each pixel in the XBM that is 1. The default is the frame's
3644 @item :background @var{background}
3645 The value, @var{background}, should be a string specifying the image
3646 background color, or @code{nil} for the default color. This color is
3647 used for each pixel in the XBM that is 0. The default is the frame's
3651 If you specify an XBM image using data within Emacs instead of an
3652 external file, use the following three properties:
3655 @item :data @var{data}
3656 The value, @var{data}, specifies the contents of the image.
3657 There are three formats you can use for @var{data}:
3661 A vector of strings or bool-vectors, each specifying one line of the
3662 image. Do specify @code{:height} and @code{:width}.
3665 A string containing the same byte sequence as an XBM file would contain.
3666 You must not specify @code{:height} and @code{:width} in this case,
3667 because omitting them is what indicates the data has the format of an
3668 XBM file. The file contents specify the height and width of the image.
3671 A string or a bool-vector containing the bits of the image (plus perhaps
3672 some extra bits at the end that will not be used). It should contain at
3673 least @var{width} * @code{height} bits. In this case, you must specify
3674 @code{:height} and @code{:width}, both to indicate that the string
3675 contains just the bits rather than a whole XBM file, and to specify the
3679 @item :width @var{width}
3680 The value, @var{width}, specifies the width of the image, in pixels.
3682 @item :height @var{height}
3683 The value, @var{height}, specifies the height of the image, in pixels.
3687 @subsection XPM Images
3690 To use XPM format, specify @code{xpm} as the image type. The
3691 additional image property @code{:color-symbols} is also meaningful with
3692 the @code{xpm} image type:
3695 @item :color-symbols @var{symbols}
3696 The value, @var{symbols}, should be an alist whose elements have the
3697 form @code{(@var{name} . @var{color})}. In each element, @var{name} is
3698 the name of a color as it appears in the image file, and @var{color}
3699 specifies the actual color to use for displaying that name.
3703 @subsection GIF Images
3706 For GIF images, specify image type @code{gif}. Because of the patents
3707 in the US covering the LZW algorithm, the continued use of GIF format is
3708 a problem for the whole Internet; to end this problem, it is a good idea
3709 for everyone, even outside the US, to stop using GIFs right away
3710 (@uref{http://www.burnallgifs.org/}). But if you still want to use
3711 them, Emacs can display them.
3714 @item :index @var{index}
3715 You can use @code{:index} to specify one image from a GIF file that
3716 contains more than one image. This property specifies use of image
3717 number @var{index} from the file. If the GIF file doesn't contain an
3718 image with index @var{index}, the image displays as a hollow box.
3722 This could be used to implement limited support for animated GIFs.
3723 For example, the following function displays a multi-image GIF file
3724 at point-min in the current buffer, switching between sub-images
3727 (defun show-anim (file max)
3728 "Display multi-image GIF file FILE which contains MAX subimages."
3729 (display-anim (current-buffer) file 0 max t))
3731 (defun display-anim (buffer file idx max first-time)
3734 (let ((img (create-image file nil :image idx)))
3737 (goto-char (point-min))
3738 (unless first-time (delete-char 1))
3740 (run-with-timer 0.1 nil 'display-anim buffer file (1+ idx) max nil)))
3743 @node Postscript Images
3744 @subsection Postscript Images
3745 @cindex Postscript images
3747 To use Postscript for an image, specify image type @code{postscript}.
3748 This works only if you have Ghostscript installed. You must always use
3749 these three properties:
3752 @item :pt-width @var{width}
3753 The value, @var{width}, specifies the width of the image measured in
3754 points (1/72 inch). @var{width} must be an integer.
3756 @item :pt-height @var{height}
3757 The value, @var{height}, specifies the height of the image in points
3758 (1/72 inch). @var{height} must be an integer.
3760 @item :bounding-box @var{box}
3761 The value, @var{box}, must be a list or vector of four integers, which
3762 specifying the bounding box of the Postscript image, analogous to the
3763 @samp{BoundingBox} comment found in Postscript files.
3766 %%BoundingBox: 22 171 567 738
3770 Displaying Postscript images from Lisp data is not currently
3771 implemented, but it may be implemented by the time you read this.
3772 See the @file{etc/NEWS} file to make sure.
3774 @node Other Image Types
3775 @subsection Other Image Types
3778 For PBM images, specify image type @code{pbm}. Color, gray-scale and
3779 monochromatic images are supported. For mono PBM images, two additional
3780 image properties are supported.
3783 @item :foreground @var{foreground}
3784 The value, @var{foreground}, should be a string specifying the image
3785 foreground color, or @code{nil} for the default color. This color is
3786 used for each pixel in the XBM that is 1. The default is the frame's
3789 @item :background @var{background}
3790 The value, @var{background}, should be a string specifying the image
3791 background color, or @code{nil} for the default color. This color is
3792 used for each pixel in the XBM that is 0. The default is the frame's
3796 For JPEG images, specify image type @code{jpeg}.
3798 For TIFF images, specify image type @code{tiff}.
3800 For PNG images, specify image type @code{png}.
3802 @node Defining Images
3803 @subsection Defining Images
3805 The functions @code{create-image}, @code{defimage} and
3806 @code{find-image} provide convenient ways to create image descriptors.
3808 @defun create-image file-or-data &optional type data-p &rest props
3809 @tindex create-image
3810 This function creates and returns an image descriptor which uses the
3811 data in @var{file-or-data}. @var{file-or-data} can be a file name or
3812 a string containing the image data; @var{data-p} should be @code{nil}
3813 for the former case, non-@code{nil} for the latter case.
3815 The optional argument @var{type} is a symbol specifying the image type.
3816 If @var{type} is omitted or @code{nil}, @code{create-image} tries to
3817 determine the image type from the file's first few bytes, or else
3818 from the file's name.
3820 The remaining arguments, @var{props}, specify additional image
3821 properties---for example,
3824 (create-image "foo.xpm" 'xpm nil :heuristic-mask t)
3827 The function returns @code{nil} if images of this type are not
3828 supported. Otherwise it returns an image descriptor.
3831 @defmac defimage symbol specs &optional doc
3833 This macro defines @var{symbol} as an image name. The arguments
3834 @var{specs} is a list which specifies how to display the image.
3835 The third argument, @var{doc}, is an optional documentation string.
3837 Each argument in @var{specs} has the form of a property list, and each
3838 one should specify at least the @code{:type} property and either the
3839 @code{:file} or the @code{:data} property. The value of @code{:type}
3840 should be a symbol specifying the image type, the value of
3841 @code{:file} is the file to load the image from, and the value of
3842 @code{:data} is a string containing the actual image data. Here is an
3846 (defimage test-image
3847 ((:type xpm :file "~/test1.xpm")
3848 (:type xbm :file "~/test1.xbm")))
3851 @code{defimage} tests each argument, one by one, to see if it is
3852 usable---that is, if the type is supported and the file exists. The
3853 first usable argument is used to make an image descriptor which is
3854 stored in @var{symbol}.
3856 If none of the alternatives will work, then @var{symbol} is defined
3860 @defun find-image specs
3862 This function provides a convenient way to find an image satisfying one
3863 of a list of image specifications @var{specs}.
3865 Each specification in @var{specs} is a property list with contents
3866 depending on image type. All specifications must at least contain the
3867 properties @code{:type @var{type}} and either @w{@code{:file @var{file}}}
3868 or @w{@code{:data @var{DATA}}}, where @var{type} is a symbol specifying
3869 the image type, e.g.@: @code{xbm}, @var{file} is the file to load the
3870 image from, and @var{data} is a string containing the actual image data.
3871 The first specification in the list whose @var{type} is supported, and
3872 @var{file} exists, is used to construct the image specification to be
3873 returned. If no specification is satisfied, @code{nil} is returned.
3875 The image is looked for first on @code{load-path} and then in
3876 @code{data-directory}.
3879 @node Showing Images
3880 @subsection Showing Images
3882 You can use an image descriptor by setting up the @code{display}
3883 property yourself, but it is easier to use the functions in this
3886 @defun insert-image image &optional string area slice
3887 This function inserts @var{image} in the current buffer at point. The
3888 value @var{image} should be an image descriptor; it could be a value
3889 returned by @code{create-image}, or the value of a symbol defined with
3890 @code{defimage}. The argument @var{string} specifies the text to put in
3891 the buffer to hold the image.
3893 The argument @var{area} specifies whether to put the image in a margin.
3894 If it is @code{left-margin}, the image appears in the left margin;
3895 @code{right-margin} specifies the right margin. If @var{area} is
3896 @code{nil} or omitted, the image is displayed at point within the
3899 The argument @var{slice} specifies a slice of the image to insert. If
3900 @var{slice} is @code{nil} or omitted the whole image is inserted.
3901 Otherwise, @var{slice} is a list @code{(@var{x} @var{y} @var{width}
3902 @var{height})} which specifies the @var{x} and @var{y} positions and
3903 @var{width} and @var{height} of the image area to insert. Integer
3904 values are in units of pixels. A floating point number in the range
3905 0.0--1.0 stands for that fraction of the width or height of the entire
3908 Internally, this function inserts @var{string} in the buffer, and gives
3909 it a @code{display} property which specifies @var{image}. @xref{Display
3913 @defun insert-sliced-image image &optional string area rows cols
3914 This function inserts @var{image} in the current buffer at point, like
3915 @code{insert-image}, but splits the image into @var{rows}x@var{cols}
3916 equally sized slices.
3919 @defun put-image image pos &optional string area
3920 This function puts image @var{image} in front of @var{pos} in the
3921 current buffer. The argument @var{pos} should be an integer or a
3922 marker. It specifies the buffer position where the image should appear.
3923 The argument @var{string} specifies the text that should hold the image
3924 as an alternative to the default.
3926 The argument @var{image} must be an image descriptor, perhaps returned
3927 by @code{create-image} or stored by @code{defimage}.
3929 The argument @var{area} specifies whether to put the image in a margin.
3930 If it is @code{left-margin}, the image appears in the left margin;
3931 @code{right-margin} specifies the right margin. If @var{area} is
3932 @code{nil} or omitted, the image is displayed at point within the
3935 Internally, this function creates an overlay, and gives it a
3936 @code{before-string} property containing text that has a @code{display}
3937 property whose value is the image. (Whew!)
3940 @defun remove-images start end &optional buffer
3941 This function removes images in @var{buffer} between positions
3942 @var{start} and @var{end}. If @var{buffer} is omitted or @code{nil},
3943 images are removed from the current buffer.
3945 This removes only images that were put into @var{buffer} the way
3946 @code{put-image} does it, not images that were inserted with
3947 @code{insert-image} or in other ways.
3950 @defun image-size spec &optional pixels frame
3952 This function returns the size of an image as a pair
3953 @w{@code{(@var{width} . @var{height})}}. @var{spec} is an image
3954 specification. @var{pixels} non-@code{nil} means return sizes
3955 measured in pixels, otherwise return sizes measured in canonical
3956 character units (fractions of the width/height of the frame's default
3957 font). @var{frame} is the frame on which the image will be displayed.
3958 @var{frame} null or omitted means use the selected frame (@pxref{Input
3963 @subsection Image Cache
3965 Emacs stores images in an image cache when it displays them, so it can
3966 display them again more efficiently. It removes an image from the cache
3967 when it hasn't been displayed for a specified period of time.
3969 When an image is looked up in the cache, its specification is compared
3970 with cached image specifications using @code{equal}. This means that
3971 all images with equal specifications share the same image in the cache.
3973 @defvar image-cache-eviction-delay
3974 @tindex image-cache-eviction-delay
3975 This variable specifies the number of seconds an image can remain in the
3976 cache without being displayed. When an image is not displayed for this
3977 length of time, Emacs removes it from the image cache.
3979 If the value is @code{nil}, Emacs does not remove images from the cache
3980 except when you explicitly clear it. This mode can be useful for
3984 @defun clear-image-cache &optional frame
3985 @tindex clear-image-cache
3986 This function clears the image cache. If @var{frame} is non-@code{nil},
3987 only the cache for that frame is cleared. Otherwise all frames' caches
3994 @cindex buttons in buffers
3995 @cindex clickable buttons in buffers
3997 The @emph{button} package defines functions for inserting and
3998 manipulating clickable (with the mouse, or via keyboard commands)
3999 buttons in Emacs buffers, such as might be used for help hyper-links,
4000 etc. Emacs uses buttons for the hyper-links in help text and the like.
4002 A button is essentially a set of properties attached (via text
4003 properties or overlays) to a region of text in an Emacs buffer, which
4004 are called its button properties. @xref{Button Properties}.
4006 One of the these properties (@code{action}) is a function, which will
4007 be called when the user invokes it using the keyboard or the mouse.
4008 The invoked function may then examine the button and use its other
4009 properties as desired.
4011 In some ways the Emacs button package duplicates functionality offered
4012 by the widget package (@pxref{Top, , Introduction, widget, The Emacs
4013 Widget Library}), but the button package has the advantage that it is
4014 much faster, much smaller, and much simpler to use (for elisp
4015 programmers---for users, the result is about the same). The extra
4016 speed and space savings are useful mainly if you need to create many
4017 buttons in a buffer (for instance an @code{*Apropos*} buffer uses
4018 buttons to make entries clickable, and may contain many thousands of
4022 * Button Properties:: Button properties with special meanings.
4023 * Button Types:: Defining common properties for classes of buttons.
4024 * Making Buttons:: Adding buttons to Emacs buffers.
4025 * Manipulating Buttons:: Getting and setting properties of buttons.
4026 * Button Buffer Commands:: Buffer-wide commands and bindings for buttons.
4027 * Manipulating Button Types::
4030 @node Button Properties
4031 @subsection Button Properties
4032 @cindex button properties
4034 Buttons have an associated list of properties defining their
4035 appearance and behavior, and other arbitrary properties may be used
4036 for application specific purposes.
4038 Some properties that have special meaning to the button package
4044 @kindex action @r{(button property)}
4045 The function to call when the user invokes the button, which is passed
4046 the single argument @var{button}. By default this is @code{ignore},
4050 @kindex mouse-action @r{(button property)}
4051 This is similar to @code{action}, and when present, will be used
4052 instead of @code{action} for button invocations resulting from
4053 mouse-clicks (instead of the user hitting @key{RET}). If not
4054 present, mouse-clicks use @code{action} instead.
4057 @kindex face @r{(button property)}
4058 This is an Emacs face controlling how buttons of this type are
4059 displayed; by default this is the @code{button} face.
4062 @kindex mouse-face @r{(button property)}
4063 This is an additional face which controls appearance during
4064 mouse-overs (merged with the usual button face); by default this is
4065 the usual Emacs @code{highlight} face.
4068 @kindex keymap @r{(button property)}
4069 The button's keymap, defining bindings active within the button
4070 region. By default this is the usual button region keymap, stored
4071 in the variable @code{button-map}, which defines @key{RET} and
4072 @key{mouse-2} to invoke the button.
4075 @kindex type @r{(button property)}
4076 The button-type of the button. When creating a button, this is
4077 usually specified using the @code{:type} keyword argument.
4078 @xref{Button Types}.
4081 @kindex help-index @r{(button property)}
4082 A string displayed by the Emacs tool-tip help system; by default,
4083 @code{"mouse-2, RET: Push this button"}.
4086 @kindex follow-link @r{(button property)}
4087 The follow-link property, defining how a @key{Mouse-1} click behaves
4088 on this button, @xref{Links and Mouse-1}.
4091 @kindex button @r{(button property)}
4092 All buttons have a non-@code{nil} @code{button} property, which may be useful
4093 in finding regions of text that comprise buttons (which is what the
4094 standard button functions do).
4097 There are other properties defined for the regions of text in a
4098 button, but these are not generally interesting for typical uses.
4101 @subsection Button Types
4102 @cindex button types
4104 Every button has a button @emph{type}, which defines default values
4105 for the button's properties. Button types are arranged in a
4106 hierarchy, with specialized types inheriting from more general types,
4107 so that it's easy to define special-purpose types of buttons for
4110 @defun define-button-type name &rest properties
4111 @tindex define-button-type
4112 Define a `button type' called @var{name}. The remaining arguments
4113 form a sequence of @var{property value} pairs, specifying default
4114 property values for buttons with this type (a button's type may be set
4115 by giving it a @code{type} property when creating the button, using
4116 the @code{:type} keyword argument).
4118 In addition, the keyword argument @code{:supertype} may be used to
4119 specify a button-type from which @var{name} inherits its default
4120 property values. Note that this inheritance happens only when
4121 @var{name} is defined; subsequent changes to a supertype are not
4122 reflected in its subtypes.
4125 Using @code{define-button-type} to define default properties for
4126 buttons is not necessary---buttons without any specified type use the
4127 built-in button-type @code{button}---but it is is encouraged, since
4128 doing so usually makes the resulting code clearer and more efficient.
4130 @node Making Buttons
4131 @subsection Making Buttons
4132 @cindex making buttons
4134 Buttons are associated with a region of text, using an overlay or
4135 text-properties to hold button-specific information, all of which are
4136 initialized from the button's type (which defaults to the built-in
4137 button type @code{button}). Like all Emacs text, the appearance of
4138 the button is governed by the @code{face} property; by default (via
4139 the @code{face} property inherited from the @code{button} button-type)
4140 this is a simple underline, like a typical web-page link.
4142 For convenience, there are two sorts of button-creation functions,
4143 those that add button properties to an existing region of a buffer,
4144 called @code{make-...button}, and those also insert the button text,
4145 called @code{insert-...button}.
4147 The button-creation functions all take the @code{&rest} argument
4148 @var{properties}, which should be a sequence of @var{property value}
4149 pairs, specifying properties to add to the button; see @ref{Button
4150 Properties}. In addition, the keyword argument @code{:type} may be
4151 used to specify a button-type from which to inherit other properties;
4152 see @ref{Button Types}. Any properties not explicitly specified
4153 during creation will be inherited from the button's type (if the type
4154 defines such a property).
4156 The following functions add a button using an overlay
4157 (@pxref{Overlays}) to hold the button properties:
4159 @defun make-button beg end &rest properties
4161 Make a button from @var{beg} to @var{end} in the current buffer.
4164 @defun insert-button label &rest properties
4165 @tindex insert-button
4166 Insert a button with the label @var{label}.
4169 The following functions are similar, but use Emacs text-properties
4170 (@pxref{Text Properties}) to hold the button properties, making the
4171 button actually part of the text instead of being a property of the
4172 buffer (using text-properties is usually faster than using overlays,
4173 so this may be preferable when creating large numbers of buttons):
4175 @defun make-text-button beg end &rest properties
4176 @tindex make-text-button
4177 Make a button from @var{beg} to @var{end} in the current buffer, using
4181 @defun insert-text-button label &rest properties
4182 @tindex insert-text-button
4183 Insert a button with the label @var{label}, using text-properties.
4186 Buttons using text-properties retain no markers into the buffer are
4187 retained, which is important for speed in cases where there are
4188 extremely large numbers of buttons.
4190 @node Manipulating Buttons
4191 @subsection Manipulating Buttons
4192 @cindex manipulating buttons
4194 These are functions for getting and setting properties of buttons.
4195 Often these are used by a button's invocation function to determine
4198 Where a @var{button} parameter is specified, it means an object
4199 referring to a specific button, either an overlay (for overlay
4200 buttons), or a buffer-position or marker (for text property buttons).
4201 Such an object is passed as the first argument to a button's
4202 invocation function when it is invoked.
4204 @defun button-start button
4205 @tindex button-start
4206 Return the position at which @var{button} starts.
4209 @defun button-end button
4211 Return the position at which @var{button} ends.
4214 @defun button-get button prop
4216 Get the property of button @var{button} named @var{prop}.
4219 @defun button-put button prop val
4221 Set @var{button}'s @var{prop} property to @var{val}.
4224 @defun button-activate button &optional use-mouse-action
4225 @tindex button-activate
4226 Call @var{button}'s @code{action} property (i.e., invoke it). If
4227 @var{use-mouse-action} is non-@code{nil}, try to invoke the button's
4228 @code{mouse-action} property instead of @code{action}; if the button
4229 has no @code{mouse-action} property, use @code{action} as normal.
4232 @defun button-label button
4233 @tindex button-label
4234 Return @var{button}'s text label.
4237 @defun button-type button
4239 Return @var{button}'s button-type.
4242 @defun button-has-type-p button type
4243 @tindex button-has-type-p
4244 Return @code{t} if @var{button} has button-type @var{type}, or one of
4245 @var{type}'s subtypes.
4248 @defun button-at pos
4250 Return the button at position @var{pos} in the current buffer, or @code{nil}.
4253 @node Button Buffer Commands
4254 @subsection Button Buffer Commands
4255 @cindex button buffer commands
4257 These are commands and functions for locating and operating on
4258 buttons in an Emacs buffer.
4260 @code{push-button} is the command that a user uses to actually `push'
4261 a button, and is bound by default in the button itself to @key{RET}
4262 and to @key{mouse-2} using a region-specific keymap. Commands
4263 that are useful outside the buttons itself, such as
4264 @code{forward-button} and @code{backward-button} are additionally
4265 available in the keymap stored in @code{button-buffer-map}; a mode
4266 which uses buttons may want to use @code{button-buffer-map} as a
4267 parent keymap for its keymap.
4269 If the button has a non-@code{nil} @code{follow-link} property, and
4270 @var{mouse-1-click-follows-link} is set, a @key{Mouse-1} click will
4271 also activate the @code{push-button} command.
4273 @deffn Command push-button &optional pos use-mouse-action
4275 Perform the action specified by a button at location @var{pos}.
4276 @var{pos} may be either a buffer position or a mouse-event. If
4277 @var{use-mouse-action} is non-@code{nil}, or @var{pos} is a
4278 mouse-event (@pxref{Mouse Events}), try to invoke the button's
4279 @code{mouse-action} property instead of @code{action}; if the button
4280 has no @code{mouse-action} property, use @code{action} as normal.
4281 @var{pos} defaults to point, except when @code{push-button} is invoked
4282 interactively as the result of a mouse-event, in which case, the mouse
4283 event's position is used. If there's no button at @var{pos}, do
4284 nothing and return @code{nil}, otherwise return @code{t}.
4287 @deffn Command forward-button n &optional wrap display-message
4288 @tindex forward-button
4289 Move to the @var{n}th next button, or @var{n}th previous button if
4290 @var{n} is negative. If @var{n} is zero, move to the start of any
4291 button at point. If @var{wrap} is non-@code{nil}, moving past either
4292 end of the buffer continues from the other end. If
4293 @var{display-message} is non-@code{nil}, the button's help-echo string
4294 is displayed. Any button with a non-@code{nil} @code{skip} property
4295 is skipped over. Returns the button found.
4298 @deffn Command backward-button n &optional wrap display-message
4299 @tindex backward-button
4300 Move to the @var{n}th previous button, or @var{n}th next button if
4301 @var{n} is negative. If @var{n} is zero, move to the start of any
4302 button at point. If @var{wrap} is non-@code{nil}, moving past either
4303 end of the buffer continues from the other end. If
4304 @var{display-message} is non-@code{nil}, the button's help-echo string
4305 is displayed. Any button with a non-@code{nil} @code{skip} property
4306 is skipped over. Returns the button found.
4309 @defun next-button pos &optional count-current
4311 Return the next button after position @var{pos} in the current buffer.
4312 If @var{count-current} is non-@code{nil}, count any button at
4313 @var{pos} in the search, instead of starting at the next button.
4316 @defun previous-button pos &optional count-current
4317 @tindex previous-button
4318 Return the @var{n}th button before position @var{pos} in the current
4319 buffer. If @var{count-current} is non-@code{nil}, count any button at
4320 @var{pos} in the search, instead of starting at the next button.
4323 @node Manipulating Button Types
4324 @subsection Manipulating Button Types
4325 @cindex manipulating button types
4327 @defun button-type-put type prop val
4328 @tindex button-type-put
4329 Set the button-type @var{type}'s @var{prop} property to @var{val}.
4332 @defun button-type-get type prop
4333 @tindex button-type-get
4334 Get the property of button-type @var{type} named @var{prop}.
4337 @defun button-type-subtype-p type supertype
4338 @tindex button-type-subtype-p
4339 Return @code{t} if button-type @var{type} is a subtype of @var{supertype}.
4343 @section Blinking Parentheses
4344 @cindex parenthesis matching
4346 @cindex balancing parentheses
4347 @cindex close parenthesis
4349 This section describes the mechanism by which Emacs shows a matching
4350 open parenthesis when the user inserts a close parenthesis.
4352 @defvar blink-paren-function
4353 The value of this variable should be a function (of no arguments) to
4354 be called whenever a character with close parenthesis syntax is inserted.
4355 The value of @code{blink-paren-function} may be @code{nil}, in which
4356 case nothing is done.
4359 @defopt blink-matching-paren
4360 If this variable is @code{nil}, then @code{blink-matching-open} does
4364 @defopt blink-matching-paren-distance
4365 This variable specifies the maximum distance to scan for a matching
4366 parenthesis before giving up.
4369 @defopt blink-matching-delay
4370 This variable specifies the number of seconds for the cursor to remain
4371 at the matching parenthesis. A fraction of a second often gives
4372 good results, but the default is 1, which works on all systems.
4375 @deffn Command blink-matching-open
4376 This function is the default value of @code{blink-paren-function}. It
4377 assumes that point follows a character with close parenthesis syntax and
4378 moves the cursor momentarily to the matching opening character. If that
4379 character is not already on the screen, it displays the character's
4380 context in the echo area. To avoid long delays, this function does not
4381 search farther than @code{blink-matching-paren-distance} characters.
4383 Here is an example of calling this function explicitly.
4387 (defun interactive-blink-matching-open ()
4388 @c Do not break this line! -- rms.
4389 @c The first line of a doc string
4390 @c must stand alone.
4391 "Indicate momentarily the start of sexp before point."
4395 (let ((blink-matching-paren-distance
4397 (blink-matching-paren t))
4398 (blink-matching-open)))
4404 @section Inverse Video
4405 @cindex Inverse Video
4407 @defopt inverse-video
4408 @cindex highlighting
4409 This variable controls whether Emacs uses inverse video for all text
4410 on the screen. Non-@code{nil} means yes, @code{nil} means no. The
4411 default is @code{nil}.
4414 @defopt mode-line-inverse-video
4415 This variable controls the use of inverse video for mode lines and menu
4416 bars. If it is non-@code{nil}, then these lines are displayed in
4417 inverse video. Otherwise, these lines are displayed normally, just like
4418 other text. The default is @code{t}.
4420 For window frames, this feature actually applies the face named
4421 @code{mode-line}; that face is normally set up as the inverse of the
4422 default face, unless you change it.
4426 @section Usual Display Conventions
4428 The usual display conventions define how to display each character
4429 code. You can override these conventions by setting up a display table
4430 (@pxref{Display Tables}). Here are the usual display conventions:
4434 Character codes 32 through 126 map to glyph codes 32 through 126.
4435 Normally this means they display as themselves.
4438 Character code 9 is a horizontal tab. It displays as whitespace
4439 up to a position determined by @code{tab-width}.
4442 Character code 10 is a newline.
4445 All other codes in the range 0 through 31, and code 127, display in one
4446 of two ways according to the value of @code{ctl-arrow}. If it is
4447 non-@code{nil}, these codes map to sequences of two glyphs, where the
4448 first glyph is the @acronym{ASCII} code for @samp{^}. (A display table can
4449 specify a glyph to use instead of @samp{^}.) Otherwise, these codes map
4450 just like the codes in the range 128 to 255.
4452 On MS-DOS terminals, Emacs arranges by default for the character code
4453 127 to be mapped to the glyph code 127, which normally displays as an
4454 empty polygon. This glyph is used to display non-@acronym{ASCII} characters
4455 that the MS-DOS terminal doesn't support. @xref{MS-DOS and MULE,,,
4456 emacs, The GNU Emacs Manual}.
4459 Character codes 128 through 255 map to sequences of four glyphs, where
4460 the first glyph is the @acronym{ASCII} code for @samp{\}, and the others are
4461 digit characters representing the character code in octal. (A display
4462 table can specify a glyph to use instead of @samp{\}.)
4465 Multibyte character codes above 256 are displayed as themselves, or as a
4466 question mark or empty box if the terminal cannot display that
4470 The usual display conventions apply even when there is a display
4471 table, for any character whose entry in the active display table is
4472 @code{nil}. Thus, when you set up a display table, you need only
4473 specify the characters for which you want special behavior.
4475 These display rules apply to carriage return (character code 13), when
4476 it appears in the buffer. But that character may not appear in the
4477 buffer where you expect it, if it was eliminated as part of end-of-line
4478 conversion (@pxref{Coding System Basics}).
4480 These variables affect the way certain characters are displayed on the
4481 screen. Since they change the number of columns the characters occupy,
4482 they also affect the indentation functions. These variables also affect
4483 how the mode line is displayed; if you want to force redisplay of the
4484 mode line using the new values, call the function
4485 @code{force-mode-line-update} (@pxref{Mode Line Format}).
4488 @cindex control characters in display
4489 This buffer-local variable controls how control characters are
4490 displayed. If it is non-@code{nil}, they are displayed as a caret
4491 followed by the character: @samp{^A}. If it is @code{nil}, they are
4492 displayed as a backslash followed by three octal digits: @samp{\001}.
4495 @c Following may have overfull hbox.
4496 @defvar default-ctl-arrow
4497 The value of this variable is the default value for @code{ctl-arrow} in
4498 buffers that do not override it. @xref{Default Value}.
4502 The value of this variable is the spacing between tab stops used for
4503 displaying tab characters in Emacs buffers. The value is in units of
4504 columns, and the default is 8. Note that this feature is completely
4505 independent of the user-settable tab stops used by the command
4506 @code{tab-to-tab-stop}. @xref{Indent Tabs}.
4509 @defopt indicate-empty-lines
4510 @tindex indicate-empty-lines
4511 @cindex fringes, and empty line indication
4512 When this is non-@code{nil}, Emacs displays a special glyph in the
4513 fringe of each empty line at the end of the buffer, on terminals that
4514 support it (window systems). @xref{Fringes}.
4517 @defvar indicate-buffer-boundaries
4518 This buffer-local variable controls how the buffer boundaries and
4519 window scrolling are indicated in the window fringes.
4521 Emacs can indicate the buffer boundaries---that is, the first and last
4522 line in the buffer---with angle icons when they appear on the screen.
4523 In addition, Emacs can display an up-arrow in the fringe to show
4524 that there is text above the screen, and a down-arrow to show
4525 there is text below the screen.
4527 There are four kinds of basic values:
4531 Don't display the icons.
4533 Display them in the left fringe.
4535 Display them in the right fringe.
4536 @item @var{anything-else}
4537 Display the icon at the top of the window top in the left fringe, and other
4538 in the right fringe.
4541 If value is a cons @code{(@var{angles} . @var{arrows})}, @var{angles}
4542 controls the angle icons, and @var{arrows} controls the arrows. Both
4543 @var{angles} and @var{arrows} work according to the table above.
4544 Thus, @code{(t . right)} places the top angle icon in the left
4545 fringe, the bottom angle icon in the right fringe, and both arrows in
4549 @defvar default-indicate-buffer-boundaries
4550 The value of this variable is the default value for
4551 @code{indicate-buffer-boundaries} in buffers that do not override it.
4554 @node Display Tables
4555 @section Display Tables
4557 @cindex display table
4558 You can use the @dfn{display table} feature to control how all possible
4559 character codes display on the screen. This is useful for displaying
4560 European languages that have letters not in the @acronym{ASCII} character
4563 The display table maps each character code into a sequence of
4564 @dfn{glyphs}, each glyph being a graphic that takes up one character
4565 position on the screen. You can also define how to display each glyph
4566 on your terminal, using the @dfn{glyph table}.
4568 Display tables affect how the mode line is displayed; if you want to
4569 force redisplay of the mode line using a new display table, call
4570 @code{force-mode-line-update} (@pxref{Mode Line Format}).
4573 * Display Table Format:: What a display table consists of.
4574 * Active Display Table:: How Emacs selects a display table to use.
4575 * Glyphs:: How to define a glyph, and what glyphs mean.
4578 @node Display Table Format
4579 @subsection Display Table Format
4581 A display table is actually a char-table (@pxref{Char-Tables}) with
4582 @code{display-table} as its subtype.
4584 @defun make-display-table
4585 This creates and returns a display table. The table initially has
4586 @code{nil} in all elements.
4589 The ordinary elements of the display table are indexed by character
4590 codes; the element at index @var{c} says how to display the character
4591 code @var{c}. The value should be @code{nil} or a vector of glyph
4592 values (@pxref{Glyphs}). If an element is @code{nil}, it says to
4593 display that character according to the usual display conventions
4594 (@pxref{Usual Display}).
4596 If you use the display table to change the display of newline
4597 characters, the whole buffer will be displayed as one long ``line.''
4599 The display table also has six ``extra slots'' which serve special
4600 purposes. Here is a table of their meanings; @code{nil} in any slot
4601 means to use the default for that slot, as stated below.
4605 The glyph for the end of a truncated screen line (the default for this
4606 is @samp{$}). @xref{Glyphs}. Newer Emacs versions, on some platforms,
4607 display arrows to indicate truncation---the display table has no effect
4608 in these situations.
4610 The glyph for the end of a continued line (the default is @samp{\}).
4611 Newer Emacs versions, on some platforms, display curved arrows to
4612 indicate continuation---the display table has no effect in these
4615 The glyph for indicating a character displayed as an octal character
4616 code (the default is @samp{\}).
4618 The glyph for indicating a control character (the default is @samp{^}).
4620 A vector of glyphs for indicating the presence of invisible lines (the
4621 default is @samp{...}). @xref{Selective Display}.
4623 The glyph used to draw the border between side-by-side windows (the
4624 default is @samp{|}). @xref{Splitting Windows}. This takes effect only
4625 when there are no scroll bars; if scroll bars are supported and in use,
4626 a scroll bar separates the two windows.
4629 For example, here is how to construct a display table that mimics the
4630 effect of setting @code{ctl-arrow} to a non-@code{nil} value:
4633 (setq disptab (make-display-table))
4636 (or (= i ?\t) (= i ?\n)
4637 (aset disptab i (vector ?^ (+ i 64))))
4639 (aset disptab 127 (vector ?^ ??)))
4642 @defun display-table-slot display-table slot
4643 This function returns the value of the extra slot @var{slot} of
4644 @var{display-table}. The argument @var{slot} may be a number from 0 to
4645 5 inclusive, or a slot name (symbol). Valid symbols are
4646 @code{truncation}, @code{wrap}, @code{escape}, @code{control},
4647 @code{selective-display}, and @code{vertical-border}.
4650 @defun set-display-table-slot display-table slot value
4651 This function stores @var{value} in the extra slot @var{slot} of
4652 @var{display-table}. The argument @var{slot} may be a number from 0 to
4653 5 inclusive, or a slot name (symbol). Valid symbols are
4654 @code{truncation}, @code{wrap}, @code{escape}, @code{control},
4655 @code{selective-display}, and @code{vertical-border}.
4658 @defun describe-display-table display-table
4659 @tindex describe-display-table
4660 This function displays a description of the display table
4661 @var{display-table} in a help buffer.
4664 @deffn Command describe-current-display-table
4665 @tindex describe-current-display-table
4666 This command displays a description of the current display table in a
4670 @node Active Display Table
4671 @subsection Active Display Table
4672 @cindex active display table
4674 Each window can specify a display table, and so can each buffer. When
4675 a buffer @var{b} is displayed in window @var{w}, display uses the
4676 display table for window @var{w} if it has one; otherwise, the display
4677 table for buffer @var{b} if it has one; otherwise, the standard display
4678 table if any. The display table chosen is called the @dfn{active}
4681 @defun window-display-table window
4682 This function returns @var{window}'s display table, or @code{nil}
4683 if @var{window} does not have an assigned display table.
4686 @defun set-window-display-table window table
4687 This function sets the display table of @var{window} to @var{table}.
4688 The argument @var{table} should be either a display table or
4692 @defvar buffer-display-table
4693 This variable is automatically buffer-local in all buffers; its value in
4694 a particular buffer specifies the display table for that buffer. If it
4695 is @code{nil}, that means the buffer does not have an assigned display
4699 @defvar standard-display-table
4700 This variable's value is the default display table, used whenever a
4701 window has no display table and neither does the buffer displayed in
4702 that window. This variable is @code{nil} by default.
4705 If there is no display table to use for a particular window---that is,
4706 if the window specifies none, its buffer specifies none, and
4707 @code{standard-display-table} is @code{nil}---then Emacs uses the usual
4708 display conventions for all character codes in that window. @xref{Usual
4711 A number of functions for changing the standard display table
4712 are defined in the library @file{disp-table}.
4718 A @dfn{glyph} is a generalization of a character; it stands for an
4719 image that takes up a single character position on the screen. Glyphs
4720 are represented in Lisp as integers, just as characters are. Normally
4721 Emacs finds glyphs in the display table (@pxref{Display Tables}).
4723 A glyph can be @dfn{simple} or it can be defined by the @dfn{glyph
4724 table}. A simple glyph is just a way of specifying a character and a
4725 face to output it in. The glyph code for a simple glyph, mod 524288,
4726 is the character to output, and the glyph code divided by 524288
4727 specifies the face number (@pxref{Face Functions}) to use while
4728 outputting it. (524288 is
4737 On character terminals, you can set up a @dfn{glyph table} to define
4738 the meaning of glyph codes. The glyph codes is the value of the
4739 variable @code{glyph-table}.
4742 The value of this variable is the current glyph table. It should be a
4743 vector; the @var{g}th element defines glyph code @var{g}.
4745 If a glyph code is greater than or equal to the length of the glyph
4746 table, that code is automatically simple. If the value of
4747 @code{glyph-table} is @code{nil} instead of a vector, then all glyphs
4748 are simple. The glyph table is not used on graphical displays, only
4749 on character terminals. On graphical displays, all glyphs are simple.
4752 Here are the possible types of elements in the glyph table:
4756 Send the characters in @var{string} to the terminal to output
4757 this glyph. This alternative is available on character terminals,
4758 but not under a window system.
4761 Define this glyph code as an alias for glyph code @var{integer}. You
4762 can use an alias to specify a face code for the glyph and use a small
4766 This glyph is simple.
4769 @defun create-glyph string
4770 @tindex create-glyph
4771 This function returns a newly-allocated glyph code which is set up to
4772 display by sending @var{string} to the terminal.
4780 This section describes how to make Emacs ring the bell (or blink the
4781 screen) to attract the user's attention. Be conservative about how
4782 often you do this; frequent bells can become irritating. Also be
4783 careful not to use just beeping when signaling an error is more
4784 appropriate. (@xref{Errors}.)
4786 @defun ding &optional do-not-terminate
4787 @cindex keyboard macro termination
4788 This function beeps, or flashes the screen (see @code{visible-bell} below).
4789 It also terminates any keyboard macro currently executing unless
4790 @var{do-not-terminate} is non-@code{nil}.
4793 @defun beep &optional do-not-terminate
4794 This is a synonym for @code{ding}.
4797 @defopt visible-bell
4798 This variable determines whether Emacs should flash the screen to
4799 represent a bell. Non-@code{nil} means yes, @code{nil} means no. This
4800 is effective on a window system, and on a character-only terminal
4801 provided the terminal's Termcap entry defines the visible bell
4802 capability (@samp{vb}).
4805 @defvar ring-bell-function
4806 If this is non-@code{nil}, it specifies how Emacs should ``ring the
4807 bell.'' Its value should be a function of no arguments. If this is
4808 non-@code{nil}, it takes precedence over the @code{visible-bell}
4812 @node Window Systems
4813 @section Window Systems
4815 Emacs works with several window systems, most notably the X Window
4816 System. Both Emacs and X use the term ``window'', but use it
4817 differently. An Emacs frame is a single window as far as X is
4818 concerned; the individual Emacs windows are not known to X at all.
4820 @defvar window-system
4821 This variable tells Lisp programs what window system Emacs is running
4822 under. The possible values are
4826 @cindex X Window System
4827 Emacs is displaying using X.
4829 Emacs is displaying using MS-DOS.
4831 Emacs is displaying using Windows.
4833 Emacs is displaying using a Macintosh.
4835 Emacs is using a character-based terminal.
4839 @defvar window-setup-hook
4840 This variable is a normal hook which Emacs runs after handling the
4841 initialization files. Emacs runs this hook after it has completed
4842 loading your init file, the default initialization file (if
4843 any), and the terminal-specific Lisp code, and running the hook
4844 @code{term-setup-hook}.
4846 This hook is used for internal purposes: setting up communication with
4847 the window system, and creating the initial window. Users should not
4852 arch-tag: ffdf5714-7ecf-415b-9023-fbc6b409c2c6