This chapter describes a number of features related to the display that Emacs presents to the user.
display PropertyThe function redraw-frame clears and redisplays the entire
contents of a given frame (see Frames). This is useful if the
screen is corrupted.
This function clears and redisplays frame frame. If frame
is omitted or nil, it redraws the selected frame.
Even more powerful is redraw-display:
This function clears and redisplays all visible frames.
In Emacs, processing user input takes priority over redisplay. If you call these functions when input is available, they don’t redisplay immediately, but the requested redisplay does happen eventually—after all the input has been processed.
On text terminals, suspending and resuming Emacs normally also refreshes the screen. Some terminal emulators record separate contents for display-oriented programs such as Emacs and for ordinary sequential display. If you are using such a terminal, you might want to inhibit the redisplay on resumption.
This variable controls whether Emacs redraws the entire screen after it
has been suspended and resumed. Non-nil means there is no need
to redraw, nil means redrawing is needed. The default is nil.
Emacs normally tries to redisplay the screen whenever it waits for input. With the following function, you can request an immediate attempt to redisplay, in the middle of Lisp code, without actually waiting for input.
This function tries immediately to redisplay. The optional argument
force, if non-nil, forces the redisplay to be performed,
instead of being preempted if input is pending.
The function returns t if it actually tried to redisplay, and
nil otherwise. A value of t does not mean that
redisplay proceeded to completion; it could have been preempted by
newly arriving input.
Although redisplay tries immediately to redisplay, it does
not change how Emacs decides which parts of its frame(s) to redisplay.
By contrast, the following function adds certain windows to the
pending redisplay work (as if their contents had completely changed),
but does not immediately try to perform redisplay.
This function forces some or all windows to be updated the next time
Emacs does a redisplay. If object is a window, that window is
to be updated. If object is a buffer or buffer name, all
windows displaying that buffer are to be updated. If object is
nil (or omitted), all windows are to be updated.
This function does not do a redisplay immediately; Emacs does that as
it waits for input, or when the function redisplay is called.
A function run just before redisplay. It is called with one argument,
the set of windows to be redisplayed. The set can be nil,
meaning only the selected window, or t, meaning all the
windows.
This hook is run just before redisplay. It is called once in each
window that is about to be redisplayed, with current-buffer set
to the buffer displayed in that window.
When a line of text extends beyond the right edge of a window, Emacs can continue the line (make it wrap to the next screen line), or truncate the line (limit it to one screen line). The additional screen lines used to display a long text line are called continuation lines. Continuation is not the same as filling; continuation happens on the screen only, not in the buffer contents, and it breaks a line precisely at the right margin, not at a word boundary. See Filling.
On a graphical display, tiny arrow images in the window fringes
indicate truncated and continued lines (see Fringes). On a text
terminal, and on a graphical display when fringe-mode was
turned off, a ‘$’ in the rightmost column of the window indicates
truncation; a ‘\’ on the rightmost column indicates a line that
wraps. (The display table can specify alternate characters to use
for this; see Display Tables).
Since wrapping and truncation of text contradict each other, Emacs turns off line truncation when wrapping is requested, and vice versa.
If this buffer-local variable is non-nil, lines that extend
beyond the right edge of the window are truncated; otherwise, they are
continued. As a special exception, the variable
truncate-partial-width-windows takes precedence in
partial-width windows (i.e., windows that do not occupy the
entire frame width).
This variable controls line truncation in partial-width windows.
A partial-width window is one that does not occupy the entire frame
width (see Splitting Windows). If the value is nil, line
truncation is determined by the variable truncate-lines (see
above). If the value is an integer n, lines are truncated if
the partial-width window has fewer than n columns, regardless of
the value of truncate-lines; if the partial-width window has
n or more columns, line truncation is determined by
truncate-lines. For any other non-nil value, lines are
truncated in every partial-width window, regardless of the value of
truncate-lines.
When horizontal scrolling (see Horizontal Scrolling) is in use in a window, that forces truncation.
If this buffer-local variable is non-nil, it defines a
wrap prefix which Emacs displays at the start of every
continuation line. (If lines are truncated, wrap-prefix is
never used.) Its value may be a string or an image (see Other Display Specifications), or a stretch of whitespace such as specified by the
:width or :align-to display properties (see Specified Spaces). The value is interpreted in the same way as a display
text property, with one important difference: the horizontal position
specified by :align-to is measured from the visual beginning of
the screen line. See The display Property.
A wrap prefix may also be specified for regions of text, using the
wrap-prefix text or overlay property. This takes precedence
over the wrap-prefix variable. See Properties with Special Meanings.
If this buffer-local variable is non-nil, it defines a
line prefix which Emacs displays at the start of every
non-continuation line. Its value may be a string or an image
(see Other Display Specifications), or a stretch of whitespace such as
specified by the :width or :align-to display properties
(see Specified Spaces). The value is interpreted in the same way
as a display text property. See The display Property.
A line prefix may also be specified for regions of text using the
line-prefix text or overlay property. This takes precedence
over the line-prefix variable. See Properties with Special Meanings.
The echo area is used for displaying error messages
(see Errors), for messages made with the message primitive,
and for echoing keystrokes. It is not the same as the minibuffer,
despite the fact that the minibuffer appears (when active) in the same
place on the screen as the echo area. See The
Minibuffer in The GNU Emacs Manual.
Apart from the functions documented in this section, you can print
Lisp objects to the echo area by specifying t as the output
stream. See Output Streams.
This section describes the standard functions for displaying messages in the echo area.
This function displays a message in the echo area.
format-string is a format string, and arguments are the
objects for its format specifications, like in the format-message
function (see Formatting Strings). The resulting formatted string
is displayed in the echo area; if it contains face text
properties, it is displayed with the specified faces (see Faces).
The string is also added to the *Messages* buffer, but without
text properties (see Logging Messages in *Messages*).
Typically grave accent and apostrophe in the format translate to
matching curved quotes, e.g., "Missing `%s'" might result in
"Missing ‘foo’". See Text Quoting Style, for how to influence
or inhibit this translation.
In batch mode, the message is printed to the standard error stream, followed by a newline.
When inhibit-message is non-nil, no message will be displayed
in the echo area, it will only be logged to ‘*Messages*’.
If format-string is nil or the empty string,
message clears the echo area; if the echo area has been
expanded automatically, this brings it back to its normal size. If
the minibuffer is active, this brings the minibuffer contents back
onto the screen immediately.
(message "Reverting `%s'..." (buffer-name)) ⊣ Reverting ‘subr.el’... ⇒ "Reverting ‘subr.el’..."
---------- Echo Area ---------- Reverting ‘subr.el’... ---------- Echo Area ----------
To automatically display a message in the echo area or in a pop-buffer,
depending on its size, use display-message-or-buffer (see below).
Warning: If you want to use your own string as a message
verbatim, don’t just write (message string). If
string contains ‘%’, ‘`’, or ‘'’ it may be
reformatted, with undesirable results. Instead, use (message
"%s" string).
The following facilities allow users and Lisp programs to control how echo-area messages are displayed.
If this variable is non-nil, it should be a function of one
argument, the text of a message to display in the echo area. That
function will be called by message and related functions. If
the function returns nil, the message is displayed in the echo
area as usual. If the function returns a string, that string is
displayed in the echo area instead of the original message. If
the function returns any other non-nil value, that means the
message was already handled, so message will not display
anything in the echo area.
The default value calls set-minibuffer-message, described
below.
If this variable is non-nil, it should be a function of no
arguments; message and related functions call it when their
argument message is nil or the empty string, to clear the echo
area.
Usually this function is called when the next input event arrives
after displaying an echo-area message. The function is expected to
clear the message displayed by its counterpart function specified by
set-message-function, but doesn’t have to. If the function
wants the echo area to remain uncleared, it should return the symbol
dont-clear-message; any other value will result in the echo
area being cleared.
The default value is the function that clears the message displayed in an active minibuffer.
The value of this user option is a list of functions to be called for
handling display of echo-area messages. Each function is called with
one argument, the text of the message to display. If the function
returns a string, that string replaces the original message, and the
next function in the list is called with the new message text. If the
function returns nil, the next function in the list is called
with the same text; if the last function in the list returns
nil, the message text is displayed in the echo area. If the
function returns a non-nil value that is not a string, the
message is considered to be handled, and no further functions in the
list are called.
The three useful functions to be put in the list that is the value of this option are described below.
This function displays message in the echo-area when the
minibuffer is not active, and at the end of the minibuffer when the
minibuffer is active. However, if the text shown in the active
minibuffer has the minibuffer-message text property
(see Properties with Special Meanings) on some character, the message will be
displayed before the first character having that property.
This function is by default the only member of the list in
set-message-functions.
If an echo-area message matches any regexp in the list that is
the value of the user option inhibit-message-regexps, this
function suppresses the display of that message and returns a
non-nil value that is not a string. Thus, if this function is
in the list set-message-functions, the rest of the functions in
the list will not be called when message matches the regexps in
inhibit-message-regexps. To ensure a matching message
will never be displayed, make this function be the first element of
the list in set-message-functions.
This function accumulates several echo-area messages emitted one after
another, and returns them as a single string in which individual
messages are separated by newlines. Up to multi-message-max
recent messages can be accumulated. The accumulated messages are
discarded when more than multi-message-timeout seconds have
elapsed since the time the first message was emitted.
When this variable is non-nil, message and related functions
will not display any messages in the Echo Area, and will also not clear
previous echo-area messages when message is called with a
nil or an empty argument. Echo-area messages are still logged in
the *Messages* buffer, though.
This construct displays a message in the echo area temporarily, during the execution of body. It displays message, executes body, then returns the value of the last body form while restoring the previous echo area contents.
This function displays a message like message, but may display it
in a dialog box instead of the echo area. If this function is called in
a command that was invoked using the mouse—more precisely, if
last-nonmenu-event (see Information from the Command Loop) is either
nil or a list—then it uses a dialog box or pop-up menu to
display the message. Otherwise, it uses the echo area. (This is the
same criterion that y-or-n-p uses to make a similar decision; see
Yes-or-No Queries.)
You can force use of the mouse or of the echo area by binding
last-nonmenu-event to a suitable value around the call.
This function displays a message like message, but uses a dialog
box (or a pop-up menu) whenever that is possible. If it is impossible
to use a dialog box or pop-up menu, because the terminal does not
support them, then message-box uses the echo area, like
message.
This function displays the message message, which may be either a
string or a buffer. If it is shorter than the maximum height of the
echo area, as defined by max-mini-window-height, it is displayed
in the echo area, using message. Otherwise,
display-buffer is used to show it in a pop-up buffer.
Returns either the string shown in the echo area, or when a pop-up buffer is used, the window used to display it.
If message is a string, then the optional argument buffer-name is the name of the buffer used to display it when a pop-up buffer is used, defaulting to *Message*. In the case where message is a string and displayed in the echo area, it is not specified whether the contents are inserted into the buffer anyway.
The optional arguments action and frame are as for
display-buffer, and only used if a buffer is displayed.
This function returns the message currently being displayed in the
echo area, or nil if there is none.
When an operation can take a while to finish, you should inform the user about the progress it makes. This way the user can estimate remaining time and clearly see that Emacs is busy working, not hung. A convenient way to do this is to use a progress reporter.
Here is a working example that does nothing useful:
(let ((progress-reporter
(make-progress-reporter "Collecting mana for Emacs..."
0 500)))
(dotimes (k 500)
(sit-for 0.01)
(progress-reporter-update progress-reporter k))
(progress-reporter-done progress-reporter))
This function creates and returns a progress reporter object, which you will use as an argument for the other functions listed below. The idea is to precompute as much data as possible to make progress reporting very fast.
When this progress reporter is subsequently used, it will display
message in the echo area, followed by progress percentage.
message is treated as a simple string. If you need it to depend
on a filename, for instance, use format-message before calling this
function.
The arguments min-value and max-value should be numbers
standing for the starting and final states of the operation. For
instance, an operation that scans a buffer should set these to the
results of point-min and point-max correspondingly.
max-value should be greater than min-value.
Alternatively, you can set min-value and max-value to
nil. In that case, the progress reporter does not report
process percentages; it instead displays a “spinner” that rotates a
notch each time you update the progress reporter.
If min-value and max-value are numbers, you can give the argument current-value a numerical value specifying the initial progress; if omitted, this defaults to min-value.
The arguments min-change and min-time control the rate of echo area updates. The progress reporter will wait for at least min-change more percents of the operation to be completed before printing next message; the default is one percent. min-time specifies the minimum time in seconds to pass between successive prints; the default is 0.2 seconds. (On some operating systems, the progress reporter may handle fractions of seconds with varying precision).
If context is the symbol async, it announces that the updates
will occur asynchronously. Backends can use that info to prevent the
progress updates from interfering with other data. For example, the
backend that displays the progress in the echo area will not display
those async updates when the echo area is in use.
This function calls progress-reporter-update, so the first
message is printed immediately.
This function does the main work of reporting progress of your operation. It displays the message of reporter, followed by progress percentage determined by value. If percentage is zero, or close enough according to the min-change and min-time arguments, then it is omitted from the output.
reporter must be the result of a call to
make-progress-reporter. value specifies the current
state of your operation and must be between min-value and
max-value (inclusive) as passed to
make-progress-reporter. For instance, if you scan a buffer,
then value should be the result of a call to point.
Optional argument update-text is a string to be displayed after
reporter’s main message and progress text. One typical use is as
the “step” of a long-running process so the user knows where it is.
If reporter is a non-numerical reporter, then value should
be nil, or a string to use instead of update-text.
This function respects min-change and min-time as passed
to make-progress-reporter and so does not output new messages
on every invocation. It is thus very fast and normally you should not
try to reduce the number of calls to it: resulting overhead will most
likely negate your effort.
This function is similar to progress-reporter-update except
that it prints a message in the echo area unconditionally.
reporter, value, and update-text have the same meaning as for
progress-reporter-update. Optional new-message allows
you to change the message of the reporter. Since this function
always updates the echo area, such a change will be immediately
presented to the user.
This function should be called when the operation is finished. It prints the message of reporter followed by word ‘done’ in the echo area.
You should always call this function and not hope for
progress-reporter-update to print ‘100%’. Firstly, it may
never print it, there are many good reasons for this not to happen.
Secondly, ‘done’ is more explicit.
This is a convenience macro that works the same way as dotimes
does, but also reports loop progress using the functions described
above. It allows you to save some typing. The argument
reporter-or-message can be either a string or a progress
reporter object.
You can rewrite the example in the beginning of this subsection using this macro as follows:
(dotimes-with-progress-reporter
(k 500)
"Collecting some mana for Emacs..."
(sit-for 0.01))
Using a reporter object as the reporter-or-message argument is useful if you want to specify the optional arguments in make-progress-reporter. For instance, you can write the previous example as follows:
(dotimes-with-progress-reporter
(k 500)
(make-progress-reporter "Collecting some mana for Emacs..." 0 500 0 1 1.5)
(sit-for 0.01))
This is another convenience macro that works the same way as dolist
does, but also reports loop progress using the functions described
above. As in dotimes-with-progress-reporter,
reporter-or-message can be a progress reporter or a string.
You can rewrite the previous example with this macro as follows:
(dolist-with-progress-reporter
(k (number-sequence 0 500))
"Collecting some mana for Emacs..."
(sit-for 0.01))
Sometimes it’s unclear whether an operation will take a long time to execute or not, or it can be inconvenient to implement a progress reporter. This macro can be used in those situations.
(with-delayed-message (2 (format "Gathering data for %s" entry)) (setq data (gather-data entry)))
In this example, if the body takes more than two seconds to execute, the message will be displayed. If it takes a shorter time than that, the message won’t be displayed. In either case, the body is evaluated as normally, and the return value of the final element in the body is the return value of the macro.
The message element is evaluated before body, and is always evaluated, whether the message is displayed or not.
Almost all the messages displayed in the echo area are also recorded
in the *Messages* buffer so that the user can refer back to
them. This includes all the messages that are output with
message. By default, this buffer is read-only and uses the major
mode messages-buffer-mode. Nothing prevents the user from
killing the *Messages* buffer, but the next display of a message
recreates it. Any Lisp code that needs to access the
*Messages* buffer directly and wants to ensure that it exists
should use the function messages-buffer.
This function returns the *Messages* buffer. If it does not
exist, it creates it, and switches it to messages-buffer-mode.
This variable specifies how many lines to keep in the *Messages*
buffer. The value t means there is no limit on how many lines to
keep. The value nil disables message logging entirely. Here’s
how to display a message and prevent it from being logged:
(let (message-log-max) (message ...))
This variable has the name of the buffer where messages should be
logged to, and defaults to *Messages*. Some packages may find
it useful to temporarily redirect the output to a different buffer
(perhaps to write the buffer out to a log file later), and they can
bind this variable to a different buffer name. (Note that this buffer
(if it doesn’t exist already), will be created and put into
messages-buffer-mode.)
To make *Messages* more convenient for the user, the logging facility combines successive identical messages. It also combines successive related messages for the sake of two cases: question followed by answer, and a series of progress messages.
A question followed by an answer has two messages like the
ones produced by y-or-n-p: the first is ‘question’,
and the second is ‘question...answer’. The first
message conveys no additional information beyond what’s in the second,
so logging the second message discards the first from the log.
A series of progress messages has successive messages like
those produced by make-progress-reporter. They have the form
‘base...how-far’, where base is the same each
time, while how-far varies. Logging each message in the series
discards the previous one, provided they are consecutive.
The functions make-progress-reporter and y-or-n-p
don’t have to do anything special to activate the message log
combination feature. It operates whenever two consecutive messages
are logged that share a common prefix ending in ‘...’.
These variables control details of how the echo area works.
This variable controls where the cursor appears when a message is
displayed in the echo area. If it is non-nil, then the cursor
appears at the end of the message. Otherwise, the cursor appears at
point—not in the echo area at all.
The value is normally nil; Lisp programs bind it to t
for brief periods of time.
This normal hook is run whenever the echo area is cleared—either by
(message nil) or for any other reason.
This variable determines how much time should elapse before command characters echo. Its value must be a number, and specifies the number of seconds to wait before echoing. If the user types a prefix key (such as C-x) and then delays this many seconds before continuing, the prefix key is echoed in the echo area. (Once echoing begins in a key sequence, all subsequent characters in the same key sequence are echoed immediately.)
If the value is zero, then command input is not echoed.
Normally, displaying a long message resizes the echo area to display
the entire message, wrapping long line as needed. But if the variable
message-truncate-lines is non-nil, long lines of
echo-area message are instead truncated to fit the mini-window width.
The variable max-mini-window-height, which specifies the
maximum height for resizing minibuffer windows, also applies to the
echo area (which is really a special use of the minibuffer window;
see Minibuffer Windows).
Warnings are a facility for a program to inform the user of a possible problem, but continue running (as opposed to signaling an error, see Errors).
Every warning is a textual message, which explains the problem for the user, with the associated severity level which is a symbol. Here are the supported severity levels, in order of decreasing severity, and their meanings:
:emergencyA problem that will seriously impair Emacs operation soon if the user does not attend to it promptly.
:errorA report about data or circumstances that are inherently wrong.
:warningA report about data or circumstances that are not inherently wrong, but raise suspicion of a possible problem.
:debugA report of information that may be useful if the user is currently debugging the Lisp program which issues the warning.
When your program encounters invalid input data, it can either
signal a Lisp error by calling error or signal
(see How to Signal an Error) or report a warning with severity
:error. Signaling a Lisp error is the easiest thing to do, but
it means the signaling program cannot continue execution. If you want
to take the trouble of implementing a way to continue processing
despite the invalid data, then reporting a warning of severity
:error is the right way of informing the user of the problem.
For instance, the Emacs Lisp byte compiler can report an error that
way and continue compiling other functions. (If the program signals a
Lisp error and then handles it with condition-case, the user
won’t see the error message; reporting that as a warning instead
avoids that problem.)
In addition to severity level, each warning has a warning type
to classify it. The warning type is either a symbol or a list of
symbols. If it is a symbol, it should be the custom group that you
use for the program’s user options; if it is a list, the first element
of the list should be that custom group. For example, byte compiler
warnings use the warning type (bytecomp). If the warning type
is a list, the elements of the list after the first one, which should
be arbitrary symbols, represent subcategories of the warning: they
will be displayed to the user to better explain the nature of the
warning.
This function reports a warning, using the string message as the
warning text and type as the warning type. level should
be the severity level, and defaults to :warning if omitted or
nil.
buffer-name, if non-nil, specifies the name of the buffer
for logging the warning message. By default, it is *Warnings*.
This function reports a warning using the value returned by
(format-message message args…) as the
message text in the *Warnings* buffer. In other respects it is
equivalent to display-warning.
This function reports a warning using the value returned by
(format-message message args…) as the
message text, emacs as the warning type, and :warning as
the severity level. It exists for compatibility only; we recommend
not using it, because you should specify a specific warning type.
Programs can customize how their warnings appear by binding the variables described in this section.
This list defines the meaning and severity order of the warning severity levels. Each element defines one severity level, and they are arranged in order of decreasing severity.
Each element has the form (level string [function]), where level is the severity level it
defines. string specifies the textual description of this
level. string should use ‘%s’ to specify where to put the
warning type information, or it can omit the ‘%s’ so as not to
include that information.
The optional function, if non-nil, is a function to call
with no arguments, to get the user’s attention. A notable example is
ding (see Beeping).
Normally you should not change the value of this variable.
If non-nil, the value is a function to generate prefix text for
warnings. Programs can bind the variable to a suitable function.
display-warning calls this function with the warnings buffer
the current buffer, and the function can insert text into it. That
text becomes the beginning of the warning message.
The function is called with two arguments, the severity level and its
entry in warning-levels. It should return a list to use
instead of that entry (the value need not be an actual member
of warning-levels, but it must have the same structure). By
constructing this value, the function can change the severity of the
warning, or specify different handling for a given severity level.
If the variable’s value is nil, there’s no prefix text, before
the warning is displayed, starting with the string part of the
entry in warning-levels corresponding to the warning’s level.
Programs can bind this variable to t to say that the next
warning should begin a series. When several warnings form a series,
that means to leave point on the first warning of the series, rather
than keep moving it for each warning so that it appears on the last one.
The series ends when the local binding of this variable is unbound and
warning-series becomes nil again.
The value can also be a symbol with a function definition. That is
equivalent to t, except that the next warning will also call
the function with no arguments with the warnings buffer the current
buffer. The function can, for example, insert text which will serve
as a header for the series of warnings.
Once a series has begun, the value of this variable is a marker which points to the buffer position in the warnings buffer of the start of the series.
The variable’s normal value is nil, which means to handle
each warning separately.
When this variable is non-nil, it specifies a fill prefix to
use for filling the text of each warning.
The column at which to fill warnings.
This variable specifies the format for displaying the warning type
in the warning text. The result of formatting the type this way
gets included in the message under the control of the string in the
entry in warning-levels. The default value is " (%s)".
If you bind it to the empty string "" then the warning type
won’t appear at all.
These variables are used by users to control what happens when a Lisp program reports a warning.
This user option controls the window in which the warnings buffer is
shown. By default, the value is t, and Emacs displays the
warnings buffer in a window at the bottom of the selected frame,
creating a new window there if needed. If customized to nil, the
warnings buffer will be shown using the default rules of
display-buffer (see Choosing a Window for Displaying a Buffer); in that case the
warning category can be used in display-buffer-alist to
customize how display-buffer will display these buffers
(see Action Alists for Buffer Display).
This user option specifies the minimum severity level that should be
shown immediately to the user, by popping the warnings buffer in some
window. The default is :warning, which means to show the
warning buffer for any warning severity except :debug. The
warnings of lower severity levels will still be written into the
warnings buffer, but the buffer will not be forced onto display.
This user option specifies the minimum severity level that should be
logged in the warnings buffer. Warnings of lower severity will be
completely ignored: not written to the warnings buffer and not
displayed. The default is :warning, which means to log
warnings of any severity except :debug.
This list specifies which warning types should not be displayed immediately when they occur. Each element of the list should be a list of symbols. If an element of this list has the same elements as the first elements in a warning type, then the warning of that type will not be shown on display by popping the warnings buffer in some window (the warning will still be logged in the warnings buffer).
For example, if the value of this variable is a list like this:
((foo) (bar subtype))
then warnings whose types are foo or (foo) or
(foo something) or (bar subtype other) will not
be shown to the user.
This list specifies which warning types should be ignored: not logged
in the warnings buffer and not shown to the user. The structure and
the matching of warning types are the same as for
warning-suppress-types above.
During startup, Emacs delays showing any warnings until after it
loads and processes the site-wide and user’s init files
(see Summary: Sequence of Actions at Startup). Let-binding (see Local Variables) the
values of these options around some code in your init files which
might emit a warning will therefore not work, because it will not be
in effect by the time the warning is actually processed. Thus, if you
want to suppress some warnings during startup, change the values of
the above options in your init file early enough, or put those
let-binding forms in your after-init-hook or
emacs-startup-hook functions. See The Init File.
Sometimes, you may wish to avoid showing a warning while a command is
running, and only show it only after the end of the command. You can
use the function delay-warning for this. Emacs automatically
delays any warnings emitted during the early stages of startup, and
shows them only after the init files are processed.
This function is the delayed counterpart to display-warning
(see Warning Basics), and it is called with the same arguments.
The warning message is queued into delayed-warnings-list.
The value of this variable is a list of warnings to be displayed after the current command has finished. Each element must be a list
(type message [level [buffer-name]])
with the same form, and the same meanings, as the argument list of
display-warning. Immediately after running
post-command-hook (see Command Loop Overview), the Emacs
command loop displays all the warnings specified by this variable,
then resets the variable to nil.
Programs which need to further customize the delayed warnings
mechanism can change the variable delayed-warnings-hook:
This is a normal hook which is run by the Emacs command loop, after
post-command-hook, in order to process and display delayed
warnings. Emacs also runs this hook during startup, after loading the
site-start and user init files (see Summary: Sequence of Actions at Startup), because
warnings emitted before that are automatically delayed.
Its default value is a list of two functions:
(collapse-delayed-warnings display-delayed-warnings)
The function collapse-delayed-warnings removes repeated entries
from delayed-warnings-list. The function
display-delayed-warnings calls display-warning on each
of the entries in delayed-warnings-list, in turn, and then sets
delayed-warnings-list to nil.
You can make characters invisible, so that they do not appear on
the screen, with the invisible property. This can be either a
text property (see Text Properties) or an overlay property
(see Overlays). Cursor motion also partly ignores these
characters; if the command loop finds that point is inside a range of
invisible text after a command, it relocates point to the other side
of the text.
In the simplest case, any non-nil invisible property makes
a character invisible. This is the default case—if you don’t alter
the default value of buffer-invisibility-spec, this is how the
invisible property works. You should normally use t
as the value of the invisible property if you don’t plan
to set buffer-invisibility-spec yourself.
More generally, you can use the variable buffer-invisibility-spec
to control which values of the invisible property make text
invisible. This permits you to classify the text into different subsets
in advance, by giving them different invisible values, and
subsequently make various subsets visible or invisible by changing the
value of buffer-invisibility-spec.
Controlling visibility with buffer-invisibility-spec is
especially useful in a program to display the list of entries in a
database. It permits the implementation of convenient filtering
commands to view just a part of the entries in the database. Setting
this variable is very fast, much faster than scanning all the text in
the buffer looking for properties to change.
This variable specifies which kinds of invisible properties
actually make a character invisible. Setting this variable makes it
buffer-local.
tA character is invisible if its invisible property is
non-nil. This is the default.
Each element of the list specifies a criterion for invisibility; if a
character’s invisible property fits any one of these criteria,
the character is invisible. The list can have two kinds of elements:
atomA character is invisible if its invisible property value is
atom or if it is a list with atom as a member; comparison
is done with eq.
(atom . t)A character is invisible if its invisible property value is
atom or if it is a list with atom as a member; comparison
is done with eq. Moreover, a sequence of such characters
displays as an ellipsis.
Two functions are specifically provided for adding elements to
buffer-invisibility-spec and removing elements from it.
This function adds the element element to
buffer-invisibility-spec. If buffer-invisibility-spec
was t, it changes to a list, (t), so that text whose
invisible property is t remains invisible.
This removes the element element from
buffer-invisibility-spec. This does nothing if element
is not in the list.
A convention for use of buffer-invisibility-spec is that a
major mode should use the mode’s own name as an element of
buffer-invisibility-spec and as the value of the
invisible property:
;; If you want to display an ellipsis: (add-to-invisibility-spec '(my-symbol . t)) ;; If you don’t want ellipsis: (add-to-invisibility-spec 'my-symbol) (overlay-put (make-overlay beginning end) 'invisible 'my-symbol) ;; When done with the invisibility: (remove-from-invisibility-spec '(my-symbol . t)) ;; Or respectively: (remove-from-invisibility-spec 'my-symbol)
You can check for invisibility using the following function:
If pos-or-prop is a marker or number, this function returns a
non-nil value if the text at that position is currently
invisible.
If pos-or-prop is any other kind of Lisp object, that is taken
to mean a possible value of the invisible text or overlay
property. In that case, this function returns a non-nil value
if that value would cause text to become invisible, based on the
current value of buffer-invisibility-spec.
The return value of this function is t if the text would be
completely hidden on display, or a non-nil, non-t value
if the text would be replaced by an ellipsis.
Ordinarily, functions that operate on text or move point do not care
whether the text is invisible, they process invisible characters and
visible characters alike. The user-level line motion commands,
such as next-line, previous-line, ignore invisible
newlines if line-move-ignore-invisible is non-nil (the
default), i.e., behave like these invisible newlines didn’t exist in
the buffer, but only because they are explicitly programmed to do so.
If a command ends with point inside or at the boundary of
invisible text, the main editing loop relocates point to one of the
two ends of the invisible text. Emacs chooses the direction of
relocation so that it is the same as the overall movement direction of
the command; if in doubt, it prefers a position where an inserted char
would not inherit the invisible property. Additionally, if the
text is not replaced by an ellipsis and the command only moved within
the invisible text, then point is moved one extra character so as to
try and reflect the command’s movement by a visible movement of the
cursor.
Thus, if the command moved point back to an invisible range (with the usual stickiness), Emacs moves point back to the beginning of that range. If the command moved point forward into an invisible range, Emacs moves point forward to the first visible character that follows the invisible text and then forward one more character.
These adjustments of point that ended up in the middle of
invisible text can be disabled by setting disable-point-adjustment
to a non-nil value. See Adjusting Point After Commands.
Incremental search can make invisible overlays visible temporarily
and/or permanently when a match includes invisible text. To enable
this, the overlay should have a non-nil
isearch-open-invisible property. The property value should be a
function to be called with the overlay as an argument. This function
should make the overlay visible permanently; it is used when the match
overlaps the overlay on exit from the search.
During the search, such overlays are made temporarily visible by
temporarily modifying their invisible and intangible properties. If you
want this to be done differently for a certain overlay, give it an
isearch-open-invisible-temporary property which is a function.
The function is called with two arguments: the first is the overlay, and
the second is nil to make the overlay visible, or t to
make it invisible again.
The invisible property is ignored in text that is covered by a
replacing display property, because such display
properties skip the text without processing its properties.
See Display Specs That Replace The Text.
Selective display refers to a pair of related features for hiding certain lines on the screen.
The first variant, explicit selective display, was designed for use in a Lisp
program: it controls which lines are hidden by altering the text. This kind of
hiding is now obsolete and deprecated; instead you should use the
invisible property (see Invisible Text) to get the same effect.
In the second variant, the choice of lines to hide is made automatically based on indentation. This variant is designed to be a user-level feature.
The way you control explicit selective display is by replacing a newline (control-j) with a carriage return (control-m). The text that was formerly a line following that newline is now hidden. Strictly speaking, it is temporarily no longer a line at all, since only newlines can separate lines; it is now part of the previous line.
Selective display does not directly affect editing commands. For
example, C-f (forward-char) moves point unhesitatingly
into hidden text. However, the replacement of newline characters with
carriage return characters affects some editing commands. For
example, next-line skips hidden lines, since it searches only
for newlines. Modes that use selective display can also define
commands that take account of the newlines, or that control which
parts of the text are hidden.
When you write a selectively displayed buffer into a file, all the control-m’s are output as newlines. This means that when you next read in the file, it looks OK, with nothing hidden. The selective display effect is seen only within Emacs.
This buffer-local variable enables selective display. This means that lines, or portions of lines, may be made hidden.
selective-display is t, then the character
control-m marks the start of hidden text; the control-m, and the rest
of the line following it, are not displayed. This is explicit selective
display.
selective-display is a positive integer, then
lines that start with more than that many columns of indentation are not
displayed.
When some portion of a buffer is hidden, the vertical movement
commands operate as if that portion did not exist, allowing a single
next-line command to skip any number of hidden lines.
However, character movement commands (such as forward-char) do
not skip the hidden portion, and it is possible (if tricky) to insert
or delete text in a hidden portion.
In the examples below, we show the display appearance of the
buffer foo, which changes with the value of
selective-display. The contents of the buffer do not
change.
(setq selective-display nil)
⇒ nil
---------- Buffer: foo ----------
1 on this column
2on this column
3n this column
3n this column
2on this column
1 on this column
---------- Buffer: foo ----------
(setq selective-display 2)
⇒ 2
---------- Buffer: foo ----------
1 on this column
2on this column
2on this column
1 on this column
---------- Buffer: foo ----------
If this buffer-local variable is non-nil, then Emacs displays
‘…’ at the end of a line that is followed by hidden text.
This example is a continuation of the previous one.
(setq selective-display-ellipses t)
⇒ t
---------- Buffer: foo ----------
1 on this column
2on this column ...
2on this column
1 on this column
---------- Buffer: foo ----------
You can use a display table to substitute other text for the ellipsis (‘…’). See Display Tables.
Temporary displays are used by Lisp programs to put output into a buffer and then present it to the user for perusal rather than for editing. Many help commands use this feature.
This function executes the forms in body while arranging to insert
any output they print into the buffer named buffer-name, which is
first created if necessary, and put into Help mode. (See the similar
form with-temp-buffer-window below.) Finally, the buffer is
displayed in some window, but that window is not selected.
If the forms in body do not change the major mode in the output
buffer, so that it is still Help mode at the end of their execution,
then with-output-to-temp-buffer makes this buffer read-only at
the end, and also scans it for function and variable names to make them
into clickable cross-references. See Tips for
Documentation Strings, in particular the item on hyperlinks in
documentation strings, for more details.
The string buffer-name specifies the temporary buffer, which need
not already exist. The argument must be a string, not a buffer. The
buffer is erased initially (with no questions asked), and it is marked
as unmodified after with-output-to-temp-buffer exits.
with-output-to-temp-buffer binds standard-output to the
temporary buffer, then it evaluates the forms in body. Output
using the Lisp output functions within body goes by default to
that buffer (but screen display and messages in the echo area, although
they are “output” in the general sense of the word, are not affected).
See Output Functions.
Several hooks are available for customizing the behavior of this construct; they are listed below.
The value of the last form in body is returned.
---------- Buffer: foo ---------- This is the contents of foo. ---------- Buffer: foo ----------
(with-output-to-temp-buffer "foo"
(print 20)
(print standard-output))
⇒ #<buffer foo>
---------- Buffer: foo ----------
20
#<buffer foo>
---------- Buffer: foo ----------
If this variable is non-nil, with-output-to-temp-buffer
calls it as a function to do the job of displaying a help buffer. The
function gets one argument, which is the buffer it should display.
It is a good idea for this function to run temp-buffer-show-hook
just as with-output-to-temp-buffer normally would, inside of
save-selected-window and with the chosen window and buffer
selected.
This normal hook is run by with-output-to-temp-buffer before
evaluating body. When the hook runs, the temporary buffer is
current. This hook is normally set up with a function to put the
buffer in Help mode.
This normal hook is run by with-output-to-temp-buffer after
displaying the temporary buffer. When the hook runs, the temporary buffer
is current, and the window it was displayed in is selected.
This macro is similar to with-output-to-temp-buffer. Like that
construct, it executes body while arranging to insert any output
it prints into the buffer named buffer-or-name and displays that
buffer in some window. Unlike with-output-to-temp-buffer,
however, it does not automatically switch that buffer to Help mode.
The argument buffer-or-name specifies the temporary buffer. It
can be either a buffer, which must already exist, or a string, in which
case a buffer of that name is created, if necessary. The buffer is
marked as unmodified and read-only when with-temp-buffer-window
exits.
This macro does not call temp-buffer-show-function. Rather, it
passes the action argument to display-buffer
(see Choosing a Window for Displaying a Buffer) in order to display the buffer.
The value of the last form in body is returned, unless the argument quit-function is specified. In that case, it is called with two arguments: the window showing the buffer and the result of body. The final return value is then whatever quit-function returns.
This macro uses the normal hooks temp-buffer-window-setup-hook
and temp-buffer-window-show-hook in place of the analogous hooks
run by with-output-to-temp-buffer.
The two constructs described next are mostly identical to
with-temp-buffer-window but differ from it as specified:
This macro is like with-temp-buffer-window but unlike that makes
the buffer specified by buffer-or-name current for running
body.
A window showing a temporary buffer can be fitted to the size of that buffer using the following mode:
When this minor mode is enabled, windows showing a temporary buffer are automatically resized to fit their buffer’s contents.
A window is resized if and only if it has been specially created for the
buffer. In particular, windows that have shown another buffer before
are not resized. By default, this mode uses fit-window-to-buffer
(see Resizing Windows) for resizing. You can specify a different
function by customizing the options temp-buffer-max-height and
temp-buffer-max-width below.
The effect of this option can be overridden by providing a suitable
window-height, window-width or window-size action
alist entry for display-buffer (see Action Alists for Buffer Display).
This option specifies the maximum height (in lines) of a window
displaying a temporary buffer when temp-buffer-resize-mode is
enabled. It can also be a function to be called to choose the height
for such a buffer. It gets one argument, the buffer, and should return
a positive integer. At the time the function is called, the window to
be resized is selected.
This option specifies the maximum width of a window (in columns)
displaying a temporary buffer when temp-buffer-resize-mode is
enabled. It can also be a function to be called to choose the width for
such a buffer. It gets one argument, the buffer, and should return a
positive integer. At the time the function is called, the window to be
resized is selected.
The following function uses the current buffer for temporary display:
This function momentarily displays string in the current buffer at position. It has no effect on the undo list or on the buffer’s modification status.
The momentary display remains until the next input event. If the next
input event is char, momentary-string-display ignores it
and returns. Otherwise, that event remains buffered for subsequent use
as input. Thus, typing char will simply remove the string from
the display, while typing (say) C-f will remove the string from
the display and later (presumably) move point forward. The argument
char is a space by default.
The return value of momentary-string-display is not meaningful.
If the string string does not contain control characters, you can
do the same job in a more general way by creating (and then subsequently
deleting) an overlay with a before-string property.
See Overlay Properties.
If message is non-nil, it is displayed in the echo area
while string is displayed in the buffer. If it is nil, a
default message says to type char to continue.
In this example, point is initially located at the beginning of the second line:
---------- Buffer: foo ---------- This is the contents of foo. ∗Second line. ---------- Buffer: foo ----------
(momentary-string-display "**** Important Message! ****" (point) ?\r "Type RET when done reading") ⇒ t
---------- Buffer: foo ---------- This is the contents of foo. **** Important Message! ****Second line. ---------- Buffer: foo ---------- ---------- Echo Area ---------- Type RET when done reading ---------- Echo Area ----------
You can use overlays to alter the appearance of a buffer’s text on the screen, for the sake of presentation features. An overlay is an object that belongs to a particular buffer, and has a specified beginning and end. It also has properties that you can examine and set; these affect the display of the text within the overlaid portion of the buffer.
Editing the text of the buffer adjusts the beginning and end of each overlay so that it stays with the text. When you create the overlay, you can specify whether text inserted at the beginning should be inside the overlay or outside, and likewise for the end of the overlay.
This section describes the functions to create, delete and move overlays, and to examine their contents. Overlay changes are not recorded in the buffer’s undo list, since the overlays are not considered part of the buffer’s contents.
This function returns t if object is an overlay.
This function creates and returns an overlay that belongs to buffer and ranges from start to end. Both start and end must specify buffer positions; they may be integers or markers. If buffer is omitted, the overlay is created in the current buffer.
An overlay whose start and end specify the same buffer position is known as empty. A non-empty overlay can become empty if the text between its start and end is deleted. When that happens, the overlay is by default not deleted, but you can cause it to be deleted by giving it the ‘evaporate’ property (see evaporate property).
The arguments front-advance and rear-advance specify what
happens when text is inserted at the beginning (i.e., before
start) and at the end. If they are both nil, the
default, then the overlay extends to include any text inserted at the
beginning, but not text inserted at the end. If front-advance
is non-nil, text inserted at the beginning of the overlay is
excluded from the overlay. If rear-advance is non-nil,
text inserted at the end of the overlay is included in the overlay.
This function returns the position at which overlay starts, as an integer.
This function returns the position at which overlay ends, as an integer.
This function returns the buffer that overlay belongs to. It
returns nil if overlay has been deleted.
This function deletes the specified overlay. The overlay continues to exist as a Lisp object, and its property list is unchanged, but it ceases to be attached to the buffer it belonged to, and ceases to have any effect on display.
A deleted overlay is not permanently disconnected. You can give it a
position in a buffer again by calling move-overlay.
This function moves overlay to buffer, and places its bounds at start and end in that buffer. Both arguments start and end must specify buffer positions; they may be integers or markers.
If buffer is omitted, overlay stays in the same buffer it was already associated with; if overlay was previously deleted (and thus isn’t associated with any buffer), it goes into the current buffer.
The return value is overlay.
This function is the only valid way to change the endpoints of an overlay.
This function clears the text in the region between start and end of any overlays whose property named name has the specified value, such that no such overlay will affect the text in the region. To do this, the function can remove overlays in the region, or move their endpoints, or split them, or do some combination of these. Specifically:
If name is omitted or nil, it means to delete/modify all
overlays that affect text in the specified region. If start
and/or end are omitted or nil, they default to the
beginning and end of the buffer, respectively. Therefore,
(remove-overlays) removes all the overlays in the current buffer.
Values of the named overlay property are compared using eq, which
is important if the values are anything but symbols or fixnums
(see Equality Predicates). It means the values passed to the
function must be the same values used to set the overlay property, not
their copies; objects which are different will not compare equal even if
they have identical contents.
The optional arguments name and value should either both be
passed and non-nil, or both omitted or nil.
This function returns a copy of overlay. The copy has the same endpoints and properties as overlay. However, the text insertion type for the start of the overlay and for the end of the overlay are set to their default values.
Here are some examples:
;; Create an overlay.
(setq foo (make-overlay 1 10))
⇒ #<overlay from 1 to 10 in display.texi>
(overlay-start foo)
⇒ 1
(overlay-end foo)
⇒ 10
(overlay-buffer foo)
⇒ #<buffer display.texi>
;; Give it a property we can check later.
(overlay-put foo 'happy t)
⇒ t
;; Verify the property is present.
(overlay-get foo 'happy)
⇒ t
;; Move the overlay.
(move-overlay foo 5 20)
⇒ #<overlay from 5 to 20 in display.texi>
(overlay-start foo)
⇒ 5
(overlay-end foo)
⇒ 20
;; Delete the overlay. (delete-overlay foo) ⇒ nil ;; Verify it is deleted. foo ⇒ #<overlay in no buffer> ;; A deleted overlay has no position. (overlay-start foo) ⇒ nil (overlay-end foo) ⇒ nil (overlay-buffer foo) ⇒ nil
;; Undelete the overlay. (move-overlay foo 1 20) ⇒ #<overlay from 1 to 20 in display.texi> ;; Verify the results. (overlay-start foo) ⇒ 1 (overlay-end foo) ⇒ 20 (overlay-buffer foo) ⇒ #<buffer display.texi>
;; Moving and deleting the overlay does not change its properties.
(overlay-get foo 'happy)
⇒ t
Overlay properties are like text properties in that the properties that alter how a character is displayed can come from either source. But in most respects they are different. See Text Properties, for comparison.
Text properties are considered a part of the text; overlays and their properties are specifically considered not to be part of the text. Thus, copying text between various buffers and strings preserves text properties, but does not try to preserve overlays. Changing a buffer’s text properties marks the buffer as modified, while moving an overlay or changing its properties does not. Unlike text property changes, overlay property changes are not recorded in the buffer’s undo list.
Since more than one overlay can specify a property value for the same character, Emacs lets you specify a priority value of each overlay. The priority value is used to decide which of the overlapping overlays will “win”.
These functions read and set the properties of an overlay:
This function returns the value of property prop recorded in
overlay, if any. If overlay does not record any value for
that property, but it does have a category property which is a
symbol, that symbol’s prop property is used. Otherwise, the value
is nil.
This function sets the value of property prop recorded in overlay to value. It returns value.
This returns a copy of the property list of overlay.
See also the function get-char-property which checks both
overlay properties and text properties for a given character.
See Examining Text Properties.
Many overlay properties have special meanings; here is a table of them:
priority ¶This property’s value determines the priority of the overlay. If you
want to specify a priority value, use either nil (or zero), or
a positive integer, or a cons of two values. Any other value triggers
undefined behavior.
The priority matters when two or more overlays cover the same
character and both specify the same property with different values;
the one whose priority value is higher overrides the other.
(For the face property, the higher priority overlay’s value
does not completely override the other value; instead, its individual
face attributes override the corresponding face attributes of the
face property whose priority is lower.) If two overlays have
the same priority value, and one is “nested” in the other (i.e.,
covers fewer buffer or string positions), then the inner one will
prevail over the outer one. If neither is nested in the other then
you should not make assumptions about which overlay will prevail.
When a Lisp program puts overlays with defined priorities on text that
might have overlays without priorities, this could cause undesirable
results, because any overlay with a positive priority value will
override all the overlays without a priority. Since most Emacs
features that use overlays don’t specify priorities for their
overlays, integer priorities should be used with care. Instead of
using integer priorities and risk overriding other overlays, you can
use priority values of the form (primary . secondary),
where the primary value is used as described above, and
secondary is the fallback value used when primary and the
nesting considerations fail to resolve the precedence between
overlays. In particular, priority value (nil . n),
with n a positive integer, enables you to have the overlays
ordered by priority when necessary without completely overriding other
overlays.
Currently, all overlays take priority over text properties.
If you need to put overlays in priority order, use the sorted
argument of overlays-at. See Searching for Overlays.
window ¶If the window property is non-nil, then the overlay
applies only on that window.
category ¶If an overlay has a category property, we call it the
category of the overlay. It should be a symbol. The properties
of the symbol serve as defaults for the properties of the overlay.
face ¶This property controls the appearance of the text (see Faces). The value of the property can be the following:
(keyword
value …), where each keyword is a face attribute
name and value is a value for that attribute.
(foreground-color . color-name)
or (background-color . color-name). This specifies the
foreground or background color, similar to (:foreground
color-name) or (:background color-name). This
form is supported for backward compatibility only, and should be
avoided.
mouse-face ¶This property is used instead of face when the mouse is within
the range of the overlay. However, Emacs ignores all face attributes
from this property that alter the text size (e.g., :height,
:weight, and :slant); those attributes are always the
same as in the unhighlighted text.
display ¶This property activates various features that change the
way text is displayed. For example, it can make text appear taller
or shorter, higher or lower, wider or narrower, or replaced with an image.
See The display Property. Note that, if the display property is a
replacing one (see Display Specs That Replace The Text), the invisible
property of the same overlay will be ignored.
help-echo ¶If an overlay has a help-echo property, then when you move the
mouse onto the text in the overlay, Emacs displays a help string in
the echo area, or as a tooltip. For details see Text help-echo.
field ¶Consecutive characters with the same field property constitute a
field. Some motion functions including forward-word and
beginning-of-line stop moving at a field boundary.
See Defining and Using Fields.
modification-hooks ¶This property’s value is a list of functions to be called if any character within the overlay is changed or if text is inserted strictly within the overlay.
The hook functions are called both before and after each change. If the functions save the information they receive, and compare notes between calls, they can determine exactly what change has been made in the buffer text.
When called before a change, each function receives four arguments: the
overlay, nil, and the beginning and end of the text range to be
modified.
When called after a change, each function receives five arguments: the
overlay, t, the beginning and end of the text range just
modified, and the length of the pre-change text replaced by that range.
(For an insertion, the pre-change length is zero; for a deletion, that
length is the number of characters deleted, and the post-change
beginning and end are equal.)
When these functions are called, inhibit-modification-hooks is
bound to non-nil. If the functions modify the buffer, you
might want to bind inhibit-modification-hooks to nil, so
as to cause the change hooks to run for these modifications. However,
doing this may call your own change hook recursively, so be sure to
prepare for that. See Change Hooks.
Text properties also support the modification-hooks property,
but the details are somewhat different (see Properties with Special Meanings).
insert-in-front-hooks ¶This property’s value is a list of functions to be called before and
after inserting text right at the beginning of the overlay. The calling
conventions are the same as for the modification-hooks functions.
insert-behind-hooks ¶This property’s value is a list of functions to be called before and
after inserting text right at the end of the overlay. The calling
conventions are the same as for the modification-hooks functions.
invisible ¶The invisible property can make the text in the overlay
invisible, which means that it does not appear on the screen. However,
if the text covered by the overlay has a replacing display
property, the invisible property will be ignored, because a
replacing display property skips the text without examining its
properties. See Invisible Text, for details.
intangible ¶The intangible property on an overlay works just like the
intangible text property. It is obsolete. See Properties with Special Meanings, for details.
isearch-open-invisibleThis property tells incremental search (see Incremental Search in The GNU Emacs Manual) how to make an invisible overlay visible, permanently, if the final match overlaps it. See Invisible Text.
isearch-open-invisible-temporaryThis property tells incremental search how to make an invisible overlay visible, temporarily, during the search. See Invisible Text.
before-string ¶This property’s value is a string to add to the display at the beginning of the overlay. The string does not appear in the buffer in any sense—only on the screen. Note that if the text at the beginning of the overlay is made invisible, the string will not be displayed.
after-string ¶This property’s value is a string to add to the display at the end of the overlay. The string does not appear in the buffer in any sense—only on the screen. Note that if the text at the end of the overlay is made invisible, the string will not be displayed.
line-prefixThis property specifies a display spec to prepend to each non-continuation line at display-time. See Truncation.
wrap-prefixThis property specifies a display spec to prepend to each continuation line at display-time. See Truncation.
evaporate ¶If this property is non-nil, the overlay is deleted automatically
if it becomes empty (i.e., if its length becomes zero). If you give an
empty overlay (see empty overlays) a non-nil evaporate
property, that deletes it immediately. Note that, unless an overlay has
this property, it will not be deleted when the text between its starting
and ending positions is deleted from the buffer.
display-line-numbers-disable ¶This property prevents display of line numbers (see display-line-numbers in The GNU Emacs Manual) for the text which is within an overlay having this property. One situation where using an overlay with this property is useful is an empty overlay at end-of-buffer, since otherwise there’s no way of preventing the display of the line number there.
keymap ¶If this property is non-nil, it specifies a keymap for a
portion of the text. This keymap takes precedence over most other
keymaps (see Active Keymaps), and it is used when point is within
the overlay, where the front-
and rear-advance properties define whether the boundaries are
considered as being within or not.
local-map ¶The local-map property is similar to keymap but replaces the
buffer’s local map rather than augmenting existing keymaps. This also means it
has lower precedence than minor mode keymaps.
The keymap and local-map properties do not affect a
string displayed by the before-string, after-string, or
display properties. This is only relevant for mouse clicks and
other mouse events that fall on the string, since point is never on
the string. To bind special mouse events for the string, assign it a
keymap or local-map text property. See Properties with Special Meanings.
This function returns a list of all the overlays that contain the character at
position pos in the current buffer. If sorted is non-nil,
the returned list is in decreasing order of priority, otherwise it is in no
particular order. An overlay contains the character at pos if it begins
at or before pos, and ends after pos.
To illustrate usage, here is a Lisp function that returns a list of the overlays that specify property prop for the character at point:
(defun find-overlays-specifying (prop)
(let ((overlays (overlays-at (point)))
found)
(while overlays
(let ((overlay (car overlays)))
(if (overlay-get overlay prop)
(setq found (cons overlay found))))
(setq overlays (cdr overlays)))
found))
Empty overlays (see empty overlays) do not contain any characters,
so this function does not return them. Use overlays-in,
described below, instead if empty overlays are of interest.
Note that this function can return overlays outside of the current narrowing of the buffer (see Narrowing) if pos is outside of the narrowing.
This function returns a list of the overlays that overlap with the region beg through end. An overlay overlaps with a region if it contains one or more characters between beg and end; this excludes the characters at (i.e. after) end.
Empty overlays do not contain any characters, so the rule for including them is different: they are said to overlap if they are at beg, strictly between beg and end excluding end, or at end when end denotes the position at the end of the buffer. (The special handling of empty overlays at end of buffer is to allow such overlays to be found and processed. For any other value of end you could increment the end position instead.) Note that if beg and end are the same position, an empty overlay that is at beg is also at end, so this case is somewhat similar to an empty overlay at the end of the buffer.
The order in which the overlays appear in the returned list is unpredictable.
Note that this function can return overlays outside of the current narrowing of the buffer if beg and/or end are outside of the narrowing.
This function returns the buffer position of the next beginning or end
of an overlay, after pos. If there is none, it returns
(point-max).
This function returns the buffer position of the previous beginning or
end of an overlay, before pos. If there is none, it returns
(point-min).
As an example, here’s a simplified (and inefficient) version of the
primitive function next-single-char-property-change
(see Text Property Search Functions). It searches forward from position
pos for the next position where the value of a given property
prop, as obtained from either overlays or text properties,
changes.
(defun next-single-char-property-change (position prop)
(save-excursion
(goto-char position)
(let ((propval (get-char-property (point) prop)))
(while (and (not (eobp))
(eq (get-char-property (point) prop) propval))
(goto-char (min (next-overlay-change (point))
(next-single-property-change (point) prop)))))
(point)))
Since not all characters have the same width, these functions let you check the width of a character. See Indentation Primitives, and Motion by Screen Lines, for related functions.
This function returns the width in columns of the character
char, if it were displayed in the current buffer (i.e., taking
into account the buffer’s display table, if any; see Display Tables). The width of a tab character is usually tab-width
(see Usual Display Conventions).
Return non-nil if char is an upper-case character
according to Unicode. Note that a character is considered to be
upper-case if the Unicode Standard defines a corresponding lower-case
character.
This function returns the width in columns of the string string,
if it were displayed in the current buffer and the selected window.
Optional arguments from and to specify the substring of
string to consider, and are interpreted as in substring
(see Creating Strings).
The return value is an approximation: it only considers the values
returned by char-width for the constituent characters, always
takes a tab character as taking tab-width columns, ignores
display properties and fonts, etc. For these reasons, we recommend
using window-text-pixel-size or string-pixel-width,
described below, instead.
This function returns a new string that is a truncation of string which fits within width columns on display.
If string is narrower than width, the result is equal to string; otherwise excess characters are omitted from the result. If a multi-column character in string exceeds the goal width, that character is omitted from the result. Thus, the result can sometimes fall short of width, but cannot go beyond it.
The optional argument start-column specifies the starting
column; it defaults to zero. If this is non-nil, then the
first start-column columns of the string are omitted from the
result. If one multi-column character in string extends across
the column start-column, that character is omitted.
The optional argument padding, if non-nil, is a padding
character added at the beginning and end of the result string, to
extend it to exactly width columns. The padding character is
appended at the end of the result if it falls short of width, as
many times as needed to reach width. It is also prepended at
the beginning of the result if a multi-column character in
string extends across the column start-column.
If ellipsis is non-nil, it should be a string which will
replace the end of string when it is truncated. In this case,
more characters will be removed from string to free enough space
for ellipsis to fit within width columns. However, if
the display width of string is less than the display width of
ellipsis, ellipsis will not be appended to the result. If
ellipsis is non-nil and not a string, it stands for the
value returned by the function truncate-string-ellipsis,
described below.
The optional argument ellipsis-text-property, if non-nil,
means hide the excess parts of string with a display text
property (see The display Property) showing the ellipsis, instead of
actually truncating the string.
See also the function truncate-string-pixelwise for pixel-level
resolution.
(truncate-string-to-width "\tab\t" 12 4)
⇒ "ab"
(truncate-string-to-width "\tab\t" 12 4 ?\s)
⇒ " ab "
This function uses string-width and char-width to find
the suitable truncation point when string is too wide, so it
suffers from the same basic issues as string-width does. In
particular, when character composition happens within string,
the display width of a string could be smaller than the sum of widths
of the constituent characters, and this function might return
inaccurate results.
This function returns the string to be used as an ellipses in
truncate-string-to-width and other similar contexts. The value
is that of the variable truncate-string-ellipsis, if it’s
non-nil, the string with the single character U+2026
HORIZONTAL ELLIPSIS if that character can be displayed on the
selected frame, and the string ‘...’ otherwise.
The following function returns the size in pixels of text as if it were
displayed in a given window. This function is used by
fit-window-to-buffer and fit-frame-to-buffer
(see Resizing Windows) to make a window exactly as large as the text
it contains.
This function returns the dimensions of the text of window’s buffer in pixels. window must be a live window and defaults to the selected one. The return value is a cons of the maximum pixel-width of any text line and the maximum pixel-height of all text lines. This function exists to allow Lisp programs to adjust the dimensions of window to the buffer text it needs to display, and for other similar situations.
The return value can also optionally (see below) include the buffer position of the first line whose dimensions were measured.
The optional argument from, if non-nil, specifies the
first text position to consider, and defaults to the minimum
accessible position of the buffer. If from is t, it
stands for the minimum accessible position that is not a newline
character. If from is a cons, its car specifies a buffer
position, and its cdr specifies the vertical offset in pixels
from that position to the first screen line whose text is to be
measured. (The measurement will start from the visual beginning of
that screen line.) In that case, the return value will instead be a
list of the pixel-width, pixel-height, and the buffer position of the
first line that was measured. The optional argument to, if
non-nil, specifies the last text position to consider, and
defaults to the maximum accessible position of the buffer. If
to is t, it stands for the maximum accessible position
that is not a newline character.
The optional argument x-limit, if non-nil, specifies the
maximum X coordinate beyond which text should be ignored; it is
therefore also the largest value of pixel-width that the function can
return. If x-limit nil or omitted, it means to use the
pixel-width of window’s body (see Window Sizes); this
default means that text of truncated lines wider than the window will
be ignored. This default is useful when the caller does not intend to
change the width of window. Otherwise, the caller should
specify here the maximum width window’s body may assume; in
particular, if truncated lines are expected and their text needs to be
accounted for, x-limit should be set to a large value. Since
calculating the width of long lines can take some time, it’s always a
good idea to make this argument as small as needed; in particular, if
the buffer might contain long lines that will be truncated anyway.
The optional argument y-limit, if non-nil, specifies the
maximum Y coordinate beyond which text is to be ignored; it is
therefore also the maximum pixel-height that the function can return.
If y-limit is nil or omitted, it means to consider all the
lines of text till the buffer position specified by to. Since
calculating the pixel-height of a large buffer can take some time, it
makes sense to specify this argument; in particular, if the caller
does not know the size of the buffer.
The optional argument mode-lines nil or omitted means to
not include the height of the mode-, tab- or header-line of window
in the return value. If it is either the symbol mode-line,
tab-line or header-line, include only the height of that
line, if present, in the return value. If it is t, include the
height of all of these lines, if present, in the return value.
The optional argument ignore-line-at-end controls whether or not to count the height of text in to’s screen line as part of the returned pixel-height. This is useful if your Lisp program is only interested in the dimensions of text up to and excluding the visual beginning of to’s screen line.
window-text-pixel-size treats the text displayed in a window as a
whole and does not care about the size of individual lines. The
following function does.
This function calculates the pixel dimensions of each line displayed in the specified window. It does so by walking window’s current glyph matrix—a matrix storing the glyph (see Glyphs) of each buffer character currently displayed in window. If successful, it returns a list of cons pairs representing the x- and y-coordinates of the lower right corner of the last character of each line. Coordinates are measured in pixels from an origin (0, 0) at the top-left corner of window. window must be a live window and defaults to the selected one.
If the optional argument first is an integer, it denotes the index
(starting with 0) of the first line of window’s glyph matrix to be
returned. Note that if window has a header line, the line with
index 0 is that header line. If first is nil, the first line to
be considered is determined by the value of the optional argument
body: If body is non-nil, this means to start with
the first line of window’s body, skipping any header line, if
present. Otherwise, this function will start with the first line of
window’s glyph matrix, possibly the header line.
If the optional argument last is an integer, it denotes the index
of the last line of window’s glyph matrix that shall be returned.
If last is nil, the last line to be considered is determined by
the value of body: If body is non-nil, this means to
use the last line of window’s body, omitting window’s mode
line, if present. Otherwise, this means to use the last line of
window which may be the mode line.
The optional argument inverse, if nil, means that the
y-pixel value returned for any line specifies the distance in pixels
from the left edge (body edge if body is non-nil) of
window to the right edge of the last glyph of that line.
inverse non-nil means that the y-pixel value returned for
any line specifies the distance in pixels from the right edge of the
last glyph of that line to the right edge (body edge if body is
non-nil) of window. This is useful for determining the
amount of slack space at the end of each line.
The optional argument left, if non-nil means to return the
x- and y-coordinates of the lower left corner of the leftmost character
on each line. This is the value that should be used for windows that
mostly display text from right to left.
If left is non-nil and inverse is nil, this
means that the y-pixel value returned for any line specifies the
distance in pixels from the left edge of the last (leftmost) glyph of
that line to the right edge (body edge if body is non-nil)
of window. If left and inverse are both
non-nil, the y-pixel value returned for any line specifies the
distance in pixels from the left edge (body edge if body is
non-nil) of window to the left edge of the last (leftmost)
glyph of that line.
This function returns nil if the current glyph matrix of
window is not up-to-date which usually happens when Emacs is busy,
for example, when processing a command. The value should be retrievable
though when this function is run from an idle timer with a delay of zero
seconds.
This is much like window-text-pixel-size, but can be used when
the buffer isn’t shown in a window. (window-text-pixel-size is
faster when it is, so this function shouldn’t be used in that case.)
buffer-or-name must specify a live buffer or the name of a live buffer and defaults to the current buffer. window must be a live window and defaults to the selected one; the function will compute the text dimensions as if buffer is displayed in window. The return value is a cons of the maximum pixel-width of any text line and the pixel-height of all the text lines of the accessible portion of the buffer specified by buffer-or-name.
The optional arguments x-limit and y-limit have the same
meaning as with window-text-pixel-size.
If you want to measure dimensions of some part of the buffer text, narrow the buffer to that part before calling this function (see Narrowing).
This is a convenience function that uses window-text-pixel-size
to compute the width of string (in pixels). Caveat: if you call
this function to measure the width of a string with embedded newlines,
it will then return the width of the widest substring that does not
include newlines. The meaning of this result is the widest line taken
by the string if inserted into a buffer. If buffer is
non-nil, use any face remappings (see Face Remapping) from
that buffer when computing the width of string.
This is a convenience function that uses window-text-pixel-size
to truncate string to max-pixels pixels. Caveat: if you
call this function to measure the width of a string with embedded
newlines, it will then return the width of the widest substring that
does not include newlines. The meaning of this result is the widest
line taken by the string if inserted into a buffer. If buffer is
non-nil, use any face remappings (see Face Remapping) from
that buffer when computing the width of string.
If ellipsis is non-nil, it should be a string which will
replace the end of string when it is truncated. In this case,
more characters will be removed from string to free enough space
for ellipsis to fit within max-pixels pixels. However, if
the pixel width of string is less than the pixel width of
ellipsis, ellipsis will not be appended to the result. If
ellipsis is non-nil and not a string, it stands for the
value returned by the function truncate-string-ellipsis,
described above.
If ellipsis-pixels is non-nil and ellipsis is
non-nil, it should be the number of pixels of ellipsis that
you should precompute using string-pixel-width, specifying the
same buffer. This is useful to avoid the cost of recomputing this value
repeatedly when you have many strings to truncate using the same
ellipsis string.
See also the function truncate-string-to-width for
character-level resolution.
This function returns the height in pixels of the line at point in the selected window. The value includes the line spacing of the line (see Line Height).
When character compositions are in effect, sequence of characters can be composed for display to form grapheme clusters, for example to display accented characters, or ligatures, or Emoji, or when complex text shaping requires that for some scripts. When that happens, characters no longer map in a simple way to display columns, and display layout decisions with such strings, such as truncating too wide strings, can be a complex job. This function helps in performing such jobs: it splits up its argument string into a list of substrings, where each substring produces a single grapheme cluster that should be displayed as a unit. Lisp programs can then use this list to construct visually-valid substrings of string which will look correctly on display, or compute the width of any substring of string by adding the width of its constituents in the returned list, etc.
For instance, if you want to display a string without the first glyph, you can say:
(apply #'insert (cdr (string-glyph-split string))))
Caveat: for this function to recognize and process character
compositions, auto-composition-mode must be enabled, and the
current buffer must be displayed in some window.
When a buffer is displayed with line numbers (see Display Custom in The GNU Emacs Manual), it is sometimes useful to know the width taken for displaying the line numbers. The following function is for Lisp programs which need this information for layout calculations.
This function returns the width used for displaying the line numbers
in the selected window. If the optional argument pixelwise is
the symbol columns, the return value is a float number of the
frame’s canonical columns; if pixelwise is t or any other
non-nil value, the value is an integer and is measured in
pixels. If pixelwise is omitted or nil, the value is the
integer number of columns of the font defined for the
line-number face, and doesn’t include the 2 columns used to pad
the numbers on display. If line numbers are not displayed in the
selected window, the value is zero regardless of the value of
pixelwise. Use with-selected-window (see Selecting Windows) if you need this information about another window.
The total height of each display line consists of the height of the contents of the line, plus optional additional vertical line spacing above or below the display line.
The height of the line contents is the maximum height of any character or image on that display line, including the final newline if there is one. (A display line that is continued doesn’t include a final newline.) That is the default line height, if you do nothing to specify a greater height. (In the most common case, this equals the height of the corresponding frame’s default font, see Frame Font.)
There are several ways to explicitly specify a larger line height, either by specifying an absolute height for the display line, or by specifying vertical space. However, no matter what you specify, the actual line height can never be less than the default.
A newline can have a line-height text or overlay property
that controls the total height of the display line ending in that
newline. The property value can be one of several forms:
tIf the property value is t, the newline character has no
effect on the displayed height of the line—the visible contents
alone determine the height. The line-spacing property of the
newline, described below, is also ignored in this case. This is
useful for tiling small images (or image slices) without adding blank
areas between the images.
(height total)If the property value is a list of the form shown, that adds extra
space below the display line. First Emacs uses height as
a height spec to control extra space above the line; then it
adds enough space below the line to bring the total line height
up to total. In this case, any value of line-spacing
property for the newline is ignored.
Any other kind of property value is a height spec, which translates into a number—the specified line height. There are several ways to write a height spec; here’s how each of them translates into a number:
integerIf the height spec is a positive integer, the height value is that integer.
floatIf the height spec is a float, float, the numeric height value is float times the frame’s default line height.
(face . ratio)If the height spec is a cons of the format shown, the numeric height
is ratio times the height of face face. ratio can
be any type of number, or nil which means a ratio of 1.
If face is t, it refers to the current face.
(nil . ratio)If the height spec is a cons of the format shown, the numeric height is ratio times the height of the contents of the line.
Thus, any valid height spec determines the height in pixels, one way or another. If the line contents’ height is less than that, Emacs adds extra vertical space above the line to achieve the specified total height.
If you don’t specify the line-height property, the line’s
height consists of the contents’ height plus the line spacing.
There are several ways to specify the line spacing for different
parts of Emacs text.
On graphical terminals, you can specify the line spacing for all
lines in a frame, using the line-spacing frame parameter
(see Layout Parameters). However, if the default value of
line-spacing is non-nil, it overrides the
frame’s line-spacing parameter. An integer specifies the
number of pixels put below lines. A floating-point number specifies
the spacing relative to the frame’s default line height.
You can specify the line spacing for all lines in a buffer via the
buffer-local line-spacing variable. An integer specifies the
number of pixels put below lines. A floating-point number specifies the
spacing relative to the default frame line height. A cons cell of
integers or floating-point numbers specifies the spacing put above and
below the line, allowing for vertically centering text. This overrides
line spacings specified for the frame.
Finally, a newline can have a line-spacing text or overlay
property that can enlarge the default frame line spacing and the
buffer local line-spacing variable: if its value is larger than
the buffer or frame defaults, that larger value is used instead, for
the display line ending in that newline (unless the newline also has
the line-height property whose value is one of the special
values which cause line-spacing to be ignored, see above).
One way or another, these mechanisms specify a Lisp value for the spacing of each line. The value is a height spec, and it translates into a Lisp value as described above. However, in this case the numeric height value specifies the line spacing, rather than the line height.
On text terminals, the line spacing cannot be altered.
A face is a collection of graphical attributes for displaying text: font, foreground color, background color, optional underlining, etc. Faces control how Emacs displays text in buffers, as well as other parts of the frame such as the mode line.
One way to represent a face is as a property list of attributes,
like (:foreground "red" :weight bold). Such a list is called
an anonymous face. For example, you can assign an anonymous
face as the value of the face text property, and Emacs will
display the underlying text with the specified attributes.
See Properties with Special Meanings.
More commonly, a face is referred to via a face name: a Lisp
symbol associated with a set of face attributes32. Named faces are
defined using the defface macro (see Defining Faces).
Emacs comes with several standard named faces (see Basic Faces).
Some parts of Emacs require named faces (e.g., the functions documented in Face Attribute Functions). Unless otherwise stated, we will use the term face to refer only to named faces.
This function returns a non-nil value if object is a
named face: a Lisp symbol or string which serves as a face name.
Otherwise, it returns nil.
Face attributes determine the visual appearance of a face. The following table lists all the face attributes, their possible values, and their effects.
Apart from the values given below, each face attribute can have the
value unspecified. This special value means that the face
doesn’t specify that attribute directly. An unspecified
attribute tells Emacs to refer instead to a parent face (see the
description :inherit attribute below); or, failing that, to an
underlying face (see Displaying Faces). (However,
unspecified is not a valid value in defface.)
A face attribute can also have the value reset. This special
value stands for the value of the corresponding attribute of the
default face.
The default face must explicitly specify all attributes, and
cannot use the special value reset.
Some of these attributes are meaningful only on certain kinds of displays. If your display cannot handle a certain attribute, the attribute is ignored.
:familyFont family name (a string). See Fonts in The GNU
Emacs Manual, for more information about font families. The function
font-family-list (see below) returns a list of available family
names.
:foundryThe name of the font foundry for the font family specified by
the :family attribute (a string). See Fonts in The
GNU Emacs Manual.
:widthRelative character width. This should be one of the symbols
ultra-condensed, extra-condensed, condensed,
semi-condensed, normal, regular, medium,
semi-expanded, expanded, extra-expanded, or
ultra-expanded.
:heightThe height of the font. In the simplest case, this is an integer in units of 1/10 point.
The value can also be floating point or a function, which specifies the height relative to an underlying face (see Displaying Faces). A floating-point value specifies the amount by which to scale the height of the underlying face. A function value is called with one argument, the height of the underlying face, and returns the height of the new face. If the function is passed an integer argument, it must return an integer.
The height of the default face must be specified using an integer; floating point and function values are not allowed.
:weightFont weight—one of the symbols (from densest to faintest)
ultra-bold, extra-bold, bold, semi-bold,
normal, semi-light, light, extra-light, or
ultra-light. On text terminals which support
variable-brightness text, any weight greater than normal is displayed
as extra bright, and any weight less than normal is displayed as
half-bright.
:slant ¶Font slant—one of the symbols italic, oblique,
normal, reverse-italic, or reverse-oblique. On
text terminals that support variable-brightness text, slanted text is
displayed as half-bright.
:foregroundForeground color, a string. The value can be a system-defined color name, or a hexadecimal color specification. See Color Names. On black-and-white displays, certain shades of gray are implemented by stipple patterns.
:distant-foregroundAlternative foreground color, a string. This is like :foreground
but the color is only used as a foreground when the background color is
near to the foreground that would have been used. This is useful for
example when marking text (i.e., the region face). If the text has a foreground
that is visible with the region face, that foreground is used.
If the foreground is near the region face background,
:distant-foreground is used instead so the text is readable.
:backgroundBackground color, a string. The value can be a system-defined color name, or a hexadecimal color specification. See Color Names.
:underline ¶Whether or not characters should be underlined, and in what
way. The possible values of the :underline attribute are:
nilDon’t underline.
tUnderline with the foreground color of the face.
Underline in color color, a string specifying a color.
(:color color :style style :position position)color is either a string, or the symbol foreground-color,
meaning the foreground color of the face. Omitting the attribute
:color means to use the foreground color of the face.
style is a symbol which sets the line-style to of the underline.
It should be one of line, double-line, wave,
dots, or dashes. GUI frames under most window systems
support all the aforementioned underline styles, while on text terminals
double-line, wave and dots are contingent on the
availability of the Smulx or Su terminfo capabilities.
Omitting the attribute :style means to use a straight line.
position, if non-nil, means to display the underline at the
descent of the text, instead of at the baseline level. If it is a
number, then it specifies the amount of pixels above the descent to
display the underline.
:overline ¶Whether or not characters should be overlined, and in what color.
If the value is t, overlining uses the foreground color of the
face. If the value is a string, overlining uses that color. The
value nil means do not overline.
:strike-through ¶Whether or not characters should be strike-through, and in what
color. The value is used like that of :overline.
:box ¶Whether or not a box should be drawn around characters, its color, the
width of the box lines, and 3D appearance. Here are the possible
values of the :box attribute, and what they mean:
nilDon’t draw a box.
tDraw a box with lines of width 1, in the foreground color.
Draw a box with lines of width 1, in color color.
(:line-width (vwidth . hwidth) :color color :style style)You can explicitly specify all aspects of the box with a plist of this form. Any element in this plist can be omitted.
The values of vwidth and hwidth specify respectively the
width of the vertical and horizontal lines to draw; they default to (1
. 1). A negative horizontal or vertical width −n means
to draw a line of width n that occupies the space of the
underlying text, thus avoiding any increase in the character height or
width. For simplification the width could be specified with only a
single number n instead of a list, such case is equivalent to
((abs n) . n).
The value of color specifies the color to draw with. The default
is the background color of the face for 3D boxes and
flat-button, and the foreground color of the face for other
boxes.
The value of style specifies whether to draw a 3D box. If it is
released-button, the box looks like a 3D button that is not
being pressed. If it is pressed-button, the box looks like a
3D button that is being pressed. If it is nil,
flat-button or omitted, a plain 2D box is used.
If you use the :box face attribute on strings displayed instead
of buffer text via the display text property, special
considerations might apply if the surrounding buffer text also has the
:box face attribute. See Display Specs That Replace The Text. Also note that the
vertical lines of the box are only drawn when :box attribute
changes from nil to non-nil or vice versa; two consecutive
face properties with a non-nil :box attribute will be
displayed without the vertical line between them.
:inverse-videoWhether or not characters should be displayed in inverse video. The
value should be t (yes) or nil (no).
:stippleThe background stipple, a bitmap.
The value can be a string; that should be the name of a file containing
external-format X bitmap data. The file is found in the directories
listed in the variable x-bitmap-file-path.
Alternatively, the value can specify the bitmap directly, with a list
of the form (width height data). Here,
width and height specify the size in pixels, and
data is a string containing the raw bits of the bitmap, row by
row. Each row occupies (width + 7) / 8 consecutive bytes
in the string (which should be a unibyte string for best results).
This means that each row always occupies at least one whole byte.
If the value is nil, that means use no stipple pattern.
Normally you do not need to set the stipple attribute, because it is used automatically to handle certain shades of gray.
:fontThe font used to display the face. Its value should be a font object or a fontset. If it is a font object, it specifies the font to be used by the face for displaying ASCII characters. See Low-Level Font Representation, for information about font objects, font specs, and font entities. See Fontsets, for information about fontsets.
When specifying this attribute using set-face-attribute or
set-face-font (see Face Attribute Functions), you may also
supply a font spec, a font entity, or a string. Emacs converts such
values to an appropriate font object, and stores that font object as
the actual attribute value. If you specify a string, the contents of
the string should be a font name (see Fonts in The GNU Emacs
Manual); if the font name is an XLFD containing wildcards, Emacs
chooses the first font matching those wildcards. Specifying this
attribute also changes the values of the :family,
:foundry, :width, :height, :weight, and
:slant attributes.
:inherit ¶The name of a face from which to inherit attributes, or a list of face
names. Attributes from inherited faces are merged into the face like
an underlying face would be, with higher priority than underlying
faces (see Displaying Faces). If the face to inherit from is
unspecified, it is treated the same as nil, since Emacs
never merges :inherit attributes. If a list of faces is used,
attributes from faces earlier in the list override those from later
faces.
:extendWhether or not this face will be extended beyond end of line and will
affect the display of the empty space between the end of line and the
edge of the window. The value should be t to display the empty
space between end of line and edge of the window using this face, or
nil to not use this face for the space between the end of the
line and the edge of the window. When Emacs merges several faces for
displaying the empty space beyond end of line, only those faces with
:extend non-nil will be merged. By default, only a
small number of faces, notably, region, have this attribute
set. This attribute is different from the others in that when a theme
doesn’t specify an explicit value for a face, the value from the
original face definition by defface is inherited
(see Defining Faces).
Some modes, like hl-line-mode, use a face with an
:extend property to mark the entire current line. Note,
however, that Emacs will always allow you to move point after the
final character in a buffer, and if the buffer ends with a newline
character, point can be placed on what is seemingly a line at the end
of the buffer—but Emacs can’t highlight that “line”, because it
doesn’t really exist.
This function returns a list of available font family names. The
optional argument frame specifies the frame on which the text is
to be displayed; if it is nil, the selected frame is used.
This variable specifies the minimum distance between the baseline and the underline, in pixels, when displaying underlined text.
This variable specifies a list of directories for searching
for bitmap files, for the :stipple attribute.
This returns t if object is a valid bitmap specification,
suitable for use with :stipple (see above). It returns
nil otherwise.
The usual way to define a face is through the defface macro.
This macro associates a face name (a symbol) with a default face
spec. A face spec is a construct which specifies what attributes a
face should have on any given terminal; for example, a face spec might
specify one foreground color on high-color terminals, and a different
foreground color on low-color terminals.
People are sometimes tempted to create a variable whose value is a
face name. In the vast majority of cases, this is not necessary; the
usual procedure is to define a face with defface, and then use
its name directly.
Note that once you have defined a face (usually with defface),
you cannot later undefine this face safely, except by restarting
Emacs.
This macro declares face as a named face whose default face spec
is given by spec. You should not quote the symbol face,
and it should not end in ‘-face’ (that would be redundant). The
argument doc is a documentation string for the face. The
additional keyword arguments have the same meanings as in
defgroup and defcustom (see Common Item Keywords).
If face already has a default face spec, this macro does nothing.
The default face spec determines face’s appearance when no customizations are in effect (see Customization Settings). If face has already been customized (via Custom themes or via customizations read from the init file), its appearance is determined by the custom face spec(s), which override the default face spec spec. However, if the customizations are subsequently removed, the appearance of face will again be determined by its default face spec.
As an exception, if you evaluate a defface form with
C-M-x (eval-defun) or with C-x C-e
(eval-last-sexp) in Emacs Lisp mode, a special feature of these
commands overrides any custom face specs on the face, causing the face
to reflect exactly what the defface says.
The spec argument is a face spec, which states how the face should appear on different kinds of terminals. It should be an alist whose elements each have the form
(display . plist)
display specifies a class of terminals (see below). plist
is a property list of face attributes and their values, specifying how
the face appears on such terminals. For backward compatibility, you
can also write an element as (display plist).
The display part of an element of spec determines which terminals the element matches. If more than one element of spec matches a given terminal, the first element that matches is the one used for that terminal. There are three possibilities for display:
defaultThis element of spec doesn’t match any terminal; instead, it specifies defaults that apply to all terminals. This element, if used, must be the first element of spec. Each of the following elements can override any or all of these defaults.
tThis element of spec matches all terminals. Therefore, any
subsequent elements of spec are never used. Normally t
is used in the last (or only) element of spec.
If display is a list, each element should have the form
(characteristic value…). Here
characteristic specifies a way of classifying terminals, and the
values are possible classifications which display should
apply to. Here are the possible values of characteristic:
typeThe kind of window system the terminal uses—either graphic
(any graphics-capable display), x, pc (for the MS-DOS
console), w32 (for MS Windows 9X/NT/2K/XP), haiku (for
Haiku), pgtk (for pure GTK), android (for Android), or
tty (a non-graphics-capable display). See window-system.
classWhat kinds of colors the terminal supports—either color,
grayscale, or mono.
backgroundThe kind of background—either light or dark.
min-colorsAn integer that represents the minimum number of colors the terminal
should support. This matches a terminal if its
display-color-cells value is at least the specified integer.
supportsWhether or not the terminal can display the face attributes given in value… (see Face Attributes). See Display Face Attribute Testing, for more information on exactly how this testing is done.
If an element of display specifies more than one value for a given characteristic, any of those values is acceptable. If display has more than one element, each element should specify a different characteristic; then each characteristic of the terminal must match one of the values specified for it in display.
For example, here’s the definition of the standard face
highlight:
(defface highlight
'((((class color) (min-colors 88) (background light))
:background "darkseagreen2")
(((class color) (min-colors 88) (background dark))
:background "darkolivegreen")
(((class color) (min-colors 16) (background light))
:background "darkseagreen2")
(((class color) (min-colors 16) (background dark))
:background "darkolivegreen")
(((class color) (min-colors 8))
:background "green" :foreground "black")
(t :inverse-video t))
"Basic face for highlighting."
:group 'basic-faces)
Internally, Emacs stores each face’s default spec in its
face-defface-spec symbol property (see Symbol Properties).
The saved-face property stores any face spec saved by the user
using the customization buffer; the customized-face property
stores the face spec customized for the current session, but not
saved; and the theme-face property stores an alist associating
the active customization settings and Custom themes with the face
specs for that face. The face’s documentation string is stored in the
face-documentation property.
Normally, a face is declared just once, using defface, and
any further changes to its appearance are applied using the Customize
framework (e.g., via the Customize user interface or via the
custom-set-faces function; see Applying Customizations), or
by face remapping (see Face Remapping). In the rare event that
you need to change a face spec directly from Lisp, you can use the
face-spec-set function.
This function applies spec as a face spec for face.
spec should be a face spec, as described in the above
documentation for defface.
This function also defines face as a valid face name if it is not already one, and (re)calculates its attributes on existing frames.
The optional argument spec-type determines which spec to set.
If it is omitted or nil or face-override-spec, this
function sets the override spec, which overrides face specs on
face of all the other types mentioned below. This is useful
when calling this function outside of Custom code. If spec-type
is customized-face or saved-face, this function sets the
customized spec or the saved custom spec, respectively. If it is
face-defface-spec, this function sets the default face spec
(the same one set by defface). If it is reset, this
function clears out all customization specs and override specs from
face (in this case, the value of spec is ignored). The
effect of any other value of spec-type on the face specs is
reserved for internal use, but the function will still define
face itself and recalculate its attributes, as described above.
This section describes functions for directly accessing and modifying the attributes of a named face.
This function returns the value of the attribute attribute for face on frame. See Face Attributes, for the supported attributes.
If frame is omitted or nil, that means the selected frame
(see Input Focus). If frame is t, this function
returns the value of the specified attribute for newly-created frames,
i.e. the value of the attribute before applying the face spec in the
face’s defface definition (see Defining Faces) or the spec
set by face-spec-set. This default value of attribute is
normally unspecified, unless you have specified some other
value using set-face-attribute; see below.
If inherit is nil, only attributes directly defined by
face are considered, so the return value may be
unspecified, or a relative value. If inherit is
non-nil, face’s definition of attribute is merged
with the faces specified by its :inherit attribute; however the
return value may still be unspecified or relative. If
inherit is a face or a list of faces, then the result is further
merged with that face (or faces), until it becomes specified and
absolute.
To ensure that the return value is always specified and absolute, use
a value of default for inherit; this will resolve any
unspecified or relative values by merging with the default face
(which is always completely specified).
For example,
(face-attribute 'bold :weight)
⇒ bold
This function returns non-nil if value, when used as the
value of the face attribute attribute, is relative. This means
it would modify, rather than completely override, any value that comes
from a subsequent face in the face list or that is inherited from
another face.
unspecified is a relative value for all attributes. For
:height, floating point and function values are also relative.
For example:
(face-attribute-relative-p :height 2.0)
⇒ t
This function returns an alist of attributes of face. The
elements of the result are name-value pairs of the form
(attr-name . attr-value). Optional argument
frame specifies the frame whose definition of face to
return; if omitted or nil, the returned value describes the
default attributes of face for newly created frames, i.e. the
values these attributes have before applying the face spec in the face’s
defface definition or the spec set by face-spec-set.
These default values of the attributes are normally unspecified,
unless you have specified some other value using
set-face-attribute; see below. The optional argument
inherit has the same meaning as the same argument to
face-attribute, which see. This is useful when you want the face
attributes to be absolute and not unspecified.
If value1 is a relative value for the face attribute attribute, returns it merged with the underlying value value2; otherwise, if value1 is an absolute value for the face attribute attribute, returns value1 unchanged.
Normally, Emacs uses the face specs of each face to automatically
calculate its attributes on each frame (see Defining Faces). The
function set-face-attribute can override this calculation by
directly assigning attributes to a face, either on a specific frame or
for all frames. This function is mostly intended for internal usage.
This function sets one or more attributes of face for frame. The attributes specified in this way override the face spec(s) belonging to face. See Face Attributes, for the supported attributes.
The extra arguments arguments specify the attributes to set, and
the values for them. They should consist of alternating attribute
names (such as :family or :underline) and values. Thus,
(set-face-attribute 'foo nil :weight 'bold :slant 'italic)
sets the attribute :weight to bold and the attribute
:slant to italic.
If frame is t, this function sets the default attributes
for newly created frames; they will effectively override the attribute
values specified by defface. If frame is nil,
this function sets the attributes for all existing frames, as well as
for newly created frames.
To reset the value of an attribute, that is, to indicate that
the face doesn’t by itself specify a value for the attribute, use the
special value unspecified (not nil!) for the
attribute, and set the frame argument to t, in addition
to the call with frame set to nil. This is because the
default attributes for newly created frames are merged with the face’s
spec in defface when a new frame is created, and so having
unspecified in the default attributes for new frames will be
unable to override defface; the special call to this function
as described above will arrange for defface to be overridden.
Note that the attribute-value pairs are evaluated in the order they
are specified, with the exception of the :family and
:foundry attributes, which are evaluated first. This means
that if a certain attribute is specified more than once, only the last
value will be used. It also means that in some cases a different
order of attributes will produce different results. For example, when
:weight is placed before :font, the weight value is
applied to the current font of the face, and might be rounded to the
closest available weight of that font, whereas when :font is
placed before :weight the weight value is applied to the
specified font.
The following commands and functions mostly provide compatibility
with old versions of Emacs. They work by calling
set-face-attribute. Values of t and nil (or
omitted) for their frame argument are handled just like
set-face-attribute and face-attribute. The commands
read their arguments using the minibuffer, if called interactively.
These set the :foreground attribute (or :background
attribute, respectively) of face to color.
This sets the :stipple attribute of face to
pattern.
Change the font-related attributes of face to those of
font (a string or a font object). See face-font-attribute,
for the supported formats of the font argument. This function
sets the attribute :font of the face, and indirectly also the
:family, :foundry, :width, :height,
:weight, and :slant attributes, as defined by the font.
If frame is non-nil, only change the attributes on the
specified frame.
This sets the :weight attribute of face to normal
if bold-p is nil, and to bold otherwise.
This sets the :slant attribute of face to normal if
italic-p is nil, and to italic otherwise.
This sets the :underline attribute of face to
underline.
This sets the :inverse-video attribute of face to
inverse-video-p.
This swaps the foreground and background colors of face face.
This sets the :extend attribute of face to
extend.
The following functions examine the attributes of a face. They
mostly provide compatibility with old versions of Emacs. If you don’t
specify frame, they refer to the selected frame; t refers
to the default data for new frames. They return unspecified if
the face doesn’t define any value for that attribute. If
inherit is nil, only an attribute directly defined by the
face is returned. If inherit is non-nil, any faces
specified by its :inherit attribute are considered as well, and
if inherit is a face or a list of faces, then they are also
considered, until a specified attribute is found. To ensure that the
return value is always specified, use a value of default for
inherit.
This function returns the name of the font used by the specified face.
If the optional argument frame is specified, it returns the name
of the font of face for that frame; frame defaults to the
selected frame if it is nil or omitted. If frame is
t, the function reports on the font defaults for face to
be used for new frames.
By default, the returned font is for displaying ASCII characters, but
if frame is anything but t, and the optional third
argument character is supplied, the function returns the font
name used by face for that character.
These functions return the foreground color (or background color,
respectively) of face face, as a string. If the color is
unspecified, they return nil.
This function returns the name of the background stipple pattern of face
face, or nil if it doesn’t have one.
This function returns a non-nil value if the :weight
attribute of face is bolder than normal (i.e., one of
semi-bold, bold, extra-bold, or
ultra-bold). Otherwise, it returns nil.
This function returns a non-nil value if the :slant
attribute of face is italic or oblique, and
nil otherwise.
This function returns non-nil if face face specifies
a non-nil :underline attribute.
This function returns non-nil if face face specifies
a non-nil :inverse-video attribute.
This function returns non-nil if face face specifies
a non-nil :extend attribute. The inherit argument
is passed to face-attribute.
When Emacs displays a given piece of text, the visual appearance of the text may be determined by faces drawn from different sources. If these various sources together specify more than one face for a particular character, Emacs merges the attributes of the various faces. Here is the order in which Emacs merges the faces, from highest to lowest priority:
region face. See Standard Faces in The GNU Emacs
Manual.
nil face
property, Emacs applies the face(s) specified by that property. If
the overlay has a mouse-face property and the mouse is near
enough to the overlay, Emacs applies the face or face attributes
specified by the mouse-face property instead. See Overlay Properties.
When multiple overlays cover the same character, an overlay with higher priority overrides those with lower priority. See Overlays.
face or mouse-face property,
Emacs applies the specified faces and face attributes. See Properties with Special Meanings. (This is how Font Lock mode faces are applied.
See Font Lock Mode.)
mode-line face. For the mode line of a
non-selected window, Emacs applies the mode-line-inactive face.
For a header line, Emacs applies the header-line face.
For a tab line, Emacs applies the tab-line face.
before-string or
after-string properties (see Overlay Properties), or from a
display string (see Other Display Specifications), and the string doesn’t
contain a face or mouse-face property, or these
properties leave some face attributes undefined, but the buffer text
affected by the overlay/display property does define a face or those
attributes, Emacs applies the face attributes of the “underlying”
buffer text. However, this does not apply to strings displayed in the
display margins, which use the margin face as the base instead
(see Displaying in the Margins).
margin face as the base, so any attribute not specified by the
string’s own face is taken from the margin face.
default face.
At each stage, if a face has a valid :inherit attribute,
Emacs treats any attribute with an unspecified value as having
the corresponding value drawn from the parent face(s). see Face Attributes. Note that the parent face(s) may also leave the
attribute unspecified; in that case, the attribute remains unspecified
at the next level of face merging.
The variable face-remapping-alist is used for buffer-local or
global changes in the appearance of a face. For instance, it is used
to implement the text-scale-adjust command (see Text
Scale in The GNU Emacs Manual).
The value of this variable is an alist whose elements have the form
(face . remapping). This causes Emacs to display
any text having the face face with remapping, rather than
the ordinary definition of face.
remapping may be any face spec suitable for a face text
property: either a face (i.e., a face name or a property list of
attribute/value pairs), or a list of faces. For details, see the
description of the face text property in Properties with Special Meanings. remapping serves as the complete specification for
the remapped face—it replaces the normal definition of face,
instead of modifying it.
If face-remapping-alist is buffer-local, its local value takes
effect only within that buffer. If face-remapping-alist
includes faces applicable only to certain windows, by using the
(:filtered (:window param val) spec),
that face takes effect only in windows that match the filter
conditions (see Properties with Special Meanings). To turn off face filtering
temporarily, bind face-filters-always-match to a non-nil
value, then all face filters will match any window.
Note: face remapping is non-recursive. If remapping references
the same face name face, either directly or via the
:inherit attribute of some other face in remapping, that
reference uses the normal definition of face. For instance, if
the mode-line face is remapped using this entry in
face-remapping-alist:
(mode-line italic mode-line)
then the new definition of the mode-line face inherits from the
italic face, and the normal (non-remapped) definition of
mode-line face.
The following functions implement a higher-level interface to
face-remapping-alist. Most Lisp code should use these
functions instead of setting face-remapping-alist directly, to
avoid trampling on remappings applied elsewhere. These functions are
intended for buffer-local remappings, so they all make
face-remapping-alist buffer-local as a side-effect. They manage
face-remapping-alist entries of the form
(face relative-spec-1 relative-spec-2 ... base-spec)
where, as explained above, each of the relative-spec-N and
base-spec is either a face name, or a property list of
attribute/value pairs. Each of the relative remapping entries,
relative-spec-N, is managed by the
face-remap-add-relative and face-remap-remove-relative
functions; these are intended for simple modifications like changing
the text size. The base remapping entry, base-spec, has
the lowest priority and is managed by the face-remap-set-base
and face-remap-reset-base functions; it is intended for major
modes to remap faces in the buffers they control.
This function adds specs as relative remappings for face face in the current buffer. specs should be a list where each element is either a face name, or a property list of attribute/value pairs.
The return value is a Lisp object that serves as a cookie; you can
pass this object as an argument to face-remap-remove-relative
if you need to remove the remapping later.
;; Remap the 'escape-glyph' face into a combination ;; of the 'highlight' and 'italic' faces: (face-remap-add-relative 'escape-glyph 'highlight 'italic) ;; Increase the size of the 'default' face by 50%: (face-remap-add-relative 'default :height 1.5)
Note that buffer-local face remapping does not work reliably for
parent faces of basic faces (see Basic Faces). (These are the
faces that are used in mode lines, header lines, and other basic
decorations of windows and frames.) For instance,
mode-line-inactive inherits from mode-line, but
remapping mode-line won’t normally have the desired effect on
mode-line-inactive, especially if done locally for some
buffers. Instead you have to remap mode-line-inactive
directly.
This function removes a relative remapping previously added by
face-remap-add-relative. cookie should be the Lisp
object returned by face-remap-add-relative when the remapping
was added.
This function sets the base remapping of face in the current
buffer to specs. If specs is empty, the default base
remapping is restored, similar to calling face-remap-reset-base
(see below); note that this is different from specs containing a
single value nil, which has the opposite result (the global
definition of face is ignored).
This overwrites the default base-spec, which inherits the global face definition, so it is up to the caller to add such inheritance if so desired.
This function sets the base remapping of face to its default value, which inherits from face’s global definition.
Here are additional functions for creating and working with faces.
This function returns a list of all defined face names.
This function returns the face number of face face. This
is a number that uniquely identifies a face at low levels within
Emacs. It is seldom necessary to refer to a face by its face number.
However, functions that manipulate glyphs, such as
make-glyph-code and glyph-face (see Glyphs) access
the face numbers internally. Note that the face number is stored as
the value of the face property of the face symbol, so we
recommend not to set that property of a face to any value of your own.
This function returns the documentation string of face face, or
nil if none was specified for it.
This returns t if the faces face1 and face2 have the
same attributes for display.
This returns non-nil if the face face displays
differently from the default face.
A face alias provides an equivalent name for a face. You can
define a face alias by giving the alias symbol the face-alias
property, with a value of the target face name. The following example
makes modeline an alias for the mode-line face.
(put 'modeline 'face-alias 'mode-line)
This macro defines obsolete-face as an alias for current-face, and also marks it as obsolete, indicating that it may be removed in the future. when should be a string indicating when obsolete-face was made obsolete (usually a version number string).
This hook is used for automatically assigning faces to text in the buffer. It is part of the implementation of Jit-Lock mode, used by Font-Lock.
This variable holds a list of functions that are called by Emacs
redisplay as needed, just before doing redisplay. They are called even
when Font Lock Mode isn’t enabled. When Font Lock Mode is enabled, this
variable usually holds just one function, jit-lock-function.
The functions are called in the order listed, with one argument, a buffer position pos. Collectively they should attempt to assign faces to the text in the current buffer starting at pos.
The functions should record the faces they assign by setting the
face property. They should also add a non-nil
fontified property to all the text they have assigned faces to.
That property tells redisplay that faces have been assigned to that text
already.
It is probably a good idea for the functions to do nothing if the
character after pos already has a non-nil fontified
property, but this is not required. If one function overrides the
assignments made by a previous one, the properties after the last
function finishes are the ones that really matter.
For efficiency, we recommend writing these functions so that they usually assign faces to around 400 to 600 characters at each call.
Note that, when the buffer text includes very long lines, these
functions are called as if they were in a with-restriction form
(see Narrowing), with a
long-line-optimizations-in-fontification-functions label and
with the buffer narrowed to a portion around pos.
If your Emacs Lisp program needs to assign some faces to text, it is often a good idea to use certain existing faces or inherit from them, rather than defining entirely new faces. This way, if other users have customized those existing faces to give Emacs a certain look, your program will fit in without additional customization.
Some of the basic faces defined in Emacs are listed below. In addition to these, you might want to make use of the Font Lock faces for syntactic highlighting, if highlighting is not already handled by Font Lock mode, or if some Font Lock faces are not in use. See Faces for Font Lock.
defaultThe default face, whose attributes are all specified. All other faces implicitly inherit from it: any unspecified attribute defaults to the attribute on this face (see Face Attributes).
mode-line-active ¶mode-line-inactiveheader-linetab-lineBasic faces used for the mode line, header line, and tab line.
tool-bar ¶tab-barfringescroll-barwindow-dividerborderchild-frame-borderBasic faces used for the corresponding decorations of GUI frames.
cursor ¶The basic face used for the text cursor.
margin ¶The basic face used for window margins, both on the left and on the
right. It is commonly used to customize the background of the empty
areas of the margins, and it also provides the base attributes for
strings displayed in the margins (see Displaying in the Margins). It
inherits from the default face.
mouse ¶The basic face used for displaying mouse-sensitive text when the mouse pointer is on that text.
bolditalicbold-italicunderlinefixed-pitchfixed-pitch-serifvariable-pitchThese have the attributes indicated by their names (e.g., bold
has a bold :weight attribute), with all other attributes
unspecified (and so given by default).
shadow ¶For dimmed-out text. For example, it is used for the ignored part of a filename in the minibuffer (see Minibuffers for File Names in The GNU Emacs Manual).
linklink-visitedFor clickable text buttons that send the user to a different buffer or location.
highlightFor stretches of text that should temporarily stand out. For example,
it is commonly assigned to the mouse-face property for cursor
highlighting (see Properties with Special Meanings).
match ¶isearchlazy-highlightFor text matching (respectively) permanent search matches, interactive search matches, and lazy highlighting other matches than the current interactive one.
error ¶warningsuccessFor text concerning errors, warnings, or successes. For example, these are used for messages in *Compilation* buffers.
Before Emacs can draw a character on a graphical display, it must
select a font for that character33. See Fonts in The GNU Emacs Manual. Normally,
Emacs automatically chooses a font based on the faces assigned to that
character—specifically, the face attributes :family,
:weight, :slant, and :width (see Face Attributes). The choice of font also depends on the character to be
displayed; some fonts can only display a limited set of characters.
If no available font exactly fits the requirements, Emacs looks for
the closest matching font. The variables in this section
control how Emacs makes this selection.
If a given family is specified but does not exist, this variable specifies alternative font families to try. Each element should have this form:
(family alternate-families...)
If family is specified but not available, Emacs will try the other families given in alternate-families, one by one, until it finds a family that does exist.
If there is no font that exactly matches all desired face attributes
(:width, :height, :weight, and :slant),
this variable specifies the order in which these attributes should be
considered when selecting the closest matching font. The value should
be a list containing those four attribute symbols, in order of
decreasing importance. The default is (:width :height :weight
:slant).
Font selection first finds the best available matches for the first attribute in the list; then, among the fonts which are best in that way, it searches for the best matches in the second attribute, and so on.
The attributes :weight and :width have symbolic values in
a range centered around normal. Matches that are more extreme
(farther from normal) are somewhat preferred to matches that are
less extreme (closer to normal); this is designed to ensure that
non-normal faces contrast with normal ones, whenever possible.
One example of a case where this variable makes a difference is when the
default font has no italic equivalent. With the default ordering, the
italic face will use a non-italic font that is similar to the
default one. But if you put :slant before :height, the
italic face will use an italic font, even if its height is not
quite right.
This variable lets you specify alternative font registries to try, if a given registry is specified and doesn’t exist. Each element should have this form:
(registry alternate-registries...)
If registry is specified but not available, Emacs will try the other registries given in alternate-registries, one by one, until it finds a registry that does exist.
Emacs can make use of scalable fonts, but by default it does not use them.
This variable controls which scalable fonts to use. A value of
nil, the default, means do not use scalable fonts. t
means to use any scalable font that seems appropriate for the text.
Otherwise, the value must be a list of regular expressions. Then a scalable font is enabled for use if its name matches any regular expression in the list. For example,
(setq scalable-fonts-allowed '("iso10646-1$"))
allows the use of scalable fonts with registry iso10646-1.
This variable specifies scaling for certain faces. Its value should be a list of elements of the form
(fontname-regexp . scale-factor)
If fontname-regexp matches the font name that is about to be used, this says to choose a larger similar font according to the factor scale-factor. You would use this feature to normalize the font size if certain fonts are bigger or smaller than their nominal heights and widths would suggest.
This function returns a list of available font names that match name. name should be a string containing a font name in either the Fontconfig, GTK+, or XLFD format (see Fonts in The GNU Emacs Manual). Within an XLFD string, wildcard characters may be used: the ‘*’ character matches any substring, and the ‘?’ character matches any single character. Case is ignored when matching font names.
If the optional arguments reference-face and frame are specified, the returned list includes only fonts that are the same size as reference-face (a face name) currently is on the frame frame.
The optional argument maximum sets a limit on how many fonts to
return. If it is non-nil, then the return value is truncated
after the first maximum matching fonts. Specifying a small
value for maximum can make this function much faster, in cases
where many fonts match the pattern.
The optional argument width specifies a desired font width. If
it is non-nil, the function only returns those fonts whose
characters are (on average) width times as wide as
reference-face.
This function returns a list describing the available fonts for family
family on frame. If family is omitted or nil,
this list applies to all families, and therefore, it contains all
available fonts. Otherwise, family must be a string; it may
contain the wildcards ‘?’ and ‘*’.
The list describes the display that frame is on; if frame is
omitted or nil, it applies to the selected frame’s display
(see Input Focus).
Each element in the list is a vector of the following form:
[family width point-size weight slant fixed-p full registry-and-encoding]
The first five elements correspond to face attributes; if you specify these attributes for a face, it will use this font.
The last three elements give additional information about the font.
fixed-p is non-nil if the font is fixed-pitch.
full is the full name of the font, and
registry-and-encoding is a string giving the registry and
encoding of the font.
A fontset is a list of fonts, each assigned to a range of character codes. An individual font cannot display the whole range of characters that Emacs supports, but a fontset can. Fontsets have names, just as fonts do, and you can use a fontset name in place of a font name when you specify the font for a frame or a face. Here is information about defining a fontset under Lisp program control.
This function defines a new fontset according to the specification string fontset-spec. The string should have this format:
fontpattern, [charset:font]...
Whitespace characters before and after the commas are ignored.
The first part of the string, fontpattern, should have the form of a standard X font name, except that the last two fields should be ‘fontset-alias’.
The new fontset has two names, one long and one short. The long name is
fontpattern in its entirety. The short name is
‘fontset-alias’. You can refer to the fontset by either
name. If a fontset with the same name already exists, an error is
signaled, unless noerror is non-nil, in which case this
function does nothing.
If optional argument style-variant-p is non-nil, that says
to create bold, italic and bold-italic variants of the fontset as well.
These variant fontsets do not have a short name, only a long one, which
is made by altering fontpattern to indicate the bold and/or italic
status.
The specification string also says which fonts to use in the fontset. See below for the details.
The construct ‘charset:font’ specifies which font to use (in this fontset) for one particular character set. Here, charset is the name of a character set, and font is the font to use for that character set. You can use this construct any number of times in the specification string.
For the remaining character sets, those that you don’t specify explicitly, Emacs chooses a font based on fontpattern: it replaces ‘fontset-alias’ with a value that names one character set. For the ASCII character set, ‘fontset-alias’ is replaced with ‘ISO8859-1’.
In addition, when several consecutive fields are wildcards, Emacs collapses them into a single wildcard. This is to prevent use of auto-scaled fonts. Fonts made by scaling larger fonts are not usable for editing, and scaling a smaller font is not useful because it is better to use the smaller font in its own size, which Emacs does.
Thus if fontpattern is this,
-*-fixed-medium-r-normal-*-24-*-*-*-*-*-fontset-24
the font specification for ASCII characters would be this:
-*-fixed-medium-r-normal-*-24-*-ISO8859-1
and the font specification for Chinese GB2312 characters would be this:
-*-fixed-medium-r-normal-*-24-*-gb2312*-*
You may not have any Chinese font matching the above font specification. Most X distributions include only Chinese fonts that have ‘song ti’ or ‘fangsong ti’ in the family field. In such a case, ‘Fontset-n’ can be specified as below:
Emacs.Fontset-0: -*-fixed-medium-r-normal-*-24-*-*-*-*-*-fontset-24,\
chinese-gb2312:-*-*-medium-r-normal-*-24-*-gb2312*-*
Then, the font specifications for all but Chinese GB2312 characters have ‘fixed’ in the family field, and the font specification for Chinese GB2312 characters has a wild card ‘*’ in the family field.
This function modifies the existing fontset to use the font specified by font-spec for displaying the specified characters.
If fontset is nil, this function modifies the fontset of
the selected frame or that of frame if frame is not
nil.
If fontset is t, this function modifies the default
fontset, whose short name as a string is ‘fontset-default’.
The characters argument can be a single character which should
be displayed using font-spec. It can also be a cons cell
(from . to), where from and to are
characters. In that case, use font-spec for all the characters
in the range from and to (inclusive).
characters may be a charset symbol (see Character Sets). In that case, use font-spec for all the characters in the charset.
characters may be a script symbol (see char-script-table). In that case, use font-spec for all the
characters belonging to the script. See also
use-default-font-for-symbols, which affects font selection
when characters specify or belong to the symbol script
(which includes symbol and punctuation characters).
characters may be nil, which means to use font-spec
for any character in fontset for which no font-spec is
specified.
font-spec may be a font-spec object created by the function
font-spec (see Low-Level Font Representation).
font-spec may be a cons cell (family . registry), where family is a family name of a font
(possibly including a foundry name at the head), and registry is
a registry name of a font (possibly including an encoding name at the
tail).
font-spec may be a font name, a string.
font-spec may be nil, which explicitly specifies that
there’s no font for the specified characters. This is useful,
for example, to avoid expensive system-wide search for fonts for
characters that have no glyphs, like those from the Unicode Private
Use Area (PUA).
The optional argument add, if non-nil, specifies how to
add font-spec to the font specifications previously set for
characters. If it is prepend, font-spec is
prepended to the existing specs. If it is append,
font-spec is appended. By default, font-spec overwrites
the previously set font specs.
For instance, this changes the default fontset to use a font whose
family name is ‘Kochi Gothic’ for all characters belonging to
the charset japanese-jisx0208:
(set-fontset-font t 'japanese-jisx0208
(font-spec :family "Kochi Gothic"))
Note that this function should generally be called from the user’s init files, and more generally before any of characters were displayed in the current Emacs session. That’s because for some scripts, Emacs caches the way they are displayed, and the cached information includes the font used for them – once these characters are displayed once, the cached font will continue to be used regardless of changes in the fontsets.
This function returns non-nil if Emacs ought to be able to
display char. Or more precisely, if the selected frame’s fontset
has a font to display the character set that char belongs to.
Fontsets can specify a font on a per-character basis; when the fontset does that, this function’s value may not be accurate.
This function may return non-nil even when there is no font
available, since it also checks whether the coding system for the text
terminal can encode the character (see Terminal I/O Encoding).
This function behaves like char-displayable-p does (relative to
frame), but in the graphical case, it does not perform the final
check of whether the underlying text terminal can encode the character.
It thus provides a displayability check for char more specific to
frame.
Normally, it is not necessary to manipulate fonts directly. In case you need to do so, this section explains how.
In Emacs Lisp, fonts are represented using three different Lisp object types: font objects, font specs, and font entities.
Return t if object is a font object, font spec, or font
entity. Otherwise, return nil.
The optional argument type, if non-nil, determines the
exact type of Lisp object to check for. In that case, type
should be one of font-object, font-spec, or
font-entity.
A font object is a Lisp object that represents a font that Emacs has opened. Font objects cannot be modified in Lisp, but they can be inspected.
Return the font object that is being used to display the character at
position position in the window window. If window
is nil, it defaults to the selected window. If string is
nil, position specifies a position in the current buffer;
otherwise, string should be a string, and position
specifies a position in that string.
A font spec is a Lisp object that contains a set of specifications that can be used to find a font. More than one font may match the specifications in a font spec.
Return a new font spec using the specifications in arguments,
which should come in property-value pairs. The possible
specifications are as follows:
:nameThe font name (a string), in either XLFD, Fontconfig, or GTK+ format. See Fonts in The GNU Emacs Manual.
:family:foundry:weight:slant:widthThese have the same meanings as the face attributes of the same name.
See Face Attributes. :family and :foundry are
strings or symbols, while the other three are either symbols or numbers,
the numerical values of the valid style symbols. As example values,
:slant may be italic, :weight may be bold
and :width may be normal.
:sizeThe font size—either a non-negative integer that specifies the pixel size, or a floating-point number that specifies the point size.
:adstyleAdditional typographic style information for the font, such as ‘sans’. The value should be a string or a symbol.
:registry ¶The charset registry and encoding of the font, such as ‘iso8859-1’. The value should be a string or a symbol.
:dpiThe resolution in dots per inch for which the font is designed. The value must be a non-negative number.
:spacingThe spacing of the font: proportional, dual, mono, or charcell. The
value should be either an integer (0 for proportional, 90 for dual,
100 for mono, 110 for charcell) or a one-letter symbol (one of
P, D, M, or C).
:avgwidthThe average width of the font in 1/10 pixel units. The value should be a non-negative number.
:scriptThe script that the font must support (a symbol).
:langThe language that the font should support. The value should be a symbol whose name is a two-letter ISO-639 language name. On X, the value is matched against the “Additional Style” field of the XLFD name of a font, if it is non-empty. On MS-Windows, fonts matching the spec are required to support codepages needed for the language. Currently, only a small set of CJK languages is supported with this property: ‘ja’, ‘ko’, and ‘zh’.
:otf ¶The font must be an OpenType font that supports these OpenType features, provided Emacs is compiled with a library, such as ‘libotf’ on GNU/Linux, that supports complex text layout for scripts which need that. The value must be a list of the form
(script-tag langsys-tag gsub gpos)
where script-tag is the OpenType script tag symbol;
langsys-tag is the OpenType language system tag symbol, or
nil to use the default language system; gsub is a list
of OpenType GSUB feature tag symbols, or nil if none is
required; and gpos is a list of OpenType GPOS feature tag
symbols, or nil if none is required. If gsub or
gpos is a list, a nil element in that list means that
the font must not match any of the remaining tag symbols. The
gpos element may be omitted. For the list of OpenType script,
language, and feature tags, see
the list of registered OTF tags.
:type ¶The symbol that specifies the font backend used to draw the
characters. The possible values depend on the platform and on how
Emacs was configured at build time. Typical values include
ftcrhb and xfthb on X, harfbuzz on MS-Windows,
ns on GNUstep, etc. It can also be nil if left
unspecified, typically in a font-spec.
Set the font property property in the font-spec font-spec to value. The property can any of the ones described above.
A font entity is a reference to a font that need not be open. Its properties are intermediate between a font object and a font spec: like a font object, and unlike a font spec, it refers to a single, specific font. Unlike a font object, creating a font entity does not load the contents of that font into computer memory. Emacs may open multiple font objects of different sizes from a single font entity referring to a scalable font.
This function returns a font entity that best matches the font spec
font-spec on frame frame. If frame is nil,
it defaults to the selected frame.
This function returns a list of all font entities that match the font spec font-spec.
The optional argument frame, if non-nil, specifies the
frame on which the fonts are to be displayed. The optional argument
num, if non-nil, should be an integer that specifies the
maximum length of the returned list. The optional argument
prefer, if non-nil, should be another font spec, which is
used to control the order of the returned list; the returned font
entities are sorted in order of decreasing closeness to that font
spec.
If you call set-face-attribute and pass a font spec, font
entity, or font name string as the value of the :font
attribute, Emacs opens the best matching font that is available
for display. It then stores the corresponding font object as the
actual value of the :font attribute for that face.
The following functions can be used to obtain information about a font. For these functions, the font argument can be a font object, a font entity, or a font spec.
This function returns the value of the font property property
for font. The property can any of the ones that
font-spec supports.
If font is a font spec and the font spec does not specify
property, the return value is nil. If font is a
font object or font entity, the value for the :script property
may be a list of scripts supported by the font, and the value of the
:otf property is a cons of the form (gsub . gpos), where gsub and gpos are lists
representing OpenType features supported by the font, of the form
((script-tag (langsys-tag feature...) ...) ...)
where script-tag, langsys-tag, and feature are symbols representing OpenType layout tags.
If font is a font object, the special property
:combining-capability is non-nil if the font backend of
font supports rendering of combining characters for non-OpenType
fonts.
This function returns a list of face attributes corresponding to
font. The optional argument frame specifies the frame on
which the font is to be displayed. If it is nil, the selected
frame is used. The return value has the form
(:family family :height height :weight weight :slant slant :width width)
where the values of family, height, weight, slant, and width are face attribute values. Some of these key-attribute pairs may be omitted from the list if they are not specified by font.
This function returns the XLFD (X Logical Font Descriptor), a string, matching font. See Fonts in The GNU Emacs Manual, for information about XLFDs.
If the optional argument fold-wildcards is non-nil,
consecutive wildcards in the XLFD are folded into one.
If the optional argument long-xlfds is omitted or nil,
then the function returns nil if the XLFD would exceed 255
characters in length; this is for compatibility with the X protocol,
which mandates that XLFDs are restricted to that length. If
long-xlfds is non-nil, this restriction is lifted, and
the function can return XLFDs of any length.
The following two functions return important information about a font.
This function returns information about a font specified by its
name, a string, as it is used on frame. If frame is
omitted or nil, it defaults to the selected frame.
The value returned by the function is a vector of the form
[opened-name full-name size height
baseline-offset relative-compose default-ascent
max-width ascent descent space-width
average-width filename capability]. Here’s the
description of each components of this vector:
The name used to open the font, a string.
The full name of the font, a string.
The pixel size of the font.
The height of the font in pixels.
The offset in pixels from the ASCII baseline, positive upward.
Numbers controlling how to compose characters.
The maximum advance width of the font.
The ascent and descent of this font. The sum of these two numbers should be equal to the value of height above.
The width, in pixels, of the font’s space character.
The average width of the font characters. Emacs uses this for calculating text layout on display; if the value of average-width is zero, Emacs uses the value of space-width instead for those purposes.
The file name of the font as a string. This can be nil if the
font back-end does not provide a way to find out the font’s file name.
A list whose first element is a symbol representing the font type, one
of x, opentype, truetype, type1,
pcf, or bdf. For OpenType fonts, the list includes 2
additional elements describing the GSUB and GPOS features
supported by the font. Each of these elements is a list of the form
((script (langsys feature …) …)
…), where script is a symbol representing an OpenType
script tag, langsys is a symbol representing an OpenType langsys
tag (or nil, which stands for the default langsys), and each
feature is a symbol representing an OpenType feature tag.
This function returns information about a font-object. (This is
in contrast to font-info, which takes the font name, a string,
as its argument.)
The value returned by the function is a vector of the form
[name filename pixel-size max-width
ascent descent space-width average-width
capability]. Here’s the description of each components of this
vector:
The font name, a string.
The file name of the font as a string. This can be nil if the
font back-end does not provide a way to find out the font’s file name.
The pixel size of the font used to open the font.
The maximum advance width of the font.
The ascent and descent of this font. The sum of these two numbers gives the font height.
The width, in pixels, of the font’s space character.
The average width of the font characters. If this is zero, Emacs uses the value of space-width instead, when it calculates text layout on display.
A list whose first element is a symbol representing the font type, one
of x, opentype, truetype, type1,
pcf, or bdf. For OpenType fonts, the list includes 2
additional elements describing the GSUB and GPOS features
supported by the font. Each of these elements is a list of the form
((script (langsys feature …) …)
…), where script is a symbol representing an OpenType
script tag, langsys is a symbol representing an OpenType langsys
tag (or nil, which stands for the default langsys), and each
feature is a symbol representing an OpenType feature tag.
The following four functions return size information about fonts used by various faces, allowing various layout considerations in Lisp programs. These functions take face remapping into consideration, returning information about the remapped face, if the face in question was remapped. See Face Remapping.
This function returns the average width in pixels of the font used by the current buffer’s default face, as that face is defined for the selected frame.
This function returns the height in pixels of the font used by the current buffer’s default face, as that face is defined for the selected frame.
This function returns the average width in pixels for the font used by
face in window. The specified window must be a live
window. If nil or omitted, window defaults to the
selected window, and face defaults to the default face in
window.
This function returns the height in pixels for the font used by
face in window. The specified window must be a live
window. If nil or omitted, window defaults to the
selected window, and face defaults to the default face in
window.
On graphical displays, Emacs draws fringes next to each window: thin vertical strips down the sides which can display bitmaps indicating truncation, continuation, horizontal scrolling, and so on.
The following buffer-local variables control the position and width of fringes in windows showing that buffer.
The fringes normally appear between the display margins and the window
text. If the value is non-nil, they appear outside the display
margins. See Displaying in the Margins.
This variable, if non-nil, specifies the width of the left
fringe in pixels. A value of nil means to use the left fringe
width from the window’s frame.
This variable, if non-nil, specifies the width of the right
fringe in pixels. A value of nil means to use the right fringe
width from the window’s frame.
Any buffer which does not specify values for these variables uses
the values specified by the left-fringe and right-fringe
frame parameters (see Layout Parameters).
The above variables actually take effect via the function
set-window-buffer (see Buffers and Windows), which calls
set-window-fringes as a subroutine. If you change one of these
variables, the fringe display is not updated in existing windows
showing the buffer, unless you call set-window-buffer again in
each affected window. You can also use set-window-fringes to
control the fringe display in individual windows.
This function sets the fringe widths of window window.
If window is nil, the selected window is used.
The argument left specifies the width in pixels of the left
fringe, and likewise right for the right fringe. A value of
nil for either one stands for the default width. If
outside-margins is non-nil, that specifies that fringes
should appear outside of the display margins.
If window is not large enough to accommodate fringes of the desired width, this leaves the fringes of window unchanged.
The values specified here may be later overridden by invoking
set-window-buffer (see Buffers and Windows) on window
with its keep-margins argument nil or omitted. However,
if the optional fifth argument persistent is non-nil and
the other arguments are processed successfully, the values specified
here unconditionally survive subsequent invocations of
set-window-buffer. This can be used to permanently turn off
fringes in the minibuffer window, consult the description of
set-window-scroll-bars for an example (see Scroll Bars).
This function returns information about the fringes of a window
window. If window is omitted or nil, the selected
window is used. The value has the form (left-width
right-width outside-margins persistent).
Fringe indicators are tiny icons displayed in the window fringe to indicate truncated or continued lines, buffer boundaries, etc.
When this is non-nil, Emacs displays a special glyph in the
fringe of each empty line at the end of the buffer, on graphical
displays. See Fringes. This variable is automatically
buffer-local in every buffer.
This buffer-local variable controls how the buffer boundaries and window scrolling are indicated in the window fringes.
Emacs can indicate the buffer boundaries—that is, the first and last line in the buffer—with angle icons when they appear on the screen. In addition, Emacs can display an up-arrow in the fringe to show that there is text above the screen, and a down-arrow to show there is text below the screen.
There are three kinds of basic values:
nilDon’t display any of these fringe icons.
leftDisplay the angle icons and arrows in the left fringe.
rightDisplay the angle icons and arrows in the right fringe.
Display the angle icons in the left fringe and don’t display the arrows.
Otherwise the value should be an alist that specifies which fringe
indicators to display and where. Each element of the alist should
have the form (indicator . position). Here,
indicator is one of top, bottom, up,
down, and t (which covers all the icons not yet
specified), while position is one of left, right
and nil.
For example, ((top . left) (t . right)) places the top angle
bitmap in left fringe, and the bottom angle bitmap as well as both
arrow bitmaps in right fringe. To show the angle bitmaps in the left
fringe, and no arrow bitmaps, use ((top . left) (bottom . left)).
This buffer-local variable specifies the mapping from logical fringe
indicators to the actual bitmaps displayed in the window fringes. The
value is an alist of elements (indicator
. bitmaps), where indicator specifies a logical indicator
type and bitmaps specifies the fringe bitmaps to use for that
indicator.
Each indicator should be one of the following symbols:
truncation, continuation.Used for truncation and continuation lines.
up, down, top, bottom, top-bottomUsed when indicate-buffer-boundaries is non-nil:
up and down indicate a buffer boundary lying above or
below the window edge; top and bottom indicate the
topmost and bottommost buffer text line; and top-bottom
indicates where there is just one line of text in the buffer.
empty-lineUsed to indicate empty lines after the buffer end when
indicate-empty-lines is non-nil.
overlay-arrowUsed for overlay arrows (see The Overlay Arrow).
Each bitmaps value may be a list of symbols (left
right [left1 right1]). The left and
right symbols specify the bitmaps shown in the left and/or right
fringe, for the specific indicator. left1 and right1 are
specific to the bottom and top-bottom indicators, and
are used to indicate that the last text line has no final newline.
Alternatively, bitmaps may be a single symbol which is used in
both left and right fringes.
See Fringe Bitmaps, for a list of standard bitmap symbols and how
to define your own. In addition, nil represents the empty
bitmap (i.e., an indicator that is not shown).
When fringe-indicator-alist has a buffer-local value, and
there is no bitmap defined for a logical indicator, or the bitmap is
t, the corresponding value from the default value of
fringe-indicator-alist is used.
When a line is exactly as wide as the window, Emacs displays the cursor in the right fringe instead of using two lines. Different bitmaps are used to represent the cursor in the fringe depending on the current buffer’s cursor type.
If this is non-nil, lines exactly as wide as the window (not
counting the final newline character) are not continued. Instead,
when point is at the end of the line, the cursor appears in the right
fringe.
This variable specifies the mapping from logical cursor type to the
actual fringe bitmaps displayed in the right fringe. The value is an
alist where each element has the form (cursor-type
. bitmap), which means to use the fringe bitmap bitmap to
display cursors of type cursor-type.
Each cursor-type should be one of box, hollow,
bar, hbar, or hollow-small. The first four have
the same meanings as in the cursor-type frame parameter
(see Cursor Parameters). The hollow-small type is used
instead of hollow when the normal hollow-rectangle
bitmap is too tall to fit on a specific display line.
Each bitmap should be a symbol specifying the fringe bitmap to be displayed for that logical cursor type. See Fringe Bitmaps.
When fringe-cursor-alist has a buffer-local value, and there is
no bitmap defined for a cursor type, the corresponding value from the
default value of fringes-indicator-alist is used.
The fringe bitmaps are the actual bitmaps which represent the
logical fringe indicators for truncated or continued lines, buffer
boundaries, overlay arrows, etc. Each bitmap is represented by a
symbol.
These symbols are referred to by the variable
fringe-indicator-alist, which maps fringe indicators to bitmaps
(see Fringe Indicators), and the variable
fringe-cursor-alist, which maps fringe cursors to bitmaps
(see Fringe Cursors).
Lisp programs can also directly display a bitmap in the left or
right fringe, by using a display property for one of the
characters appearing in the line (see Other Display Specifications). Such
a display specification has the form
(fringe bitmap [face])
fringe is either the symbol left-fringe or
right-fringe. bitmap is a symbol identifying the bitmap
to display. The optional face names a face whose foreground and
background colors are to be used to display the bitmap, using the
attributes of the fringe face for colors that face didn’t
specify. If face is omitted, that means to use the attributes
of the default face for the colors which the fringe face
didn’t specify. For predictable results that don’t depend on the
attributes of the default and fringe faces, we recommend
you never omit face, but always provide a specific face. In
particular, if you want the bitmap to be always displayed in the
fringe face, use fringe as face.
For instance, to display an arrow in the left fringe, using the
warning face, you could say something like:
(overlay-put
(make-overlay (point) (point))
'before-string (propertize
"x" 'display
`(left-fringe right-arrow warning)))
Here is a list of the standard fringe bitmaps defined in Emacs, and
how they are currently used in Emacs (via
fringe-indicator-alist and fringe-cursor-alist):
left-arrow, right-arrowUsed to indicate truncated lines.
left-curly-arrow, right-curly-arrowUsed to indicate continued lines.
right-triangle, left-triangleThe former is used by overlay arrows. The latter is unused.
up-arrow, down-arrowbottom-left-angle, bottom-right-angletop-left-angle, top-right-angleleft-bracket, right-bracketempty-lineUsed to indicate buffer boundaries.
filled-rectangle, hollow-rectanglefilled-square, hollow-squarevertical-bar, horizontal-barUsed for different types of fringe cursors.
exclamation-mark, question-marklarge-circleNot used by core Emacs features.
The next subsection describes how to define your own fringe bitmaps.
This function returns the fringe bitmaps of the display line
containing position pos in window window. The return
value has the form (left right ov), where left
is the symbol for the fringe bitmap in the left fringe (or nil
if no bitmap), right is similar for the right fringe, and ov
is non-nil if there is an overlay arrow in the left fringe.
The value is nil if pos is not visible in window.
If window is nil, that stands for the selected window.
If pos is nil, that stands for the value of point in
window.
This function defines the symbol bitmap as a new fringe bitmap, or replaces an existing bitmap with that name.
The argument bits specifies the image to use. It should be either a string or a vector of integers, where each element (an integer) corresponds to one row of the bitmap. Each bit of an integer corresponds to one pixel of the bitmap, where the low bit corresponds to the rightmost pixel of the bitmap. (Note that this order of bits is the opposite of the order in XBM images; see XBM Images.)
The height is normally the length of bits. However, you
can specify a different height with non-nil height. The width
is normally 8, but you can specify a different width with non-nil
width. The width must be an integer between 1 and 16.
The argument align specifies the positioning of the bitmap
relative to the range of rows where it is used; the default is to
center the bitmap. The allowed values are top, center,
or bottom.
The align argument may also be a list (align
periodic) where align is interpreted as described above.
If periodic is non-nil, it specifies that the rows in
bits should be repeated enough times to reach the specified
height.
This function destroys the fringe bitmap identified by bitmap. If bitmap identifies a standard fringe bitmap, it actually restores the standard definition of that bitmap, instead of eliminating it entirely.
This sets the face for the fringe bitmap bitmap to face.
If face is nil, it selects the fringe face. The
bitmap’s face controls the color to draw it in.
face is merged with the fringe face, so normally
face should specify only the foreground color.
The overlay arrow is useful for directing the user’s attention to a particular line in a buffer. For example, in the modes used for interface to debuggers, the overlay arrow indicates the line of code about to be executed. This feature has nothing to do with overlays (see Overlays).
This variable holds the string to display to call attention to a
particular line, or nil if the arrow feature is not in use.
On a graphical display the contents of the string are ignored if the
left fringe is shown; instead a glyph is displayed in the fringe area
to the left of the display area.
This variable holds a marker that indicates where to display the overlay arrow. It should point at the beginning of a line. On a non-graphical display, or when the left fringe is not shown, the arrow text appears at the beginning of that line, overlaying any text that would otherwise appear. Since the arrow is usually short, and the line usually begins with indentation, normally nothing significant is overwritten.
The overlay-arrow string is displayed in any given buffer if the value
of overlay-arrow-position in that buffer points into that
buffer. Thus, it is possible to display multiple overlay arrow strings
by creating buffer-local bindings of overlay-arrow-position.
However, it is usually cleaner to use
overlay-arrow-variable-list to achieve this result.
You can do a similar job by creating an overlay with a
before-string property. See Overlay Properties.
You can define multiple overlay arrows via the variable
overlay-arrow-variable-list.
This variable’s value is a list of variables, each of which specifies
the position of an overlay arrow. The variable
overlay-arrow-position has its normal meaning because it is on
this list.
Each variable on this list can have properties
overlay-arrow-string and overlay-arrow-bitmap that
specify an overlay arrow string (for text terminals or graphical
terminals without the left fringe shown) or fringe bitmap
(for graphical terminals with a left fringe) to display at the
corresponding overlay arrow position. If either property is not set,
the default overlay-arrow-string or overlay-arrow fringe
indicator is used.
Normally the frame parameter vertical-scroll-bars controls
whether the windows in the frame have vertical scroll bars, and whether
they are on the left or right. The frame parameter
scroll-bar-width specifies how wide they are (nil meaning
the default).
The frame parameter horizontal-scroll-bars controls whether
the windows in the frame have horizontal scroll bars. The frame
parameter scroll-bar-height specifies how high they are
(nil meaning the default). See Layout Parameters.
Horizontal scroll bars are not available on all platforms. The
function horizontal-scroll-bars-available-p which takes no
argument returns non-nil if they are available on your system.
The following three functions take as argument a live frame which defaults to the selected one.
This function reports the scroll bar types for frame frame. The
value is a cons cell (vertical-type .
horizontal-type), where vertical-type is either
left, right, or nil (which means no vertical scroll
bar.) horizontal-type is either bottom or nil
(which means no horizontal scroll bar).
This function returns the width of vertical scroll bars of frame in pixels.
This function returns the height of horizontal scroll bars of frame in pixels.
You can override the frame specific settings for individual windows by using the following function:
This function sets the width and/or height and the types of scroll bars
for window window. If window is nil, the selected
window is used.
width specifies the width of the vertical scroll bar in pixels
(nil means use the width specified for the frame).
vertical-type specifies whether to have a vertical scroll bar and,
if so, where. The possible values are left, right,
t, which means to use the frame’s default, and nil for no
vertical scroll bar.
height specifies the height of the horizontal scroll bar in
pixels (nil means use the height specified for the frame).
horizontal-type specifies whether to have a horizontal scroll
bar. The possible values are bottom, t, which means to
use the frame’s default, and nil for no horizontal scroll bar.
Note that for a mini window the value t has the same meaning as
nil, namely to not show a horizontal scroll bar. You have to
explicitly specify bottom in order to show a horizontal scroll
bar in a mini window.
If window is not large enough to accommodate a scroll bar of the desired dimension, this leaves the corresponding scroll bar unchanged.
The values specified here may be later overridden by invoking
set-window-buffer (see Buffers and Windows) on window
with its keep-margins argument nil or omitted. However,
if the optional fifth argument persistent is non-nil and
the other arguments are processed successfully, the values specified
here unconditionally survive subsequent invocations of
set-window-buffer.
Using the persistent argument of set-window-scroll-bars
and set-window-fringes (see Fringe Size and Position) you can
reliably and permanently turn off scroll bars and/or fringes in any
minibuffer window by adding the following snippet to your early init
file (see The Init File).
(add-hook 'after-make-frame-functions
(lambda (frame)
(set-window-scroll-bars
(minibuffer-window frame) 0 nil 0 nil t)
(set-window-fringes
(minibuffer-window frame) 0 0 nil t)))
The following four functions take as argument a live window which defaults to the selected one.
This function returns a list of the form (width
columns vertical-type height lines
horizontal-type persistent).
The value width is the value that was specified for the width of
the vertical scroll bar (which may be nil); columns is the
(possibly rounded) number of columns that the vertical scroll bar
actually occupies.
The value height is the value that was specified for the height of
the horizontal scroll bar (which may be nil); lines is the
(possibly rounded) number of lines that the horizontally scroll bar
actually occupies.
The value of persistent is the value specified for window
with the last successful invocation of set-window-scroll-bars,
nil if there never was one.
This function reports the scroll bar type for window window. The
value is a cons cell (vertical-type .
horizontal-type). Unlike window-scroll-bars, this reports
the scroll bar type actually used, once frame defaults and
scroll-bar-mode are taken into account.
This function returns the width in pixels of window’s vertical scrollbar.
This function returns the height in pixels of window’s horizontal scrollbar.
If you do not specify a window’s scroll bar settings via
set-window-scroll-bars, the buffer-local variables
vertical-scroll-bar, horizontal-scroll-bar,
scroll-bar-width and scroll-bar-height in the buffer being
displayed control the window’s scroll bars. The function
set-window-buffer examines these variables. If you change them
in a buffer that is already visible in a window, you can make the window
take note of the new values by calling set-window-buffer
specifying the same buffer that is already displayed.
You can control the appearance of scroll bars for a particular buffer by setting the following variables which automatically become buffer-local when set.
This variable specifies the location of the vertical scroll bar. The
possible values are left, right, t, which means to
use the frame’s default, and nil for no scroll bar.
This variable specifies the location of the horizontal scroll bar. The
possible values are bottom, t, which means to use the
frame’s default, and nil for no scroll bar.
This variable specifies the width of the buffer’s vertical scroll bars,
measured in pixels. A value of nil means to use the value
specified by the frame.
This variable specifies the height of the buffer’s horizontal scroll
bar, measured in pixels. A value of nil means to use the value
specified by the frame.
Finally you can toggle the display of scroll bars on all frames by
customizing the variables scroll-bar-mode and
horizontal-scroll-bar-mode.
This variable controls whether and where to put vertical scroll bars in
all frames. The possible values are nil for no scroll bars,
left to put scroll bars on the left and right to put
scroll bars on the right.
This variable controls whether to display horizontal scroll bars on all frames.
Window dividers are bars drawn between a frame’s windows. A right
divider is drawn between a window and any adjacent windows on the right.
Its width (thickness) is specified by the frame parameter
right-divider-width. A bottom divider is drawn between a
window and adjacent windows on the bottom or the echo area. Its width
is specified by the frame parameter bottom-divider-width. In
either case, specifying a width of zero means to not draw such dividers.
See Layout Parameters.
Technically, a right divider belongs to the window on its left, which means that its width contributes to the total width of that window. A bottom divider belongs to the window above it, which means that its width contributes to the total height of that window. See Window Sizes. When a window has both, a right and a bottom divider, the bottom divider prevails. This means that a bottom divider is drawn over the full total width of its window while the right divider ends above the bottom divider.
Dividers can be dragged with the mouse and are therefore useful for adjusting the sizes of adjacent windows with the mouse. They also serve to visually set apart adjacent windows when no scroll bars or mode lines are present. The following three faces allow the customization of the appearance of dividers:
window-dividerWhen a divider is less than three pixels wide, it is drawn solidly with the foreground of this face. For larger dividers this face is used for the inner part only, excluding the first and last pixel.
window-divider-first-pixelThis is the face used for drawing the first pixel of a divider that is
at least three pixels wide. To obtain a solid appearance, set this to
the same value used for the window-divider face.
window-divider-last-pixelThis is the face used for drawing the last pixel of a divider that is at
least three pixels wide. To obtain a solid appearance, set this to the
same value used for the window-divider face.
You can get the sizes of the dividers of a specific window with the following two functions.
Return the width (thickness) in pixels of window’s right divider. window must be a live window and defaults to the selected one. The return value is always zero for a rightmost window.
Return the width (thickness) in pixels of window’s bottom divider. window must be a live window and defaults to the selected one. The return value is zero for the minibuffer window or a bottommost window on a minibuffer-less frame.
display Property ¶The display text property (or overlay property) is used to
insert images into text, and to control other aspects of how text
displays. Display specifications in the same display
property value generally apply in parallel to the text they cover.
If several sources (overlays and/or a text property) specify values
for the display property, only one of the values takes effect,
following the rules of get-char-property. See Examining Text Properties.
The value of the display property should be a display
specification, or a list or vector containing several display
specifications.
This convenience function can be used to get the value of a specific
display specification, no matter whether the display property is
a vector, a list or a single display specification. This is like
get-text-property (see Examining Text Properties), but works on
the display property only. For specifications with a single
value (e.g. height), this returns the value itself; for
properties with a list of values (e.g. slice), this returns the
list of values.
position is the position in the buffer or string to examine, and
spec is the CAR of the display specification to return. The
optional object argument should be either a string or a buffer,
and defaults to the current buffer. If the optional properties
argument is non-nil, it should be a display property, and
in that case, position and object are ignored. (This can be
useful if you’ve already gotten the display property with
get-char-property, for instance (see Examining Text Properties).
Add the display specification (prop value) to the
text from start to end.
If any text in the region has a non-nil display
property, those properties are retained. For instance:
(add-display-text-property 4 8 'height 2.0) (add-display-text-property 2 12 'raise 0.5)
After doing this, the region from 2 to 4 will have the raise
display specification, the region from 4 to 8 will have both the
raise and height display specifications, and finally the
region from 8 to 12 will only have the raise display
specification.
object is either a string or a buffer to add the specification to. If omitted, object defaults to the current buffer.
Remove the display specification spec from the text from
start to end. spec is the CAR of the display
specification to remove, e.g. height or '(margin nil).
If any text in the region has any other display properties, those
properties are retained. For instance:
(add-display-text-property 1 8 'raise 0.5) (add-display-text-property 4 8 'height 2.0) (remove-display-text-property 2 6 'raise)
After doing this, the text will have the following display
properties:
raise
height
raise and height
object is either a string or a buffer to remove the specification from. If omitted, object defaults to the current buffer.
Some of the display specifications allow inclusion of Lisp forms,
which are evaluated at display time. This could be unsafe in certain
situations, e.g., when the display specification was generated by some
external program/agent. Wrapping a display specification in a list
that begins with the special symbol disable-eval, as in
(disable-eval spec), will disable evaluation of any
Lisp in spec, while still supporting all the other display
property features.
The rest of this section describes several kinds of display specifications and what they mean.
Some kinds of display specifications specify something to display instead of the text that has the property. These are called replacing display specifications. Emacs does not allow the user to interactively move point into the middle of buffer text that is replaced in this way.
If a list of display specifications includes more than one replacing
display specification, the first overrides the rest. Replacing
display specifications make most other display specifications
irrelevant, since those don’t apply to the replacement. In addition,
any invisible and composition properties of the text that
is replaced are ignored, because the replaced text is skipped and its
properties are not processed.
For replacing display specifications, the text that has the
property means all the consecutive characters that have the same
Lisp object as their display property; these characters are
replaced as a single unit. If two characters have different Lisp
objects as their display properties (i.e., objects which are
not eq), they are handled separately.
Here is an example which illustrates this point. A string serves as a replacing display specification, which replaces the text that has the property with the specified string (see Other Display Specifications). Consider the following function:
(defun foo ()
(dotimes (i 5)
(let ((string (concat "A"))
(start (+ i i (point-min))))
(put-text-property start (1+ start) 'display string)
(put-text-property start (+ 2 start) 'display string))))
This function gives each of the first ten characters in the buffer a
display property which is a string "A", but they don’t
all get the same string object. The first two characters get the same
string object, so they are replaced with one ‘A’; the fact that
the display property was assigned in two separate calls to
put-text-property is irrelevant. Similarly, the next two
characters get a second string (concat creates a new string
object), so they are replaced with one ‘A’; and so on. Thus, the
ten characters appear as five A’s.
Note: Using :box face attribute (see Face Attributes) on a
replacing display string that is adjacent to normal text with
the same :box style can lead to display artifacts when moving
the cursor across the text with this face attribute. These can be
avoided by applying the :box attribute directly to the text
being replaced, rather than (or in addition to) the display
string itself. Here’s an example:
;; Causes display artifacts when moving the cursor across text (progn (put-text-property 1 2 'display (propertize " [" 'face '(:box t))) (put-text-property 2 3 'face '(:box t)) (put-text-property 3 4 'display (propertize "] " 'face '(:box t))))
;; No display artifacts due to `:box' (progn (add-text-properties 1 2 '(face (:box t) display " [")) (put-text-property 2 3 'face '(:box t)) (add-text-properties 3 4 '(face (:box t) display "] ")))
To display a space of specified width and/or height, use a display
specification of the form (space . props), where
props is a property list (a list of alternating properties and
values). You can put this property on one or more consecutive
characters; a space of the specified height and width is displayed in
place of all of those characters. These are the properties you
can use in props to specify the weight of the space:
:width widthIf width is a number, it specifies that the space width should be width times the normal character width. width can also be a pixel width specification (see Pixel Specification for Spaces).
:relative-width factorSpecifies that the width of the stretch should be computed from the
first character in the group of consecutive characters that have the
same display property. The space width is the pixel width of
that character, multiplied by factor. (On text-mode terminals,
the “pixel width” of a character is usually 1, but it could be more
for TABs and double-width CJK characters.)
:align-to hposSpecifies that the space should be wide enough to reach the column
hpos. If hpos is a number, it is a column number, and is
measured in units of the canonical character width (see Frame Font). hpos can also be a pixel width specification
(see Pixel Specification for Spaces). When the current line is wider than
the window, and is either displayed by one or more continuation lines,
or is truncated and possibly scrolled horizontally (see Horizontal Scrolling), hpos is measured from the beginning of the logical
line, not from the visual beginning of the screen line. This way,
alignment produced by :align-to is consistent with functions
that count columns, such as current-column and
move-to-column (see Counting Columns). (There’s a single exception
from this rule: when :align-to is used to specify whitespace of
the wrap-prefix variable or text property, see Truncation.)
You should use one and only one of the above properties. You can also specify the height of the space, with these properties:
:height heightSpecifies the height of the space. If height is a number, it specifies that the space height should be height times the normal character height. The height may also be a pixel height specification (see Pixel Specification for Spaces).
:relative-height factorSpecifies the height of the space, multiplying the ordinary height of the text having this display specification by factor.
:ascent ascentIf the value of ascent is a non-negative number no greater than 100, it specifies that ascent percent of the height of the space should be considered as the ascent of the space—that is, the part above the baseline. The ascent may also be specified in pixel units with a pixel ascent specification (see Pixel Specification for Spaces).
Don’t use both :height and :relative-height together.
The :width and :align-to properties are supported on
non-graphic terminals, but the other space properties in this section
are not.
Note that space properties are treated as paragraph separators for the purposes of reordering bidirectional text for display. See Bidirectional Display, for the details.
The value of the :width, :align-to, :height,
and :ascent properties can be a special kind of expression that
is evaluated during redisplay. The result of the evaluation is used
as an absolute number of pixels.
The following expressions are supported:
expr ::= num | (num) | unit | elem | pos | image | xwidget | form num ::= integer | float | symbol unit ::= in | mm | cm | width | height
elem ::= left-fringe | right-fringe | left-margin | right-margin
| scroll-bar | text
pos ::= left | center | right
form ::= (num . expr) | (op expr ...)
op ::= + | -
The form num specifies a fraction of the default frame font
height or width. The form (num) specifies an absolute
number of pixels. If num is a symbol, symbol, its
buffer-local variable binding is used; that binding can be either a
number or a cons cell of the forms shown above (including yet another
cons cell whose car is a symbol that has a buffer-local
binding).
The in, mm, and cm units specify the number of
pixels per inch, millimeter, and centimeter, respectively. The
width and height units correspond to the default width
and height of the current face. An image specification of the form
(image . props) (see Image Descriptors)
corresponds to the width or height of the specified image. Similarly,
an xwidget specification of the form (xwidget . props)
stands for the width or height of the specified xwidget.
See Embedded Native Widgets.
The elements left-fringe, right-fringe,
left-margin, right-margin, scroll-bar, and
text specify the width of the corresponding area of the window.
When the window displays line numbers (see Size of Displayed Text), the width of the text area is decreased by the screen
space taken by the line-number display.
The left, center, and right positions can be
used with :align-to to specify a position relative to the left
edge, center, or right edge of the text area. When the window
displays line numbers, and :align-to is used in display
properties of buffer text (as opposed to header line, see below), the
left and the center positions are offset to account for
the screen space taken by the line-number display.
Any of the above window elements (except text) can also be
used with :align-to to specify that the position is relative to
the left edge of the given area. Once the base offset for a relative
position has been set (by the first occurrence of one of these
symbols), further occurrences of these symbols are interpreted as the
width of the specified area. For example, to align to the center of
the left-margin, use
:align-to (+ left-margin (0.5 . left-margin))
If no specific base offset is set for alignment, it is always relative to the left edge of the text area. For example, ‘:align-to 0’ aligns with the first text column in the text area. When the window displays line numbers, the text is considered to start where the space used for line-number display ends.
A value of the form (num . expr) stands for the
product of the values of num and expr. For example,
(2 . in) specifies a width of 2 inches, while (0.5 .
image) specifies half the width (or height) of the specified
image (which should be given by its image spec).
The form (+ expr ...) adds up the value of the
expressions. The form (- expr ...) negates or subtracts
the value of the expressions.
Text shown in the header line that uses :align-to display
specifications is not automatically realigned when
display-line-numbers-mode is turned on and off, or when the
width of line numbers on display changes. To arrange for the
header-line text alignment to be updated, thus keeping the header-line
text aligned with the buffer text, turn on the
header-line-indent-mode in the buffer and use its two
variables, header-line-indent and
header-line-indent-width, in the display specification.
See Window Header Lines. Here’s a simple example:
(setq header-line-format
(concat (propertize " "
'display
'(space :align-to
(+ header-line-indent-width 10)))
"Column"))
This will keep the text ‘Column’ on the header line aligned with
column 10 of buffer text, regardless of whether
display-line-numbers-mode is on or off, and also when
line-number display changes its width.
Here are the other sorts of display specifications that you can use
in the display text property.
stringDisplay string instead of the text that has this property.
Recursive display specifications are not supported—string’s
display properties, if any, are not used.
(image . image-props)This kind of display specification is an image descriptor (see Image Descriptors). When used as a display specification, it means to display the image instead of the text that has the display specification.
(slice x y width height)This specification together with image specifies a slice
(a partial area) of the image to display. More precisely, the
specification should have the following form:
((slice x y width height) image-desc)
where image-desc is an image descriptor described above. The elements x and y specify the top left corner of the slice, within the image; width and height specify the width and height of the slice. Integers are numbers of pixels. A floating-point number in the range 0.0–1.0 stands for that fraction of the width or height of the entire image.
((margin nil) string)A display specification of this form means to display string instead of the text that has the display specification, at the same position as that text. It is equivalent to using just string, but it is done as a special case of marginal display (see Displaying in the Margins).
(left-fringe bitmap [face])(right-fringe bitmap [face])This display specification on any character of a line of text causes the specified bitmap be displayed in the left or right fringes for that line, instead of the characters that have the display specification. The optional face specifies the face whose colors are to be used for the bitmap display. See Fringe Bitmaps, for the details.
It also possible to add context help for fringe bitmaps through the
show-help-function mechanism by using left-fringe-help and
right-fringe-help text properties (see Properties with Special Meanings).
(space-width factor)This display specification affects all the space characters within the text that has the specification. It displays all of these spaces factor times as wide as normal. The element factor should be an integer or float. Characters other than spaces are not affected at all; in particular, this has no effect on tab characters.
(min-width (width))This display specification ensures the text that has it takes at least width space on display, by adding a stretch of white space to the end of the text if the text is shorter than width. The text is partitioned using the identity of the parameter, which is why the parameter is a list with one element. For instance:
(insert (propertize "foo" 'display '(min-width (6.0))))
This will add padding after ‘foo’ bringing the total width up to
the width of six normal characters. Note that the affected characters
are identified by the (6.0) list in the display property,
compared with eq. The element width can be either an
integer or a float specifying the required minimum width of the text
(see Pixel Specification for Spaces).
(height height)This display specification makes the text taller or shorter. Here are the possibilities for height:
(+ n)This means to use a font that is n steps larger. A step is defined by the set of available fonts—specifically, those that match what was otherwise specified for this text, in all attributes except height. Each size for which a suitable font is available counts as another step. n should be an integer.
(- n)This means to use a font that is n steps smaller.
A number, factor, means to use a font that is factor times as tall as the default font.
A symbol is a function to compute the height. It is called with the current height as argument, and should return the new height to use.
If the height value doesn’t fit the previous possibilities, it is
a form. Emacs evaluates it to get the new height, with the symbol
height bound to the current specified font height.
(raise factor)This kind of display specification raises or lowers the text it applies to, relative to the baseline of the line. It is mainly meant to support display of subscripts and superscripts.
The factor must be a number, which is interpreted as a multiple of the height of the affected text. If it is positive, that means to display the characters raised. If it is negative, that means to display them lower down.
Note that if the text also has a height display specification,
which was specified before (i.e. to the left of) raise, the
latter will affect the amount of raising or lowering in pixels,
because that is based on the height of the text being raised.
Therefore, if you want to display a sub- or superscript that is
smaller than the normal text height, consider specifying raise
before height.
You can make any display specification conditional. To do that,
package it in another list of the form
(when condition . spec).
Then the specification spec applies only when
condition evaluates to a non-nil value. During the
evaluation, object is bound to the string or buffer having the
conditional display property. position and
buffer-position are bound to the position within object
and the buffer position where the display property was found,
respectively. Both positions can be different when object is a
string.
Note that condition will only be evaluated when redisplay examines the text where this display spec is located, so this feature is best suited for conditions that are relatively stable, i.e. yield, for each particular buffer position, the same results on every evaluation. If the results change for the same text location, e.g., if the result depends on the position of point, then the conditional specification might not do what you want, because redisplay examines only those parts of buffer text where it has reasons to assume that something changed since the last display cycle.
A buffer can have blank areas called display margins on the
left and on the right. Ordinary text never appears in these areas,
but you can put things into the display margins using the
display property.
The way to display something in the margins is to specify it in a
margin display specification in the display property of some
text. This is a replacing display specification, meaning that the
text you put it on does not get displayed; the margin display appears,
but that text does not.
A margin display specification looks like ((margin
right-margin) spec) or ((margin left-margin) spec).
Here, spec is another display specification that says what to
display in the margin. Typically it is a string of text to display,
or an image descriptor.
To display something in the margin in association with
certain buffer text, without altering or preventing the display of
that text, put on that text an overlay with a before-string
property, and put the margin display specification on the contents of
the before-string.
Note that if the string to be displayed in the margin doesn’t fully
specify its face, the nonspecified attributes are inherited from the
margin face (see Basic Faces). If you want a margin string
to have a specific appearance independent of the margin face,
make sure the string has a face specifying all required attributes.
Before the display margins can display anything, you must give them a nonzero width. The usual way to do that is to set these variables:
This variable specifies the width of the left margin, in character
cell (a.k.a. “column”) units. It is buffer-local in all buffers.
A value of nil means no left marginal area.
This variable specifies the width of the right margin, in character
cell units. It is buffer-local in all buffers. A value of nil
means no right marginal area.
Setting these variables does not immediately affect the window. These
variables are checked when a new buffer is displayed in the window.
Thus, you can make changes take effect by calling
set-window-buffer. Do not use these variables to try to
determine the current width of the left or right margin. Instead, use
the function window-margins.
You can also set the margin widths immediately.
This function specifies the margin widths for window window, in
character cell units. The argument left controls the left
margin, and right controls the right margin (default 0).
If window is not large enough to accommodate margins of the desired width, this leaves the margins of window unchanged.
The values specified here may be later overridden by invoking
set-window-buffer (see Buffers and Windows) on window
with its keep-margins argument nil or omitted.
This function returns the width of the left and right margins of
window as a cons cell of the form (left . right). If one of the two marginal areas does not exist,
its width is returned as nil; if neither of the two margins exist,
the function returns (nil). If window is nil, the
selected window is used.
To display an image in an Emacs buffer, you must first create an image
descriptor, then use it as a display specifier in the display
property of text that is displayed (see The display Property).
Emacs is usually able to display images when it is run on a
graphical terminal. Images cannot be displayed in a text terminal, on
certain graphical terminals that lack the support for this, or if
Emacs is compiled without image support. You can use the function
display-images-p to determine if images can in principle be
displayed (see Display Feature Testing).
Emacs can display a number of different image formats. Some of
these image formats are supported only if particular support libraries
are installed. On some platforms, Emacs can load support libraries on
demand; if so, the variable dynamic-library-alist can be used
to modify the set of known names for these dynamic libraries.
See Dynamically Loaded Libraries.
Supported image formats (and the required support libraries) include
PBM and XBM (which do not depend on support libraries and are always
available), XPM (libXpm), GIF (libgif or
libungif), JPEG (libjpeg), TIFF (libtiff), PNG
(libpng), SVG (librsvg), and WebP (libwebp).
Each of these image formats is associated with an image type
symbol. The symbols for the above formats are, respectively,
pbm, xbm, xpm, gif, jpeg,
tiff, png, svg, and webp.
On some platforms, the built-in image support that doesn’t require any optional libraries includes BMP images.34
Furthermore, if you build Emacs with ImageMagick
(libMagickWand) support, Emacs can display any image format
that ImageMagick can. See ImageMagick Images. All images
displayed via ImageMagick have type symbol imagemagick.
This variable contains a list of type symbols for image formats which are potentially supported in the current configuration.
“Potentially” means that Emacs knows about the image types, not
necessarily that they can be used (for example, they could depend on
unavailable dynamic libraries). To know which image types are really
available, use image-type-available-p.
This function returns non-nil if images of type type can
be loaded and displayed. type must be an image type symbol.
For image types whose support libraries are statically linked, this
function always returns t. For image types whose support
libraries are dynamically loaded, it returns t if the library
could be loaded and nil otherwise.
An image descriptor is a list which specifies the underlying
data for an image, and how to display it. It is typically used as the
value of a display overlay or text property (see Other Display Specifications); but See Showing Images, for convenient helper
functions to insert images into buffers.
Each image descriptor has the form (image . props),
where props is a property list of alternating keyword symbols
and values, including at least the pair :type type that
specifies the image type.
Image descriptors which define image dimensions, :width,
:height, :max-width and :max-height, may take
either an integer, which represents the dimension in pixels, or a pair
(value . em), where value is the dimension’s
length in ems35. One em is equivalent to the size of the font
and value may be an integer or a float. Also, dimension can be
specified in (value . ch) and (value . cw)
forms, where ch means height of the canonical character and
cw means width of the canonical character.
The following is a list of properties that are meaningful for all image types (there are also properties which are meaningful only for certain image types, as documented in the following subsections):
:type typeThe image type. See Image Formats. Every image descriptor must include this property.
:file fileThis says to load the image from file file. If file is
not an absolute file name, it is expanded relative to each of the
directories mentioned by image-load-path (see Defining Images).
:data dataThis specifies the raw image data. Each image descriptor must have
either :data or :file, but not both.
For most image types, the value of a :data property should be a
string containing the image data. Some image types do not support
:data; for some others, :data alone is not enough, so
you need to use other image properties along with :data. See
the following subsections for details.
:margin marginThis specifies how many pixels to add as an extra margin around the
image. The value, margin, must be a non-negative number, or a
pair (x . y) of such numbers. If it is a pair,
x specifies how many pixels to add horizontally, and y
specifies how many pixels to add vertically. If :margin is not
specified, the default is zero.
:ascent ascentThis specifies the amount of the image’s height to use for its
ascent—that is, the part above the baseline. The value,
ascent, must be a number in the range 0 to 100, or the symbol
center.
If ascent is a number, that percentage of the image’s height is used for its ascent.
If ascent is center, the image is vertically centered
around a centerline which would be the vertical centerline of text drawn
at the position of the image, in the manner specified by the text
properties and overlays that apply to the image.
If this property is omitted, it defaults to 50.
:relief reliefThis adds a shadow rectangle around the image. The value, relief, specifies the width of the shadow lines, in pixels. If relief is negative, shadows are drawn so that the image appears as a pressed button; otherwise, it appears as an unpressed button.
:width width, :height heightThe :width and :height keywords are used for scaling the
image. If only one of them is specified, the other one will be
calculated so as to preserve the aspect ratio. If both are specified,
aspect ratio may not be preserved.
:max-width max-width, :max-height max-heightThe :max-width and :max-height keywords are used for
scaling if the size of the image exceeds these values. If
:width is set, it will have precedence over max-width,
and if :height is set, it will have precedence over
max-height, but you can otherwise mix these keywords as you
wish.
If both :max-width and :height are specified, but
:width is not, preserving the aspect ratio might require that
width exceeds :max-width. If this happens, scaling will use a
smaller value for the height so as to preserve the aspect ratio while
not exceeding :max-width. Similarly when both
:max-height and :width are specified, but :height
is not. For example, if you have a 200x100 image and specify that
:width should be 400 and :max-height should be 150,
you’ll end up with an image that is 300x150: Preserving the aspect
ratio and not exceeding the “max” setting. This combination of
parameters is a useful way of saying “display this image as large as
possible, but no larger than the available display area”.
:scale scaleThis should be a scaling factor for the image, a number. Values higher
than 1 mean to increase the image size, and lower values mean to
decrease the size, by multiplying both the width and height of the image
by the factor. For instance, a value of 0.25 will make the image a
quarter size of what it originally was. If the scaling makes the image
larger than specified by :max-width or :max-height, the
resulting size will not exceed those two values. If both :scale
and :height/:width are specified, the height/width will be
adjusted by the specified scaling factor.
The value of scale can also be the symbol default, which
means to use the value of image-scaling-factor. If that value is
a number, it is the scale factor to use; if it is auto (the
default), it means to compute the scaling factor based on pixel size of
the font used by the frame’s default face (see Low-Level Font Representation).
Specifically, if the pixel width of the default face’s font is greater
than 10, the image is enlarged by the factor computed as the ratio of
the font width to 10; if the font width is 10 pixels or less, the image
is not scaled. For example, if the default font’s width is 15, the
image will be scaled by the factor 1.5.
If scale is not provided, create-image scales the image
according to the value of image-scaling-factor.
:rotation angleSpecifies a rotation angle in degrees. Only multiples of 90 degrees
are supported, unless the image type is imagemagick. Positive
values rotate clockwise, negative values counter-clockwise. Rotation
is performed after scaling and cropping.
:flip flipIf this is t, the image will be horizontally flipped.
Currently it has no effect if the image type is imagemagick.
Vertical flipping can be achieved by rotating the image 180 degrees
and toggling this value.
:transform-smoothing smoothIf this is t, any image transform will have smoothing applied;
if nil, no smoothing will be applied. The exact algorithm used
is platform dependent, but should be equivalent to bilinear
filtering. Disabling smoothing will use the nearest neighbor
algorithm.
If this property is not specified, create-image will use the
image-transform-smoothing user option to say whether smoothing
should be done or not. This option can be nil (no smoothing),
t (use smoothing) or a predicate function that’s called with
the image object as the only parameter, and should return either
nil or t. The default is for down-scaling to apply
smoothing, and for large up-scaling to not apply smoothing.
:index frameSee Multi-Frame Images.
:conversion algorithmThis specifies a conversion algorithm that should be applied to the image before it is displayed; the value, algorithm, specifies which algorithm.
laplaceembossSpecifies the Laplace edge detection algorithm, which blurs out small differences in color while highlighting larger differences. People sometimes consider this useful for displaying the image for a disabled button.
(edge-detection :matrix matrix :color-adjust adjust) ¶Specifies a general edge-detection algorithm. matrix must be either a nine-element list or a nine-element vector of numbers. A pixel at position x/y in the transformed image is computed from original pixels around that position. matrix specifies, for each pixel in the neighborhood of x/y, a factor with which that pixel will influence the transformed pixel; element 0 specifies the factor for the pixel at x-1/y-1, element 1 the factor for the pixel at x/y-1 etc., as shown below:
(x-1/y-1 x/y-1 x+1/y-1 x-1/y x/y x+1/y x-1/y+1 x/y+1 x+1/y+1)
The resulting pixel is computed from the color intensity of the color resulting from summing up the RGB values of surrounding pixels, multiplied by the specified factors, and dividing that sum by the sum of the factors’ absolute values.
Laplace edge-detection currently uses a matrix of
(1 0 0 0 0 0 0 0 -1)
Emboss edge-detection uses a matrix of
( 2 -1 0
-1 0 1
0 1 -2)
disabledSpecifies transforming the image so that it looks disabled.
:mask maskIf mask is heuristic or (heuristic bg), build
a clipping mask for the image, so that the background of a frame is
visible behind the image. If bg is not specified, or if bg
is t, determine the background color of the image by looking at
the four corners of the image, assuming the most frequently occurring
color from the corners is the background color of the image. Otherwise,
bg must be a list (red green blue)
specifying the color to assume for the background of the image.
If mask is nil, remove a mask from the image, if it has
one. Images in some formats include a mask which can be removed by
specifying :mask nil.
:pointer shapeThis specifies the pointer shape when the mouse pointer is over this image. See Pointer Shape, for available pointer shapes.
:map map ¶This associates an image map of hot spots with this image.
An image map is an alist where each element has the format
(area id plist). An area is specified
as either a rectangle, a circle, or a polygon.
A rectangle is a cons
(rect . ((x0 . y0) . (x1 . y1)))
which specifies the pixel coordinates of the upper left and bottom right
corners of the rectangle area.
A circle is a cons
(circle . ((x0 . y0) . r))
which specifies the center and the radius of the circle; r may
be a float or integer.
A polygon is a cons
(poly . [x0 y0 x1 y1 ...])
where each pair in the vector describes one corner in the polygon.
When the mouse pointer lies on a hot-spot area of an image, the
plist of that hot-spot is consulted; if it contains a help-echo
property, that defines a tool-tip for the hot-spot, and if it contains
a pointer property, that defines the shape of the mouse cursor when
it is on the hot-spot.
See Pointer Shape, for available pointer shapes.
When you click the mouse when the mouse pointer is over a hot-spot, an
event is composed by combining the id of the hot-spot with the
mouse event; for instance, [area4 mouse-1] if the hot-spot’s
id is area4.
Note that the map’s coordinates should reflect the displayed image
after all transforms have been done (rotation, scaling and so on), and
also note that Emacs (by default) performs auto-scaling of images, so
to make things match up, you should either specify :scale 1.0
when creating the image, or use the result of
image-compute-scaling-factor to compute the elements of the
map.
When an image’s :scale, :rotation, or :flip is
changed, :map will be recomputed based on the value of
:original-map and the values of those transformation.
:original-map original-map ¶This specifies the untransformed image map which will be used to
recompute :map after the image’s :scale, :rotation,
or :flip is changed.
If :original-map is not specified when creating an image with
create-image, it will be computed based on the supplied
:map, as well as any of :scale, :rotation, or
:flip which are non-nil.
Conversely, if :original-map is specified but :map is not,
:map will be computed based on :original-map,
:scale, :rotation, and :flip.
Set this user option to nil to prevent Emacs from automatically
recomputing an image :map based on its :original-map.
This function returns t if image spec has a mask bitmap.
frame is the frame on which the image will be displayed.
frame nil or omitted means to use the selected frame
(see Input Focus).
This function returns non-nil if frame supports image
scaling and rotation. frame nil or omitted means to use
the selected frame (see Input Focus). The returned list includes
symbols that indicate which image transform operations are supported:
scaleImage scaling is supported by frame via the :scale,
:width, :height, :max-width, and
:max-height properties.
rotate90Image rotation is supported by frame if the rotation angle is an integral multiple of 90 degrees.
If image transforms are not supported, :rotation, :crop,
:width, :height, :scale, :max-width and
:max-height will only be usable through ImageMagick, if
available (see ImageMagick Images).
To use XBM format, specify xbm as the image type. This image
format doesn’t require an external library, so images of this type are
always supported.
Additional image properties supported for the xbm image type are:
:foreground foregroundThe value, foreground, should be a string specifying the image
foreground color, or nil for the default color. This color is
used for each pixel in the XBM that is 1. The default is the frame’s
foreground color.
:background backgroundThe value, background, should be a string specifying the image
background color, or nil for the default color. This color is
used for each pixel in the XBM that is 0. The default is the frame’s
background color.
To specify an XBM image using data within Emacs instead of an external file, use the following properties:
:data dataThe value, data, specifies the contents of the image. There are three formats you can use for data:
:data-height and :data-width.
stride * height bits, where
stride is the smallest multiple of 8 greater than or equal to
the width of the image. In this case, you should specify
:data-height, :data-width and :stride, both to
indicate that the string contains just the bits rather than a whole
XBM file, and to specify the size of the image.
:stride strideThe number of bool vector entries stored for each row; the smallest multiple of 8 greater than or equal to width.
To use XPM format, specify xpm as the image type. The
additional image property :color-symbols is also meaningful with
the xpm image type:
:color-symbols symbolsThe value, symbols, should be an alist whose elements have the
form (name . color). In each element, name is
the name of a color as it appears in the image file, and color
specifies the actual color to use for displaying that name.
If your Emacs build has ImageMagick support, you can use the
ImageMagick library to load many image formats (see File
Conveniences in The GNU Emacs Manual). The image type symbol
for images loaded via ImageMagick is imagemagick, regardless of
the actual underlying image format.
To check for ImageMagick support, use the following:
(image-type-available-p 'imagemagick)
This function returns a list of image file extensions supported by the
current ImageMagick installation. Each list element is a symbol
representing an internal ImageMagick name for an image type, such as
BMP for .bmp images.
The value of this variable is a list of ImageMagick image types which
Emacs may attempt to render using ImageMagick. Each list element
should be one of the symbols in the list returned by
imagemagick-types, or an equivalent string. Alternatively, a
value of t enables ImageMagick for all possible image types.
Regardless of the value of this variable,
imagemagick-types-inhibit (see below) takes precedence.
The value of this variable lists the ImageMagick image types which
should never be rendered using ImageMagick, regardless of the value of
imagemagick-enabled-types. A value of t disables
ImageMagick entirely.
This variable is an alist mapping image types to file name extensions.
Emacs uses this in conjunction with the :format image property
(see below) to give a hint to the ImageMagick library as to the type
of an image. Each element has the form (type
extension), where type is a symbol specifying an image
content-type, and extension is a string that specifies the
associated file name extension.
Images loaded with ImageMagick support the following additional image descriptor properties:
:background backgroundbackground, if non-nil, should be a string specifying a
color, which is used as the image’s background color if the image
supports transparency. If the value is nil, it defaults to the
frame’s background color.
:format typeThe value, type, should be a symbol specifying the type of the
image data, as found in image-format-suffixes. This is used
when the image does not have an associated file name, to provide a
hint to ImageMagick to help it detect the image type.
:crop geometryThe value of geometry should be a list of the form
(width height x y). width and
height specify the width and height of the cropped image. If
x is a positive number it specifies the offset of the cropped
area from the left of the original image, and if negative the offset
from the right. If y is a positive number it specifies the
offset from the top of the original image, and if negative from the
bottom. If x or y are nil or unspecified the crop
area will be centered on the original image.
If the crop area is outside or overlaps the edge of the image it will
be reduced to exclude any areas outside of the image. This means it
is not possible to use :crop to increase the size of the image
by entering large width or height values.
Cropping is performed after scaling but before rotation.
SVG (Scalable Vector Graphics) is an XML format for specifying images. SVG images support the following additional image descriptor properties:
:foreground foregroundforeground, if non-nil, should be a string specifying a
color, which is used as the CSS ‘currentcolor’ value. If the value is
nil, it defaults to the current face’s foreground color.
:background backgroundbackground, if non-nil, should be a string specifying a
color, which is used as the image’s background color if the image
supports transparency. If the value is nil, it defaults to the
current face’s background color.
:css csscss, if non-nil, should be a string specifying the CSS to
override the default CSS used when generating the image.
If your Emacs build has SVG support, you can create and manipulate these images with the following functions from the svg.el library.
Create a new, empty SVG image with the specified dimensions. args is an argument plist with you can specify following:
:stroke-widthThe default width (in pixels) of any lines created.
:strokeThe default stroke color on any lines created.
This function returns an SVG object, a Lisp data structure that specifies an SVG image, and all the following functions work on that structure. The argument svg in the following functions specifies such an SVG object.
Create a gradient in svg with identifier id. type
specifies the gradient type, and can be either linear or
radial. stops is a list of percentage/color pairs.
The following will create a linear gradient that goes from red at the start, to green 25% of the way, to blue at the end:
(svg-gradient svg "gradient1" 'linear
'((0 . "red") (25 . "green") (100 . "blue")))
The gradient created (and inserted into the SVG object) can later be used by all functions that create shapes.
All the following functions take an optional list of keyword parameters that alter the various attributes from their default values. Valid attributes include:
:stroke-widthThe width (in pixels) of lines drawn, and outlines around solid shapes.
:stroke-colorThe color of lines drawn, and outlines around solid shapes.
:fill-colorThe color used for solid shapes.
:idThe identified of the shape.
:gradientIf given, this should be the identifier of a previously defined gradient object.
:clip-pathIdentifier of a clip path.
Add to svg a rectangle whose upper left corner is at position x/y and whose size is width/height.
(svg-rectangle svg 100 100 500 500 :gradient "gradient1")
Add to svg a circle whose center is at x/y and whose radius is radius.
Add to svg an ellipse whose center is at x/y, and whose horizontal radius is x-radius and the vertical radius is y-radius.
Add to svg a line that starts at x1/y1 and extends to x2/y2.
Add to svg a multiple-segment line (a.k.a. “polyline”) that goes through points, which is a list of X/Y position pairs.
(svg-polyline svg '((200 . 100) (500 . 450) (80 . 100))
:stroke-color "green")
Add a polygon to svg where points is a list of X/Y pairs that describe the outer circumference of the polygon.
(svg-polygon svg '((100 . 100) (200 . 150) (150 . 90))
:stroke-color "blue" :fill-color "red")
Add the outline of a shape to svg according to commands, see SVG Path Commands.
Coordinates by default are absolute. To use coordinates relative to
the last position, or – initially – to the origin, set the attribute
:relative to t. This attribute can be specified for the
function or for individual commands. If specified for the function,
then all commands use relative coordinates by default. To make an
individual command use absolute coordinates, set :relative to
nil.
(svg-path svg '((moveto ((100 . 100))) (lineto ((200 . 0) (0 . 200) (-200 . 0))) (lineto ((100 . 100)) :relative nil)) :stroke-color "blue" :fill-color "lightblue" :relative t)
Add the specified text to svg.
(svg-text svg "This is a text" :font-size "40" :font-weight "bold" :stroke "black" :fill "white" :font-family "impact" :letter-spacing "4pt" :x 300 :y 400 :stroke-width 1)
Add an embedded (raster) image to svg. If datap is
nil, image should be a file name; otherwise it should be a
string containing the image data as raw bytes. image-type should be a
MIME image type, for instance "image/jpeg".
(svg-embed svg "~/rms.jpg" "image/jpeg" nil
:width "100px" :height "100px"
:x "50px" :y "75px")
To svg add an embedded (raster) image placed at
relative-filename. relative-filename is searched inside
file-name-directory of the :base-uri svg image property.
:base-uri specifies a (possibly non-existing) file name of the
svg image to be created, thus all the embedded files are searched
relatively to the :base-uri filename’s directory. If
:base-uri is omitted, then filename from where svg image is
loaded is used. Using :base-uri improves the performance of
embedding large images, comparing to svg-embed, because all the
work is done directly by librsvg.
;; Embedding /tmp/subdir/rms.jpg and /tmp/another/rms.jpg
(svg-embed-base-uri-image svg "subdir/rms.jpg"
:width "100px" :height "100px"
:x "50px" :y "75px")
(svg-embed-base-uri-image svg "another/rms.jpg"
:width "100px" :height "100px"
:x "75px" :y "50px")
(svg-image svg :scale 1.0
:base-uri "/tmp/dummy"
:width 175 :height 175)
Add a clipping path to svg. If applied to a shape via the :clip-path property, parts of that shape which lie outside of the clipping path are not drawn.
(let ((clip-path (svg-clip-path svg :id "foo")))
(svg-circle clip-path 200 200 175))
(svg-rectangle svg 50 50 300 300
:fill-color "red"
:clip-path "url(#foo)")
Add the custom node tag to svg.
(svg-node svg
'rect
:width 300 :height 200 :x 50 :y 100 :fill-color "green")
Remove the element with identifier id from the svg.
Finally, the svg-image takes an SVG object as its argument and
returns an image object suitable for use in functions like
insert-image.
Here’s a complete example that creates and inserts an image with a circle:
(let ((svg (svg-create 400 400 :stroke-width 10)))
(svg-gradient svg "gradient1" 'linear '((0 . "red") (100 . "blue")))
(svg-circle svg 200 200 100 :gradient "gradient1"
:stroke-color "green")
(insert-image (svg-image svg)))
SVG paths allow creation of complex images by combining lines, curves, arcs, and other basic shapes. The functions described below allow invoking SVG path commands from a Lisp program.
Move the pen to the first point in points. Additional points
are connected with lines. points is a list of X/Y coordinate
pairs. Subsequent moveto commands represent the start of a
new subpath.
(svg-path svg '((moveto ((200 . 100) (100 . 200) (0 . 100))))
:fill "white" :stroke "black")
End the current subpath by connecting it back to its initial point. A line is drawn along the connection.
(svg-path svg '((moveto ((200 . 100) (100 . 200) (0 . 100)))
(closepath)
(moveto ((75 . 125) (100 . 150) (125 . 125)))
(closepath))
:fill "red" :stroke "black")
Draw a line from the current point to the first element in points, a list of X/Y position pairs. If more than one point is specified, draw a polyline.
(svg-path svg '((moveto ((200 . 100)))
(lineto ((100 . 200) (0 . 100))))
:fill "yellow" :stroke "red")
Draw a horizontal line from the current point to the first element in x-coordinates. Specifying multiple coordinates is possible, although this usually doesn’t make sense.
(svg-path svg '((moveto ((100 . 200)))
(horizontal-lineto (300)))
:stroke "green")
Draw vertical lines.
(svg-path svg '((moveto ((200 . 100)))
(vertical-lineto (300)))
:stroke "green")
Using the first element in coordinate-sets, draw a cubic Bézier
curve from the current point. If there are multiple coordinate sets,
draw a polybezier. Each coordinate set is a list of the form
(x1 y1 x2 y2 x y), where
(x, y) is the curve’s end point. (x1, y1) and (x2, y2) are control points at the
beginning and at the end, respectively.
(svg-path svg '((moveto ((100 . 100)))
(curveto ((200 100 100 200 200 200)
(300 200 0 100 100 100))))
:fill "transparent" :stroke "red")
Using the first element in coordinate-sets, draw a cubic Bézier
curve from the current point. If there are multiple coordinate sets,
draw a polybezier. Each coordinate set is a list of the form
(x2 y2 x y), where (x, y) is the curve’s end point and (x2, y2) is the
corresponding control point. The first control point is the
reflection of the second control point of the previous command
relative to the current point, if that command was curveto
or smooth-curveto. Otherwise the first control point
coincides with the current point.
(svg-path svg '((moveto ((100 . 100)))
(curveto ((200 100 100 200 200 200)))
(smooth-curveto ((0 100 100 100))))
:fill "transparent" :stroke "blue")
Using the first element in coordinate-sets, draw a quadratic
Bézier curve from the current point. If there are multiple coordinate
sets, draw a polybezier. Each coordinate set is a list of the form
(x1 y1 x y), where (x, y) is the curve’s end point and (x1, y1) is the
control point.
(svg-path svg '((moveto ((200 . 100)))
(quadratic-bezier-curveto ((300 100 300 200)))
(quadratic-bezier-curveto ((300 300 200 300)))
(quadratic-bezier-curveto ((100 300 100 200)))
(quadratic-bezier-curveto ((100 100 200 100))))
:fill "transparent" :stroke "pink")
Using the first element in coordinate-sets, draw a quadratic
Bézier curve from the current point. If there are multiple coordinate
sets, draw a polybezier. Each coordinate set is a list of the form
(x y), where (x, y) is the curve’s
end point. The control point is the reflection of the control point
of the previous command relative to the current point, if that command
was quadratic-bezier-curveto or
smooth-quadratic-bezier-curveto. Otherwise the control
point coincides with the current point.
(svg-path svg '((moveto ((200 . 100)))
(quadratic-bezier-curveto ((300 100 300 200)))
(smooth-quadratic-bezier-curveto ((200 300)))
(smooth-quadratic-bezier-curveto ((100 200)))
(smooth-quadratic-bezier-curveto ((200 100))))
:fill "transparent" :stroke "lightblue")
Using the first element in coordinate-sets, draw an elliptical
arc from the current point. If there are multiple coordinate sets,
draw a sequence of elliptical arcs. Each coordinate set is a list of
the form (rx ry x y), where
(x, y) is the end point of the ellipse, and
(rx, ry) are its radii. Attributes may be appended to
the list:
:x-axis-rotationThe angle in degrees by which the x-axis of the ellipse is rotated relative to the x-axis of the current coordinate system.
:large-arcIf set to t, draw an arc sweep greater than or equal to 180
degrees. Otherwise, draw an arc sweep smaller than or equal to 180
degrees.
:sweepIf set to t, draw an arc in positive angle direction.
Otherwise, draw it in negative angle direction.
(svg-path svg '((moveto ((200 . 250)))
(elliptical-arc ((75 75 200 350))))
:fill "transparent" :stroke "red")
(svg-path svg '((moveto ((200 . 250)))
(elliptical-arc ((75 75 200 350 :large-arc t))))
:fill "transparent" :stroke "green")
(svg-path svg '((moveto ((200 . 250)))
(elliptical-arc ((75 75 200 350 :sweep t))))
:fill "transparent" :stroke "blue")
(svg-path svg '((moveto ((200 . 250)))
(elliptical-arc ((75 75 200 350 :large-arc t
:sweep t))))
:fill "transparent" :stroke "gray")
(svg-path svg '((moveto ((160 . 100)))
(elliptical-arc ((40 100 80 0)))
(elliptical-arc ((40 100 -40 -70
:x-axis-rotation -120)))
(elliptical-arc ((40 100 -40 70
:x-axis-rotation -240))))
:stroke "pink" :fill "lightblue"
:relative t)
For PBM images, specify image type pbm. Color, gray-scale and
monochromatic images are supported. For mono PBM images, two additional
image properties are supported.
:foreground foregroundThe value, foreground, should be a string specifying the image
foreground color, or nil for the default color. This color is
used for each pixel in the PBM that is 1. The default is the frame’s
foreground color.
:background backgroundThe value, background, should be a string specifying the image
background color, or nil for the default color. This color is
used for each pixel in the PBM that is 0. The default is the frame’s
background color.
The remaining image types that Emacs can support are:
Image type gif.
Supports the :index property. See Multi-Frame Images.
Image type jpeg.
Image type png.
Image type tiff.
Supports the :index property. See Multi-Frame Images.
Image type webp.
Supports the :index property. See Multi-Frame Images.
The functions create-image, defimage and
find-image provide convenient ways to create image descriptors.
This function creates and returns an image descriptor which uses the
data in file-or-data. file-or-data can be a file name or
a string containing the image data; data-p should be nil
for the former case, non-nil for the latter case. If
file-or-data is a relative file name, the function will search
for it in directories mentioned in image-load-path.
The optional argument type is a symbol specifying the image type.
If type is omitted or nil, create-image tries to
determine the image type from the file’s first few bytes, or else
from the file’s name.
The remaining arguments, props, specify additional image properties—for example,
(create-image "foo.xpm" 'xpm nil :mask 'heuristic)
See Image Descriptors, for the list of supported properties. Some properties are specific to certain image types, and are described in subsections specific to those types.
The function returns nil if images of this type are not
supported. Otherwise it returns an image descriptor.
This macro defines symbol as an image name. The arguments specs is a list which specifies how to display the image. The third argument, doc, is an optional documentation string.
Each argument in specs has the form of a property list, and each
one should specify at least the :type property and either the
:file or the :data property. The value of :type
should be a symbol specifying the image type, the value of
:file is the file to load the image from, and the value of
:data is a string containing the actual image data. Here is an
example:
(defimage test-image ((:type xpm :file "~/test1.xpm") (:type xbm :file "~/test1.xbm")))
defimage tests each argument, one by one, to see if it is
usable—that is, if the type is supported and the file exists. The
first usable argument is used to make an image descriptor which is
stored in symbol.
If none of the alternatives will work, then symbol is defined
as nil.
Return the value of property in image. Properties can be
set by using setf. Setting a property to nil will
remove the property from the image.
This function provides a convenient way to find an image satisfying one of a list of image specifications specs.
Each specification in specs is a property list with contents
depending on image type. All specifications must at least contain the
properties :type type and either :file file
or :data data, where type is a symbol specifying
the image type, e.g., xbm, file is the file to load the
image from, and data is a string containing the actual image data.
The first specification in the list whose type is supported, and
file exists, is used to construct the image specification to be
returned. If no specification is satisfied, nil is returned.
The image is looked for in image-load-path.
This variable’s value is a list of locations in which to search for image files. If an element is a string or a variable symbol whose value is a string, the string is taken to be the name of a directory to search. If an element is a variable symbol whose value is a list, that is taken to be a list of directories to search.
The default is to search in the images subdirectory of the
directory specified by data-directory, then the directory
specified by data-directory, and finally in the directories in
load-path. Subdirectories are not automatically included in
the search, so if you put an image file in a subdirectory, you have to
supply the subdirectory explicitly. For example, to find the
image images/foo/bar.xpm within data-directory, you
should specify the image as follows:
(defimage foo-image '((:type xpm :file "foo/bar.xpm")))
This function returns a suitable search path for images used by the Lisp package library.
The function searches for image first using image-load-path,
excluding data-directory/images, and then in
load-path, followed by a path suitable for library, which
includes ../../etc/images and ../etc/images relative to
the library file itself, and finally in
data-directory/images.
Then this function returns a list of directories which contains first
the directory in which image was found, followed by the value of
load-path. If path is given, it is used instead of
load-path.
If no-error is non-nil and a suitable path can’t be
found, don’t signal an error. Instead, return a list of directories as
before, except that nil appears in place of the image directory.
Here is an example of using image-load-path-for-library:
(defvar image-load-path) ; shush compiler
(let* ((load-path (image-load-path-for-library
"mh-e" "mh-logo.xpm"))
(image-load-path (cons (car load-path)
image-load-path)))
(mh-tool-bar-folder-buttons-init))
Images are automatically scaled when created based on the
image-scaling-factor variable. The value is either a floating
point number (where numbers higher than 1 means to increase the size
and lower means to shrink the size), or the symbol auto, which
will compute a scaling factor based on the font pixel size. See Image Descriptors.
You can use an image descriptor by setting up the display
property yourself, but it is easier to use the functions in this
section.
This function inserts image in the current buffer at point. The
value image should be an image descriptor; it could be a value
returned by create-image, or the value of a symbol defined with
defimage. The argument string specifies the text to put
in the buffer to hold the image. If it is omitted or nil,
insert-image uses " " by default.
The argument area specifies whether to put the image in a margin.
If it is left-margin, the image appears in the left margin;
right-margin specifies the right margin. If area is
nil or omitted, the image is displayed at point within the
buffer’s text.
The argument slice specifies a slice of the image to insert. If
slice is nil or omitted the whole image is inserted.
(However, note that images are chopped on display at the window’s
right edge, because wrapping images is not supported.) Otherwise,
slice is a list (x y width
height) which specifies the x and y positions and
width and height of the image area to insert. Integer
values are in units of pixels. A floating-point number in the range
0.0–1.0 stands for that fraction of the width or height of the entire
image.
Internally, this function inserts string in the buffer, and gives
it a display property which specifies image. See The display Property. By default, doing interactive searches in the buffer will
consider string when searching. If inhibit-isearch is
non-nil, this is inhibited.
This function inserts image in the current buffer at point, like
insert-image, but splits the image into rowsxcols
equally sized slices.
Emacs displays each slice as a separate image, and allows more intuitive scrolling up/down, instead of jumping up/down the entire image when paging through a buffer that displays (large) images.
This function puts image image in front of pos in the current buffer. The argument pos should be an integer or a marker. It specifies the buffer position where the image should appear. The argument string specifies the text that should hold the image as an alternative to the default ‘x’.
The argument image must be an image descriptor, perhaps returned
by create-image or stored by defimage.
The argument area specifies whether to put the image in a margin.
If it is left-margin, the image appears in the left margin;
right-margin specifies the right margin. If area is
nil or omitted, the image is displayed at point within the
buffer’s text.
Internally, this function creates an overlay, and gives it a
before-string property containing text that has a display
property whose value is the image. (Whew! that was a mouthful…).
It returns the created overlay upon success, and also sets its
put-image property to t.
This function removes images in buffer between positions
start and end. If buffer is omitted or nil,
images are removed from the current buffer.
This removes only images that were put into buffer the way
put-image does it, not images that were inserted with
insert-image or in other ways.
This function returns the size of an image as a pair
(width . height). spec is an image
specification. pixels non-nil means return sizes measured
in pixels, otherwise return sizes measured in the default character size
of frame (see Frame Font). frame is the frame on which
the image will be displayed. frame nil or omitted means
use the selected frame (see Input Focus).
This variable is used to define the maximum size of image that Emacs will load. Emacs will refuse to load (and display) any image that is larger than this limit.
If the value is an integer, it directly specifies the maximum image height and width, measured in pixels. If it is floating point, it specifies the maximum image height and width as a ratio to the frame height and width. If the value is non-numeric, there is no explicit limit on the size of images.
The purpose of this variable is to prevent unreasonably large images
from accidentally being loaded into Emacs. It only takes effect the
first time an image is loaded. Once an image is placed in the image
cache, it can always be displayed, even if the value of
max-image-size is subsequently changed (see Image Cache).
This function returns t if point is on an image, and nil
otherwise.
Images inserted with the insertion functions above also get a local keymap installed in the text properties (or overlays) that span the displayed image. This keymap defines the following commands:
Increase the image size (image-increase-size)
Decrease the image size (image-decrease-size).
Rotate the image (image-rotate).
Flip the image horizontally (image-flip-horizontally).
Flip the image vertically (image-flip-vertically).
Save the image to a file (image-save).
Interactively crop the image (image-crop).
Interactively cut a rectangle from the image (image-cut).
See Image Mode in The GNU Emacs Manual, for more details about these image-specific key bindings.
Some image files can contain more than one image. We say that there are multiple “frames” in the image. At present, Emacs supports multiple frames for GIF, TIFF, WebP, and certain ImageMagick formats such as DJVM.
The frames can be used either to represent multiple pages (this is usually the case with multi-frame TIFF files, for example), or to create animation (usually the case with multi-frame GIF files).
A multi-frame image has a property :index, whose value is an
integer (counting from 0) that specifies which frame is being displayed.
This function returns non-nil if image contains more than
one frame. The actual return value is a cons (nimages
. delay), where nimages is the number of frames and
delay is the delay in seconds between them, or nil
if the image does not specify a delay. Images that are intended to be
animated usually specify a frame delay, whereas ones that are intended
to be treated as multiple pages do not.
This function returns the index of the current frame number for image, counting from 0.
This function switches image to frame number n. It
replaces a frame number outside the valid range with that of the end
of the range, unless nocheck is non-nil. If image
does not contain a frame with the specified number, the image displays
as a hollow box.
This function animates image. The optional integer index
specifies the frame from which to start (default 0). The optional
argument limit controls the length of the animation. If omitted
or nil, the image animates once only; if t it loops
forever; if a number animation stops after that many seconds.
Animation operates by means of a timer. Note that Emacs imposes a
minimum frame delay of 0.01 (image-minimum-frame-delay) seconds.
If the image itself does not specify a delay, Emacs uses
image-default-frame-delay.
This function returns the timer responsible for animating image, if there is one.
Emacs caches images so that it can display them again more
efficiently. When Emacs displays an image, it searches the image
cache for an existing image specification equal to the desired
specification. If a match is found, the image is displayed from the
cache. Otherwise, Emacs loads the image normally.
This function removes the image with specification spec from the
image cache of frame frame. Image specifications are compared
using equal. If frame is nil, it defaults to the
selected frame. If frame is t, the image is flushed on
all existing frames.
In Emacs’s current implementation, each graphical terminal possesses an image cache, which is shared by all the frames on that terminal (see Multiple Terminals). Thus, refreshing an image in one frame also refreshes it in all other frames on the same terminal.
One use for image-flush is to tell Emacs about a change in an
image file. If an image specification contains a :file
property, the image is cached based on the file’s contents when the
image is first displayed. Even if the file subsequently changes,
Emacs continues displaying the old version of the image. Calling
image-flush flushes the image from the cache, forcing Emacs to
re-read the file the next time it needs to display that image.
Another use for image-flush is for memory conservation. If
your Lisp program creates a large number of temporary images over a
period much shorter than image-cache-eviction-delay (see
below), you can opt to flush unused images yourself, instead of
waiting for Emacs to do it automatically.
This function clears an image cache, removing all the images stored in
it. If filter is omitted or nil, it clears the cache for
the selected frame. If filter is a frame, it clears the cache
for that frame. If filter is t, all image caches are
cleared. Otherwise, filter is taken to be a file name, and all
images associated with that file name are removed from all image
caches.
This function also clears the image animation cache, which is a separate
cache that Emacs maintains for animated multi-frame images
(see Multi-Frame Images). If animation-filter is omitted or
nil, it clears the animation cache in addition to the image
caches selected by filter. Otherwise, this function removes the
image with specification eq to animation-filter only from
the animation cache, and does not clear any image caches. This can help
reduce memory usage after an animation is stopped but the image is still
displayed.
If an image in the image cache has not been displayed for a specified period of time, Emacs removes it from the cache and frees the associated memory.
This variable specifies the number of seconds an image can remain in the cache without being displayed. When an image is not displayed for this length of time, Emacs removes it from the image cache.
Under some circumstances, if the number of images in the cache grows too large, the actual eviction delay may be shorter than this.
If the value is nil, Emacs does not remove images from the cache
except when you explicitly clear it. This mode can be useful for
debugging.
This function returns the total size of the current image cache, in bytes. An image of size 200x100 with 24 bits per color will have a cache size of 60000 bytes, for instance.
Emacs sometimes uses buttons (for clicking on) or small graphics (to illustrate something). Since Emacs is available on a wide variety of systems with different capabilities, and users have different preferences, Emacs provides a facility to handle this in a convenient way, allowing customization, graceful degradation, accessibility, as well as themability: Icons.
The central macro here is define-icon, and here’s a simple
example:
(define-icon outline-open button
'((image "right.svg" "open.xpm" "open.pbm" :height line)
(emoji "▶️")
(symbol "▶" "➤")
(text "open" :face icon-button))
"Icon used for buttons for opening a section in outline buffers."
:version "29.1"
:help-echo "Open this section")
Which alternative will actually be displayed depends on the value of
the user option icon-preference (see Icons in The GNU
Emacs Manual) and on the results of run-time checks for what the
current frame’s terminal can actually display.
The macro in the example above defines outline-open as an icon,
and inherits properties from the icon called button (so this is
meant as a clickable button to be inserted in a buffer). It is
followed by a list of icon types along with the actual icon
shapes themselves. In addition, there’s a doc string and various
keywords that contain additional information and properties.
To instantiate an icon, you use icon-string, which will
consult the current Customize theming, and the icon-preference
user option, and finally what the Emacs is able to actually display.
If icon-preference is (image emoji symbol text) (i.e.,
allowing all of these forms of icons), in this case,
icon-string will first check that Emacs is able to display
images at all, and then whether it has support for each of those
different image formats. If that fails, Emacs will check whether
Emacs can display emojis (in the current frame). If that fails, it’ll
check whether it can display the symbol in question. If that fails,
it’ll use the plain text version.
For instance, if icon-preference doesn’t contain image
or emoji, it’ll skip those entries.
Code can confidently call icon-string in all circumstances and
be sure that something readable will appear on the screen, no
matter whether the user is on a graphical terminal or a text terminal,
and no matter which features Emacs was built with.
Define an icon name, a symbol, with the display alternatives in
spec, that can be later instantiated using icon-string.
The name is the name of the resulting keyword.
The resulting icon will inherit specs from parent, and from their parent’s parents, and so on, and the lowest descendent element wins.
specs is a list of icon specifications. The first element of each specification is the type, and the rest is something that can be used as an icon of that type, and then optionally followed by a keyword list. The following icon types are available:
imageIn this case, there may be many images listed as candidates. Emacs
will choose the first one that the current Emacs instance can show.
If an image is listed is an absolute file name, it’s used as is, but it’s
otherwise looked up in the list image-load-path
(see Defining Images).
emojiThis should be a (possibly colorful) emoji.
symbolThis should be a (monochrome) symbol character.
textIcons should also have a textual fallback. This can also be used for
the visually impaired: if icon-preference is just
(text), all icons will be replaced by text.
Various keywords may follow the list of icon specifications. For instance:
(symbol "▶" "➤" :face icon-button)
Unknown keywords are ignored. The following keywords are allowed:
:faceThe face to be used for the icon.
:heightThis is only valid for image icons, and can be either a number
(which specifies the height in pixels), or the symbol line,
which will use the default line height in the currently selected
window.
:widthThis is only valid for image icons, and can be either a number
(which specifies the width in pixels), or the symbol font,
which will use the width in pixels of the current buffer’s default
face font.
doc should be a doc string.
keywords is a list of keyword/value pairs. The following keywords are allowed:
:versionThe (approximate) Emacs version this button first appeared. (This keyword is mandatory.)
:groupThe customization group this icon belongs in. If not present, it is inferred.
:help-echoThe help string shown when hovering over the icon with the mouse pointer.
This function returns a string suitable for display in the current buffer for icon.
Alternatively, you can get a “deconstructed” version of icon
with this function. It returns a plist (see Property Lists) where
the keys are string, face and image. (The latter
is only present if the icon is represented by an image.) This can be
useful if the icon isn’t to be inserted directly in the buffer, but
needs some sort of pre-processing first.
Icons can be customized with M-x customize-icon. Themes can specify changes to icons with, for instance:
(custom-theme-set-icons
'my-theme
'(outline-open ((image :height 100)
(text " OPEN ")))
'(outline-close ((image :height 100)
(text " CLOSE " :face warning))))
Emacs is able to display native widgets, such as GTK+ WebKit widgets,
in Emacs buffers when it was built with the necessary support
libraries and is running on a graphical terminal. To test whether
Emacs supports display of embedded widgets, check that the
xwidget-internal feature is available (see Features).
To display an embedded widget in a buffer, you must first create an
xwidget object, and then use that object as the display specifier
in a display text or overlay property (see The display Property).
Embedded widgets can send events notifying Lisp code about changes occurring within them. (see Xwidget events).
This creates and returns an xwidget object. If
buffer is omitted or nil, it defaults to the current
buffer. If buffer names a buffer that doesn’t exist, it will be
created. The type identifies the type of the xwidget component,
it can be one of the following:
webkitThe WebKit component.
The width and height arguments specify the widget size in pixels, and title, a string, specifies its title. related is used internally by the WebKit widget, and specifies another WebKit widget that the newly created widget should share settings and subprocesses with.
The xwidget that is returned will be killed alongside its buffer
(see Killing Buffers). You can also kill it using
kill-xwidget. Once it is killed, the xwidget may continue to
exist as a Lisp object and act as a display property until all
references to it are gone, but most actions that can be performed on
live xwidgets will no longer be available.
This function returns t if object is an xwidget,
nil otherwise.
This function returns t if object is an xwidget that
hasn’t been killed, and nil otherwise.
This function kills xwidget, by removing it from its buffer and releasing window system resources it holds.
This function returns the property list of xwidget.
This function replaces the property list of xwidget with a new property list given by plist.
This function returns the buffer of xwidget. If xwidget
has been killed, it returns nil.
This function sets the buffer of xwidget to buffer.
This function returns a list of xwidget objects associated with the
buffer, which can be specified as a buffer object or a name of
an existing buffer, a string. The value is nil if buffer
contains no xwidgets.
This function browses the specified uri in the given xwidget. The uri is a string that specifies the name of a file or a URL.
This function causes the browser widget specified by xwidget to
execute the specified JavaScript script.
This function returns the title of xwidget as a string.
This function resizes the specified xwidget to the size widthxheight pixels.
This function returns the desired size of xwidget as a list of
the form (width height). The dimensions are in
pixels.
This function returns the attributes of xwidget as a vector of
the form [type title width height].
The attributes are usually determined by make-xwidget when the
xwidget is created.
This function allows you to arrange that Emacs will ask the user for
confirmation before exiting or before killing a buffer that has
xwidget associated with it. If flag is non-nil,
Emacs will query the user, otherwise it will not.
This function returns the current setting of xwidgets
query-on-exit flag, either t or nil.
Send an input event event to xwidget. The precise action performed is platform-specific. See Input Events.
You can optionally pass the frame on which the event was generated via
frame. On X11, modifier keys in key events will not be
considered if frame is nil, and the selected frame is not
an X-Windows frame.
On GTK, only keyboard and function key events are supported. Mouse, motion, and click events are dispatched to the xwidget without going through Lisp code, and as such shouldn’t require this function to be called.
Start an incremental search on the WebKit widget xwidget with the string query as the query. case-insensitive denotes whether or not the search is case-insensitive, backwards determines if the search is performed backwards towards the start of the document, and wrap-around determines whether or not the search terminates at the end of the document.
If the function is called while a search query is already present, then the query specified here will replace the existing query.
To stop a search query, use xwidget-webkit-finish-search.
Display the next search result in xwidget. This function will
signal an error if a search query has not been already started in
xwidget through xwidget-webkit-search.
If wrap-around was non-nil when xwidget-webkit-search
was called, then the search will restart from the beginning of the
document when its end is reached.
Display the previous search result in xwidget. This function
signals an error if a search query has not been already started in
xwidget through xwidget-webkit-search.
If wrap-around was non-nil when xwidget-webkit-search
was called, then the search will restart from the end of the
document when its beginning is reached.
Finish a search operation started with xwidget-webkit-search in
xwidget. If there is no query currently ongoing, this function
signals an error.
Load text, a string, into xwidget, which should be a WebKit xwidget. Any HTML markup in text will be processed by xwidget while rendering the text.
Optional argument base-uri, which should be a string, specifies the absolute location of the web resources referenced by text, to be used for resolving relative links in text.
Make xwidget, a WebKit widget, load the rel-posth element in its navigation history.
If rel-pos is zero, the current page will be reloaded instead.
Return the navigation history of xwidget, up to limit items in each direction. If not specified, limit defaults to 50.
The returned value is a list of the form (back here forward), where here is the current
navigation item, while back is a list of items containing the
items recorded by WebKit before the current navigation item, and
forward is a list of items recorded after the current navigation
item. back, here and forward can all be nil.
When here is nil, it means that no items have been
recorded yet; if back or forward are nil, it means
that there is no history recorded before or after the current item
respectively.
Navigation items are themselves lists of the form (idx title uri). In these lists, idx is an index that
can be passed to xwidget-webkit-goto-history, title is
the human-readable title of the item, and uri is the URI of the
item. The user should normally have no reason to load uri
manually to reach a specific history item. Instead, idx should
be passed as an index to xwidget-webkit-goto-history.
Return an estimate of how much data is remaining to be transferred before the page displayed by the WebKit widget xwidget is fully loaded.
The value returned is a float ranging between 0.0 and 1.0.
Make the WebKit widget xwidget store cookies in file.
file must be an absolute file name. The new setting will also
affect any xwidget that was created with xwidget as the
related argument to make-xwidget, and widgets related to
those as well.
If this function is not called at least once on xwidget or a related widget, xwidget will not store cookies on disk at all.
Terminate any data transfer still in progress in the WebKit widget xwidget as part of a page-loading operation. If a page is not being loaded, this function does nothing.
The Button package defines functions for inserting and manipulating buttons that can be activated with the mouse or via keyboard commands. These buttons are typically used for various kinds of hyperlinks.
A button is essentially a set of text or overlay properties, attached to a stretch of text in a buffer. These properties are called button properties. One of these properties, the action property, specifies a function which is called when the user invokes the button using the keyboard or the mouse. The action function may examine the button and use its other properties as desired.
In some ways, the Button package duplicates the functionality in the Widget package. See Introduction in The Emacs Widget Library. The advantage of the Button package is that it is faster, smaller, and simpler to program. From the point of view of the user, the interfaces produced by the two packages are very similar.
Each button has an associated list of properties defining its appearance and behavior, and other arbitrary properties may be used for application specific purposes. The following properties have special meaning to the Button package:
action ¶The function to call when the user invokes the button, which is passed
the single argument button. By default this is ignore,
which does nothing.
mouse-action ¶This is similar to action, and when present, will be used
instead of action for button invocations resulting from
mouse-clicks (instead of the user hitting RET). If not
present, mouse-clicks use action instead.
face ¶This is an Emacs face controlling how buttons of this type are
displayed; by default this is the button face.
mouse-face ¶This is an additional face which controls appearance during
mouse-overs (merged with the usual button face); by default this is
the usual Emacs highlight face.
keymap ¶The button’s keymap, defining bindings active within the button
region. By default this is the usual button region keymap, stored
in the variable button-map, which defines RET and
mouse-2 to invoke the button.
type ¶The button type. See Button Types.
help-echo ¶A string displayed by the Emacs tooltip help system; by default,
"mouse-2, RET: Push this button". Alternatively, a function
that returns, or a form that evaluates to, a string to be displayed or
nil. For details see Text help-echo.
The function is called with three arguments, window,
object, and pos. The second argument, object, is
either the overlay that had the property (for overlay buttons), or the
buffer containing the button (for text property buttons). The other
arguments have the same meaning as for the special text property
help-echo.
follow-link ¶The follow-link property, defining how a mouse-1 click
behaves on this button, See Defining Clickable Text.
button ¶All buttons have a non-nil button property, which may be useful
in finding regions of text that comprise buttons (which is what the
standard button functions do).
There are other properties defined for the regions of text in a button, but these are not generally interesting for typical uses.
Every button has a button type, which defines default values for the button’s properties. Button types are arranged in a hierarchy, with specialized types inheriting from more general types, so that it’s easy to define special-purpose types of buttons for specific tasks.
Define a button type called name (a symbol).
The remaining arguments
form a sequence of property value pairs, specifying default
property values for buttons with this type (a button’s type may be set
by giving it a type property when creating the button, using
the :type keyword argument).
In addition, the keyword argument :supertype may be used to
specify a button-type from which name inherits its default
property values. Note that this inheritance happens only when
name is defined; subsequent changes to a supertype are not
reflected in its subtypes.
Using define-button-type to define default properties for
buttons is not necessary—buttons without any specified type use the
built-in button-type button—but it is encouraged, since
doing so usually makes the resulting code clearer and more efficient.
Buttons are associated with a region of text, using an overlay or
text properties to hold button-specific information, all of which are
initialized from the button’s type (which defaults to the built-in
button type button). Like all Emacs text, the appearance of
the button is governed by the face property; by default (via
the face property inherited from the button button-type)
this is a simple underline, like a typical web-page link.
For convenience, there are two sorts of button-creation functions,
those that add button properties to an existing region of a buffer,
called make-...button, and those that also insert the button
text, called insert-...button.
The button-creation functions all take the &rest argument
properties, which should be a sequence of property value
pairs, specifying properties to add to the button; see Button Properties. In addition, the keyword argument :type may be
used to specify a button-type from which to inherit other properties;
see Button Types. Any properties not explicitly specified
during creation will be inherited from the button’s type (if the type
defines such a property).
The following functions add a button using an overlay (see Overlays) to hold the button properties:
This makes a button from beg to end in the current buffer, and returns it.
This inserts a button with the label label at point, and returns it.
The following functions are similar, but using text properties (see Text Properties) to hold the button properties. Such buttons do not add markers to the buffer, so editing in the buffer does not slow down if there is an extremely large numbers of buttons. However, if there is an existing face text property on the text (e.g., a face assigned by Font Lock mode), the button face may not be visible. Both of these functions return the starting position of the new button.
This makes a button from beg to end in the current buffer, using text properties.
This inserts a button with the label label at point, using text properties.
Sometimes it’s more convenient to make a string into a button without
inserting it into a buffer immediately, for instance when creating
data structures that may then, later, be inserted into a buffer. This
function makes string into such a string, and callback
will be called when the user clicks on the button. The optional
data parameter will be used as the parameter when callback
is called. If nil, the button is used as the parameter instead.
Sometimes it’s more convenient to convert existing text in a buffer to a
button instead of inserting new text. This function makes the region
between start and end into a button. Arguments
callback and data have the same meanings as for
buttonize. Optional argument help-echo is used as the
help-echo property of the button.
This function removes all buttons between start and end in the current buffer (both overlay and text-property based ones).
These are functions for getting and setting properties of buttons. Often these are used by a button’s invocation function to determine what to do.
Where a button parameter is specified, it means an object referring to a specific button, either an overlay (for overlay buttons), or a buffer-position or marker (for text property buttons). Such an object is passed as the first argument to a button’s invocation function when it is invoked.
Return the position at which button starts.
Return the position at which button ends.
Get the property of button button named prop.
Set button’s prop property to val.
Call button’s action property (i.e., invoke the function
that is the value of that property, passing it the single argument
button). If use-mouse-action is non-nil, try to
invoke the button’s mouse-action property instead of
action; if the button has no mouse-action property, use
action as normal. If the button-data property is
present in button, use that as the argument for the
action function instead of button.
Return button’s text label.
Return button’s button-type.
Return t if button has button-type type, or one of
type’s subtypes.
Return the button at position pos in the current buffer, or
nil. If the button at pos is a text property button, the
return value is a marker pointing to pos.
Set the button-type type’s prop property to val.
Get the property of button-type type named prop.
Return t if button-type type is a subtype of supertype.
These are commands and functions for locating and operating on buttons in an Emacs buffer.
push-button is the command that a user uses to actually push
a button, and is bound by default in the button itself to RET
and to mouse-2 using a local keymap in the button’s overlay or
text properties. Commands that are useful outside the buttons itself,
such as forward-button and backward-button are
additionally available in the keymap stored in
button-buffer-map; a mode which uses buttons may want to use
button-buffer-map as a parent keymap for its keymap.
Alternatively, the button-mode can be switched on for much the
same effect: It’s a minor mode that does nothing else than install
button-buffer-map as a minor mode keymap (note that disabling
button-mode will remove all the buttons in the current buffer).
If the button has a non-nil follow-link property, and
mouse-1-click-follows-link is set, a quick mouse-1 click
will also activate the push-button command.
See Defining Clickable Text.
Perform the action specified by a button at location pos.
pos may be either a buffer position or a mouse-event. If
use-mouse-action is non-nil, or pos is a
mouse-event (see Mouse Events), try to invoke the button’s
mouse-action property instead of action; if the button
has no mouse-action property, use action as normal.
pos defaults to point, except when push-button is invoked
interactively as the result of a mouse-event, in which case, the mouse
event’s position is used. If there’s no button at pos, do
nothing and return nil, otherwise return t.
Move to the nth next button, or nth previous button if
n is negative. If n is zero, move to the start of any
button at point. If wrap is non-nil, moving past either
end of the buffer continues from the other end. If
display-message is non-nil, the button’s help-echo string
is displayed. Any button with a non-nil skip property
is skipped over. Returns the button found, and signals an error if no
buttons can be found. If no-error is non-nil, return nil
instead of signaling the error.
Move to the nth previous button, or nth next button if
n is negative. If n is zero, move to the start of any
button at point. If wrap is non-nil, moving past either
end of the buffer continues from the other end. If
display-message is non-nil, the button’s help-echo string
is displayed. Any button with a non-nil skip property
is skipped over. Returns the button found, and signals an error if no
buttons can be found. If no-error is non-nil, return nil
instead of signaling the error.
Return the next button after (for next-button) or before (for
previous-button) position pos in the current buffer. If
count-current is non-nil, count any button at pos
in the search, instead of starting at the next button.
The Ewoc package constructs buffer text that represents a structure of Lisp objects, and updates the text to follow changes in that structure. This is like the “view” component in the “model–view–controller” design paradigm. Ewoc means “Emacs’s Widget for Object Collections”.
An ewoc is a structure that organizes information required to construct buffer text that represents certain Lisp data. The buffer text of the ewoc has three parts, in order: first, fixed header text; next, textual descriptions of a series of data elements (Lisp objects that you specify); and last, fixed footer text. Specifically, an ewoc contains information on:
Typically, you define an ewoc with ewoc-create, and then pass
the resulting ewoc structure to other functions in the Ewoc package to
build nodes within it, and display it in the buffer. Once it is
displayed in the buffer, other functions determine the correspondence
between buffer positions and nodes, move point from one node’s textual
representation to another, and so forth. See Abstract Display Functions.
A node encapsulates a data element much the way a variable holds a value. Normally, encapsulation occurs as a part of adding a node to the ewoc. You can retrieve the data element value and place a new value in its place, like so:
(ewoc-data node) ⇒ value (ewoc-set-data node new-value) ⇒ new-value
You can also use, as the data element value, a Lisp object (list or vector) that is a container for the real value, or an index into some other structure. The example (see Abstract Display Example) uses the latter approach.
When the data changes, you will want to update the text in the
buffer. You can update all nodes by calling ewoc-refresh, or
just specific nodes using ewoc-invalidate, or all nodes
satisfying a predicate using ewoc-map. Alternatively, you can
delete invalid nodes using ewoc-delete or ewoc-filter,
and add new nodes in their place. Deleting a node from an ewoc deletes
its associated textual description from buffer, as well.
In this subsection, ewoc and node stand for the structures described above (see Abstract Display), while data stands for an arbitrary Lisp object used as a data element.
This constructs and returns a new ewoc, with no nodes (and thus no data
elements). pretty-printer should be a function that takes one
argument, a data element of the sort you plan to use in this ewoc, and
inserts its textual description at point using insert (and never
insert-before-markers, because that would interfere with the
Ewoc package’s internal mechanisms).
Normally, a newline is automatically inserted after the header,
the footer and every node’s textual description. If nosep
is non-nil, no newline is inserted. This may be useful for
displaying an entire ewoc on a single line, for example, or for
making nodes invisible by arranging for pretty-printer
to do nothing for those nodes.
An ewoc maintains its text in the buffer that is current when
you create it, so switch to the intended buffer before calling
ewoc-create.
This returns the buffer where ewoc maintains its text.
This returns a cons cell (header . footer)
made from ewoc’s header and footer.
This sets the header and footer of ewoc to the strings header and footer, respectively.
These add a new node encapsulating data, putting it, respectively, at the beginning or end of ewoc’s chain of nodes.
These add a new node encapsulating data, adding it to ewoc before or after node, respectively.
These return, respectively, the previous node and the next node of node in ewoc.
This returns the node in ewoc found at zero-based index n.
A negative n means count from the end. ewoc-nth returns
nil if n is out of range.
This extracts the data encapsulated by node and returns it.
This sets the data encapsulated by node to data.
This determines the node in ewoc which contains point (or
pos if specified), and returns that node. If ewoc has no
nodes, it returns nil. If pos is before the first node,
it returns the first node; if pos is after the last node, it returns
the last node. The optional third arg guess
should be a node that is likely to be near pos; this doesn’t
alter the result, but makes the function run faster.
This returns the start position of node.
These move point to the previous or next, respectively, argth node
in ewoc. ewoc-goto-prev does not move if it is already at
the first node or if ewoc is empty, whereas ewoc-goto-next
moves past the last node, returning nil. Excepting this special
case, these functions return the node moved to.
This moves point to the start of node in ewoc.
This function regenerates the text of ewoc. It works by deleting the text between the header and the footer, i.e., all the data elements’ representations, and then calling the pretty-printer function for each node, one by one, in order.
This is similar to ewoc-refresh, except that only nodes in
ewoc are updated instead of the entire set.
This deletes each node in nodes from ewoc.
This calls predicate for each data element in ewoc and
deletes those nodes for which predicate returns nil.
Any args are passed to predicate.
This calls predicate for each data element in ewoc
and returns a list of those elements for which predicate
returns non-nil. The elements in the list are ordered
as in the buffer. Any args are passed to predicate.
This calls map-function for each data element in ewoc and
updates those nodes for which map-function returns non-nil.
Any args are passed to map-function.
Here is a simple example using functions of the ewoc package to implement a color components display, an area in a buffer that represents a vector of three integers (itself representing a 24-bit RGB value) in various ways.
(setq colorcomp-ewoc nil
colorcomp-data nil
colorcomp-mode-map nil
colorcomp-labels ["Red" "Green" "Blue"])
(defun colorcomp-pp (data)
(if data
(let ((comp (aref colorcomp-data data)))
(insert (aref colorcomp-labels data) "\t: #x"
(format "%02X" comp) " "
(make-string (ash comp -2) ?#) "\n"))
(let ((cstr (format "#%02X%02X%02X"
(aref colorcomp-data 0)
(aref colorcomp-data 1)
(aref colorcomp-data 2)))
(samp " (sample text) "))
(insert "Color\t: "
(propertize samp 'face
`(foreground-color . ,cstr))
(propertize samp 'face
`(background-color . ,cstr))
"\n"))))
(defun colorcomp (color)
"Allow fiddling with COLOR in a new buffer.
The buffer is in Color Components mode."
(interactive "sColor (name or #RGB or #RRGGBB): ")
(when (string= "" color)
(setq color "green"))
(unless (color-values color)
(error "No such color: %S" color))
(switch-to-buffer
(generate-new-buffer (format "originally: %s" color)))
(kill-all-local-variables)
(setq major-mode 'colorcomp-mode
mode-name "Color Components")
(use-local-map colorcomp-mode-map)
(erase-buffer)
(buffer-disable-undo)
(let ((data (apply 'vector (mapcar (lambda (n) (ash n -8))
(color-values color))))
(ewoc (ewoc-create 'colorcomp-pp
"\nColor Components\n\n"
(substitute-command-keys
"\n\\{colorcomp-mode-map}"))))
(set (make-local-variable 'colorcomp-data) data)
(set (make-local-variable 'colorcomp-ewoc) ewoc)
(ewoc-enter-last ewoc 0)
(ewoc-enter-last ewoc 1)
(ewoc-enter-last ewoc 2)
(ewoc-enter-last ewoc nil)))
This example can be extended to be a color selection widget (in
other words, the “controller” part of the “model–view–controller”
design paradigm) by defining commands to modify colorcomp-data
and to finish the selection process, and a keymap to tie it all
together conveniently.
(defun colorcomp-mod (index limit delta)
(let ((cur (aref colorcomp-data index)))
(unless (= limit cur)
(aset colorcomp-data index (+ cur delta)))
(ewoc-invalidate
colorcomp-ewoc
(ewoc-nth colorcomp-ewoc index)
(ewoc-nth colorcomp-ewoc -1))))
(defun colorcomp-R-more () (interactive) (colorcomp-mod 0 255 1))
(defun colorcomp-G-more () (interactive) (colorcomp-mod 1 255 1))
(defun colorcomp-B-more () (interactive) (colorcomp-mod 2 255 1))
(defun colorcomp-R-less () (interactive) (colorcomp-mod 0 0 -1))
(defun colorcomp-G-less () (interactive) (colorcomp-mod 1 0 -1))
(defun colorcomp-B-less () (interactive) (colorcomp-mod 2 0 -1))
(defun colorcomp-copy-as-kill-and-exit ()
"Copy the color components into the kill ring and kill the buffer.
The string is formatted #RRGGBB (hash followed by six hex digits)."
(interactive)
(kill-new (format "#%02X%02X%02X"
(aref colorcomp-data 0)
(aref colorcomp-data 1)
(aref colorcomp-data 2)))
(kill-buffer nil))
(setq colorcomp-mode-map
(define-keymap :suppress t
"i" 'colorcomp-R-less
"o" 'colorcomp-R-more
"k" 'colorcomp-G-less
"l" 'colorcomp-G-more
"," 'colorcomp-B-less
"." 'colorcomp-B-more
"SPC" 'colorcomp-copy-as-kill-and-exit))
Note that we never modify the data in each node, which is fixed when the
ewoc is created to be either nil or an index into the vector
colorcomp-data, the actual color components.
This section describes the mechanism by which Emacs shows a matching open parenthesis when the user inserts a close parenthesis.
The value of this variable should be a function (of no arguments) to
be called whenever a character with close parenthesis syntax is inserted.
The value of blink-paren-function may be nil, in which
case nothing is done.
If this variable is nil, then blink-matching-open does
nothing.
This variable specifies the maximum distance to scan for a matching parenthesis before giving up.
This variable specifies the number of seconds to keep indicating the matching parenthesis. A fraction of a second often gives good results, but the default is 1, which works on all systems.
This function is the default value of blink-paren-function. It
assumes that point follows a character with close parenthesis syntax
and applies the appropriate effect momentarily to the matching opening
character. If that character is not already on the screen, it
displays the character’s context in the echo area. To avoid long
delays, this function does not search farther than
blink-matching-paren-distance characters.
Here is an example of calling this function explicitly.
(defun interactive-blink-matching-open () "Indicate momentarily the start of parenthesized sexp before point." (interactive)
(let ((blink-matching-paren-distance
(buffer-size))
(blink-matching-paren t))
(blink-matching-open)))
This section describes how characters are actually displayed by Emacs. Typically, a character is displayed as a glyph (a graphical symbol which occupies one character position on the screen), whose appearance corresponds to the character itself. For example, the character ‘a’ (character code 97) is displayed as ‘a’. Some characters, however, are displayed specially. For example, the formfeed character (character code 12) is usually displayed as a sequence of two glyphs, ‘^L’, while the newline character (character code 10) starts a new screen line.
You can modify how each character is displayed by defining a display table, which maps each character code into a sequence of glyphs. See Display Tables.
Here are the conventions for displaying each character code (in the absence of a display table, which can override these conventions; see Display Tables).
tab-width controls the number of
spaces per tab stop (see below).
ctl-arrow. If this variable is non-nil (the default),
these characters are displayed as sequences of two glyphs, where the
first glyph is ‘^’ (a display table can specify a glyph to use
instead of ‘^’); e.g., the DEL character is displayed as
‘^?’.
If ctl-arrow is nil, these characters are displayed as
octal escapes (see below).
This rule also applies to carriage return (character code 13), if that character appears in the buffer. But carriage returns usually do not appear in buffer text; they are eliminated as part of end-of-line conversion (see Basic Concepts of Coding Systems).
The above display conventions apply even when there is a display
table, for any character whose entry in the active display table is
nil. Thus, when you set up a display table, you need only
specify the characters for which you want special display behavior.
The following variables affect how certain characters are displayed
on the screen. Since they change the number of columns the characters
occupy, they also affect the indentation functions. They also affect
how the mode line is displayed; if you want to force redisplay of the
mode line using the new values, call the function
force-mode-line-update (see Mode Line Format).
This buffer-local variable controls how control characters are
displayed. If it is non-nil, they are displayed as a caret
followed by the character: ‘^A’. If it is nil, they are
displayed as octal escapes: a backslash followed by three octal
digits, as in ‘\001’.
The value of this buffer-local variable is the spacing between tab
stops used for displaying tab characters in Emacs buffers. The value
is in units of columns, and the default is 8. Note that this feature
is completely independent of the user-settable tab stops used by the
command tab-to-tab-stop. See Adjustable Tab Stops.
A display table is a special-purpose char-table
(see Char-Tables), with display-table as its subtype, which
is used to override the usual character display conventions. This
section describes how to make, inspect, and assign elements to a
display table object. The next section (see Active Display Table)
describes the various standard display tables and their precedence.
This creates and returns a display table. The table initially has
nil in all elements.
The ordinary elements of the display table are indexed by character
codes; the element at index c says how to display the character
code c. The value should be nil (which means to display
the character c according to the usual display conventions;
see Usual Display Conventions), or a vector of glyph codes (which means to
display the character c as those glyphs; see Glyphs).
Warning: if you use the display table to change the display of newline characters, the whole buffer will be displayed as one long line.
The display table also has six extra slots which serve special
purposes. Here is a table of their meanings; nil in any slot
means to use the default for that slot, as stated below.
The glyph for the end of a truncated screen line (the default for this is ‘$’). See Glyphs. On graphical terminals, Emacs by default uses arrows in the fringes to indicate truncation, so the display table has no effect, unless you disable the fringes (see Window Fringes in the GNU Emacs Manual).
The glyph for the end of a continued line (the default is ‘\’). On graphical terminals, Emacs by default uses curved arrows in the fringes to indicate continuation, so the display table has no effect, unless you disable the fringes.
The glyph for indicating a character displayed as an octal character code (the default is ‘\’).
The glyph for indicating a control character (the default is ‘^’).
A vector of glyphs for indicating the presence of invisible lines (the default is ‘...’). See Selective Display.
The glyph used to draw the border between side-by-side windows (the default is ‘|’). See Splitting Windows. This currently has effect only on text terminals; on graphical terminals, if vertical scroll bars are supported and in use, a scroll bar separates the two windows, and if there are no vertical scroll bars and no dividers (see Window Dividers), Emacs uses a thin line to indicate the border.
The glyphs for a single-line border around child frames on a terminal, in the order of vertical, horizontal, down-right edge, down-left edge, up-right, and up-left edge glyphs. The horizontal glyph is also used for the single-line tty menu separator.
The glyphs for a double-line border, in the order of vertical, horizontal, down-right edge, down-left edge, up-right, and up-left edge glyphs. The horizontal glyph is also used for the single-line TTY menu separator, the other glyphs are not yet used.
For example, here is how to construct a display table that mimics
the effect of setting ctl-arrow to a non-nil value
(see Glyphs, for the function make-glyph-code):
(setq disptab (make-display-table))
(dotimes (i 32)
(or (= i ?\t)
(= i ?\n)
(aset disptab i
(vector (make-glyph-code ?^ 'escape-glyph)
(make-glyph-code (+ i 64) 'escape-glyph)))))
(aset disptab 127
(vector (make-glyph-code ?^ 'escape-glyph)
(make-glyph-code ?? 'escape-glyph)))
This function returns the value of the extra slot slot of display-table. The argument slot may be a number from 0 to 17 inclusive, or a slot name, a symbol.
This function stores value in the extra slot slot of display-table. The argument slot may be a number from 0 to 17 inclusive, or a slot name, a symbol.
Valid slot name symbols are truncation, wrap,
escape, control, selective-display,
vertical-border, box-vertical, box-horizontal,
box-down-right, box-down-left, box-up-right,
box-up-left, box-double-vertical,
box-double-horizontal, box-double-down-right,
box-double-down-left, box-double-up-right,
box-double-up-left.
This function displays a description of the display table display-table in a help buffer.
This function sets the extra slots of standard-display-table with suitable Unicode characters.
This command displays a description of the current display table in a help buffer.
Each window can specify a display table, and so can each buffer.
The window’s display table, if there is one, takes precedence over the
buffer’s display table. If neither exists, Emacs tries to use the
standard display table; if that is nil, Emacs uses the usual
character display conventions (see Usual Display Conventions). (Emacs does
not “merge” display tables: For instance, if the window has a
display table, the buffer’s display table and the standard display
table are completely ignored.)
Note that display tables affect how the mode line is displayed, so
if you want to force redisplay of the mode line using a new display
table, call force-mode-line-update (see Mode Line Format).
This function returns window’s display table, or nil if
there is none. The default for window is the selected window.
This function sets the display table of window to table.
The argument table should be either a display table or
nil.
This variable is automatically buffer-local in all buffers; its value
specifies the buffer’s display table. If it is nil, there is
no buffer display table.
The value of this variable is the standard display table, which is
used when Emacs is displaying a buffer in a window with neither a
window display table nor a buffer display table defined, or when Emacs
is outputting text to the standard output or error streams. Although its
default is typically nil, in an interactive session if the
terminal cannot display curved quotes, its default maps curved quotes
to ASCII approximations. See Text Quoting Style.
The disp-table library defines several functions for changing the standard display table.
A glyph is a graphical symbol which occupies a single character position on the screen. Each glyph is represented in Lisp as a glyph code, which specifies a character and optionally a face to display it in (see Faces). The main use of glyph codes is as the entries of display tables (see Display Tables). The following functions are used to manipulate glyph codes:
This function returns a glyph code representing char char with
face face. If face is omitted or nil, the glyph
uses the default face; in that case, the glyph code is an integer. If
face is non-nil, the glyph code is not necessarily an
integer object.
This function returns the character of glyph code glyph.
This function returns face of glyph code glyph, or nil if
glyph uses the default face.
You can set up a glyph table to change how glyph codes are
actually displayed on text terminals. This feature is semi-obsolete;
use glyphless-char-display instead (see Glyphless Character Display).
The value of this variable, if non-nil, is the current glyph
table. It takes effect only on character terminals; on graphical
displays, all glyphs are displayed literally. The glyph table should
be a vector whose gth element specifies how to display glyph
code g, where g is the glyph code for a glyph whose face
is unspecified. Each element should be one of the following:
nilDisplay this glyph literally.
Display this glyph by sending the specified string to the terminal.
Display the specified glyph code instead.
Any integer glyph code greater than or equal to the length of the glyph table is displayed literally.
Glyphless characters are characters which are displayed in a special way, e.g., as a box containing a hexadecimal code, instead of being displayed literally. These include characters which are explicitly defined to be glyphless, as well as characters for which there is no available font (on a graphical display), and characters which cannot be encoded by the terminal’s coding system (on a text terminal).
The glyphless-display-mode minor mode can be used to toggle
displaying glyphless characters in a convenient manner in the current
buffer. If this mode is enabled, all the glyphless characters are
displayed as boxes that display acronyms of their character names.
For more fine-grained (and global) control, this variable can be used. The value of this variable is a char-table which defines glyphless characters and how they are displayed. Each entry must be one of the following display methods:
nilDisplay the character in the usual way.
zero-widthDon’t display the character.
thin-spaceDisplay a thin space, 1-pixel wide on graphical displays, or 1-character wide on text terminals.
empty-boxDisplay an empty box.
hex-codeDisplay a box containing the Unicode codepoint of the character, in hexadecimal notation.
Display a box containing that string. The string should contain at most 6 ASCII characters. As an exception, if the string includes just one character, on text-mode terminals that character will be displayed without a box; this enables treating such “acronyms” as replacement characters for characters that cannot be displayed by the terminal.
(graphical . text)Display with graphical on graphical displays, and with text on text terminals. Both graphical and text must be one of the display methods described above.
The thin-space, empty-box, hex-code, and
ASCII string display methods are drawn with the
glyphless-char face. On text terminals, a box is emulated by
square brackets, ‘[]’.
The char-table has one extra slot, which determines how to display any
character that cannot be displayed with any available font, or cannot
be encoded by the terminal’s coding system. Its value should be one
of the above display methods, except zero-width.
If a character has a non-nil entry in an active display table,
the display table takes effect; in this case, Emacs does not consult
glyphless-char-display at all.
This user option provides a convenient way to set
glyphless-char-display for groups of similar characters. Do
not set its value directly from Lisp code; the value takes effect only
via a custom :set function (see Defining Customization Variables),
which updates glyphless-char-display.
Its value should be an alist of elements (group
. method), where group is a symbol specifying a group of
characters, and method is a symbol specifying how to display
them.
group should be one of the following:
c0-controlASCII control characters U+0000 to U+001F,
excluding the newline and tab characters (normally displayed as escape
sequences like ‘^A’; see How Text Is Displayed in The GNU Emacs Manual).
c1-controlNon-ASCII, non-printing characters U+0080 to
U+009F (normally displayed as octal escape sequences like
‘\230’).
format-controlCharacters of Unicode General Category [Cf], such as U+200E LEFT-TO-RIGHT MARK, but excluding characters that have graphic images, such as U+00AD SOFT HYPHEN.
bidi-controlThis is a subset of format-control, but only includes
characters that are related to bidirectional formatting control, like
U+2069 POP DIRECTIONAL ISOLATE and U+202A LEFT-TO-RIGHT
EMBEDDING. See Bidirectional Display.
Characters of Unicode General Category [Cf], such as U+200E LEFT-TO-RIGHT MARK, but excluding characters that have graphic images, such as U+00AD SOFT HYPHEN.
variation-selectorsUnicode VS-1 through VS-256 (U+FE00 through U+FE0F and U+E0100 through U+E01EF), which are used to select between different glyphs for the same codepoints (typically emojis).
no-fontCharacters for which there is no suitable font, or which cannot be encoded by the terminal’s coding system, or those for which the text-mode terminal has no glyphs.
The method symbol should be one of zero-width,
thin-space, empty-box, or hex-code. These have
the same meanings as in glyphless-char-display, above.
This section describes how to make Emacs ring the bell (or blink the screen) to attract the user’s attention. Be conservative about how often you do this; frequent bells can become irritating. Also be careful not to use just beeping when signaling an error is more appropriate (see Errors).
This function beeps, or flashes the screen (see visible-bell below).
It also terminates any keyboard macro currently executing unless
do-not-terminate is non-nil.
This is a synonym for ding.
This variable determines whether Emacs should flash the screen to
represent a bell. Non-nil means yes, nil means no.
This is effective on graphical displays, and on text terminals
provided the terminal’s Termcap entry defines the visible bell
capability (‘vb’).
If this is non-nil, it specifies how Emacs should ring the
bell. Its value should be a function of no arguments. If this is
non-nil, it takes precedence over the visible-bell
variable.
Emacs works with several window systems, most notably the X Window System. Both Emacs and X use the term “window”, but use it differently. An Emacs frame is a single window as far as X is concerned; the individual Emacs windows are not known to X at all.
This terminal-local variable tells Lisp programs what window system Emacs is using for displaying the frame. The possible values are
x ¶Emacs is displaying the frame using X.
w32Emacs is displaying the frame using native MS-Windows GUI.
nsEmacs is displaying the frame using the Nextstep interface (used on GNUstep and macOS).
pcEmacs is displaying the frame using MS-DOS direct screen writes.
haikuEmacs is displaying the frame using the Application Kit on Haiku.
pgtkEmacs is displaying the frame using pure GTK facilities.
androidEmacs is displaying the frame on Android.
nilEmacs is displaying the frame on a character-based terminal.
This variable holds the value of window-system used for the
first frame created by Emacs during startup. (When Emacs is invoked
as a daemon, it does not create any initial
frames, so initial-window-system is nil, except on
MS-Windows, where it is still w32. See daemon in The GNU Emacs Manual.)
This function returns a symbol whose name tells what window system is
used for displaying frame (which defaults to the currently
selected frame). The list of possible symbols it returns is the same
one documented for the variable window-system above.
Do not use window-system and
initial-window-system as predicates or boolean flag variables,
if you want to write code that works differently on text terminals and
graphic displays. That is because window-system is not a good
indicator of Emacs capabilities on a given display type. Instead, use
display-graphic-p or any of the other display-*-p
predicates described in Display Feature Testing.
Tooltips are special frames (see Frames) that are used to display helpful hints (a.k.a. “tips”) related to the current position of the mouse pointer. Emacs uses tooltips to display help strings about active portions of text (see Properties with Special Meanings) and about various UI elements, such as menu items (see Extended Menu Items) and tool-bar buttons (see Tool bars).
Tooltip Mode is a minor mode that enables display of tooltips. Turning off this mode causes the tooltips be displayed in the echo area. On text-mode (a.k.a. “TTY”) frames, tooltips are always displayed in the echo area.
When Emacs is built with the GTK+ toolkit or Haiku windowing support,
it by default displays tooltips using toolkit functions, and the
appearance of the tooltips is then controlled by the toolkit’s
settings. Toolkit-provided tooltips can be disabled by changing the
value of the variable use-system-tooltips to nil. The
rest of this subsection describes how to control non-toolkit tooltips,
which are presented by Emacs itself.
Tooltips are displayed in special frames called tooltip frames, which have their own frame parameters (see Frame Parameters). Unlike other frames, the default parameters for tooltip frames are stored in a special variable.
This customizable option holds the default frame parameters used for
displaying tooltips. Any font and color parameters are ignored, and the
corresponding attributes of the tooltip face are used instead.
If left or top parameters are included, they are used as
absolute frame-relative coordinates where the tooltip should be shown.
(Mouse-relative position of the tooltip can be customized using the
variables described in Tooltips in The GNU Emacs Manual.)
Note that the left and top parameters, if present,
override the values of mouse-relative offsets.
The tooltip face determines the appearance of text shown in
tooltips. It should generally use a variable-pitch font of size that
is preferably smaller than the default frame font.
This abnormal hook is a list of functions to call when Emacs needs to
display a tooltip. Each function is called with a single argument
event which is a copy of the last mouse movement event. If a
function on this list actually displays the tooltip, it should return
non-nil, and then the rest of the functions will not be
called. The default value of this variable is a single function
tooltip-help-tips.
If you write your own function to be put on the
tooltip-functions list, you may need to know the buffer of the
mouse event that triggered the tooltip display. The following
function provides that information.
This function returns the buffer over which event occurred.
Call it with the argument of the function from
tooltip-functions to obtain the buffer whose text triggered the
tooltip. Note that the event might occur not over a buffer (e.g.,
over the tool bar), in which case this function will return
nil.
Other aspects of tooltip display are controlled by several customizable settings; see Tooltips in The GNU Emacs Manual.
Emacs can display text written in scripts, such as Arabic, Farsi, and Hebrew, whose natural ordering for horizontal text display runs from right to left. Furthermore, segments of Latin script and digits embedded in right-to-left text are displayed left-to-right, while segments of right-to-left script embedded in left-to-right text (e.g., Arabic or Hebrew text in comments or strings in a program source file) are appropriately displayed right-to-left. We call such mixtures of left-to-right and right-to-left text bidirectional text. This section describes the facilities and options for editing and displaying bidirectional text.
Text is stored in Emacs buffers and strings in logical (or reading) order, i.e., the order in which a human would read each character. In right-to-left and bidirectional text, the order in which characters are displayed on the screen (called visual order) is not the same as logical order; the characters’ screen positions do not increase monotonically with string or buffer position. In performing this bidirectional reordering, Emacs follows the Unicode Bidirectional Algorithm (a.k.a. UBA), which is described in Annex #9 of the Unicode standard (https://www.unicode.org/reports/tr9/). Emacs provides a “Full Bidirectionality” class implementation of the UBA, consistent with the requirements of the Unicode Standard v9.0. Note, however, that the way Emacs displays continuation lines when text direction is opposite to the base paragraph direction deviates from the UBA, which requires performing line wrapping before reordering text for display.
If the value of this buffer-local variable is non-nil (the
default), Emacs performs bidirectional reordering for display. The
reordering affects buffer text, as well as display strings and overlay
strings from text and overlay properties in the buffer (see Overlay Properties, and see The display Property). If the value is
nil, Emacs does not perform bidirectional reordering in the
buffer.
The default value of bidi-display-reordering controls the
reordering of strings which are not directly supplied by a buffer,
including the text displayed in mode lines (see Mode Line Format)
and header lines (see Window Header Lines).
Emacs never reorders the text of a unibyte buffer, even if
bidi-display-reordering is non-nil in the buffer. This
is because unibyte buffers contain raw bytes, not characters, and thus
lack the directionality properties required for reordering.
Therefore, to test whether text in a buffer will be reordered for
display, it is not enough to test the value of
bidi-display-reordering alone. The correct test is this:
(if (and enable-multibyte-characters
bidi-display-reordering)
;; Buffer is being reordered for display
)
However, unibyte display and overlay strings are reordered if their parent buffer is reordered. This is because plain-ASCII strings are stored by Emacs as unibyte strings. If a unibyte display or overlay string includes non-ASCII characters, these characters are assumed to have left-to-right direction.
Text covered by display text properties, by overlays with
display properties whose value is a string, and by any other
properties that replace buffer text, is treated as a single unit when
it is reordered for display. That is, the entire chunk of text
covered by these properties is reordered together. Moreover, the
bidirectional properties of the characters in such a chunk of text are
ignored, and Emacs reorders them as if they were replaced with a
single character U+FFFC, known as the Object Replacement
Character. This means that placing a display property over a portion
of text may change the way that the surrounding text is reordered for
display. To prevent this unexpected effect, always place such
properties on text whose directionality is identical with text that
surrounds it.
Each paragraph of bidirectional text has a base direction, either right-to-left or left-to-right. Left-to-right paragraphs are displayed beginning at the left margin of the window, and are truncated or continued when the text reaches the right margin. Right-to-left paragraphs are displayed beginning at the right margin, and are continued or truncated at the left margin.
Where exactly paragraphs start and end, for the purpose of the Emacs
UBA implementation, is determined by the following two
buffer-local variables (note that paragraph-start and
paragraph-separate have no influence on this). By default both
of these variables are nil, and paragraphs are bounded by empty
lines, i.e., lines that consist entirely of zero or more whitespace
characters followed by a newline.
If non-nil, this variable’s value should be a regular
expression matching a line that starts or separates two paragraphs.
The regular expression is always matched after a newline, so it is
best to anchor it, i.e., begin it with a "^".
If non-nil, this variable’s value should be a regular
expression matching a line separates two paragraphs. The regular
expression is always matched after a newline, so it is best to anchor
it, i.e., begin it with a "^".
If you modify any of these two variables, you should normally modify
both, to make sure they describe paragraphs consistently. For
example, to have each new line start a new paragraph for
bidi-reordering purposes, set both variables to "^".
By default, Emacs determines the base direction of each paragraph by looking at the text at its beginning. The precise method of determining the base direction is specified by the UBA; in a nutshell, the first character in a paragraph that has an explicit directionality determines the base direction of the paragraph. However, sometimes a buffer may need to force a certain base direction for its paragraphs. For example, buffers containing program source code should force all paragraphs to be displayed left-to-right. You can use following variable to do this:
If the value of this buffer-local variable is the symbol
right-to-left or left-to-right, all paragraphs in the
buffer are assumed to have that specified direction. Any other value
is equivalent to nil (the default), which means to determine
the base direction of each paragraph from its contents.
Modes for program source code should set this to left-to-right.
Prog mode does this by default, so modes derived from Prog mode do not
need to set this explicitly (see Basic Major Modes).
This function returns the paragraph direction at point in the named
buffer. The returned value is a symbol, either
left-to-right or right-to-left. If buffer is
omitted or nil, it defaults to the current buffer. If the
buffer-local value of the variable bidi-paragraph-direction is
non-nil, the returned value will be identical to that value;
otherwise, the returned value reflects the paragraph direction
determined dynamically by Emacs. For buffers whose value of
bidi-display-reordering is nil as well as unibyte
buffers, this function always returns left-to-right.
Sometimes there’s a need to move point in strict visual order, either to the left or to the right of its current screen position. Emacs provides a primitive to do that.
This function moves point of the currently selected window to the buffer position that appears immediately to the right or to the left of point on the screen. If direction is positive, point will move one screen position to the right, otherwise it will move one screen position to the left. Note that, depending on the surrounding bidirectional context, this could potentially move point many buffer positions away. If invoked at the end of a screen line, the function moves point to the rightmost or leftmost screen position of the next or previous screen line, as appropriate for the value of direction.
The function returns the new buffer position as its value.
Bidirectional reordering can have surprising and unpleasant effects when two strings with bidirectional content are juxtaposed in a buffer, or otherwise programmatically concatenated into a string of text. A typical problematic case is when a buffer consists of sequences of text fields separated by whitespace or punctuation characters, like Buffer Menu mode or Rmail Summary Mode. Because the punctuation characters used as separators have weak directionality, they take on the directionality of surrounding text. As result, a numeric field that follows a field with bidirectional content can be displayed to the left of the preceding field, messing up the expected layout. There are several ways to avoid this problem:
bidi-string-mark-left-to-right, described below, comes
in handy for this purpose. (In a right-to-left paragraph, use
U+200F RIGHT-TO-LEFT MARK, or RLM, instead.) This
is one of the solutions recommended by the UBA.
display property or overlay with a
property value of the form (space . PROPS) (see Specified Spaces). Emacs treats this display specification as a paragraph
separator, and reorders the text on either side separately.
This function returns its argument string, possibly modified,
such that the result can be safely concatenated with another string,
or juxtaposed with another string in a buffer, without disrupting the
relative layout of this string and the next one on display. If the
string returned by this function is displayed as part of a
left-to-right paragraph, it will always appear on display to the left
of the text that follows it. The function works by examining the
characters of its argument, and if any of those characters could cause
reordering on display, the function appends the LRM
character to the string. The appended LRM character is made
invisible by giving it an invisible text property of t
(see Invisible Text).
The reordering algorithm uses the bidirectional properties of the
characters stored as their bidi-class property
(see Character Properties). Lisp programs can change these
properties by calling the put-char-code-property function.
However, doing this requires a thorough understanding of the
UBA, and is therefore not recommended. Any changes to the
bidirectional properties of a character have global effect: they
affect all Emacs frames and windows.
Similarly, the mirroring property is used to display the
appropriate mirrored character in the reordered text. Lisp programs
can affect the mirrored display by changing this property. Again, any
such changes affect all of Emacs display.
The bidirectional properties of characters can be overridden by inserting into the text special directional control characters, LEFT-TO-RIGHT OVERRIDE (LRO) and RIGHT-TO-LEFT OVERRIDE (RLO). Any characters between a RLO and the following newline or POP DIRECTIONAL FORMATTING (PDF) control character, whichever comes first, will be displayed as if they were strong right-to-left characters, i.e. they will be reversed on display. Similarly, any characters between LRO and PDF or newline will display as if they were strong left-to-right, and will not be reversed even if they are strong right-to-left characters.
These overrides are useful when you want to make some text unaffected by the reordering algorithm, and instead directly control the display order. But they can also be used for malicious purposes, known as phishing. Specifically, a URL on a Web page or a link in an email message can be manipulated to make its visual appearance unrecognizable, or similar to some popular benign location, while the real location, interpreted by a browser in the logical order, is very different.
Emacs provides a primitive that applications can use to detect instances of text whose bidirectional properties were overridden so as to make a left-to-right character display as if it were a right-to-left character, or vice versa.
This function looks at the text of the specified object between
positions from (inclusive) and to (exclusive), and returns
the first position where it finds a strong left-to-right character
whose directional properties were forced to display the character as
right-to-left, or for a strong right-to-left character that was forced
to display as left-to-right. If it finds no such characters in the
specified region of text, it returns nil.
The optional argument object specifies which text to search, and
defaults to the current buffer. If object is non-nil, it
can be some other buffer, or it can be a string or a window. If it is
a string, the function searches that string. If it is a window, the
function searches the buffer displayed in that window. If a buffer
whose text you want to examine is displayed in some window, we
recommend to specify it by that window, rather than pass the buffer to
the function. This is because telling the function about the window
allows it to correctly account for window-specific overlays, which
might change the result of the function if some text in the buffer is
covered by overlays.
When text that includes mixed right-to-left and left-to-right characters and bidirectional controls is copied into a different location, it can change its visual appearance, and also can affect the visual appearance of the surrounding text at destination. This is because reordering of bidirectional text specified by the UBA has non-trivial context-dependent effects both on the copied text and on the text at copy destination that will surround it.
Sometimes, a Lisp program may need to preserve the exact visual appearance of the copied text at destination, and of the text that surrounds the copy. Lisp programs can use the following function to achieve that effect.
This function works similar to buffer-substring (see Examining Buffer Contents), but it prepends and appends to the copied text bidi
directional control characters necessary to preserve the visual
appearance of the text when it is inserted at another place. Optional
argument no-properties, if non-nil, means remove the text
properties from the copy of the text.
For backward compatibility, you can also use a string to specify a face name; that is equivalent to a Lisp symbol with the same name.
In this context, the term font has nothing to do with Font Lock (see Font Lock Mode).
On MS-Windows, this requires w32-use-native-image-API to be set
non-nil.
In typography an em is a distance equivalent to the height of the type. For example when using 12 point type 1 em is equal to 12 points. Its use ensures distances and type remain proportional.