2 @c This is part of the GNU Emacs Lisp Reference Manual.
3 @c Copyright (C) 1990-1995, 1998-1999, 2001-2012
4 @c Free Software Foundation, Inc.
5 @c See the file elisp.texi for copying conditions.
6 @node System Interface, Packaging, Display, Top
7 @chapter Operating System Interface
9 This chapter is about starting and getting out of Emacs, access to
10 values in the operating system environment, and terminal input, output.
12 @xref{Building Emacs}, for related information. @xref{Display}, for
13 additional operating system status information pertaining to the
14 terminal and the screen.
17 * Starting Up:: Customizing Emacs startup processing.
18 * Getting Out:: How exiting works (permanent or temporary).
19 * System Environment:: Distinguish the name and kind of system.
20 * User Identification:: Finding the name and user id of the user.
21 * Time of Day:: Getting the current time.
22 * Time Conversion:: Converting a time from numeric form to
23 calendrical data and vice versa.
24 * Time Parsing:: Converting a time from numeric form to text
26 * Processor Run Time:: Getting the run time used by Emacs.
27 * Time Calculations:: Adding, subtracting, comparing times, etc.
28 * Timers:: Setting a timer to call a function at a certain time.
29 * Idle Timers:: Setting a timer to call a function when Emacs has
30 been idle for a certain length of time.
31 * Terminal Input:: Accessing and recording terminal input.
32 * Terminal Output:: Controlling and recording terminal output.
33 * Sound Output:: Playing sounds on the computer's speaker.
34 * X11 Keysyms:: Operating on key symbols for X Windows.
35 * Batch Mode:: Running Emacs without terminal interaction.
36 * Session Management:: Saving and restoring state with X Session Management.
37 * Notifications:: Desktop notifications.
38 * Dynamic Libraries:: On-demand loading of support libraries.
42 @section Starting Up Emacs
44 This section describes what Emacs does when it is started, and how you
45 can customize these actions.
48 * Startup Summary:: Sequence of actions Emacs performs at startup.
49 * Init File:: Details on reading the init file.
50 * Terminal-Specific:: How the terminal-specific Lisp file is read.
51 * Command-Line Arguments:: How command-line arguments are processed,
52 and how you can customize them.
56 @subsection Summary: Sequence of Actions at Startup
57 @cindex initialization of Emacs
58 @cindex startup of Emacs
59 @cindex @file{startup.el}
61 When Emacs is started up, it performs the following operations
62 (see @code{normal-top-level} in @file{startup.el}):
66 It adds subdirectories to @code{load-path}, by running the file named
67 @file{subdirs.el} in each directory in the list. Normally, this file
68 adds the directory's subdirectories to the list, and those are scanned
69 in their turn. The files @file{subdirs.el} are normally generated
70 automatically when Emacs is installed.
73 It registers input methods by loading any @file{leim-list.el} file
74 found in the @code{load-path}.
76 @c It removes PWD from the environment if it is not accurate.
77 @c It abbreviates default-directory.
79 @c Now normal-top-level calls command-line.
81 @vindex before-init-time
83 It sets the variable @code{before-init-time} to the value of
84 @code{current-time} (@pxref{Time of Day}). It also sets
85 @code{after-init-time} to @code{nil}, which signals to Lisp programs
86 that Emacs is being initialized.
88 @c set-locale-environment
90 It sets the language environment and the terminal coding system,
91 if requested by environment variables such as @env{LANG}.
94 It does some basic parsing of the command-line arguments.
96 @vindex initial-window-system@r{, and startup}
97 @vindex window-system-initialization-alist
99 If not running in batch mode, it initializes the window system that
100 the variable @code{initial-window-system} specifies (@pxref{Window
101 Systems, initial-window-system}). The initialization function for
102 each supported window system is specified by
103 @code{window-system-initialization-alist}. If the value
104 of @code{initial-window-system} is @var{windowsystem}, then the
105 appropriate initialization function is defined in the file
106 @file{term/@var{windowsystem}-win.el}. This file should have been
107 compiled into the Emacs executable when it was built.
110 It runs the normal hook @code{before-init-hook}.
113 If appropriate, it creates a graphical frame. This is not done if the
114 options @samp{--batch} or @samp{--daemon} were specified.
117 It initializes the initial frame's faces, and sets up the menu bar
118 and tool bar if needed. If graphical frames are supported, it sets up
119 the tool bar even if the current frame is not a graphical one, since a
120 graphical frame may be created later on.
123 It use @code{custom-reevaluate-setting} to re-initialize the members
124 of the list @code{custom-delayed-init-variables}. These are any
125 pre-loaded user options whose default value depends on the run-time,
126 rather than build-time, context.
127 @xref{Building Emacs, custom-initialize-delay}.
130 @c It registers the colors available for tty frames.
133 It loads the library @file{site-start}, if it exists. This is not
134 done if the options @samp{-Q} or @samp{--no-site-file} were specified.
135 @cindex @file{site-start.el}
138 It loads your init file (@pxref{Init File}). This is not done if the
139 options @samp{-q}, @samp{-Q}, or @samp{--batch} were specified. If
140 the @samp{-u} option was specified, Emacs looks for the init file in
141 that user's home directory instead.
144 It loads the library @file{default}, if it exists. This is not done
145 if @code{inhibit-default-init} is non-@code{nil}, nor if the options
146 @samp{-q}, @samp{-Q}, or @samp{--batch} were specified.
147 @cindex @file{default.el}
150 It loads your abbrevs from the file specified by
151 @code{abbrev-file-name}, if that file exists and can be read
152 (@pxref{Abbrev Files, abbrev-file-name}). This is not done if the
153 option @samp{--batch} was specified.
156 If @code{package-enable-at-startup} is non-@code{nil}, it calls the
157 function @code{package-initialize} to activate any optional Emacs Lisp
158 package that has been installed. @xref{Packaging Basics}.
160 @vindex after-init-time
162 It sets the variable @code{after-init-time} to the value of
163 @code{current-time}. This variable was set to @code{nil} earlier;
164 setting it to the current time signals that the initialization phase
165 is over, and, together with @code{before-init-time}, provides the
166 measurement of how long it took.
169 It runs the normal hook @code{after-init-hook}.
172 If the buffer @file{*scratch*} exists and is still in Fundamental mode
173 (as it should be by default), it sets its major mode according to
174 @code{initial-major-mode}.
177 If started on a text terminal, it loads the terminal-specific
178 Lisp library, which is specified by the variable
179 @code{term-file-prefix} (@pxref{Terminal-Specific}). This is not done
180 in @code{--batch} mode, nor if @code{term-file-prefix} is @code{nil}.
182 @c Now command-line calls command-line-1.
185 It displays the initial echo area message, unless you have suppressed
186 that with @code{inhibit-startup-echo-area-message}.
189 It processes any command-line options that were not handled earlier.
191 @c This next one is back in command-line, but the remaining bits of
192 @c command-line-1 are not done if noninteractive.
194 It now exits if the option @code{--batch} was specified.
197 If @code{initial-buffer-choice} is a string, it visits the file with
198 that name. If the @file{*scratch*} buffer exists and is
199 empty, it inserts @code{initial-scratch-message} into that buffer.
201 @c To make things nice and confusing, the next three items can be
202 @c called from two places. If displaying a startup screen, they are
203 @c called in command-line-1 before the startup screen is shown.
204 @c inhibit-startup-hooks is then set and window-setup-hook set to nil.
205 @c If not displaying a startup screen, they are are called in
207 @c FIXME? So it seems they can be called before or after the
208 @c daemon/session restore step?
211 It runs @code{emacs-startup-hook} and then @code{term-setup-hook}.
214 It calls @code{frame-notice-user-settings}, which modifies the
215 parameters of the selected frame according to whatever the init files
219 It runs @code{window-setup-hook}. @xref{Window Systems}.
222 It displays the @dfn{startup screen}, which is a special buffer that
223 contains information about copyleft and basic Emacs usage. This is
224 not done if @code{inhibit-startup-screen} or @code{initial-buffer-choice}
225 are non-@code{nil}, or if the @samp{--no-splash} or @samp{-Q} command-line
226 options were specified.
228 @c End of command-line-1.
230 @c Back to command-line from command-line-1.
232 @c This is the point at which we actually exit in batch mode, but the
233 @c last few bits of command-line-1 are not done in batch mode.
236 If the option @code{--daemon} was specified, it calls
237 @code{server-start} and detaches from the controlling terminal.
238 @xref{Emacs Server,,, emacs, The GNU Emacs Manual}.
241 If started by the X session manager, it calls
242 @code{emacs-session-restore} passing it as argument the ID of the
243 previous session. @xref{Session Management}.
245 @c End of command-line.
247 @c Back to normal-top-level from command-line.
252 The following options affect some aspects of the startup sequence.
254 @defopt inhibit-startup-screen
255 This variable, if non-@code{nil}, inhibits the startup screen. In
256 that case, Emacs typically displays the @file{*scratch*} buffer; but
257 see @code{initial-buffer-choice}, below.
259 Do not set this variable in the init file of a new user, or in a way
260 that affects more than one user, as that would prevent new users from
261 receiving information about copyleft and basic Emacs usage.
263 @vindex inhibit-startup-message
264 @vindex inhibit-splash-screen
265 @code{inhibit-startup-message} and @code{inhibit-splash-screen} are
266 aliases for this variable.
269 @defopt initial-buffer-choice
270 If non-@code{nil}, this variable is a string that specifies a file or
271 directory for Emacs to display after starting up, instead of the
274 @c I do not think this should be mentioned. AFAICS it is just a dodge
275 @c around inhibit-startup-screen not being settable on a site-wide basis.
276 If its value is @code{t}, Emacs displays the @file{*scratch*} buffer.
280 @defopt inhibit-startup-echo-area-message
281 This variable controls the display of the startup echo area message.
282 You can suppress the startup echo area message by adding text with this
283 form to your init file:
286 (setq inhibit-startup-echo-area-message
287 "@var{your-login-name}")
290 Emacs explicitly checks for an expression as shown above in your init
291 file; your login name must appear in the expression as a Lisp string
292 constant. You can also use the Customize interface. Other methods of
293 setting @code{inhibit-startup-echo-area-message} to the same value do
294 not inhibit the startup message. This way, you can easily inhibit the
295 message for yourself if you wish, but thoughtless copying of your init
296 file will not inhibit the message for someone else.
299 @defopt initial-scratch-message
300 This variable, if non-@code{nil}, should be a string, which is
301 inserted into the @file{*scratch*} buffer when Emacs starts up. If it
302 is @code{nil}, the @file{*scratch*} buffer is empty.
306 The following command-line options affect some aspects of the startup
307 sequence. @xref{Initial Options,,, emacs, The GNU Emacs Manual}.
311 Do not display a splash screen.
314 Run without an interactive terminal. @xref{Batch Mode}.
317 Do not initialize any display; just start a server in the background.
321 Do not load either the init file, or the @file{default} library.
324 Do not load the @file{site-start} library.
328 Equivalent to @samp{-q --no-site-file --no-splash}.
329 @c and --no-site-lisp, but let's not mention that here.
334 @subsection The Init File
336 @cindex @file{.emacs}
337 @cindex @file{init.el}
339 When you start Emacs, it normally attempts to load your @dfn{init
340 file}. This is either a file named @file{.emacs} or @file{.emacs.el}
341 in your home directory, or a file named @file{init.el} in a
342 subdirectory named @file{.emacs.d} in your home directory.
344 Whichever place you use, you can also compile the file (@pxref{Byte
345 Compilation}); then the actual file loaded will be @file{.emacs.elc}
349 The command-line switches @samp{-q}, @samp{-Q}, and @samp{-u}
350 control whether and where to find the init file; @samp{-q} (and the
351 stronger @samp{-Q}) says not to load an init file, while @samp{-u
352 @var{user}} says to load @var{user}'s init file instead of yours.
353 @xref{Entering Emacs,,, emacs, The GNU Emacs Manual}. If neither
354 option is specified, Emacs uses the @env{LOGNAME} environment
355 variable, or the @env{USER} (most systems) or @env{USERNAME} (MS
356 systems) variable, to find your home directory and thus your init
357 file; this way, even if you have su'd, Emacs still loads your own init
358 file. If those environment variables are absent, though, Emacs uses
359 your user-id to find your home directory.
361 @cindex default init file
362 An Emacs installation may have a @dfn{default init file}, which is a
363 Lisp library named @file{default.el}. Emacs finds this file through
364 the standard search path for libraries (@pxref{How Programs Do
365 Loading}). The Emacs distribution does not come with this file; it is
366 intended for local customizations. If the default init file exists,
367 it is loaded whenever you start Emacs. But your own personal init
368 file, if any, is loaded first; if it sets @code{inhibit-default-init}
369 to a non-@code{nil} value, then Emacs does not subsequently load the
370 @file{default.el} file. In batch mode, or if you specify @samp{-q}
371 (or @samp{-Q}), Emacs loads neither your personal init file nor
372 the default init file.
374 Another file for site-customization is @file{site-start.el}. Emacs
375 loads this @emph{before} the user's init file. You can inhibit the
376 loading of this file with the option @samp{--no-site-file}.
378 @defopt site-run-file
379 This variable specifies the site-customization file to load before the
380 user's init file. Its normal value is @code{"site-start"}. The only
381 way you can change it with real effect is to do so before dumping
383 @c So why even mention it here. I imagine it is almost never changed.
386 @xref{Init Examples,, Init File Examples, emacs, The GNU Emacs Manual}, for
387 examples of how to make various commonly desired customizations in your
390 @defopt inhibit-default-init
391 If this variable is non-@code{nil}, it prevents Emacs from loading the
392 default initialization library file. The default value is @code{nil}.
395 @defvar before-init-hook
396 This normal hook is run, once, just before loading all the init files
397 (@file{site-start.el}, your init file, and @file{default.el}).
398 (The only way to change it with real effect is before dumping Emacs.)
401 @defvar after-init-hook
402 This normal hook is run, once, just after loading all the init files
403 (@file{site-start.el}, your init file, and @file{default.el}),
404 before loading the terminal-specific library (if started on a text
405 terminal) and processing the command-line action arguments.
408 @defvar emacs-startup-hook
409 This normal hook is run, once, just after handling the command line
410 arguments, just before @code{term-setup-hook}. In batch mode, Emacs
411 does not run either of these hooks.
414 @defvar user-init-file
415 This variable holds the absolute file name of the user's init file. If the
416 actual init file loaded is a compiled file, such as @file{.emacs.elc},
417 the value refers to the corresponding source file.
420 @defvar user-emacs-directory
421 This variable holds the name of the @file{.emacs.d} directory. It is
422 @file{~/.emacs.d} on all platforms but MS-DOS.
425 @node Terminal-Specific
426 @subsection Terminal-Specific Initialization
427 @cindex terminal-specific initialization
429 Each terminal type can have its own Lisp library that Emacs loads when
430 run on that type of terminal. The library's name is constructed by
431 concatenating the value of the variable @code{term-file-prefix} and the
432 terminal type (specified by the environment variable @env{TERM}).
433 Normally, @code{term-file-prefix} has the value
434 @code{"term/"}; changing this is not recommended. Emacs finds the file
435 in the normal manner, by searching the @code{load-path} directories, and
436 trying the @samp{.elc} and @samp{.el} suffixes.
439 The usual role of a terminal-specific library is to enable special
440 keys to send sequences that Emacs can recognize. It may also need to
441 set or add to @code{input-decode-map} if the Termcap or Terminfo entry
442 does not specify all the terminal's function keys. @xref{Terminal
445 When the name of the terminal type contains a hyphen or underscore, and no library
446 is found whose name is identical to the terminal's name, Emacs strips
447 from the terminal's name the last hyphen or underscore and everything that follows
448 it, and tries again. This process is repeated until Emacs finds a
449 matching library, or until there are no more hyphens or underscores in the name
450 (i.e.@: there is no terminal-specific library). For example, if the
451 terminal name is @samp{xterm-256color} and there is no
452 @file{term/xterm-256color.el} library, Emacs tries to load
453 @file{term/xterm.el}. If necessary, the terminal library can evaluate
454 @code{(getenv "TERM")} to find the full name of the terminal type.
456 Your init file can prevent the loading of the
457 terminal-specific library by setting the variable
458 @code{term-file-prefix} to @code{nil}. This feature is useful when
459 experimenting with your own peculiar customizations.
461 You can also arrange to override some of the actions of the
462 terminal-specific library by setting the variable
463 @code{term-setup-hook}. This is a normal hook that Emacs runs
464 at the end of its initialization, after loading both
465 your init file and any terminal-specific libraries. You could
466 use this hook to define initializations for terminals that do not
467 have their own libraries. @xref{Hooks}.
469 @defvar term-file-prefix
470 @cindex @env{TERM} environment variable
471 If the value of this variable is non-@code{nil}, Emacs loads a
472 terminal-specific initialization file as follows:
475 (load (concat term-file-prefix (getenv "TERM")))
479 You may set the @code{term-file-prefix} variable to @code{nil} in your
480 init file if you do not wish to load the
481 terminal-initialization file.
483 On MS-DOS, Emacs sets the @env{TERM} environment variable to @samp{internal}.
486 @defvar term-setup-hook
487 This variable is a normal hook that Emacs runs after loading your
488 init file, the default initialization file (if any) and the
489 terminal-specific Lisp file.
491 You can use @code{term-setup-hook} to override the definitions made by a
492 terminal-specific file.
494 For a related feature, @pxref{Window Systems, window-setup-hook}.
497 @node Command-Line Arguments
498 @subsection Command-Line Arguments
499 @cindex command-line arguments
501 You can use command-line arguments to request various actions when
502 you start Emacs. Note that the recommended way of using Emacs is to
503 start it just once, after logging in, and then do all editing in the same
504 Emacs session (@pxref{Entering Emacs,,, emacs, The GNU Emacs Manual}).
505 For this reason, you might not use command-line arguments very often;
506 nonetheless, they can be useful when invoking Emacs from session
507 scripts or debugging Emacs. This section describes how Emacs
508 processes command-line arguments.
511 This function parses the command line that Emacs was called with,
512 processes it, and (amongst other things) loads the user's init file and
513 displays the startup messages.
516 @defvar command-line-processed
517 The value of this variable is @code{t} once the command line has been
520 If you redump Emacs by calling @code{dump-emacs}, you may wish to set
521 this variable to @code{nil} first in order to cause the new dumped Emacs
522 to process its new command-line arguments.
525 @defvar command-switch-alist
526 @cindex switches on command line
527 @cindex options on command line
528 @cindex command-line options
529 This variable is an alist of user-defined command-line options and
530 associated handler functions. By default it is empty, but you can
531 add elements if you wish.
533 A @dfn{command-line option} is an argument on the command line, which
540 The elements of the @code{command-switch-alist} look like this:
543 (@var{option} . @var{handler-function})
546 The @sc{car}, @var{option}, is a string, the name of a command-line
547 option (not including the initial hyphen). The @var{handler-function}
548 is called to handle @var{option}, and receives the option name as its
551 In some cases, the option is followed in the command line by an
552 argument. In these cases, the @var{handler-function} can find all the
553 remaining command-line arguments in the variable
554 @code{command-line-args-left}. (The entire list of command-line
555 arguments is in @code{command-line-args}.)
557 The command-line arguments are parsed by the @code{command-line-1}
558 function in the @file{startup.el} file. See also @ref{Emacs
559 Invocation, , Command Line Arguments for Emacs Invocation, emacs, The
563 @defvar command-line-args
564 The value of this variable is the list of command-line arguments passed
568 @defvar command-line-args-left
570 The value of this variable is the list of command-line arguments that
571 have not yet been processed.
572 @c Don't mention this, since it is a "bad name for a dynamically bound variable"
573 @c @code{argv} is an alias for this.
576 @defvar command-line-functions
577 This variable's value is a list of functions for handling an
578 unrecognized command-line argument. Each time the next argument to be
579 processed has no special meaning, the functions in this list are called,
580 in order of appearance, until one of them returns a non-@code{nil}
583 These functions are called with no arguments. They can access the
584 command-line argument under consideration through the variable
585 @code{argi}, which is bound temporarily at this point. The remaining
586 arguments (not including the current one) are in the variable
587 @code{command-line-args-left}.
589 When a function recognizes and processes the argument in @code{argi}, it
590 should return a non-@code{nil} value to say it has dealt with that
591 argument. If it has also dealt with some of the following arguments, it
592 can indicate that by deleting them from @code{command-line-args-left}.
594 If all of these functions return @code{nil}, then the argument is treated
595 as a file name to visit.
599 @section Getting Out of Emacs
600 @cindex exiting Emacs
602 There are two ways to get out of Emacs: you can kill the Emacs job,
603 which exits permanently, or you can suspend it, which permits you to
604 reenter the Emacs process later. (In a graphical environment, you can
605 of course simply switch to another application without doing anything
606 special to Emacs, then switch back to Emacs when you want.)
609 * Killing Emacs:: Exiting Emacs irreversibly.
610 * Suspending Emacs:: Exiting Emacs reversibly.
614 @comment node-name, next, previous, up
615 @subsection Killing Emacs
616 @cindex killing Emacs
618 Killing Emacs means ending the execution of the Emacs process.
619 If you started Emacs from a terminal, the parent process normally
620 resumes control. The low-level primitive for killing Emacs is
623 @deffn Command kill-emacs &optional exit-data
624 This command calls the hook @code{kill-emacs-hook}, then exits the
625 Emacs process and kills it.
627 If @var{exit-data} is an integer, that is used as the exit status of
628 the Emacs process. (This is useful primarily in batch operation; see
631 If @var{exit-data} is a string, its contents are stuffed into the
632 terminal input buffer so that the shell (or whatever program next reads
633 input) can read them.
639 @cindex operating system signal
640 The @code{kill-emacs} function is normally called via the
641 higher-level command @kbd{C-x C-c}
642 (@code{save-buffers-kill-terminal}). @xref{Exiting,,, emacs, The GNU
643 Emacs Manual}. It is also called automatically if Emacs receives a
644 @code{SIGTERM} or @code{SIGHUP} operating system signal (e.g. when the
645 controlling terminal is disconnected), or if it receives a
646 @code{SIGINT} signal while running in batch mode (@pxref{Batch Mode}).
648 @defvar kill-emacs-hook
649 This normal hook is run by @code{kill-emacs}, before it kills Emacs.
651 Because @code{kill-emacs} can be called in situations where user
652 interaction is impossible (e.g. when the terminal is disconnected),
653 functions on this hook should not attempt to interact with the user.
654 If you want to interact with the user when Emacs is shutting down, use
655 @code{kill-emacs-query-functions}, described below.
658 When Emacs is killed, all the information in the Emacs process,
659 aside from files that have been saved, is lost. Because killing Emacs
660 inadvertently can lose a lot of work, the
661 @code{save-buffers-kill-terminal} command queries for confirmation if
662 you have buffers that need saving or subprocesses that are running.
663 It also runs the abnormal hook @code{kill-emacs-query-functions}:
665 @defvar kill-emacs-query-functions
666 When @code{save-buffers-kill-terminal} is killing Emacs, it calls the
667 functions in this hook, after asking the standard questions and before
668 calling @code{kill-emacs}. The functions are called in order of
669 appearance, with no arguments. Each function can ask for additional
670 confirmation from the user. If any of them returns @code{nil},
671 @code{save-buffers-kill-emacs} does not kill Emacs, and does not run
672 the remaining functions in this hook. Calling @code{kill-emacs}
673 directly does not run this hook.
676 @node Suspending Emacs
677 @subsection Suspending Emacs
678 @cindex suspending Emacs
680 On text terminals, it is possible to @dfn{suspend Emacs}, which
681 means stopping Emacs temporarily and returning control to its superior
682 process, which is usually the shell. This allows you to resume
683 editing later in the same Emacs process, with the same buffers, the
684 same kill ring, the same undo history, and so on. To resume Emacs,
685 use the appropriate command in the parent shell---most likely
688 @cindex controlling terminal
689 Suspending works only on a terminal device from which the Emacs
690 session was started. We call that device the @dfn{controlling
691 terminal} of the session. Suspending is not allowed if the
692 controlling terminal is a graphical terminal. Suspending is usually
693 not relevant in graphical environments, since you can simply switch to
694 another application without doing anything special to Emacs.
696 @c FIXME? Are there any systems Emacs still supports that do not
699 Some operating systems (those without @code{SIGTSTP}, or MS-DOS) do
700 not support suspension of jobs; on these systems, ``suspension''
701 actually creates a new shell temporarily as a subprocess of Emacs.
702 Then you would exit the shell to return to Emacs.
704 @deffn Command suspend-emacs &optional string
705 This function stops Emacs and returns control to the superior process.
706 If and when the superior process resumes Emacs, @code{suspend-emacs}
707 returns @code{nil} to its caller in Lisp.
709 This function works only on the controlling terminal of the Emacs
710 session; to relinquish control of other tty devices, use
711 @code{suspend-tty} (see below). If the Emacs session uses more than
712 one terminal, you must delete the frames on all the other terminals
713 before suspending Emacs, or this function signals an error.
714 @xref{Multiple Terminals}.
716 If @var{string} is non-@code{nil}, its characters are sent to Emacs's
717 superior shell, to be read as terminal input.
718 @c FIXME? It seems to me that shell does echo STRING.
719 The characters in @var{string} are not echoed by the superior shell;
720 only the results appear.
722 Before suspending, @code{suspend-emacs} runs the normal hook
723 @code{suspend-hook}. After the user resumes Emacs,
724 @code{suspend-emacs} runs the normal hook @code{suspend-resume-hook}.
727 The next redisplay after resumption will redraw the entire screen,
728 unless the variable @code{no-redraw-on-reenter} is non-@code{nil}.
729 @xref{Refresh Screen}.
731 Here is an example of how you could use these hooks:
735 (add-hook 'suspend-hook
736 (lambda () (or (y-or-n-p "Really suspend? ")
737 (error "Suspend canceled"))))
739 (add-hook 'suspend-resume-hook (lambda () (message "Resumed!")
742 @c The sit-for prevents the ``nil'' that suspend-emacs returns
743 @c hiding the message.
745 Here is what you would see upon evaluating @code{(suspend-emacs "pwd")}:
749 ---------- Buffer: Minibuffer ----------
750 Really suspend? @kbd{y}
751 ---------- Buffer: Minibuffer ----------
755 ---------- Parent Shell ----------
761 ---------- Echo Area ----------
766 @c FIXME? AFAICS, it is echoed.
767 Note that @samp{pwd} is not echoed after Emacs is suspended. But it
768 is read and executed by the shell.
772 This variable is a normal hook that Emacs runs before suspending.
775 @defvar suspend-resume-hook
776 This variable is a normal hook that Emacs runs on resuming
780 @defun suspend-tty &optional tty
781 If @var{tty} specifies a terminal device used by Emacs, this function
782 relinquishes the device and restores it to its prior state. Frames
783 that used the device continue to exist, but are not updated and Emacs
784 doesn't read input from them. @var{tty} can be a terminal object, a
785 frame (meaning the terminal for that frame), or @code{nil} (meaning
786 the terminal for the selected frame). @xref{Multiple Terminals}.
788 If @var{tty} is already suspended, this function does nothing.
790 @vindex suspend-tty-functions
791 This function runs the hook @code{suspend-tty-functions}, passing the
792 terminal object as an argument to each function.
795 @defun resume-tty &optional tty
796 This function resumes the previously suspended terminal device
797 @var{tty}; where @var{tty} has the same possible values as it does
798 for @code{suspend-tty}.
800 @vindex resume-tty-functions
801 This function reopens the terminal device, re-initializes it, and
802 redraws it with that terminal's selected frame. It then runs the
803 hook @code{resume-tty-functions}, passing the terminal object as an
804 argument to each function.
806 If the same device is already used by another Emacs terminal, this
807 function signals an error. If @var{tty} is not suspended, this
808 function does nothing.
811 @defun controlling-tty-p &optional tty
812 This function returns non-@code{nil} if @var{tty} is the
813 controlling terminal of the Emacs session; @var{tty} can be a
814 terminal object, a frame (meaning the terminal for that frame), or
815 @code{nil} (meaning the terminal for the selected frame).
818 @deffn Command suspend-frame
819 This command @dfn{suspends} a frame. For GUI frames, it calls
820 @code{iconify-frame} (@pxref{Visibility of Frames}); for frames on
821 text terminals, it calls either @code{suspend-emacs} or
822 @code{suspend-tty}, depending on whether the frame is displayed on the
823 controlling terminal device or not.
826 @node System Environment
827 @section Operating System Environment
828 @cindex operating system environment
830 Emacs provides access to variables in the operating system environment
831 through various functions. These variables include the name of the
832 system, the user's @acronym{UID}, and so on.
834 @defvar system-configuration
835 This variable holds the standard GNU configuration name for the
836 hardware/software configuration of your system, as a string. For
837 example, a typical value for a 64-bit GNU/Linux system is
838 @samp{"x86_64-unknown-linux-gnu"}.
841 @cindex system type and name
843 The value of this variable is a symbol indicating the type of operating
844 system Emacs is running on. The possible values are:
851 Berkeley BSD and its variants.
854 Cygwin, a Posix layer on top of MS-Windows.
860 The GNU system (using the GNU kernel, which consists of the HURD and Mach).
863 A GNU/Linux system---that is, a variant GNU system, using the Linux
864 kernel. (These systems are the ones people often call ``Linux'', but
865 actually Linux is just the kernel, not the whole system.)
868 A GNU (glibc-based) system with a FreeBSD kernel.
871 Hewlett-Packard HPUX operating system.
874 Silicon Graphics Irix system.
877 Microsoft's DOS. Emacs compiled with DJGPP for MS-DOS binds
878 @code{system-type} to @code{ms-dos} even when you run it on MS-Windows.
884 Microsoft Windows NT, 9X and later. The value of @code{system-type}
885 is always @code{windows-nt}, e.g. even on Windows 7.
889 We do not wish to add new symbols to make finer distinctions unless it
890 is absolutely necessary! In fact, we hope to eliminate some of these
891 alternatives in the future. If you need to make a finer distinction
892 than @code{system-type} allows for, you can test
893 @code{system-configuration}, e.g. against a regexp.
897 This function returns the name of the machine you are running on, as a
901 The symbol @code{system-name} is a variable as well as a function. In
902 fact, the function returns whatever value the variable
903 @code{system-name} currently holds. Thus, you can set the variable
904 @code{system-name} in case Emacs is confused about the name of your
905 system. The variable is also useful for constructing frame titles
906 (@pxref{Frame Titles}).
908 @c FIXME seems like this section is not the best place for this option?
909 @defopt mail-host-address
910 If this variable is non-@code{nil}, it is used instead of
911 @code{system-name} for purposes of generating email addresses. For
912 example, it is used when constructing the default value of
913 @code{user-mail-address}. @xref{User Identification}. (Since this is
914 done when Emacs starts up, the value actually used is the one saved when
915 Emacs was dumped. @xref{Building Emacs}.)
916 @c FIXME sounds like should probably give this a :set-after and some
917 @c custom-initialize-delay voodoo.
920 @deffn Command getenv var &optional frame
921 @cindex environment variable access
922 This function returns the value of the environment variable @var{var},
923 as a string. @var{var} should be a string. If @var{var} is undefined
924 in the environment, @code{getenv} returns @code{nil}. It returns
925 @samp{""} if @var{var} is set but null. Within Emacs, a list of environment
926 variables and their values is kept in the variable @code{process-environment}.
935 The shell command @code{printenv} prints all or part of the environment:
940 PATH=/usr/local/bin:/usr/bin:/bin
952 @deffn Command setenv variable &optional value substitute
953 This command sets the value of the environment variable named
954 @var{variable} to @var{value}. @var{variable} should be a string.
955 Internally, Emacs Lisp can handle any string. However, normally
956 @var{variable} should be a valid shell identifier, that is, a sequence
957 of letters, digits and underscores, starting with a letter or
958 underscore. Otherwise, errors may occur if subprocesses of Emacs try
959 to access the value of @var{variable}. If @var{value} is omitted or
960 @code{nil} (or, interactively, with a prefix argument), @code{setenv}
961 removes @var{variable} from the environment. Otherwise, @var{value}
964 If the optional argument @var{substitute} is non-@code{nil}, Emacs
965 calls the function @code{substitute-env-vars} to expand any
966 environment variables in @var{value}.
968 @code{setenv} works by modifying @code{process-environment}; binding
969 that variable with @code{let} is also reasonable practice.
971 @code{setenv} returns the new value of @var{variable}, or @code{nil}
972 if it removed @var{variable} from the environment.
975 @defvar process-environment
976 This variable is a list of strings, each describing one environment
977 variable. The functions @code{getenv} and @code{setenv} work by means
983 @result{} ("PATH=/usr/local/bin:/usr/bin:/bin"
994 If @code{process-environment} contains ``duplicate'' elements that
995 specify the same environment variable, the first of these elements
996 specifies the variable, and the other ``duplicates'' are ignored.
999 @defvar initial-environment
1000 This variable holds the list of environment variables Emacs inherited
1001 from its parent process when Emacs started.
1004 @defvar path-separator
1005 This variable holds a string that says which character separates
1006 directories in a search path (as found in an environment variable). Its
1007 value is @code{":"} for Unix and GNU systems, and @code{";"} for MS systems.
1010 @defun parse-colon-path path
1011 This function takes a search path string such as the value of
1012 the @env{PATH} environment variable, and splits it at the separators,
1013 returning a list of directory names. @code{nil} in this list means
1014 the current directory. Although the function's name says
1015 ``colon'', it actually uses the value of @code{path-separator}.
1018 (parse-colon-path ":/foo:/bar")
1019 @result{} (nil "/foo/" "/bar/")
1023 @defvar invocation-name
1024 This variable holds the program name under which Emacs was invoked. The
1025 value is a string, and does not include a directory name.
1028 @defvar invocation-directory
1029 This variable holds the directory from which the Emacs executable was
1030 invoked, or @code{nil} if that directory cannot be determined.
1033 @defvar installation-directory
1034 If non-@code{nil}, this is a directory within which to look for the
1035 @file{lib-src} and @file{etc} subdirectories. In an installed Emacs,
1036 it is normally @code{nil}. It is non-@code{nil}
1037 when Emacs can't find those directories in their standard installed
1038 locations, but can find them in a directory related somehow to the one
1039 containing the Emacs executable (i.e., @code{invocation-directory}).
1042 @defun load-average &optional use-float
1043 This function returns the current 1-minute, 5-minute, and 15-minute
1044 system load averages, in a list. The load average indicates the
1045 number of processes trying to run on the system.
1047 By default, the values are integers that are 100 times the system load
1048 averages, but if @var{use-float} is non-@code{nil}, then they are
1049 returned as floating point numbers without multiplying by 100.
1051 If it is impossible to obtain the load average, this function signals
1052 an error. On some platforms, access to load averages requires
1053 installing Emacs as setuid or setgid so that it can read kernel
1054 information, and that usually isn't advisable.
1055 @c FIXME which platforms are these? Are they still relevant?
1057 If the 1-minute load average is available, but the 5- or 15-minute
1058 averages are not, this function returns a shortened list containing
1059 the available averages.
1064 @result{} (169 48 36)
1068 @result{} (1.69 0.48 0.36)
1072 The shell command @code{uptime} returns similar information.
1076 This function returns the process @acronym{ID} of the Emacs process,
1080 @defvar tty-erase-char
1081 This variable holds the erase character that was selected
1082 in the system's terminal driver, before Emacs was started.
1083 @c FIXME? Seems untrue since 23.1. For me, it is 0.
1084 @c The value is @code{nil} if Emacs is running under a window system.
1087 @node User Identification
1088 @section User Identification
1089 @cindex user identification
1091 @defvar init-file-user
1092 This variable says which user's init files should be used by
1093 Emacs---or @code{nil} if none. @code{""} stands for the user who
1094 originally logged in. The value reflects command-line options such as
1095 @samp{-q} or @samp{-u @var{user}}.
1097 Lisp packages that load files of customizations, or any other sort of
1098 user profile, should obey this variable in deciding where to find it.
1099 They should load the profile of the user name found in this variable.
1100 If @code{init-file-user} is @code{nil}, meaning that the @samp{-q}
1101 option was used, then Lisp packages should not load any customization
1102 files or user profile.
1105 @defopt user-mail-address
1106 This holds the nominal email address of the user who is using Emacs.
1107 Emacs normally sets this variable to a default value after reading your
1108 init files, but not if you have already set it. So you can set the
1109 variable to some other value in your init file if you do not
1110 want to use the default value.
1113 @defun user-login-name &optional uid
1114 This function returns the name under which the user is logged in.
1115 It uses the environment variables @env{LOGNAME} or @env{USER} if
1116 either is set. Otherwise, the value is based on the effective
1117 @acronym{UID}, not the real @acronym{UID}.
1119 If you specify @var{uid} (a number), the result is the user name that
1120 corresponds to @var{uid}, or @code{nil} if there is no such user.
1123 @defun user-real-login-name
1124 This function returns the user name corresponding to Emacs's real
1125 @acronym{UID}. This ignores the effective @acronym{UID}, and the
1126 environment variables @env{LOGNAME} and @env{USER}.
1129 @defun user-full-name &optional uid
1130 This function returns the full name of the logged-in user---or the value
1131 of the environment variable @env{NAME}, if that is set.
1133 If the Emacs process's user-id does not correspond to any known user (and
1134 provided @code{NAME} is not set), the result is @code{"unknown"}.
1136 If @var{uid} is non-@code{nil}, then it should be a number (a user-id)
1137 or a string (a login name). Then @code{user-full-name} returns the full
1138 name corresponding to that user-id or login name. If you specify a
1139 user-id or login name that isn't defined, it returns @code{nil}.
1142 @vindex user-full-name
1143 @vindex user-real-login-name
1144 @vindex user-login-name
1145 The symbols @code{user-login-name}, @code{user-real-login-name} and
1146 @code{user-full-name} are variables as well as functions. The functions
1147 return the same values that the variables hold. These variables allow
1148 you to ``fake out'' Emacs by telling the functions what to return. The
1149 variables are also useful for constructing frame titles (@pxref{Frame
1152 @defun user-real-uid
1153 This function returns the real @acronym{UID} of the user.
1154 The value may be a floating point number, in the (unlikely) event that
1155 the UID is too large to fit in a Lisp integer.
1159 This function returns the effective @acronym{UID} of the user.
1160 The value may be a floating point number.
1164 @section Time of Day
1166 This section explains how to determine the current time and time
1170 Most of these functions represent time as a list of either three
1171 integers, @code{(@var{sec-high} @var{sec-low} @var{microsec})}, or of
1172 two integers, @code{(@var{sec-high} @var{sec-low})}. The integers
1173 @var{sec-high} and @var{sec-low} give the high and low bits of an
1174 integer number of seconds. This integer number,
1176 @var{high} * 2**16 + @var{low},
1181 is the number of seconds from the @dfn{epoch} (0:00 January 1, 1970
1182 UTC) to the specified time. The third list element @var{microsec}, if
1183 present, gives the number of microseconds from the start of that
1184 second to the specified time.
1186 The return value of @code{current-time} represents time using three
1187 integers, while the timestamps in the return value of
1188 @code{file-attributes} use two integers (@pxref{Definition of
1189 file-attributes}). In function arguments, e.g.@: the @var{time-value}
1190 argument to @code{current-time-string}, both two- and three-integer
1191 lists are accepted. You can convert times from the list
1192 representation into standard human-readable strings using
1193 @code{current-time}, or to other forms using the @code{decode-time}
1194 and @code{format-time-string} functions documented in the following
1197 @defun current-time-string &optional time-value
1198 This function returns the current time and date as a human-readable
1199 string. The format does not vary for the initial part of the string,
1200 which contains the day of week, month, day of month, and time of day
1201 in that order: the number of characters used for these fields is
1202 always the same, so you can reliably
1203 use @code{substring} to extract them. You should count
1204 characters from the beginning of the string rather than from the end,
1205 as the year might not have exactly four digits, and additional
1206 information may some day be added at the end.
1208 The argument @var{time-value}, if given, specifies a time to format
1209 (represented as a list of integers), instead of the current time.
1213 (current-time-string)
1214 @result{} "Wed Oct 14 22:21:05 1987"
1220 This function returns the current time, represented as a list of three
1221 integers @code{(@var{sec-high} @var{sec-low} @var{microsec})}. On
1222 systems with only one-second time resolutions, @var{microsec} is 0.
1225 @defun float-time &optional time-value
1226 This function returns the current time as a floating-point number of
1227 seconds since the epoch. The optional argument @var{time-value}, if
1228 given, specifies a time (represented as a list of integers) to convert
1229 instead of the current time.
1231 @emph{Warning}: Since the result is floating point, it may not be
1232 exact. Do not use this function if precise time stamps are required.
1235 @defun current-time-zone &optional time-value
1236 This function returns a list describing the time zone that the user is
1239 The value has the form @code{(@var{offset} @var{name})}. Here
1240 @var{offset} is an integer giving the number of seconds ahead of UTC
1241 (east of Greenwich). A negative value means west of Greenwich. The
1242 second element, @var{name}, is a string giving the name of the time
1243 zone. Both elements change when daylight saving time begins or ends;
1244 if the user has specified a time zone that does not use a seasonal time
1245 adjustment, then the value is constant through time.
1247 If the operating system doesn't supply all the information necessary to
1248 compute the value, the unknown elements of the list are @code{nil}.
1250 The argument @var{time-value}, if given, specifies a time (represented
1251 as a list of integers) to analyze instead of the current time.
1254 The current time zone is determined by the @env{TZ} environment
1255 variable. @xref{System Environment}. For example, you can tell Emacs
1256 to use universal time with @code{(setenv "TZ" "UTC0")}. If @env{TZ}
1257 is not in the environment, Emacs uses a platform-dependent default
1260 @node Time Conversion
1261 @section Time Conversion
1263 These functions convert time values (lists of two or three integers,
1264 as explained in the previous section) into calendrical information and
1267 Many 32-bit operating systems are limited to time values containing
1268 32 bits of information; these systems typically handle only the times
1269 from 1901-12-13 20:45:52 UTC through 2038-01-19 03:14:07 UTC.
1270 However, 64-bit and some 32-bit operating systems have larger time
1271 values, and can represent times far in the past or future.
1273 Time conversion functions always use the Gregorian calendar, even
1274 for dates before the Gregorian calendar was introduced. Year numbers
1275 count the number of years since the year 1 B.C., and do not skip zero
1276 as traditional Gregorian years do; for example, the year number
1277 @minus{}37 represents the Gregorian year 38 B.C@.
1279 @defun decode-time &optional time
1280 This function converts a time value into calendrical information. If
1281 you don't specify @var{time}, it decodes the current time. The return
1282 value is a list of nine elements, as follows:
1285 (@var{seconds} @var{minutes} @var{hour} @var{day} @var{month} @var{year} @var{dow} @var{dst} @var{zone})
1288 Here is what the elements mean:
1292 The number of seconds past the minute, as an integer between 0 and 59.
1293 On some operating systems, this is 60 for leap seconds.
1295 The number of minutes past the hour, as an integer between 0 and 59.
1297 The hour of the day, as an integer between 0 and 23.
1299 The day of the month, as an integer between 1 and 31.
1301 The month of the year, as an integer between 1 and 12.
1303 The year, an integer typically greater than 1900.
1305 The day of week, as an integer between 0 and 6, where 0 stands for
1308 @code{t} if daylight saving time is effect, otherwise @code{nil}.
1310 An integer indicating the time zone, as the number of seconds east of
1314 @strong{Common Lisp Note:} Common Lisp has different meanings for
1315 @var{dow} and @var{zone}.
1318 @defun encode-time seconds minutes hour day month year &optional zone
1319 This function is the inverse of @code{decode-time}. It converts seven
1320 items of calendrical data into a time value. For the meanings of the
1321 arguments, see the table above under @code{decode-time}.
1323 Year numbers less than 100 are not treated specially. If you want them
1324 to stand for years above 1900, or years above 2000, you must alter them
1325 yourself before you call @code{encode-time}.
1327 The optional argument @var{zone} defaults to the current time zone and
1328 its daylight saving time rules. If specified, it can be either a list
1329 (as you would get from @code{current-time-zone}), a string as in the
1330 @env{TZ} environment variable, @code{t} for Universal Time, or an
1331 integer (as you would get from @code{decode-time}). The specified
1332 zone is used without any further alteration for daylight saving time.
1334 If you pass more than seven arguments to @code{encode-time}, the first
1335 six are used as @var{seconds} through @var{year}, the last argument is
1336 used as @var{zone}, and the arguments in between are ignored. This
1337 feature makes it possible to use the elements of a list returned by
1338 @code{decode-time} as the arguments to @code{encode-time}, like this:
1341 (apply 'encode-time (decode-time @dots{}))
1344 You can perform simple date arithmetic by using out-of-range values for
1345 the @var{seconds}, @var{minutes}, @var{hour}, @var{day}, and @var{month}
1346 arguments; for example, day 0 means the day preceding the given month.
1348 The operating system puts limits on the range of possible time values;
1349 if you try to encode a time that is out of range, an error results.
1350 For instance, years before 1970 do not work on some systems;
1351 on others, years as early as 1901 do work.
1355 @section Parsing and Formatting Times
1357 These functions convert time values (lists of two or three integers)
1358 to text in a string, and vice versa.
1360 @defun date-to-time string
1361 This function parses the time-string @var{string} and returns the
1362 corresponding time value.
1365 @defun format-time-string format-string &optional time universal
1366 This function converts @var{time} (or the current time, if @var{time} is
1367 omitted) to a string according to @var{format-string}. The argument
1368 @var{format-string} may contain @samp{%}-sequences which say to
1369 substitute parts of the time. Here is a table of what the
1370 @samp{%}-sequences mean:
1374 This stands for the abbreviated name of the day of week.
1376 This stands for the full name of the day of week.
1378 This stands for the abbreviated name of the month.
1380 This stands for the full name of the month.
1382 This is a synonym for @samp{%x %X}.
1384 This has a locale-specific meaning. In the default locale (named C), it
1385 is equivalent to @samp{%A, %B %e, %Y}.
1387 This stands for the day of month, zero-padded.
1389 This is a synonym for @samp{%m/%d/%y}.
1391 This stands for the day of month, blank-padded.
1393 This is a synonym for @samp{%b}.
1395 This stands for the hour (00-23).
1397 This stands for the hour (01-12).
1399 This stands for the day of the year (001-366).
1401 This stands for the hour (0-23), blank padded.
1403 This stands for the hour (1-12), blank padded.
1405 This stands for the month (01-12).
1407 This stands for the minute (00-59).
1409 This stands for a newline.
1411 This stands for the nanoseconds (000000000-999999999). To ask for
1412 fewer digits, use @samp{%3N} for milliseconds, @samp{%6N} for
1413 microseconds, etc. Any excess digits are discarded, without rounding.
1414 Currently Emacs time stamps are at best microsecond resolution so the
1415 last three digits generated by plain @samp{%N} are always zero.
1417 This stands for @samp{AM} or @samp{PM}, as appropriate.
1419 This is a synonym for @samp{%I:%M:%S %p}.
1421 This is a synonym for @samp{%H:%M}.
1423 This stands for the seconds (00-59).
1425 This stands for a tab character.
1427 This is a synonym for @samp{%H:%M:%S}.
1429 This stands for the week of the year (01-52), assuming that weeks
1432 This stands for the numeric day of week (0-6). Sunday is day 0.
1434 This stands for the week of the year (01-52), assuming that weeks
1437 This has a locale-specific meaning. In the default locale (named
1438 @samp{C}), it is equivalent to @samp{%D}.
1440 This has a locale-specific meaning. In the default locale (named
1441 @samp{C}), it is equivalent to @samp{%T}.
1443 This stands for the year without century (00-99).
1445 This stands for the year with century.
1447 This stands for the time zone abbreviation (e.g., @samp{EST}).
1449 This stands for the time zone numerical offset (e.g., @samp{-0500}).
1452 You can also specify the field width and type of padding for any of
1453 these @samp{%}-sequences. This works as in @code{printf}: you write
1454 the field width as digits in the middle of a @samp{%}-sequences. If you
1455 start the field width with @samp{0}, it means to pad with zeros. If you
1456 start the field width with @samp{_}, it means to pad with spaces.
1458 For example, @samp{%S} specifies the number of seconds since the minute;
1459 @samp{%03S} means to pad this with zeros to 3 positions, @samp{%_3S} to
1460 pad with spaces to 3 positions. Plain @samp{%3S} pads with zeros,
1461 because that is how @samp{%S} normally pads to two positions.
1463 The characters @samp{E} and @samp{O} act as modifiers when used between
1464 @samp{%} and one of the letters in the table above. @samp{E} specifies
1465 using the current locale's ``alternative'' version of the date and time.
1466 In a Japanese locale, for example, @code{%Ex} might yield a date format
1467 based on the Japanese Emperors' reigns. @samp{E} is allowed in
1468 @samp{%Ec}, @samp{%EC}, @samp{%Ex}, @samp{%EX}, @samp{%Ey}, and
1471 @samp{O} means to use the current locale's ``alternative''
1472 representation of numbers, instead of the ordinary decimal digits. This
1473 is allowed with most letters, all the ones that output numbers.
1475 If @var{universal} is non-@code{nil}, that means to describe the time as
1476 Universal Time; @code{nil} means describe it using what Emacs believes
1477 is the local time zone (see @code{current-time-zone}).
1479 This function uses the C library function @code{strftime}
1480 (@pxref{Formatting Calendar Time,,, libc, The GNU C Library Reference
1481 Manual}) to do most of the work. In order to communicate with that
1482 function, it first encodes its argument using the coding system
1483 specified by @code{locale-coding-system} (@pxref{Locales}); after
1484 @code{strftime} returns the resulting string,
1485 @code{format-time-string} decodes the string using that same coding
1489 @defun seconds-to-time seconds
1490 This function converts @var{seconds}, a floating point number of
1491 seconds since the epoch, to a time value and returns that. To perform
1492 the inverse conversion, use @code{float-time}.
1495 @defun format-seconds format-string seconds
1496 This function converts its argument @var{seconds} into a string of
1497 years, days, hours, etc., according to @var{format-string}. The
1498 argument @var{format-string} may contain @samp{%}-sequences which
1499 control the conversion. Here is a table of what the
1500 @samp{%}-sequences mean:
1505 The integer number of 365-day years.
1508 The integer number of days.
1511 The integer number of hours.
1514 The integer number of minutes.
1517 The integer number of seconds.
1519 Non-printing control flag. When it is used, other specifiers must be
1520 given in the order of decreasing size, i.e.@: years before days, hours
1521 before minutes, etc. Nothing will be produced in the result string to
1522 the left of @samp{%z} until the first non-zero conversion is
1523 encountered. For example, the default format used by
1524 @code{emacs-uptime} (@pxref{Processor Run Time, emacs-uptime})
1525 @w{@code{"%Y, %D, %H, %M, %z%S"}} means that the number of seconds
1526 will always be produced, but years, days, hours, and minutes will only
1527 be shown if they are non-zero.
1529 Produces a literal @samp{%}.
1532 Upper-case format sequences produce the units in addition to the
1533 numbers, lower-case formats produce only the numbers.
1535 You can also specify the field width by following the @samp{%} with a
1536 number; shorter numbers will be padded with blanks. An optional
1537 period before the width requests zero-padding instead. For example,
1538 @code{"%.3Y"} might produce @code{"004 years"}.
1540 @emph{Warning:} This function works only with values of @var{seconds}
1541 that don't exceed @code{most-positive-fixnum} (@pxref{Integer Basics,
1542 most-positive-fixnum}).
1545 @node Processor Run Time
1546 @section Processor Run time
1547 @cindex processor run time
1548 @cindex Emacs process run time
1550 Emacs provides several functions and primitives that return time,
1551 both elapsed and processor time, used by the Emacs process.
1553 @deffn Command emacs-uptime &optional format
1554 This function returns a string representing the Emacs
1555 @dfn{uptime}---the elapsed wall-clock time this instance of Emacs is
1556 running. The string is formatted by @code{format-seconds} according
1557 to the optional argument @var{format}. For the available format
1558 descriptors, see @ref{Time Parsing, format-seconds}. If @var{format}
1559 is @code{nil} or omitted, it defaults to @code{"%Y, %D, %H, %M,
1562 When called interactively, it prints the uptime in the echo area.
1565 @defun get-internal-run-time
1566 This function returns the processor run time used by Emacs as a list
1567 of three integers: @code{(@var{high} @var{low} @var{microsec})}. The
1568 integers @var{high} and @var{low} combine to give the number of
1571 @var{high} * 2**16 + @var{low}.
1577 The third element, @var{microsec}, gives the microseconds (or 0 for
1578 systems that return time with the resolution of only one second).
1580 Note that the time returned by this function excludes the time Emacs
1581 was not using the processor, and if the Emacs process has several
1582 threads, the returned value is the sum of the processor times used up
1583 by all Emacs threads.
1585 If the system doesn't provide a way to determine the processor run
1586 time, @code{get-internal-run-time} returns the same time as
1587 @code{current-time}.
1590 @deffn Command emacs-init-time
1591 This function returns the duration of the Emacs initialization
1592 (@pxref{Startup Summary}) in seconds, as a string. When called
1593 interactively, it prints the duration in the echo area.
1596 @node Time Calculations
1597 @section Time Calculations
1599 These functions perform calendrical computations using time values
1600 (the kind of list that @code{current-time} returns).
1602 @defun time-less-p t1 t2
1603 This returns @code{t} if time value @var{t1} is less than time value
1607 @defun time-subtract t1 t2
1608 This returns the time difference @var{t1} @minus{} @var{t2} between
1609 two time values, in the same format as a time value.
1612 @defun time-add t1 t2
1613 This returns the sum of two time values, one of which ought to
1614 represent a time difference rather than a point in time.
1615 Here is how to add a number of seconds to a time value:
1618 (time-add @var{time} (seconds-to-time @var{seconds}))
1622 @defun time-to-days time
1623 This function returns the number of days between the beginning of year
1627 @defun time-to-day-in-year time
1628 This returns the day number within the year corresponding to @var{time}.
1631 @defun date-leap-year-p year
1632 This function returns @code{t} if @var{year} is a leap year.
1636 @section Timers for Delayed Execution
1639 You can set up a @dfn{timer} to call a function at a specified
1640 future time or after a certain length of idleness.
1642 Emacs cannot run timers at any arbitrary point in a Lisp program; it
1643 can run them only when Emacs could accept output from a subprocess:
1644 namely, while waiting or inside certain primitive functions such as
1645 @code{sit-for} or @code{read-event} which @emph{can} wait. Therefore, a
1646 timer's execution may be delayed if Emacs is busy. However, the time of
1647 execution is very precise if Emacs is idle.
1649 Emacs binds @code{inhibit-quit} to @code{t} before calling the timer
1650 function, because quitting out of many timer functions can leave
1651 things in an inconsistent state. This is normally unproblematical
1652 because most timer functions don't do a lot of work. Indeed, for a
1653 timer to call a function that takes substantial time to run is likely
1654 to be annoying. If a timer function needs to allow quitting, it
1655 should use @code{with-local-quit} (@pxref{Quitting}). For example, if
1656 a timer function calls @code{accept-process-output} to receive output
1657 from an external process, that call should be wrapped inside
1658 @code{with-local-quit}, to ensure that @kbd{C-g} works if the external
1661 It is usually a bad idea for timer functions to alter buffer
1662 contents. When they do, they usually should call @code{undo-boundary}
1663 both before and after changing the buffer, to separate the timer's
1664 changes from user commands' changes and prevent a single undo entry
1665 from growing to be quite large.
1667 Timer functions should also avoid calling functions that cause Emacs
1668 to wait, such as @code{sit-for} (@pxref{Waiting}). This can lead to
1669 unpredictable effects, since other timers (or even the same timer) can
1670 run while waiting. If a timer function needs to perform an action
1671 after a certain time has elapsed, it can do this by scheduling a new
1674 If a timer function calls functions that can change the match data,
1675 it should save and restore the match data. @xref{Saving Match Data}.
1677 @deffn Command run-at-time time repeat function &rest args
1678 This sets up a timer that calls the function @var{function} with
1679 arguments @var{args} at time @var{time}. If @var{repeat} is a number
1680 (integer or floating point), the timer is scheduled to run again every
1681 @var{repeat} seconds after @var{time}. If @var{repeat} is @code{nil},
1682 the timer runs only once.
1684 @var{time} may specify an absolute or a relative time.
1686 Absolute times may be specified using a string with a limited variety
1687 of formats, and are taken to be times @emph{today}, even if already in
1688 the past. The recognized forms are @samp{@var{xxxx}},
1689 @samp{@var{x}:@var{xx}}, or @samp{@var{xx}:@var{xx}} (military time),
1690 and @samp{@var{xx}am}, @samp{@var{xx}AM}, @samp{@var{xx}pm},
1691 @samp{@var{xx}PM}, @samp{@var{xx}:@var{xx}am},
1692 @samp{@var{xx}:@var{xx}AM}, @samp{@var{xx}:@var{xx}pm}, or
1693 @samp{@var{xx}:@var{xx}PM}. A period can be used instead of a colon
1694 to separate the hour and minute parts.
1696 To specify a relative time as a string, use numbers followed by units.
1701 denotes 1 minute from now.
1703 denotes 65 seconds from now.
1704 @item 1 min 2 sec 3 hour 4 day 5 week 6 fortnight 7 month 8 year
1705 denotes exactly 103 months, 123 days, and 10862 seconds from now.
1708 For relative time values, Emacs considers a month to be exactly thirty
1709 days, and a year to be exactly 365.25 days.
1711 Not all convenient formats are strings. If @var{time} is a number
1712 (integer or floating point), that specifies a relative time measured in
1713 seconds. The result of @code{encode-time} can also be used to specify
1714 an absolute value for @var{time}.
1716 In most cases, @var{repeat} has no effect on when @emph{first} call
1717 takes place---@var{time} alone specifies that. There is one exception:
1718 if @var{time} is @code{t}, then the timer runs whenever the time is a
1719 multiple of @var{repeat} seconds after the epoch. This is useful for
1720 functions like @code{display-time}.
1722 The function @code{run-at-time} returns a timer value that identifies
1723 the particular scheduled future action. You can use this value to call
1724 @code{cancel-timer} (see below).
1727 A repeating timer nominally ought to run every @var{repeat} seconds,
1728 but remember that any invocation of a timer can be late. Lateness of
1729 one repetition has no effect on the scheduled time of the next
1730 repetition. For instance, if Emacs is busy computing for long enough
1731 to cover three scheduled repetitions of the timer, and then starts to
1732 wait, it will immediately call the timer function three times in
1733 immediate succession (presuming no other timers trigger before or
1734 between them). If you want a timer to run again no less than @var{n}
1735 seconds after the last invocation, don't use the @var{repeat} argument.
1736 Instead, the timer function should explicitly reschedule the timer.
1738 @defopt timer-max-repeats
1739 This variable's value specifies the maximum number of times to repeat
1740 calling a timer function in a row, when many previously scheduled
1741 calls were unavoidably delayed.
1744 @defmac with-timeout (seconds timeout-forms@dots{}) body@dots{}
1745 Execute @var{body}, but give up after @var{seconds} seconds. If
1746 @var{body} finishes before the time is up, @code{with-timeout} returns
1747 the value of the last form in @var{body}. If, however, the execution of
1748 @var{body} is cut short by the timeout, then @code{with-timeout}
1749 executes all the @var{timeout-forms} and returns the value of the last
1752 This macro works by setting a timer to run after @var{seconds} seconds. If
1753 @var{body} finishes before that time, it cancels the timer. If the
1754 timer actually runs, it terminates execution of @var{body}, then
1755 executes @var{timeout-forms}.
1757 Since timers can run within a Lisp program only when the program calls a
1758 primitive that can wait, @code{with-timeout} cannot stop executing
1759 @var{body} while it is in the midst of a computation---only when it
1760 calls one of those primitives. So use @code{with-timeout} only with a
1761 @var{body} that waits for input, not one that does a long computation.
1764 The function @code{y-or-n-p-with-timeout} provides a simple way to use
1765 a timer to avoid waiting too long for an answer. @xref{Yes-or-No
1768 @defun cancel-timer timer
1769 This cancels the requested action for @var{timer}, which should be a
1770 timer---usually, one previously returned by @code{run-at-time} or
1771 @code{run-with-idle-timer}. This cancels the effect of that call to
1772 one of these functions; the arrival of the specified time will not
1773 cause anything special to happen.
1777 @section Idle Timers
1779 Here is how to set up a timer that runs when Emacs is idle for a
1780 certain length of time. Aside from how to set them up, idle timers
1781 work just like ordinary timers.
1783 @deffn Command run-with-idle-timer secs repeat function &rest args
1784 Set up a timer which runs the next time Emacs is idle for @var{secs}
1785 seconds. The value of @var{secs} may be an integer or a floating
1786 point number; a value of the type returned by @code{current-idle-time}
1789 If @var{repeat} is @code{nil}, the timer runs just once, the first time
1790 Emacs remains idle for a long enough time. More often @var{repeat} is
1791 non-@code{nil}, which means to run the timer @emph{each time} Emacs
1792 remains idle for @var{secs} seconds.
1794 The function @code{run-with-idle-timer} returns a timer value which you
1795 can use in calling @code{cancel-timer} (@pxref{Timers}).
1799 Emacs becomes @dfn{idle} when it starts waiting for user input, and
1800 it remains idle until the user provides some input. If a timer is set
1801 for five seconds of idleness, it runs approximately five seconds after
1802 Emacs first becomes idle. Even if @var{repeat} is non-@code{nil},
1803 this timer will not run again as long as Emacs remains idle, because
1804 the duration of idleness will continue to increase and will not go
1805 down to five seconds again.
1807 Emacs can do various things while idle: garbage collect, autosave or
1808 handle data from a subprocess. But these interludes during idleness do
1809 not interfere with idle timers, because they do not reset the clock of
1810 idleness to zero. An idle timer set for 600 seconds will run when ten
1811 minutes have elapsed since the last user command was finished, even if
1812 subprocess output has been accepted thousands of times within those ten
1813 minutes, and even if there have been garbage collections and autosaves.
1815 When the user supplies input, Emacs becomes non-idle while executing the
1816 input. Then it becomes idle again, and all the idle timers that are
1817 set up to repeat will subsequently run another time, one by one.
1819 @defun current-idle-time
1820 If Emacs is idle, this function returns the length of time Emacs has
1821 been idle, as a list of three integers: @code{(@var{sec-high}
1822 @var{sec-low} @var{microsec})}, where @var{high} and @var{low} are the
1823 high and low bits for the number of seconds and @var{microsec} is the
1824 additional number of microseconds (@pxref{Time of Day}).
1826 When Emacs is not idle, @code{current-idle-time} returns @code{nil}.
1827 This is a convenient way to test whether Emacs is idle.
1829 The main use of this function is when an idle timer function wants to
1830 ``take a break'' for a while. It can set up another idle timer to
1831 call the same function again, after a few seconds more idleness.
1835 (defvar resume-timer nil
1836 "Timer that `timer-function' used to reschedule itself, or nil.")
1838 (defun timer-function ()
1839 ;; @r{If the user types a command while @code{resume-timer}}
1840 ;; @r{is active, the next time this function is called from}
1841 ;; @r{its main idle timer, deactivate @code{resume-timer}.}
1843 (cancel-timer resume-timer))
1844 ...@var{do the work for a while}...
1845 (when @var{taking-a-break}
1847 (run-with-idle-timer
1848 ;; Compute an idle time @var{break-length}
1849 ;; more than the current value.
1850 (time-add (current-idle-time)
1851 (seconds-to-time @var{break-length}))
1857 Do not write an idle timer function containing a loop which does a
1858 certain amount of processing each time around, and exits when
1859 @code{(input-pending-p)} is non-@code{nil}. This approach seems very
1860 natural but has two problems:
1864 It blocks out all process output (since Emacs accepts process output
1865 only while waiting).
1868 It blocks out any idle timers that ought to run during that time.
1872 The correct approach is for the idle timer to reschedule itself after
1873 a brief pause, using the method in the @code{timer-function} example
1876 @node Terminal Input
1877 @section Terminal Input
1878 @cindex terminal input
1880 This section describes functions and variables for recording or
1881 manipulating terminal input. See @ref{Display}, for related
1885 * Input Modes:: Options for how input is processed.
1886 * Recording Input:: Saving histories of recent or all input events.
1890 @subsection Input Modes
1892 @cindex terminal input modes
1894 @defun set-input-mode interrupt flow meta &optional quit-char
1895 This function sets the mode for reading keyboard input. If
1896 @var{interrupt} is non-null, then Emacs uses input interrupts. If it is
1897 @code{nil}, then it uses @sc{cbreak} mode. The default setting is
1898 system-dependent. Some systems always use @sc{cbreak} mode regardless
1899 of what is specified.
1901 When Emacs communicates directly with X, it ignores this argument and
1902 uses interrupts if that is the way it knows how to communicate.
1904 If @var{flow} is non-@code{nil}, then Emacs uses @sc{xon/xoff}
1905 (@kbd{C-q}, @kbd{C-s}) flow control for output to the terminal. This
1906 has no effect except in @sc{cbreak} mode.
1909 The argument @var{meta} controls support for input character codes
1910 above 127. If @var{meta} is @code{t}, Emacs converts characters with
1911 the 8th bit set into Meta characters. If @var{meta} is @code{nil},
1912 Emacs disregards the 8th bit; this is necessary when the terminal uses
1913 it as a parity bit. If @var{meta} is neither @code{t} nor @code{nil},
1914 Emacs uses all 8 bits of input unchanged. This is good for terminals
1915 that use 8-bit character sets.
1918 If @var{quit-char} is non-@code{nil}, it specifies the character to
1919 use for quitting. Normally this character is @kbd{C-g}.
1923 The @code{current-input-mode} function returns the input mode settings
1924 Emacs is currently using.
1927 @defun current-input-mode
1928 This function returns the current mode for reading keyboard input. It
1929 returns a list, corresponding to the arguments of @code{set-input-mode},
1930 of the form @code{(@var{interrupt} @var{flow} @var{meta} @var{quit})} in
1934 is non-@code{nil} when Emacs is using interrupt-driven input. If
1935 @code{nil}, Emacs is using @sc{cbreak} mode.
1937 is non-@code{nil} if Emacs uses @sc{xon/xoff} (@kbd{C-q}, @kbd{C-s})
1938 flow control for output to the terminal. This value is meaningful only
1939 when @var{interrupt} is @code{nil}.
1941 is @code{t} if Emacs treats the eighth bit of input characters as
1942 the meta bit; @code{nil} means Emacs clears the eighth bit of every
1943 input character; any other value means Emacs uses all eight bits as the
1944 basic character code.
1946 is the character Emacs currently uses for quitting, usually @kbd{C-g}.
1950 @node Recording Input
1951 @subsection Recording Input
1952 @cindex recording input
1955 This function returns a vector containing the last 300 input events from
1956 the keyboard or mouse. All input events are included, whether or not
1957 they were used as parts of key sequences. Thus, you always get the last
1958 100 input events, not counting events generated by keyboard macros.
1959 (These are excluded because they are less interesting for debugging; it
1960 should be enough to see the events that invoked the macros.)
1962 A call to @code{clear-this-command-keys} (@pxref{Command Loop Info})
1963 causes this function to return an empty vector immediately afterward.
1966 @deffn Command open-dribble-file filename
1967 @cindex dribble file
1968 This function opens a @dfn{dribble file} named @var{filename}. When a
1969 dribble file is open, each input event from the keyboard or mouse (but
1970 not those from keyboard macros) is written in that file. A
1971 non-character event is expressed using its printed representation
1972 surrounded by @samp{<@dots{}>}.
1974 You close the dribble file by calling this function with an argument
1977 This function is normally used to record the input necessary to
1978 trigger an Emacs bug, for the sake of a bug report.
1982 (open-dribble-file "~/dribble")
1988 See also the @code{open-termscript} function (@pxref{Terminal Output}).
1990 @node Terminal Output
1991 @section Terminal Output
1992 @cindex terminal output
1994 The terminal output functions send output to a text terminal, or keep
1995 track of output sent to the terminal. The variable @code{baud-rate}
1996 tells you what Emacs thinks is the output speed of the terminal.
1999 This variable's value is the output speed of the terminal, as far as
2000 Emacs knows. Setting this variable does not change the speed of actual
2001 data transmission, but the value is used for calculations such as
2004 It also affects decisions about whether to scroll part of the
2005 screen or repaint on text terminals. @xref{Forcing Redisplay},
2006 for the corresponding functionality on graphical terminals.
2008 The value is measured in baud.
2011 If you are running across a network, and different parts of the
2012 network work at different baud rates, the value returned by Emacs may be
2013 different from the value used by your local terminal. Some network
2014 protocols communicate the local terminal speed to the remote machine, so
2015 that Emacs and other programs can get the proper value, but others do
2016 not. If Emacs has the wrong value, it makes decisions that are less
2017 than optimal. To fix the problem, set @code{baud-rate}.
2019 @defun send-string-to-terminal string &optional terminal
2020 This function sends @var{string} to @var{terminal} without alteration.
2021 Control characters in @var{string} have terminal-dependent effects.
2022 This function operates only on text terminals. @var{terminal} may be
2023 a terminal object, a frame, or @code{nil} for the selected frame's
2024 terminal. In batch mode, @var{string} is sent to @code{stdout} when
2025 @var{terminal} is @code{nil}.
2027 One use of this function is to define function keys on terminals that
2028 have downloadable function key definitions. For example, this is how (on
2029 certain terminals) to define function key 4 to move forward four
2030 characters (by transmitting the characters @kbd{C-u C-f} to the
2035 (send-string-to-terminal "\eF4\^U\^F")
2041 @deffn Command open-termscript filename
2042 @cindex termscript file
2043 This function is used to open a @dfn{termscript file} that will record
2044 all the characters sent by Emacs to the terminal. It returns
2045 @code{nil}. Termscript files are useful for investigating problems
2046 where Emacs garbles the screen, problems that are due to incorrect
2047 Termcap entries or to undesirable settings of terminal options more
2048 often than to actual Emacs bugs. Once you are certain which characters
2049 were actually output, you can determine reliably whether they correspond
2050 to the Termcap specifications in use.
2052 You close the termscript file by calling this function with an
2053 argument of @code{nil}.
2055 See also @code{open-dribble-file} in @ref{Recording Input}.
2059 (open-termscript "../junk/termscript")
2066 @section Sound Output
2069 To play sound using Emacs, use the function @code{play-sound}. Only
2070 certain systems are supported; if you call @code{play-sound} on a
2071 system which cannot really do the job, it gives an error.
2073 The sound must be stored as a file in RIFF-WAVE format (@samp{.wav})
2074 or Sun Audio format (@samp{.au}).
2076 @defun play-sound sound
2077 This function plays a specified sound. The argument, @var{sound}, has
2078 the form @code{(sound @var{properties}...)}, where the @var{properties}
2079 consist of alternating keywords (particular symbols recognized
2080 specially) and values corresponding to them.
2082 Here is a table of the keywords that are currently meaningful in
2083 @var{sound}, and their meanings:
2086 @item :file @var{file}
2087 This specifies the file containing the sound to play.
2088 If the file name is not absolute, it is expanded against
2089 the directory @code{data-directory}.
2091 @item :data @var{data}
2092 This specifies the sound to play without need to refer to a file. The
2093 value, @var{data}, should be a string containing the same bytes as a
2094 sound file. We recommend using a unibyte string.
2096 @item :volume @var{volume}
2097 This specifies how loud to play the sound. It should be a number in the
2098 range of 0 to 1. The default is to use whatever volume has been
2101 @item :device @var{device}
2102 This specifies the system device on which to play the sound, as a
2103 string. The default device is system-dependent.
2106 Before actually playing the sound, @code{play-sound}
2107 calls the functions in the list @code{play-sound-functions}.
2108 Each function is called with one argument, @var{sound}.
2111 @deffn Command play-sound-file file &optional volume device
2112 This function is an alternative interface to playing a sound @var{file}
2113 specifying an optional @var{volume} and @var{device}.
2116 @defvar play-sound-functions
2117 A list of functions to be called before playing a sound. Each function
2118 is called with one argument, a property list that describes the sound.
2122 @section Operating on X11 Keysyms
2125 To define system-specific X11 keysyms, set the variable
2126 @code{system-key-alist}.
2128 @defvar system-key-alist
2129 This variable's value should be an alist with one element for each
2130 system-specific keysym. Each element has the form @code{(@var{code}
2131 . @var{symbol})}, where @var{code} is the numeric keysym code (not
2132 including the ``vendor specific'' bit,
2139 and @var{symbol} is the name for the function key.
2141 For example @code{(168 . mute-acute)} defines a system-specific key (used
2142 by HP X servers) whose numeric code is
2151 It is not crucial to exclude from the alist the keysyms of other X
2152 servers; those do no harm, as long as they don't conflict with the ones
2153 used by the X server actually in use.
2155 The variable is always local to the current terminal, and cannot be
2156 buffer-local. @xref{Multiple Terminals}.
2159 You can specify which keysyms Emacs should use for the Meta, Alt, Hyper, and Super modifiers by setting these variables:
2161 @defvar x-alt-keysym
2162 @defvarx x-meta-keysym
2163 @defvarx x-hyper-keysym
2164 @defvarx x-super-keysym
2165 The name of the keysym that should stand for the Alt modifier
2166 (respectively, for Meta, Hyper, and Super). For example, here is
2167 how to swap the Meta and Alt modifiers within Emacs:
2169 (setq x-alt-keysym 'meta)
2170 (setq x-meta-keysym 'alt)
2178 The command-line option @samp{-batch} causes Emacs to run
2179 noninteractively. In this mode, Emacs does not read commands from the
2180 terminal, it does not alter the terminal modes, and it does not expect
2181 to be outputting to an erasable screen. The idea is that you specify
2182 Lisp programs to run; when they are finished, Emacs should exit. The
2183 way to specify the programs to run is with @samp{-l @var{file}}, which
2184 loads the library named @var{file}, or @samp{-f @var{function}}, which
2185 calls @var{function} with no arguments, or @samp{--eval @var{form}}.
2187 Any Lisp program output that would normally go to the echo area,
2188 either using @code{message}, or using @code{prin1}, etc., with @code{t}
2189 as the stream, goes instead to Emacs's standard error descriptor when
2190 in batch mode. Similarly, input that would normally come from the
2191 minibuffer is read from the standard input descriptor.
2192 Thus, Emacs behaves much like a noninteractive
2193 application program. (The echo area output that Emacs itself normally
2194 generates, such as command echoing, is suppressed entirely.)
2196 @defvar noninteractive
2197 This variable is non-@code{nil} when Emacs is running in batch mode.
2200 @node Session Management
2201 @section Session Management
2202 @cindex session manager
2204 Emacs supports the X Session Management Protocol, which is used to
2205 suspend and restart applications. In the X Window System, a program
2206 called the @dfn{session manager} is responsible for keeping track of
2207 the applications that are running. When the X server shuts down, the
2208 session manager asks applications to save their state, and delays the
2209 actual shutdown until they respond. An application can also cancel
2212 When the session manager restarts a suspended session, it directs
2213 these applications to individually reload their saved state. It does
2214 this by specifying a special command-line argument that says what
2215 saved session to restore. For Emacs, this argument is @samp{--smid
2218 @defvar emacs-save-session-functions
2219 Emacs supports saving state via a hook called
2220 @code{emacs-save-session-functions}. Emacs runs this hook when the
2221 session manager tells it that the window system is shutting down. The
2222 functions are called with no arguments, and with the current buffer
2223 set to a temporary buffer. Each function can use @code{insert} to add
2224 Lisp code to this buffer. At the end, Emacs saves the buffer in a
2225 file, called the @dfn{session file}.
2227 @findex emacs-session-restore
2228 Subsequently, when the session manager restarts Emacs, it loads the
2229 session file automatically (@pxref{Loading}). This is performed by a
2230 function named @code{emacs-session-restore}, which is called during
2231 startup. @xref{Startup Summary}.
2233 If a function in @code{emacs-save-session-functions} returns
2234 non-@code{nil}, Emacs tells the session manager to cancel the
2238 Here is an example that just inserts some text into @file{*scratch*} when
2239 Emacs is restarted by the session manager.
2243 (add-hook 'emacs-save-session-functions 'save-yourself-test)
2247 (defun save-yourself-test ()
2248 (insert "(save-current-buffer
2249 (switch-to-buffer \"*scratch*\")
2250 (insert \"I am restored\"))")
2256 @section Desktop Notifications
2257 @cindex desktop notifications
2259 Emacs is able to send @dfn{notifications} on systems that support the
2260 freedesktop.org Desktop Notifications Specification. In order to use
2261 this functionality, Emacs must have been compiled with D-Bus support,
2262 and the @code{notifications} library must be loaded.
2264 @defun notifications-notify &rest params
2265 This function sends a notification to the desktop via D-Bus,
2266 consisting of the parameters specified by the @var{params} arguments.
2267 These arguments should consist of alternating keyword and value pairs.
2268 The supported keywords and values are as follows:
2271 @item :title @var{title}
2272 The notification title.
2274 @item :body @var{text}
2275 The notification body text. Depending on the implementation of the
2276 notification server, the text could contain HTML markups, like
2277 @samp{"<b>bold text</b>"}, hyperlinks, or images.
2279 @item :app-name @var{name}
2280 The name of the application sending the notification. The default is
2281 @code{notifications-application-name}.
2283 @item :replaces-id @var{id}
2284 The notification @var{id} that this notification replaces. @var{id}
2285 must be the result of a previous @code{notifications-notify} call.
2287 @item :app-icon @var{icon-file}
2288 The file name of the notification icon. If set to @code{nil}, no icon
2289 is displayed. The default is @code{notifications-application-icon}.
2291 @item :actions (@var{key} @var{title} @var{key} @var{title} ...)
2292 A list of actions to be applied. @var{key} and @var{title} are both
2293 strings. The default action (usually invoked by clicking the
2294 notification) should have a key named @samp{"default"}. The title can
2295 be anything, though implementations are free not to display it.
2297 @item :timeout @var{timeout}
2298 The timeout time in milliseconds since the display of the notification
2299 at which the notification should automatically close. If -1, the
2300 notification's expiration time is dependent on the notification
2301 server's settings, and may vary for the type of notification. If 0,
2302 the notification never expires. Default value is -1.
2304 @item :urgency @var{urgency}
2305 The urgency level. It can be @code{low}, @code{normal}, or @code{critical}.
2308 When this keyword is given, the @var{title} string of the actions is
2309 interpreted as icon name.
2311 @item :category @var{category}
2312 The type of notification this is, a string.
2314 @item :desktop-entry @var{filename}
2315 This specifies the name of the desktop filename representing the
2316 calling program, like @samp{"emacs"}.
2318 @item :image-data (@var{width} @var{height} @var{rowstride} @var{has-alpha} @var{bits} @var{channels} @var{data})
2319 This is a raw data image format that describes the width, height,
2320 rowstride, whether there is an alpha channel, bits per sample,
2321 channels and image data, respectively.
2323 @item :image-path @var{path}
2324 This is represented either as a URI (@samp{file://} is the only URI
2325 schema supported right now) or a name in a freedesktop.org-compliant
2326 icon theme from @samp{$XDG_DATA_DIRS/icons}, like @samp{"mail-message-new"}.
2328 @item :sound-file @var{filename}
2329 The path to a sound file to play when the notification pops up.
2331 @item :sound-name @var{name}
2332 A themable named sound from the freedesktop.org sound naming
2333 specification from @samp{$XDG_DATA_DIRS/sounds}, to play when the
2334 notification pops up. Similar to the icon name, only for sounds. An
2335 example would be @samp{"message-new-instant"}.
2337 @item :suppress-sound
2338 Causes the server to suppress playing any sounds, if it has that
2342 When set the server will not automatically remove the notification
2343 when an action has been invoked. The notification will remain resident
2344 in the server until it is explicitly removed by the user or by the
2345 sender. This hint is likely only useful when the server has the
2346 @code{:persistence} capability.
2349 When set the server will treat the notification as transient and
2350 by-pass the server's persistence capability, if it should exist.
2352 @item :x @var{position}
2353 @itemx :y @var{position}
2354 Specifies the X, Y location on the screen that the
2355 notification should point to. Both arguments must be used together.
2357 @item :on-action @var{function}
2358 Function to call when an action is invoked. The notification @var{id}
2359 and the @var{key} of the action are passed as arguments to the
2362 @item :on-close @var{function}
2363 Function to call when the notification has been closed by timeout or
2364 by the user. The function receive the notification @var{id} and the closing
2365 @var{reason} as arguments:
2368 @item @code{expired} if the notification has expired
2369 @item @code{dismissed} if the notification was dismissed by the user
2370 @item @code{close-notification} if the notification was closed by a call to
2371 @code{notifications-close-notification}
2372 @item @code{undefined} if the notification server hasn't provided a reason
2376 Which parameters are accepted by the notification server can be
2377 checked via @code{notifications-get-capabilities}.
2379 This function returns a notification id, an integer, which can be used
2380 to manipulate the notification item with
2381 @code{notifications-close-notification} or the @code{:replaces-id}
2382 argument of another @code{notifications-notify} call. For example:
2386 (defun my-on-action-function (id key)
2387 (message "Message %d, key \"%s\" pressed" id key))
2388 @result{} my-on-action-function
2392 (defun my-on-close-function (id reason)
2393 (message "Message %d, closed due to \"%s\"" id reason))
2394 @result{} my-on-close-function
2398 (notifications-notify
2400 :body "This is <b>important</b>."
2401 :actions '("Confirm" "I agree" "Refuse" "I disagree")
2402 :on-action 'my-on-action-function
2403 :on-close 'my-on-close-function)
2408 A message window opens on the desktop. Press "I agree"
2409 @result{} Message 22, key "Confirm" pressed
2410 Message 22, closed due to "dismissed"
2415 @defun notifications-close-notification id
2416 This function closes a notification with identifier @var{id}.
2419 @defun notifications-get-capabilities
2420 Returns the capabilities of the notification server, a list of strings.
2421 The following capabilities can be expected:
2425 The server will provide the specified actions to the user.
2430 @item :body-hyperlinks
2431 The server supports hyperlinks in the notifications.
2434 The server supports images in the notifications.
2437 Supports markup in the body text.
2440 The server will render an animation of all the frames in a given image
2444 Supports display of exactly 1 frame of any given image array. This
2445 value is mutually exclusive with @code{:icon-multi}.
2448 The server supports persistence of notifications.
2451 The server supports sounds on notifications.
2454 Further vendor-specific caps start with @code{:x-vendor}, like
2455 @code{:x-gnome-foo-cap}.
2459 @node Dynamic Libraries
2460 @section Dynamically Loaded Libraries
2461 @cindex dynamic libraries
2463 A @dfn{dynamically loaded library} is a library that is loaded on
2464 demand, when its facilities are first needed. Emacs supports such
2465 on-demand loading of support libraries for some of its features.
2467 @defvar dynamic-library-alist
2468 This is an alist of dynamic libraries and external library files
2471 Each element is a list of the form
2472 @w{@code{(@var{library} @var{files}@dots{})}}, where the @code{car} is
2473 a symbol representing a supported external library, and the rest are
2474 strings giving alternate filenames for that library.
2476 Emacs tries to load the library from the files in the order they
2477 appear in the list; if none is found, the running session of Emacs
2478 won't have access to that library, and the features that depend on the
2479 library will be unavailable.
2481 Image support on some platforms uses this facility. Here's an example
2482 of setting this variable for supporting images on MS-Windows:
2485 (setq dynamic-library-alist
2486 '((xpm "libxpm.dll" "xpm4.dll" "libXpm-nox4.dll")
2487 (png "libpng12d.dll" "libpng12.dll" "libpng.dll"
2488 "libpng13d.dll" "libpng13.dll")
2489 (jpeg "jpeg62.dll" "libjpeg.dll" "jpeg-62.dll" "jpeg.dll")
2490 (tiff "libtiff3.dll" "libtiff.dll")
2491 (gif "giflib4.dll" "libungif4.dll" "libungif.dll")
2492 (svg "librsvg-2-2.dll")
2493 (gdk-pixbuf "libgdk_pixbuf-2.0-0.dll")
2494 (glib "libglib-2.0-0.dll")
2495 (gobject "libgobject-2.0-0.dll")))
2498 Note that image types @code{pbm} and @code{xbm} do not need entries in
2499 this variable because they do not depend on external libraries and are
2500 always available in Emacs.
2502 Also note that this variable is not meant to be a generic facility for
2503 accessing external libraries; only those already known by Emacs can
2504 be loaded through it.
2506 This variable is ignored if the given @var{library} is statically