]> code.delx.au - gnu-emacs/blob - man/screen.texi
Clarify cursors with multiple windows.
[gnu-emacs] / man / screen.texi
1 @c This is part of the Emacs manual.
2 @c Copyright (C) 1985,86,87,93,94,95,1997,2001 Free Software Foundation, Inc.
3 @c See file emacs.texi for copying conditions.
4 @node Screen, User Input, Acknowledgments, Top
5 @chapter The Organization of the Screen
6 @cindex screen
7 @cindex parts of the screen
8 @c
9
10 On a text-only terminal, the Emacs display occupies the whole screen.
11 On the X Window System, Emacs creates its own X windows to use. We use
12 the term @dfn{frame} to mean an entire text-only screen or an entire X
13 window used by Emacs. Emacs uses both kinds of frames in the same way
14 to display your editing. Emacs normally starts out with just one frame,
15 but you can create additional frames if you wish. @xref{Frames}.
16
17 When you start Emacs, the entire frame except for the top and bottom
18 is devoted to the text you are editing. This area is called the
19 @dfn{window}. At the top there is normally a @dfn{menu bar} where you
20 can access a series of menus; then there may be a @dfn{tool bar}, a
21 row of icons that perform editing commands if you click on them.
22 Below this, the window begins. The last line is a special @dfn{echo
23 area} or @dfn{minibuffer window}, where prompts appear and where you
24 enter information when Emacs asks for it. See below for more
25 information about these special lines.
26
27 You can subdivide the large text window horizontally or vertically
28 into multiple text windows, each of which can be used for a different
29 file (@pxref{Windows}). In this manual, the word ``window'' always
30 refers to the subdivisions of a frame within Emacs.
31
32 At any time, one window is the @dfn{selected window}; the most
33 prominent cursor indicates which window is selected. Most Emacs
34 commands implicitly apply to the text in the selected window (though
35 mouse commands generally operate on whatever window you click them in,
36 whether selected or not). The other windows display text for
37 reference only, unless/until you select them. If you use multiple
38 frames under the X Window System, then giving the input focus to a
39 particular frame selects a window in that frame.
40
41 Each window's last line is a @dfn{mode line}, which describes what
42 is going on in that window. It appears in inverse video, if the
43 terminal supports that; its contents normally begin with
44 @w{@samp{--:-- @ *scratch*}} when Emacs starts. The mode line
45 displays status information such as what buffer is being displayed
46 above it in the window, what major and minor modes are in use, and
47 whether the buffer contains unsaved changes.
48
49 @menu
50 * Point:: The place in the text where editing commands operate.
51 * Echo Area:: Short messages appear at the bottom of the screen.
52 * Mode Line:: Interpreting the mode line.
53 * Menu Bar:: How to use the menu bar.
54 @end menu
55
56 @node Point
57 @section Point
58 @cindex point
59 @cindex cursor
60
61 Within Emacs, the terminal's cursor shows the location at which
62 editing commands will take effect. This location is called @dfn{point}.
63 Many Emacs commands move point through the text, so that you can edit at
64 different places in it. You can also place point by clicking mouse
65 button 1.
66
67 While the cursor appears to point @emph{at} a character, you should
68 think of point as @emph{between} two characters; it points @emph{before}
69 the character that appears under the cursor. For example, if your text
70 looks like @samp{frob} with the cursor over the @samp{b}, then point is
71 between the @samp{o} and the @samp{b}. If you insert the character
72 @samp{!} at that position, the result is @samp{fro!b}, with point
73 between the @samp{!} and the @samp{b}. Thus, the cursor remains over
74 the @samp{b}, as before.
75
76 Sometimes people speak of ``the cursor'' when they mean ``point,'' or
77 speak of commands that move point as ``cursor motion'' commands.
78
79 If you are editing several files in Emacs, each in its own buffer,
80 each buffer has its own point location. A buffer that is not
81 currently displayed remembers its point location in case you display
82 it again later. When Emacs displays multiple windows, each window has
83 its own point location. If the same buffer appears in more than one
84 window, each window has its own position for point in that buffer, and
85 (when possible) its own cursor.
86
87 A text-only terminal has just one cursor, so Emacs puts it
88 in the selected window. The other windows do not show a cursor, even
89 though they do have a location of point. When Emacs updates the
90 screen on a text-only terminal, it has to put the cursor temporarily
91 at the place the output goes. This doesn't mean point is there,
92 though. Once display updating finishes, Emacs puts the cursor where
93 point is.
94
95 On graphical terminals, Emacs shows a cursor in each window; the
96 selected window's cursor is solid or blinking, and the other cursors
97 are just hollow. Thus, the most striking cursor always shows you
98 the selected window, on all kinds of terminals.
99
100 @xref{Cursor Display}, for customization options that control display
101 of the cursor or cursors.
102
103 The term ``point'' comes from the character @samp{.}, which was the
104 command in TECO (the language in which the original Emacs was written)
105 for accessing the value now called ``point.''
106
107 @node Echo Area
108 @section The Echo Area
109 @cindex echo area
110 @c
111
112 The line at the bottom of the frame (below the mode line) is the
113 @dfn{echo area}. It is used to display small amounts of text for
114 several purposes.
115
116 @dfn{Echoing} means displaying the characters that you type. Outside
117 Emacs, the operating system normally echoes all your input. Emacs
118 handles echoing differently.
119
120 Single-character commands do not echo in Emacs, and multi-character
121 commands echo only if you pause while typing them. As soon as you pause
122 for more than a second in the middle of a command, Emacs echoes all the
123 characters of the command so far. This is to @dfn{prompt} you for the
124 rest of the command. Once echoing has started, the rest of the command
125 echoes immediately as you type it. This behavior is designed to give
126 confident users fast response, while giving hesitant users maximum
127 feedback. You can change this behavior by setting a variable
128 (@pxref{Display Custom}).
129
130 @cindex error message in the echo area
131 If a command cannot be executed, it may display an @dfn{error message}
132 in the echo area. Error messages are accompanied by beeping or by
133 flashing the screen. The error also discards any input you have typed
134 ahead.
135
136 Some commands display informative messages in the echo area. These
137 messages look much like error messages, but they are not announced with
138 a beep and do not throw away input. Sometimes the message tells you
139 what the command has done, when this is not obvious from looking at the
140 text being edited. Sometimes the sole purpose of a command is to show
141 you a message giving you specific information---for example, @kbd{C-x =}
142 displays a message describing the character position of point in the text
143 and its current column in the window. Commands that take a long time
144 often display messages ending in @samp{...} while they are working, and
145 add @samp{done} at the end when they are finished.
146
147 @cindex @samp{*Messages*} buffer
148 @cindex saved echo area messages
149 @cindex messages saved from echo area
150 Echo-area informative messages are saved in an editor buffer named
151 @samp{*Messages*}. (We have not explained buffers yet; see
152 @ref{Buffers}, for more information about them.) If you miss a message
153 that appears briefly on the screen, you can switch to the
154 @samp{*Messages*} buffer to see it again. (Successive progress messages
155 are often collapsed into one in that buffer.)
156
157 @vindex message-log-max
158 The size of @samp{*Messages*} is limited to a certain number of lines.
159 The variable @code{message-log-max} specifies how many lines. Once the
160 buffer has that many lines, each line added at the end deletes one line
161 from the beginning. @xref{Variables}, for how to set variables such as
162 @code{message-log-max}.
163
164 The echo area is also used to display the @dfn{minibuffer}, a window that
165 is used for reading arguments to commands, such as the name of a file to be
166 edited. When the minibuffer is in use, the echo area begins with a prompt
167 string that usually ends with a colon; also, the cursor appears in that line
168 because it is the selected window. You can always get out of the
169 minibuffer by typing @kbd{C-g}. @xref{Minibuffer}.
170
171 @node Mode Line
172 @section The Mode Line
173 @cindex mode line
174 @cindex top level
175 @c
176
177 Each text window's last line is a @dfn{mode line}, which describes
178 what is going on in that window. When there is only one text window,
179 the mode line appears right above the echo area; it is the
180 next-to-last line in the frame. The mode line starts and ends with
181 dashes. On a text-mode display, the mode line is in inverse video if
182 the terminal supports that; on a graphics display, the mode line has a
183 3D box appearance to help it stand out. The mode line of the
184 selected window has a slightly different appearance than those of
185 other windows; see @ref{Optional Mode Line}, for more about this.
186
187 Normally, the mode line looks like this:
188
189 @example
190 -@var{cs}:@var{ch} @var{buf} (@var{major} @var{minor})--@var{line}--@var{pos}------
191 @end example
192
193 @noindent
194 This gives information about the buffer being displayed in the window: the
195 buffer's name, what major and minor modes are in use, whether the buffer's
196 text has been changed, and how far down the buffer you are currently
197 looking.
198
199 @var{ch} contains two stars @samp{**} if the text in the buffer has
200 been edited (the buffer is ``modified''), or @samp{--} if the buffer has
201 not been edited. For a read-only buffer, it is @samp{%*} if the buffer
202 is modified, and @samp{%%} otherwise.
203
204 @var{buf} is the name of the window's @dfn{buffer}. In most cases
205 this is the same as the name of a file you are editing. @xref{Buffers}.
206
207 The buffer displayed in the selected window (the window that the
208 cursor is in) is also Emacs's current buffer, the one that editing
209 takes place in. When we speak of what some command does to ``the
210 buffer,'' we are talking about the current buffer.
211
212 @var{line} is @samp{L} followed by the current line number of point.
213 This is present when Line Number mode is enabled (which it normally is).
214 You can optionally display the current column number too, by turning on
215 Column Number mode (which is not enabled by default because it is
216 somewhat slower). @xref{Optional Mode Line}.
217
218 @var{pos} tells you whether there is additional text above the top of
219 the window, or below the bottom. If your buffer is small and it is all
220 visible in the window, @var{pos} is @samp{All}. Otherwise, it is
221 @samp{Top} if you are looking at the beginning of the buffer, @samp{Bot}
222 if you are looking at the end of the buffer, or @samp{@var{nn}%}, where
223 @var{nn} is the percentage of the buffer above the top of the
224 window.@refill
225
226 @var{major} is the name of the @dfn{major mode} in effect in the
227 buffer. At any time, each buffer is in one and only one of the possible
228 major modes. The major modes available include Fundamental mode (the
229 least specialized), Text mode, Lisp mode, C mode, Texinfo mode, and many
230 others. @xref{Major Modes}, for details of how the modes differ and how
231 to select one.@refill
232
233 Some major modes display additional information after the major mode
234 name. For example, Rmail buffers display the current message number and
235 the total number of messages. Compilation buffers and Shell buffers
236 display the status of the subprocess.
237
238 @var{minor} is a list of some of the @dfn{minor modes} that are turned
239 on at the moment in the window's chosen buffer. For example,
240 @samp{Fill} means that Auto Fill mode is on. @samp{Abbrev} means that
241 Word Abbrev mode is on. @samp{Ovwrt} means that Overwrite mode is on.
242 @xref{Minor Modes}, for more information. @samp{Narrow} means that the
243 buffer being displayed has editing restricted to only a portion of its
244 text. This is not really a minor mode, but is like one.
245 @xref{Narrowing}. @samp{Def} means that a keyboard macro is being
246 defined. @xref{Keyboard Macros}.
247
248 In addition, if Emacs is currently inside a recursive editing level,
249 square brackets (@samp{[@dots{}]}) appear around the parentheses that
250 surround the modes. If Emacs is in one recursive editing level within
251 another, double square brackets appear, and so on. Since recursive
252 editing levels affect Emacs globally, not just one buffer, the square
253 brackets appear in every window's mode line or not in any of them.
254 @xref{Recursive Edit}.@refill
255
256 Non-windowing terminals can only show a single Emacs frame at a time
257 (@pxref{Frames}). On such terminals, the mode line displays the name of
258 the selected frame, after @var{ch}. The initial frame's name is
259 @samp{F1}.
260
261 @var{cs} states the coding system used for the file you are editing.
262 A dash indicates the default state of affairs: no code conversion,
263 except for end-of-line translation if the file contents call for that.
264 @samp{=} means no conversion whatsoever. Nontrivial code conversions
265 are represented by various letters---for example, @samp{1} refers to ISO
266 Latin-1. @xref{Coding Systems}, for more information. If you are using
267 an input method, a string of the form @samp{@var{i}>} is added to the
268 beginning of @var{cs}; @var{i} identifies the input method. (Some input
269 methods show @samp{+} or @samp{@@} instead of @samp{>}.) @xref{Input
270 Methods}.
271
272 When you are using a character-only terminal (not a window system),
273 @var{cs} uses three characters to describe, respectively, the coding
274 system for keyboard input, the coding system for terminal output, and
275 the coding system used for the file you are editing.
276
277 When multibyte characters are not enabled, @var{cs} does not appear at
278 all. @xref{Enabling Multibyte}.
279
280 @cindex end-of-line conversion, mode-line indication
281 The colon after @var{cs} can change to another string in certain
282 circumstances. Emacs uses newline characters to separate lines in the buffer.
283 Some files use different conventions for separating lines: either
284 carriage-return linefeed (the MS-DOS convention) or just carriage-return
285 (the Macintosh convention). If the buffer's file uses carriage-return
286 linefeed, the colon changes to either a backslash (@samp{\}) or
287 @samp{(DOS)}, depending on the operating system. If the file uses just
288 carriage-return, the colon indicator changes to either a forward slash
289 (@samp{/}) or @samp{(Mac)}. On some systems, Emacs displays
290 @samp{(Unix)} instead of the colon even for files that use newline to
291 separate lines.
292
293 @vindex eol-mnemonic-unix
294 @vindex eol-mnemonic-dos
295 @vindex eol-mnemonic-mac
296 @vindex eol-mnemonic-undecided
297 You can customize the mode line display for each of the end-of-line
298 formats by setting each of the variables @code{eol-mnemonic-unix},
299 @code{eol-mnemonic-dos}, @code{eol-mnemonic-mac}, and
300 @code{eol-mnemonic-undecided} to any string you find appropriate.
301 @xref{Variables}, for an explanation of how to set variables.
302
303 @xref{Optional Mode Line}, for features that add other handy
304 information to the mode line, such as the current column number of
305 point, the current time, and whether new mail for you has arrived.
306
307 The mode line is mouse-sensitive; when you move the mouse across
308 various parts of it, Emacs displays help text to say what a click in
309 that place will do. @xref{Mode Line Mouse}.
310
311 @node Menu Bar
312 @section The Menu Bar
313 @cindex menu bar
314
315 Each Emacs frame normally has a @dfn{menu bar} at the top which you
316 can use to perform certain common operations. There's no need to list
317 them here, as you can more easily see for yourself.
318
319 @kindex M-`
320 @kindex F10
321 @findex tmm-menubar
322 When you are using a window system, you can use the mouse to choose a
323 command from the menu bar. An arrow pointing right, after the menu
324 item, indicates that the item leads to a subsidiary menu; @samp{...} at
325 the end means that the command will read arguments from the keyboard
326 before it actually does anything.
327
328 To view the full command name and documentation for a menu item, type
329 @kbd{C-h k}, and then select the menu bar with the mouse in the usual
330 way (@pxref{Key Help}).
331
332 On text-only terminals with no mouse, you can use the menu bar by
333 typing @kbd{M-`} or @key{F10} (these run the command
334 @code{tmm-menubar}). This command enters a mode in which you can select
335 a menu item from the keyboard. A provisional choice appears in the echo
336 area. You can use the left and right arrow keys to move through the
337 menu to different choices. When you have found the choice you want,
338 type @key{RET} to select it.
339
340 Each menu item also has an assigned letter or digit which designates
341 that item; it is usually the initial of some word in the item's name.
342 This letter or digit is separated from the item name by @samp{=>}. You
343 can type the item's letter or digit to select the item.
344
345 Some of the commands in the menu bar have ordinary key bindings as
346 well; if so, the menu lists one equivalent key binding in parentheses
347 after the item itself.