screen.texi 16 KB

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