|
408
|
1 @c This is part of the XEmacs manual.
|
|
|
2 @c Copyright (C) 1985, 1986, 1987, 1993, 1994, 1995 Free Software Foundation, Inc.
|
|
|
3 @c See file xemacs.texi for copying conditions.
|
|
0
|
4 @node Entering Emacs, Exiting, Pull-down Menus, Top
|
|
|
5 @chapter Entering and Exiting Emacs
|
|
|
6 @cindex entering XEmacs
|
|
408
|
7 @cindex starting XEmacs
|
|
|
8
|
|
|
9 The usual way to invoke XEmacs is to type @kbd{xemacs @key{RET}} at
|
|
|
10 the shell. XEmacs clears the screen and then displays an initial
|
|
|
11 advisory message and copyright notice. You can begin typing XEmacs
|
|
|
12 commands immediately afterward.
|
|
0
|
13
|
|
408
|
14 Some operating systems insist on discarding all type-ahead when XEmacs
|
|
|
15 starts up; they give XEmacs no way to prevent this. Therefore, it is
|
|
|
16 advisable to wait until XEmacs clears the screen before typing your first
|
|
|
17 editing command.
|
|
0
|
18
|
|
408
|
19 If you run XEmacs from a shell window under the X Window System, run it
|
|
|
20 in the background with @samp{xemacs&}. This way, XEmacs does not tie up
|
|
|
21 the shell window, so you can use that to run other shell commands while
|
|
|
22 XEmacs operates its own X windows. You can begin typing XEmacs commands
|
|
|
23 as soon as you direct your keyboard input to the XEmacs frame.
|
|
0
|
24
|
|
|
25 @vindex initial-major-mode
|
|
|
26 Before Emacs reads the first command, you have not had a chance to
|
|
408
|
27 give a command to specify a file to edit. Since Emacs must always have
|
|
|
28 a current buffer for editing, it presents a buffer, by default, a buffer
|
|
|
29 named @samp{*scratch*}. The buffer is in Lisp Interaction mode; you can
|
|
|
30 use it to type Lisp expressions and evaluate them, or you can ignore
|
|
2757
|
31 that capability and simply doodle. (Which is where the name comes from;
|
|
|
32 a ``scratch pad'' is a set of paper for doodling on, something not
|
|
|
33 necessarily clear to all the English-speakers who read this.)
|
|
|
34
|
|
|
35 You can specify a different major mode for this buffer by setting the
|
|
|
36 variable @code{initial-major-mode} in your init file. @xref{Init File}.
|
|
408
|
37
|
|
|
38 It is possible to specify files to be visited, Lisp files to be
|
|
|
39 loaded, and functions to be called, by giving Emacs arguments in the
|
|
|
40 shell command line. @xref{Command Switches}. But we don't recommend
|
|
|
41 doing this. The feature exists mainly for compatibility with other
|
|
|
42 editors.
|
|
0
|
43
|
|
408
|
44 Many other editors are designed to be started afresh each time you
|
|
|
45 want to edit. You edit one file and then exit the editor. The next
|
|
|
46 time you want to edit either another file or the same one, you must run
|
|
|
47 the editor again. With these editors, it makes sense to use a
|
|
|
48 command-line argument to say which file to edit.
|
|
|
49
|
|
|
50 But starting a new Emacs each time you want to edit a different file
|
|
|
51 does not make sense. For one thing, this would be annoyingly slow. For
|
|
|
52 another, this would fail to take advantage of Emacs's ability to visit
|
|
|
53 more than one file in a single editing session. And it would lose the
|
|
|
54 other accumulated context, such as registers, undo history, and the mark
|
|
|
55 ring.
|
|
|
56
|
|
|
57 The recommended way to use XEmacs is to start it only once, just
|
|
|
58 after you log in, and do all your editing in the same Emacs session.
|
|
|
59 Each time you want to edit a different file, you visit it with the
|
|
|
60 existing Emacs, which eventually comes to have many files in it ready
|
|
|
61 for editing. Usually you do not kill the Emacs until you are about to
|
|
|
62 log out. @xref{Files}, for more information on visiting more than one
|
|
|
63 file.
|
|
0
|
64
|
|
|
65 @node Exiting, Command Switches, Entering Emacs, Top
|
|
|
66 @section Exiting Emacs
|
|
|
67 @cindex exiting
|
|
|
68 @cindex killing Emacs
|
|
|
69 @cindex suspending
|
|
408
|
70 @cindex leaving Emacs
|
|
|
71 @cindex quitting Emacs
|
|
0
|
72 @cindex shrinking XEmacs frame
|
|
|
73
|
|
|
74 There are two commands for exiting Emacs because there are two kinds
|
|
|
75 of exiting: @dfn{suspending} Emacs and @dfn{killing} Emacs.
|
|
408
|
76
|
|
|
77 @dfn{Suspending} means stopping Emacs temporarily and returning
|
|
|
78 control to its parent process (usually a shell), allowing you to resume
|
|
|
79 editing later in the same Emacs job, with the same buffers, same kill
|
|
|
80 ring, same undo history, and so on. This is the usual way to exit.
|
|
|
81
|
|
|
82 @dfn{Killing} Emacs means destroying the Emacs job. You can run Emacs
|
|
|
83 again later, but you will get a fresh Emacs; there is no way to resume
|
|
|
84 the same editing session after it has been killed.
|
|
0
|
85
|
|
|
86 @table @kbd
|
|
|
87 @item C-z
|
|
408
|
88 Suspend Emacs or iconify a frame
|
|
|
89 (@code{suspend-emacs-or-iconify-frame}). If used under the X window
|
|
|
90 system, shrink the X window containing the Emacs frame to an icon (see
|
|
|
91 below).
|
|
0
|
92 @item C-x C-c
|
|
|
93 Kill Emacs (@code{save-buffers-kill-emacs}).
|
|
|
94 @end table
|
|
|
95
|
|
|
96 If you use XEmacs under the X window system, @kbd{C-z} shrinks
|
|
|
97 the X window containing the Emacs frame to an icon. The Emacs process
|
|
|
98 is stopped temporarily, and control is returned to the window manager.
|
|
|
99 If more than one frame is associated with the Emacs process, only the
|
|
408
|
100 frame from which you used @kbd{C-z} is iconified.
|
|
0
|
101
|
|
|
102 To activate the "suspended" Emacs, use the appropriate window manager
|
|
|
103 mouse gestures. Usually left-clicking on the icon reactivates and
|
|
|
104 reopens the X window containing the Emacs frame, but the window manager
|
|
|
105 you use determines what exactly happens. To actually kill the Emacs
|
|
408
|
106 process, use @kbd{C-x C-c} or the @b{Exit XEmacs} item on the @b{File}
|
|
0
|
107 menu.
|
|
|
108
|
|
|
109 @kindex C-z
|
|
|
110 @findex suspend-emacs
|
|
408
|
111 To suspend Emacs, type @kbd{C-z} (@code{suspend-emacs}). This takes
|
|
|
112 you back to the shell from which you invoked Emacs. You can resume
|
|
|
113 Emacs with the shell command @samp{%xemacs} in most common shells.
|
|
|
114
|
|
|
115 On systems that do not support suspending programs, @kbd{C-z} starts
|
|
|
116 an inferior shell that communicates directly with the terminal.
|
|
|
117 Emacs waits until you exit the subshell. (The way to do that is
|
|
|
118 probably with @kbd{C-d} or @samp{exit}, but it depends on which shell
|
|
|
119 you use.) The only way on these systems to get back to the shell from
|
|
|
120 which Emacs was run (to log out, for example) is to kill Emacs.
|
|
|
121
|
|
|
122 Suspending also fails if you run Emacs under a shell that doesn't
|
|
|
123 support suspending programs, even if the system itself does support it.
|
|
|
124 In such a case, you can set the variable @code{cannot-suspend} to a
|
|
|
125 non-@code{nil} value to force @kbd{C-z} to start an inferior shell.
|
|
|
126 (One might also describe Emacs's parent shell as ``inferior'' for
|
|
|
127 failing to support job control properly, but that is a matter of taste.)
|
|
|
128
|
|
|
129 When Emacs communicates directly with an X server and creates its own
|
|
|
130 dedicated X windows, @kbd{C-z} has a different meaning. Suspending an
|
|
|
131 applications that uses its own X windows is not meaningful or useful.
|
|
|
132 Instead, @kbd{C-z} runs the command @code{iconify-or-deiconify-frame},
|
|
|
133 which temporarily closes up the selected Emacs frame.
|
|
|
134 The way to get back to a shell window is with the window manager.
|
|
0
|
135
|
|
|
136 @kindex C-x C-c
|
|
|
137 @findex save-buffers-kill-emacs
|
|
|
138 To kill Emacs, type @kbd{C-x C-c} (@code{save-buffers-kill-emacs}). A
|
|
408
|
139 two-character key is used for this to make it harder to type. Selecting
|
|
|
140 the @b{Exit XEmacs} option of the @b{File} menu is an alternate way of
|
|
|
141 issuing the command.
|
|
0
|
142
|
|
|
143 Unless a numeric argument is used, this command first offers to save any
|
|
408
|
144 modified file-visiting buffers. If you do not save all buffers, you are
|
|
|
145 asked for reconfirmation with @kbd{yes} before killing Emacs, since any
|
|
|
146 changes not saved will be lost forever. If any subprocesses are still
|
|
|
147 running, @kbd{C-x C-c} asks you to confirm killing them, since killing
|
|
|
148 Emacs will kill the subprocesses immediately.
|
|
0
|
149
|
|
408
|
150 There is no way to restart an Emacs session once you have killed it.
|
|
|
151 You can, however, arrange for Emacs to record certain session
|
|
|
152 information, such as which files are visited, when you kill it, so that
|
|
|
153 the next time you restart Emacs it will try to visit the same files and
|
|
|
154 so on.
|
|
|
155 @c @xref{Saving Emacs Sessions}.
|
|
0
|
156
|
|
408
|
157 The operating system usually listens for certain special characters
|
|
|
158 whose meaning is to kill or suspend the program you are running.
|
|
|
159 @b{This operating system feature is turned off while you are in Emacs.}
|
|
|
160 The meanings of @kbd{C-z} and @kbd{C-x C-c} as keys in Emacs were
|
|
|
161 inspired by the use of @kbd{C-z} and @kbd{C-c} on several operating
|
|
|
162 systems as the characters for stopping or killing a program, but that is
|
|
|
163 their only relationship with the operating system. You can customize
|
|
|
164 these keys to run any commands of your choice (@pxref{Keymaps}).
|
