info.texi 52 KB

12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455565758596061626364656667686970717273747576777879808182838485868788899091929394959697989910010110210310410510610710810911011111211311411511611711811912012112212312412512612712812913013113213313413513613713813914014114214314414514614714814915015115215315415515615715815916016116216316416516616716816917017117217317417517617717817918018118218318418518618718818919019119219319419519619719819920020120220320420520620720820921021121221321421521621721821922022122222322422522622722822923023123223323423523623723823924024124224324424524624724824925025125225325425525625725825926026126226326426526626726826927027127227327427527627727827928028128228328428528628728828929029129229329429529629729829930030130230330430530630730830931031131231331431531631731831932032132232332432532632732832933033133233333433533633733833934034134234334434534634734834935035135235335435535635735835936036136236336436536636736836937037137237337437537637737837938038138238338438538638738838939039139239339439539639739839940040140240340440540640740840941041141241341441541641741841942042142242342442542642742842943043143243343443543643743843944044144244344444544644744844945045145245345445545645745845946046146246346446546646746846947047147247347447547647747847948048148248348448548648748848949049149249349449549649749849950050150250350450550650750850951051151251351451551651751851952052152252352452552652752852953053153253353453553653753853954054154254354454554654754854955055155255355455555655755855956056156256356456556656756856957057157257357457557657757857958058158258358458558658758858959059159259359459559659759859960060160260360460560660760860961061161261361461561661761861962062162262362462562662762862963063163263363463563663763863964064164264364464564664764864965065165265365465565665765865966066166266366466566666766866967067167267367467567667767867968068168268368468568668768868969069169269369469569669769869970070170270370470570670770870971071171271371471571671771871972072172272372472572672772872973073173273373473573673773873974074174274374474574674774874975075175275375475575675775875976076176276376476576676776876977077177277377477577677777877978078178278378478578678778878979079179279379479579679779879980080180280380480580680780880981081181281381481581681781881982082182282382482582682782882983083183283383483583683783883984084184284384484584684784884985085185285385485585685785885986086186286386486586686786886987087187287387487587687787887988088188288388488588688788888989089189289389489589689789889990090190290390490590690790890991091191291391491591691791891992092192292392492592692792892993093193293393493593693793893994094194294394494594694794894995095195295395495595695795895996096196296396496596696796896997097197297397497597697797897998098198298398498598698798898999099199299399499599699799899910001001100210031004100510061007100810091010101110121013101410151016101710181019102010211022102310241025102610271028102910301031103210331034103510361037103810391040104110421043104410451046104710481049105010511052105310541055105610571058105910601061106210631064106510661067106810691070107110721073107410751076107710781079108010811082108310841085108610871088108910901091109210931094109510961097109810991100110111021103110411051106110711081109111011111112111311141115111611171118111911201121112211231124112511261127112811291130113111321133113411351136113711381139114011411142114311441145114611471148114911501151115211531154115511561157115811591160116111621163116411651166116711681169117011711172117311741175117611771178117911801181118211831184118511861187118811891190119111921193119411951196119711981199120012011202120312041205120612071208120912101211121212131214121512161217121812191220122112221223122412251226122712281229123012311232123312341235123612371238123912401241124212431244124512461247124812491250125112521253125412551256125712581259126012611262126312641265126612671268126912701271127212731274127512761277127812791280
  1. \input texinfo.tex @c -*-texinfo-*-
  2. @c We must \input texinfo.tex instead of texinfo, otherwise make
  3. @c distcheck in the Texinfo distribution fails, because the texinfo Info
  4. @c file is made first, and texi2dvi must include . first in the path.
  5. @comment %**start of header
  6. @setfilename info.info
  7. @settitle Info
  8. @include docstyle.texi
  9. @syncodeindex fn cp
  10. @syncodeindex vr cp
  11. @syncodeindex ky cp
  12. @comment %**end of header
  13. @copying
  14. This file describes how to use Info, the menu-driven GNU
  15. documentation system.
  16. Copyright @copyright{} 1989, 1992, 1996--2015 Free Software Foundation, Inc.
  17. @quotation
  18. Permission is granted to copy, distribute and/or modify this document
  19. under the terms of the GNU Free Documentation License, Version 1.3 or
  20. any later version published by the Free Software Foundation; with no
  21. Invariant Sections, with the Front-Cover Texts being ``A GNU Manual,''
  22. and with the Back-Cover Texts as in (a) below. A copy of the license
  23. is included in the section entitled ``GNU Free Documentation License''.
  24. (a) The FSF's Back-Cover Text is: ``You have the freedom to copy and
  25. modify this GNU manual.''
  26. @end quotation
  27. @end copying
  28. @dircategory Texinfo documentation system
  29. @direntry
  30. * Info: (info). How to use the documentation browsing system.
  31. @end direntry
  32. @titlepage
  33. @title Info
  34. @subtitle The online, hyper-text GNU documentation system
  35. @author Brian Fox
  36. @author and the GNU Texinfo community
  37. @page
  38. @vskip 0pt plus 1filll
  39. @insertcopying
  40. @end titlepage
  41. @contents
  42. @ifnottex
  43. @node Top
  44. @top Info: An Introduction
  45. The GNU Project distributes most of its manuals in the
  46. @dfn{Info format}, which you read using an @dfn{Info reader}. You are
  47. probably using an Info reader to read this now.
  48. There are two primary Info readers: @code{info}, a stand-alone program
  49. designed just to read Info files (@pxref{Top,,What is Info?,
  50. info-stnd, GNU Info}), and the @code{info} package in GNU Emacs, a
  51. general-purpose editor. At present, only the Emacs reader supports
  52. using a mouse.
  53. @ifinfo
  54. If you are new to the Info reader and want to learn how to use it,
  55. type the command @kbd{h} now. It brings you to a programmed
  56. instruction sequence.
  57. To read about advanced Info commands, type @kbd{n} twice. This
  58. brings you to @cite{Advanced Info Commands}, skipping over the ``Getting
  59. Started'' chapter.
  60. Type @kbd{H} to see a summary of all available commands.
  61. @end ifinfo
  62. @end ifnottex
  63. @insertcopying
  64. @menu
  65. * Getting Started:: Getting started using an Info reader.
  66. * Advanced:: Advanced Info commands.
  67. * Further Reading:: Where to learn more about Info files.
  68. * GNU Free Documentation License:: The license for this documentation.
  69. * Index:: An index of topics, commands, and variables.
  70. @end menu
  71. @node Getting Started
  72. @chapter Getting Started
  73. This first part of this Info manual describes how to get around inside
  74. of Info. The second part of the manual describes various advanced
  75. Info commands. The third part contains references to other sources,
  76. which explain how to generate Info files from Texinfo files.
  77. @ifnotinfo
  78. This manual is primarily designed for browsing with an Info reader
  79. program on a computer, so that you can try Info commands while reading
  80. about them. Reading it on paper or with an HTML browser is less
  81. effective, since you must take it on faith that the commands described
  82. really do what the manual says. By all means go through this manual
  83. now that you have it; but please try going through the Info version
  84. as well.
  85. @cindex Info reader, how to invoke
  86. @cindex entering Info
  87. There are two ways of looking at the online version of this manual:
  88. @enumerate
  89. @item
  90. Type @code{info} at your shell's command line. This approach uses a
  91. stand-alone program designed just to read Info files.
  92. @item
  93. Type @code{emacs} at the command line; then type @kbd{C-h i}
  94. (@kbd{Control-h}, followed by @kbd{i}). This approach uses the Info
  95. mode of the Emacs editor.
  96. @end enumerate
  97. In either case, then type @kbd{mInfo} (just the letters), followed by
  98. @key{RET}---the ``Return'' or ``Enter'' key. At this point, you should
  99. be ready to follow the instructions in this manual as you read them on
  100. the screen.
  101. @c FIXME! (pesch@cygnus.com, 14 dec 1992)
  102. @c Is it worth worrying about what-if the beginner goes to somebody
  103. @c else's Emacs session, which already has an Info running in the middle
  104. @c of something---in which case these simple instructions won't work?
  105. @end ifnotinfo
  106. @menu
  107. * Help-Small-Screen:: Starting Info on a Small Screen.
  108. * Help:: How to use Info.
  109. * Help-P:: Returning to the Previous node.
  110. * Help-^L:: The Space, DEL, B and ^L commands.
  111. * Help-Inv:: Invisible text in Emacs Info.
  112. * Help-M:: Menus.
  113. * Help-Xref:: Following cross-references.
  114. * Help-Int:: Some intermediate Info commands.
  115. * Help-Q:: Quitting Info.
  116. @end menu
  117. @node Help-Small-Screen
  118. @section Starting Info on a Small Screen
  119. @ifnotinfo
  120. (In Info, you only see this section if your terminal has a small
  121. number of lines; most readers pass by it without seeing it.)
  122. @end ifnotinfo
  123. @cindex small screen, moving around
  124. Since your terminal has a relatively small number of lines on its
  125. screen, it is necessary to give you special advice at the beginning.
  126. If the entire text you are looking at fits on the screen, the text
  127. @samp{All} will be displayed near the bottom of the screen, on the
  128. mode line (usually, the line in inverse video). If you see the text
  129. @samp{Top} instead, it means that there is more text below that does
  130. not fit. To move forward through the text and see another screenful,
  131. press @key{SPC}, the Space bar. To move back up, press the key
  132. labeled @samp{Backspace} or @samp{DEL} (on some keyboards, this key
  133. might be labeled @samp{Delete}). In a graphical Emacs, you can also use
  134. @kbd{S-@key{SPC}} (press and hold the @key{Shift} key and then press
  135. @key{SPC}) to move backwards, but this does not work in the
  136. stand-alone Info reader (nor in Emacs, if you are using it in a
  137. text-mode terminal).
  138. @ifinfo
  139. Here are 40 lines of junk, so you can try @key{SPC} and @key{DEL} and
  140. see what they do. At the end are instructions of what you should do
  141. next.
  142. @format
  143. This is line 20
  144. This is line 21
  145. This is line 22
  146. This is line 23
  147. This is line 24
  148. This is line 25
  149. This is line 26
  150. This is line 27
  151. This is line 28
  152. This is line 29
  153. This is line 30
  154. This is line 31
  155. This is line 32
  156. This is line 33
  157. This is line 34
  158. This is line 35
  159. This is line 36
  160. This is line 37
  161. This is line 38
  162. This is line 39
  163. This is line 40
  164. This is line 41
  165. This is line 42
  166. This is line 43
  167. This is line 44
  168. This is line 45
  169. This is line 46
  170. This is line 47
  171. This is line 48
  172. This is line 49
  173. This is line 50
  174. This is line 51
  175. This is line 52
  176. This is line 53
  177. This is line 54
  178. This is line 55
  179. This is line 56
  180. This is line 57
  181. This is line 58
  182. This is line 59
  183. @end format
  184. If you have managed to get here, go back to the beginning with
  185. @key{DEL} (or @key{BACKSPACE}), and come back here again, then you
  186. understand about the @samp{Space} and @samp{Backspace} keys. So now
  187. type an @kbd{n}---just one character; don't type the quotes and don't
  188. type the Return key afterward---to get to the normal start of the
  189. course.
  190. @end ifinfo
  191. @node Help
  192. @section How to use Info
  193. You are talking to the program Info, for reading documentation.
  194. There are two ways to use Info: from within Emacs or as a
  195. stand-alone reader that you can invoke from a shell using the command
  196. @command{info}.
  197. @cindex node, in Info documents
  198. Right now you are looking at one @dfn{Node} of Information.
  199. A node contains text describing a specific topic at a specific
  200. level of detail. This node's topic is ``how to use Info''. The mode
  201. line says that this is node @samp{Help} in the file @file{info}.
  202. @cindex header of Info node
  203. The top line of a node is its @dfn{header}. This node's header
  204. (look at it now) says that the @samp{Next} node after this one is the
  205. node called @samp{Help-P}. An advanced Info command lets you go to
  206. any node whose name you know. In the stand-alone Info reader program,
  207. the header line shows the names of this node and the Info file as
  208. well. In Emacs, the header line is displayed with a special typeface,
  209. and remains at the top of the window all the time even if you scroll
  210. through the node.
  211. Besides a @samp{Next}, a node can have a @samp{Previous} link, or an
  212. @samp{Up} link, or both. As you can see, this node has all of these
  213. links.
  214. @kindex n @r{(Info mode)}
  215. Now it is time to move on to the @samp{Next} node, named @samp{Help-P}.
  216. @format
  217. >> Type @kbd{n} to move there. Type just one character;
  218. do not type the quotes and do not type a @key{RET} afterward.
  219. @end format
  220. @noindent
  221. @samp{>>} in the margin means it is really time to try a command.
  222. @format
  223. >> If you are in Emacs and have a mouse, and if you already practiced
  224. typing @kbd{n} to get to the next node, click now with the left
  225. mouse button on the @samp{Next} link to do the same ``the mouse way''.
  226. @end format
  227. @node Help-P
  228. @section Returning to the Previous node
  229. @kindex p @r{(Info mode)}
  230. This node is called @samp{Help-P}. The @samp{Previous} node, as you see,
  231. is @samp{Help}, which is the one you just came from using the @kbd{n}
  232. command. Another @kbd{n} command now would take you to the next
  233. node, @samp{Help-^L}.
  234. @format
  235. >> But do not type @kbd{n} yet. First, try the @kbd{p} command, or
  236. (in Emacs) click on the @samp{Prev} link. That takes you to
  237. the @samp{Previous} node. Then use @kbd{n} to return here.
  238. @end format
  239. If you read this in Emacs, you will see an @samp{Info} item in the
  240. menu bar, close to its right edge. Clicking the mouse on the
  241. @samp{Info} menu-bar item opens a menu of commands which include
  242. @samp{Next} and @samp{Previous} (and also some others which you didn't yet
  243. learn about).
  244. This all probably seems insultingly simple so far, but @emph{please
  245. don't} start skimming. Things will get complicated soon enough!
  246. Also, please do not try a new command until you are told it is time
  247. to. You could make Info skip past an important warning that was
  248. coming up.
  249. @format
  250. >> Now do an @kbd{n}, or (in Emacs) click the middle mouse button on
  251. the @samp{Next} link, to get to the node @samp{Help-^L} and learn more.
  252. @end format
  253. @node Help-^L
  254. @section The Space, DEL, B and ^L commands
  255. This node's mode line tells you that you are now at node
  256. @samp{Help-^L}, and the header line tells you that @kbd{p} would get
  257. you back to @samp{Help-P}. The node's title is highlighted and may be
  258. underlined as well; it says what the node is about.
  259. This is a big node and it does not all fit on your display screen.
  260. You can tell that there is more that is not visible because you
  261. can see the text @samp{Top} rather than @samp{All} near the bottom of
  262. the screen.
  263. @kindex SPC @r{(Info mode)}
  264. @kindex DEL @r{(Info mode)}
  265. @kindex BACKSPACE @r{(Info mode)}
  266. @findex Info-scroll-up
  267. @findex Info-scroll-down
  268. The @key{SPC}, @key{BACKSPACE} (or @key{DEL})@footnote{The key which
  269. we call ``Backspace or DEL'' in this manual is labeled differently on
  270. different keyboards. Look for a key which is a little ways above the
  271. @key{ENTER} or @key{RET} key and which you normally use outside Emacs
  272. to erase the character before the cursor, i.e., the character you
  273. typed last. It might be labeled @samp{Backspace} or @samp{<-} or
  274. @samp{DEL}, or sometimes @samp{Delete}.} and @kbd{b} commands exist to
  275. allow you to ``move around'' in a node that does not all fit on the
  276. screen at once. @key{SPC} moves forward, to show what was below the
  277. bottom of the screen. @key{DEL} or @key{BACKSPACE} moves backward, to
  278. show what was above the top of the screen (there is not anything above
  279. the top until you have typed some spaces).
  280. @format
  281. >> Now try typing a @key{SPC} (afterward, type a @key{BACKSPACE} to
  282. return here).
  283. @end format
  284. When you type the @key{SPC}, the two lines that were at the bottom of
  285. the screen appear at the top, followed by more lines. @key{DEL} or
  286. @key{BACKSPACE} takes the two lines from the top and moves them to the
  287. bottom, @emph{usually}, but if there are not a full screen's worth of
  288. lines above them they may not make it all the way to the bottom.
  289. If you are reading this in Emacs, note that the header line is
  290. always visible, never scrolling off the display. That way, you can
  291. always see the @samp{Next}, @samp{Prev}, and @samp{Up} links, and you
  292. can conveniently go to one of these links at any time by
  293. clicking the middle mouse button on the link.
  294. @cindex reading Info documents top to bottom
  295. @cindex Info documents as tutorials
  296. @key{SPC} and @key{DEL} not only move forward and backward through
  297. the current node. They also move between nodes. @key{SPC} at the end
  298. of a node moves to the next node; @key{DEL} (or @key{BACKSPACE}) at
  299. the beginning of a node moves to the previous node. In effect, these
  300. commands scroll through all the nodes in an Info file as a single
  301. logical sequence. You can read an entire manual top to bottom by just
  302. typing @key{SPC}, and move backward through the entire manual from
  303. bottom to top by typing @key{DEL} (or @key{BACKSPACE}).
  304. In this sequence, a node's subnodes appear following their parent.
  305. If a node has a menu, @key{SPC} takes you into the subnodes listed in
  306. the menu, one by one. Once you reach the end of a node, and have seen
  307. all of its subnodes, @key{SPC} takes you to the next node or to the
  308. parent's next node.
  309. @kindex PAGEUP @r{(Info mode)}
  310. @kindex PAGEDOWN @r{(Info mode)}
  311. Many keyboards nowadays have two scroll keys labeled @samp{PageUp}
  312. and @samp{PageDown} (or maybe @samp{Prior} and @samp{Next}). If your
  313. keyboard has these keys, you can use them to move forward and backward
  314. through the text of one node, like @key{SPC} and @key{BACKSPACE} (or
  315. @key{DEL}). However, @key{PAGEUP} and @key{PAGEDOWN} keys never
  316. scroll beyond the beginning or the end of the current node.
  317. @kindex C-l @r{(Info mode)}
  318. If your screen is ever garbaged, you can tell Info to display it
  319. again by typing @kbd{C-l} (@kbd{Control-L}---that is, hold down
  320. @key{CTRL} and type @kbd{L} or @kbd{l}).
  321. @format
  322. >> Type @kbd{C-l} now.
  323. @end format
  324. @kindex b @r{(Info mode)}
  325. To move back to the beginning of the node you are on, you can type
  326. the @key{BACKSPACE} key (or @key{DEL}) many times. You can also type
  327. @kbd{b} just once. @kbd{b} stands for ``beginning.''
  328. @format
  329. >> Try that now. (We have put in enough verbiage to push this past
  330. the first screenful, but screens are so big nowadays that perhaps it
  331. isn't enough. You may need to shrink your Emacs or Info window.)
  332. Then come back, by typing @key{SPC} one or more times.
  333. @end format
  334. @kindex ? @r{(Info mode)}
  335. @findex Info-summary
  336. You have just learned a considerable number of commands. If you
  337. want to use one but have trouble remembering which, you should type
  338. @kbd{?}, which displays a brief list of commands. When you are
  339. finished looking at the list, make it go away by typing @key{SPC}
  340. repeatedly.
  341. @format
  342. >> Type a @key{?} now. Press @key{SPC} to see consecutive screenfuls of
  343. the list until finished. Then type @key{SPC} several times. If
  344. you are using Emacs, the help will then go away automatically.
  345. If you are using the stand-alone Info reader, type @kbd{x} to
  346. return here.
  347. @end format
  348. From now on, you will encounter large nodes without warning, and
  349. will be expected to know how to use @key{SPC} and @key{BACKSPACE} to
  350. move around in them without being told. Since not all terminals have
  351. the same size screen, it would be impossible to warn you anyway.
  352. @format
  353. >> Now type @kbd{n}, or click the middle mouse button on the @samp{Next} link,
  354. to visit the next node.
  355. @end format
  356. @node Help-Inv
  357. @section Invisible text in Emacs Info
  358. Before discussing menus, we need to make some remarks that are only
  359. relevant to users reading Info using Emacs. Users of the stand-alone
  360. version can skip this node by typing @kbd{]} now.
  361. @cindex invisible text in Emacs
  362. In Emacs, certain text that appears in the stand-alone version is
  363. normally hidden, technically because it has the @samp{invisibility}
  364. property. Invisible text is really a part of the text. It becomes
  365. visible (by default) after killing and yanking, it appears in printed
  366. output, it gets saved to file just like any other text, and so on.
  367. Thus it is useful to know it is there.
  368. @findex visible-mode
  369. You can make invisible text visible by using the command @kbd{M-x
  370. visible-mode}. Visible mode is a minor mode, so using the command a
  371. second time will make the text invisible again. Watch the effects of
  372. the command on the ``menu'' below and the top line of this node.
  373. If you prefer to @emph{always} see the invisible text, you can set
  374. @code{Info-hide-note-references} to @code{nil}. Enabling Visible mode
  375. permanently is not a real alternative, because Emacs Info also uses
  376. (although less extensively) another text property that can change the
  377. text being displayed, the @samp{display} property. Only the
  378. invisibility property is affected by Visible mode. When, in this
  379. tutorial, we refer to the @samp{Emacs} behavior, we mean the
  380. @emph{default} Emacs behavior.
  381. Now type @kbd{]}, to learn about the @kbd{]} and @kbd{[} commands.
  382. @menu
  383. * ]: Help-]. Node telling about ].
  384. * stuff: Help-]. Same node.
  385. * Help-]:: Yet again, same node.
  386. @end menu
  387. @node Help-], , , Help-Inv
  388. @subsection The @kbd{]} and @kbd{[} commands
  389. If you type @kbd{n} now, you get an error message saying that this
  390. node has no next node. Similarly, if you type @kbd{p}, the error
  391. message tells you that there is no previous node. (The exact message
  392. depends on the Info reader you use.) This is because @kbd{n} and
  393. @kbd{p} carry you to the next and previous node @emph{at the same
  394. level}. The present node is contained in a menu (see next) of the
  395. node you came from, and hence is considered to be at a lower level.
  396. It is the only node in the previous node's menu (even though it was
  397. listed three times). Hence it has no next or previous node that
  398. @kbd{n} or @kbd{p} could move to.
  399. If you systematically move through a manual by typing @kbd{n}, you run
  400. the risk of skipping many nodes. You do not run this risk if you
  401. systematically use @kbd{@key{SPC}}, because, when you scroll to the
  402. bottom of a node and type another @kbd{@key{SPC}}, then this carries
  403. you to the following node in the manual @emph{regardless of level}.
  404. If you immediately want to go to that node, without having to scroll
  405. to the bottom of the screen first, you can type @kbd{]}.
  406. Similarly, @kbd{@key{BACKSPACE}} carries you to the preceding node
  407. regardless of level, after you scrolled to the beginning of the
  408. present node. If you want to go to the preceding node immediately,
  409. you can type @kbd{[}.
  410. For instance, typing this sequence will come back here in three steps:
  411. @kbd{[ n [}. To do the same backward, type @kbd{] p ]}.
  412. Now type @kbd{]} to go to the next node and learn about menus.
  413. @node Help-M
  414. @section Menus and the @kbd{m} command
  415. @cindex menus in an Info document
  416. @cindex Info menus
  417. With only the @kbd{n} (next), @kbd{p} (previous), @kbd{@key{SPC}},
  418. @kbd{@key{BACKSPACE}}, @kbd{]} and @kbd{[} commands for moving between
  419. nodes, nodes are restricted to a linear sequence. Menus allow a
  420. branching structure. A menu is a list of other nodes you can move to.
  421. It is actually just part of the text of the node formatted specially
  422. so that Info can interpret it. The beginning of a menu is always
  423. identified by a line which starts with @w{@samp{* Menu:}}. A node
  424. contains a menu if and only if it has a line in it which starts that
  425. way. The only menu you can use at any moment is the one in the node
  426. you are in. To use a menu in any other node, you must move to that
  427. node first.
  428. After the start of the menu, each line that starts with a @samp{*}
  429. identifies one subtopic. The line usually contains a brief name for
  430. the subtopic (followed by a @samp{:}, normally hidden in Emacs), the
  431. name of the node that talks about that subtopic (again, normally
  432. hidden in Emacs), and optionally some further description of the
  433. subtopic. Lines in the menu that do not start with a @samp{*} have no
  434. special meaning---they are only for the human reader's benefit and do
  435. not define additional subtopics. Here is an example:
  436. @example
  437. * Foo: Node about FOO. This tells about FOO.
  438. @end example
  439. The subtopic name is Foo, and the node describing it is @samp{Node
  440. about FOO}. The rest of the line is just for the reader's
  441. Information. [[ But this line is not a real menu item, simply because
  442. there is no line above it which starts with @w{@samp{* Menu:}}. Also,
  443. in a real menu item, the @samp{*} would appear at the very start of
  444. the line. This is why the ``normally hidden'' text in Emacs, namely
  445. @samp{: Node about FOO.}, is actually visible in this example, even
  446. when Visible mode is off.]]
  447. When you use a menu to go to another node (in a way that will be
  448. described soon), what you specify is the subtopic name, the first
  449. thing in the menu line. Info uses it to find the menu line, extracts
  450. the node name from it, and goes to that node. The reason that there
  451. is both a subtopic name and a node name is that the node name must be
  452. meaningful to the computer and may therefore have to be ugly looking.
  453. The subtopic name can be chosen just to be convenient for the user to
  454. specify. Often the node name is convenient for the user to specify
  455. and so both it and the subtopic name are the same. There is an
  456. abbreviation for this:
  457. @example
  458. * Foo:: This tells about FOO.
  459. @end example
  460. @noindent
  461. This means that the subtopic name and node name are the same; they are
  462. both @samp{Foo}. (The @samp{::} is normally hidden in Emacs.)
  463. @format
  464. >> Now use @key{SPC} to find the menu in this node, then come back to
  465. the front with a @kbd{b} and some @key{SPC}s. As you see, a menu is
  466. actually visible in its node. If you cannot find a menu in a node
  467. by looking at it, then the node does not have a menu and the
  468. @kbd{m} command is not available.
  469. @end format
  470. If you keep typing @key{SPC} once the menu appears on the screen, it
  471. will move to another node (the first one in the menu). If that
  472. happens, type @key{BACKSPACE} to come back.
  473. @kindex m @r{(Info mode)}
  474. The command to go to one of the subnodes is @kbd{m}. This is very
  475. different from the commands you have used: it is a command that
  476. prompts you for more input.
  477. The Info commands you know do not need additional input; when you
  478. type one of them, Info processes it instantly and then is ready for
  479. another command. The @kbd{m} command is different: it needs to know
  480. the @dfn{name of the subtopic}. Once you have typed @kbd{m}, Info
  481. tries to read the subtopic name.
  482. Now, in the stand-alone Info, look for the line containing many
  483. dashes near the bottom of the screen. (This is the stand-alone
  484. equivalent for the mode line in Emacs.) There is one more line
  485. beneath that one, but usually it is blank. (In Emacs, this is the
  486. echo area.) When it is blank, Info is ready for a command, such as
  487. @kbd{n} or @kbd{b} or @key{SPC} or @kbd{m}. If that line contains
  488. text ending in a colon, it means Info is reading more input for the
  489. last command. You can't type an Info command then, because Info is
  490. trying to read input, not commands. You must either give the input
  491. and finish the command you started, or type @kbd{Control-g} to cancel
  492. the command. When you have done one of those things, the input entry
  493. line becomes blank again. Then you can type Info commands again.
  494. @findex Info-menu
  495. The command to go to a subnode via a menu is @kbd{m}. After you type
  496. the @kbd{m}, the line at the bottom of the screen says @samp{Menu item: }.
  497. You must then type the name of the subtopic you want, and end it with
  498. a @key{RET}.
  499. @cindex abbreviating Info subnodes
  500. You can abbreviate the subtopic name. If the abbreviation is not
  501. unique, the first matching subtopic is chosen. Some menus put
  502. the shortest possible abbreviation for each subtopic name in capital
  503. letters, so you can see how much you need to type. It does not
  504. matter whether you use upper case or lower case when you type the
  505. subtopic. You should not put any spaces at the end, or inside of the
  506. item name, except for one space where a space appears in the item in
  507. the menu.
  508. @cindex completion of Info node names
  509. You can also use the @dfn{completion} feature to help enter the
  510. subtopic name. If you type the @key{TAB} key after entering part of a
  511. name, it will fill in more of the name---as much as Info can deduce
  512. from the part you have entered.
  513. If you move the cursor to one of the menu subtopic lines, then you do
  514. not need to type the argument: you just type a @key{RET}, and it
  515. stands for the subtopic of the line you are on. You can also click
  516. the middle mouse button directly on the subtopic line to go there.
  517. Here is a menu to give you a chance to practice. This menu gives you
  518. three ways of going to one place, Help-FOO:
  519. @menu
  520. * Foo: Help-FOO. A node you can visit for fun.
  521. * Bar: Help-FOO. We have made two ways to get to the same place.
  522. * Help-FOO:: And yet another!
  523. @end menu
  524. (Turn Visible mode on if you are using Emacs.)
  525. @format
  526. >> Now type just an @kbd{m} and see what happens:
  527. @end format
  528. Now you are ``inside'' an @kbd{m} command. Commands cannot be used
  529. now; the next thing you will type must be the name of a subtopic.
  530. You can change your mind about doing the @kbd{m} by typing
  531. @kbd{Control-g}.
  532. @format
  533. >> Try that now; notice the bottom line clear.
  534. @end format
  535. @format
  536. >> Then type another @kbd{m}.
  537. @end format
  538. @format
  539. >> Now type @kbd{BAR}, the item name. Do not type @key{RET} yet.
  540. @end format
  541. While you are typing the item name, you can use the @key{DEL} (or
  542. @key{BACKSPACE}) key to cancel one character at a time if you make a
  543. mistake.
  544. @format
  545. >> Press @key{DEL} to cancel the @samp{R}. You could type another @kbd{R}
  546. to replace it. But you do not have to, since @samp{BA} is a valid
  547. abbreviation.
  548. @end format
  549. @format
  550. >> Now you are ready to go. Type a @key{RET}.
  551. @end format
  552. After visiting @samp{Help-FOO}, you should return here.
  553. Another way to move to the menu subtopic lines and between them is
  554. to type @key{TAB}. Each time you type a @key{TAB}, you move to the
  555. next subtopic line. To move to a previous subtopic line in the
  556. stand-alone reader, type @kbd{M-@key{TAB}}---that is, press and hold
  557. the @key{META} key and then press @key{TAB}. (On some keyboards, the
  558. @key{META} key might be labeled @samp{Alt}.) In Emacs Info, type
  559. @kbd{S-@key{TAB}} to move to a previous subtopic line (press and hold
  560. the @key{Shift} key and then press @key{TAB}).
  561. Once you move cursor to a subtopic line, press @key{RET} to go to
  562. that subtopic's node.
  563. @cindex mouse support in Info mode
  564. @kindex Mouse-2 @r{(Info mode)}
  565. If your terminal supports a mouse, you have yet another way of going
  566. to a subtopic. Move your mouse pointer to the subtopic line,
  567. somewhere between the beginning @samp{*} and the colon @samp{:} which
  568. ends the subtopic's brief name. You will see the subtopic's name
  569. change its appearance (usually, its background color will change), and
  570. the shape of the mouse pointer will change if your platform supports
  571. that. After a while, if you leave the mouse on that spot, a small
  572. window will pop up, saying ``Mouse-2: go to that node,'' or the same
  573. message may appear at the bottom of the screen.
  574. @kbd{Mouse-2} is the second button of your mouse counting from the
  575. left---the middle button on a 3-button mouse. (On a 2-button mouse,
  576. you may have to press both buttons together to ``press the middle
  577. button''.) The message tells you pressing @kbd{Mouse-2} with the
  578. current position of the mouse pointer (on subtopic in the menu) will
  579. go to that subtopic.
  580. @findex Info-mouse-follow-nearest-node
  581. More generally, @kbd{Mouse-2} in an Info buffer finds the nearest
  582. link to another node and goes there. For example, near a cross
  583. reference it acts like @kbd{f}, in a menu it acts like @kbd{m}, on the
  584. node's header line it acts like @kbd{n}, @kbd{p}, or @kbd{u}, etc. At
  585. end of the node's text @kbd{Mouse-2} moves to the next node, or up if
  586. there's no next node.
  587. @format
  588. >> Type @kbd{n} to see more commands.
  589. @end format
  590. @node Help-FOO, , , Help-M
  591. @subsection The @kbd{u} command
  592. Congratulations! This is the node @samp{Help-FOO}. It has an @samp{Up}
  593. pointer @samp{Help-M}, the node you just came from via the @kbd{m}
  594. command. This is the usual convention---the nodes you reach from a menu
  595. have @samp{Up} nodes that lead back to the menu. Menus move Down in the
  596. tree, and @samp{Up} moves Up. @samp{Previous}, on the other hand, is
  597. usually used to ``stay on the same level but go backwards''.
  598. @kindex u @r{(Info mode)}
  599. @findex Info-up
  600. You can go back to the node @samp{Help-M} by typing the command
  601. @kbd{u} for ``Up''. This puts you at the menu subtopic line pointing
  602. to the subnode that the @kbd{u} command brought you from. (Some Info
  603. readers may put you at the @emph{front} of the node instead---to get
  604. back to where you were reading, you have to type some @key{SPC}s.)
  605. Another way to go Up is to click @kbd{Mouse-2} on the @samp{Up}
  606. pointer shown in the header line (provided that you have a mouse).
  607. @format
  608. >> Now type @kbd{u} to move back up to @samp{Help-M}.
  609. @end format
  610. @node Help-Xref
  611. @section Following Cross-References
  612. @cindex cross references in Info documents
  613. In Info documentation, you will see many @dfn{cross references}.
  614. Cross references look like this: @xref{Help-Cross, Cross}. That text
  615. is a real, live cross reference, whose name is @samp{Cross} and which
  616. points to the node named @samp{Help-Cross}. (The node name is hidden
  617. in Emacs. Do @kbd{M-x visible-mode} to show or hide it.)
  618. @kindex f @r{(Info mode)}
  619. @findex Info-follow-reference
  620. You can follow a cross reference by moving the cursor to it and
  621. press @key{RET}, just as in a menu. In Emacs, you can also click
  622. @kbd{Mouse-1} on a cross reference to follow it; you can see that the
  623. cross reference is mouse-sensitive by moving the mouse pointer to the
  624. reference and watching how the underlying text and the mouse pointer
  625. change in response.
  626. Another way to follow a cross reference is to type @kbd{f} and then
  627. specify the name of the cross reference (in this case, @samp{Cross})
  628. as an argument. For this command, it does not matter where the cursor
  629. was. If the cursor is on or near a cross reference, @kbd{f} suggests
  630. that reference name in parentheses as the default; typing @key{RET}
  631. will follow that reference. However, if you type a different
  632. reference name, @kbd{f} will follow the other reference which has that
  633. name.
  634. @format
  635. >> Type @kbd{f}, followed by @kbd{Cross}, and then @key{RET}.
  636. @end format
  637. As you enter the reference name, you can use the @key{DEL} (or
  638. @key{BACKSPACE}) key to edit your input. If you change your mind
  639. about following any reference, you can use @kbd{Control-g} to cancel
  640. the command. Completion is available in the @kbd{f} command; you can
  641. complete among all the cross reference names in the current node by
  642. typing a @key{TAB}.
  643. To get a list of all the cross references in the current node, you
  644. can type @kbd{?} after an @kbd{f}. The @kbd{f} continues to await a
  645. cross reference name even after displaying the list, so if you don't
  646. actually want to follow a reference, you should type a @kbd{Control-g}
  647. to cancel the @kbd{f}.
  648. @format
  649. >> Type @kbd{f?} to get a list of the cross references in this node. Then
  650. type a @kbd{Control-g} and see how the @samp{f} gives up.
  651. @end format
  652. The @key{TAB}, @kbd{M-@key{TAB}} and @kbd{S-@key{TAB}} keys,
  653. which move between menu items in a menu, also move between cross
  654. references outside of menus.
  655. Sometimes a cross reference (or a node) can lead to another file (in
  656. other words another ``manual''), or, on occasion, even a file on a
  657. remote machine (although Info files distributed with Emacs or the
  658. stand-alone Info avoid using remote links). Such a cross reference
  659. looks like this: @xref{Top,, Overview of Texinfo, texinfo, Texinfo:
  660. The GNU Documentation Format}. (After following this link, type
  661. @kbd{l} to get back to this node.) Here the name @samp{texinfo}
  662. between parentheses refers to the file name. This file name appears
  663. in cross references and node names if it differs from the current
  664. file, so you can always know that you are going to be switching to
  665. another manual and which one.
  666. However, Emacs normally hides some other text in cross-references.
  667. If you put your mouse over the cross reference, then the information
  668. appearing in a separate box (tool tip) or in the echo area will show
  669. the full cross-reference including the file name and the node name of
  670. the cross reference. If you have a mouse, just leave it over the
  671. cross reference @xref{Top,, Overview of Texinfo, texinfo, Texinfo:
  672. The GNU Documentation Format}, and watch what happens. If you
  673. always like to have that information visible without having to move
  674. your mouse over the cross reference, use @kbd{M-x visible-mode}, or
  675. set @code{Info-hide-note-references} to a value other than @code{t}
  676. (@pxref{Emacs Info Variables}).
  677. @format
  678. >> Now type @kbd{n} to learn more commands.
  679. @end format
  680. @menu
  681. * Help-Cross:: Target of a cross-reference.
  682. @end menu
  683. @node Help-Cross, , , Help-Xref
  684. @subsection The node reached by the cross reference in Info
  685. This is the node reached by the cross reference named @samp{Cross}.
  686. While this node is specifically intended to be reached by a cross
  687. reference, most cross references lead to nodes that ``belong''
  688. someplace else far away in the structure of an Info document. So you
  689. cannot expect this node to have a @samp{Next}, @samp{Previous} or
  690. @samp{Up} links pointing back to where you came from. In general, the
  691. @kbd{l} (el) command is the only way to get back there.
  692. @format
  693. >> Type @kbd{l} to return to the node where the cross reference was.
  694. @end format
  695. @node Help-Int
  696. @section Some intermediate Info commands
  697. The introductory course is almost over; please continue
  698. a little longer to learn some intermediate-level commands.
  699. Most Info files have an index, which is actually a large node
  700. containing little but a menu. The menu has one menu item for each
  701. topic listed in the index. (As a special feature, menus for indices
  702. may also include the line number within the node of the index entry.
  703. This allows Info readers to go to the exact line of an entry, not just
  704. the start of the containing node.)
  705. You can get to the index from the main menu of the file with the
  706. @kbd{m} command and the name of the index node; then you can use the
  707. @kbd{m} command again in the index node to go to the node that
  708. describes the topic you want.
  709. There is also a short-cut Info command, @kbd{i}, which does all of
  710. that for you. It searches the index for a given topic (a string) and
  711. goes to the node which is listed in the index for that topic.
  712. @xref{Search Index}, for a full explanation.
  713. @kindex l @r{(Info mode)}
  714. @findex Info-history-back
  715. @cindex going back in Info history
  716. If you have been moving around to different nodes and wish to
  717. retrace your steps, the @kbd{l} command (@kbd{l} for @dfn{last}) will
  718. do that, one node-step at a time. As you move from node to node, Info
  719. records the nodes where you have been in a special history list. The
  720. @kbd{l} command revisits nodes in the history list; each successive
  721. @kbd{l} command moves one step back through the history.
  722. @format
  723. >> Try typing @kbd{p p n} and then three @kbd{l}'s, pausing in between
  724. to see what each @kbd{l} does. You should wind up right back here.
  725. @end format
  726. Note the difference between @kbd{l} and @kbd{p}: @kbd{l} moves to
  727. where @emph{you} last were, whereas @kbd{p} always moves to the node
  728. which the header says is the @samp{Previous} node (from this node, the
  729. @samp{Prev} link leads to @samp{Help-Xref}).
  730. @kindex r @r{(Info mode)}
  731. @findex Info-history-forward
  732. @cindex going forward in Info history
  733. You can use the @kbd{r} command (@code{Info-history-forward} in Emacs)
  734. to revisit nodes in the history list in the forward direction, so that
  735. @kbd{r} will return you to the node you came from by typing @kbd{l}.
  736. @kindex L @r{(Info mode)}
  737. @findex Info-history
  738. @cindex history list of visited nodes
  739. The @kbd{L} command (@code{Info-history} in Emacs) creates a virtual
  740. node that contains a list of all nodes you visited. You can select
  741. a previously visited node from this menu to revisit it.
  742. @kindex d @r{(Info mode)}
  743. @findex Info-directory
  744. @cindex go to Directory node
  745. The @kbd{d} command (@code{Info-directory} in Emacs) gets you
  746. instantly to the Directory node. This node, which is the first one
  747. you saw when you entered Info, has a menu which leads (directly or
  748. indirectly, through other menus), to all the nodes that exist. The
  749. Directory node lists all the manuals and other Info documents that
  750. are, or could be, installed on your system.
  751. @format
  752. >> Try doing a @kbd{d}, then do an @kbd{l} to return here (yes,
  753. @emph{do} return).
  754. @end format
  755. @kindex t @r{(Info mode)}
  756. @findex Info-top-node
  757. @cindex go to Top node
  758. The @kbd{t} command moves to the @samp{Top} node of the manual.
  759. This is useful if you want to browse the manual's main menu, or select
  760. some specific top-level menu item. The Emacs command run by @kbd{t}
  761. is @code{Info-top-node}.
  762. @format
  763. >> Now type @kbd{n} to see the last node of the course.
  764. @end format
  765. @xref{Advanced}, for more advanced Info features.
  766. @c If a menu appears at the end of this node, remove it.
  767. @c It is an accident of the menu updating command.
  768. @node Help-Q
  769. @section Quitting Info
  770. @kindex q @r{(Info mode)}
  771. @findex Info-exit
  772. @cindex quitting Info mode
  773. To get out of Info, back to what you were doing before, type @kbd{q}
  774. for @dfn{Quit}. This runs @code{Info-exit} in Emacs.
  775. This is the end of the basic course on using Info. You have learned
  776. how to move in an Info document, and how to follow menus and cross
  777. references. This makes you ready for reading manuals top to bottom,
  778. as new users should do when they learn a new package.
  779. Another set of Info commands is useful when you need to find
  780. something quickly in a manual---that is, when you need to use a manual
  781. as a reference rather than as a tutorial. We urge you to learn
  782. these search commands as well. If you want to do that now, follow this
  783. cross reference to @ref{Advanced}.
  784. Yet another set of commands are meant for experienced users; you can
  785. find them by looking in the Directory node for documentation on Info.
  786. Finding them will be a good exercise in using Info in the usual
  787. manner.
  788. @format
  789. >> Type @kbd{d} to go to the Info directory node; then type
  790. @kbd{mInfo} and Return, to get to the node about Info and
  791. see what other help is available.
  792. @end format
  793. @node Advanced
  794. @chapter Advanced Info Commands
  795. This chapter describes various advanced Info commands. (If you
  796. are using a stand-alone Info reader, there are additional commands
  797. specific to it, which are documented in several chapters of @ref{Top,,
  798. GNU Info, info-stnd, GNU Info}.)
  799. @kindex C-q @r{(Info mode)}
  800. One advanced command useful with most of the others described here
  801. is @kbd{C-q}, which ``quotes'' the next character so that it is
  802. entered literally (@pxref{Inserting Text,,,emacs,The GNU Emacs
  803. Manual}). For example, pressing @kbd{?} ordinarily brings up a list
  804. of completion possibilities. If you want to (for example) search for
  805. an actual @samp{?} character, the simplest way is to insert it using
  806. @kbd{C-q ?}. This works the same in Emacs and stand-alone Info.
  807. @menu
  808. * Search Text:: How to search Info documents.
  809. * Search Index:: How to search the indices for specific subjects.
  810. * Go to node:: How to go to a node by name.
  811. * Choose menu subtopic:: How to choose a menu subtopic by its number.
  812. * Create Info buffer:: How to create a new Info buffer in Emacs.
  813. * Emacs Info Variables:: Variables modifying the behavior of Emacs Info.
  814. @end menu
  815. @node Search Text
  816. @section @kbd{s} searches Info documents
  817. @cindex searching Info documents
  818. @cindex Info document as a reference
  819. The commands which move between and inside nodes allow you to read
  820. the entire manual or its large portions. But what if you need to find
  821. some information in the manual as fast as you can, and you don't know
  822. or don't remember in what node to look for it? This need arises when
  823. you use a manual as a @dfn{reference}, or when it is impractical to
  824. read the entire manual before you start using the programs it
  825. describes.
  826. Info has powerful searching facilities that let you find things
  827. quickly. You can search either the manual text or its indices.
  828. @kindex s @r{(Info mode)}
  829. @findex Info-search
  830. The @kbd{s} command allows you to search a whole Info file for a string.
  831. It switches to the next node if and when that is necessary. You
  832. type @kbd{s} followed by the string to search for, terminated by
  833. @key{RET}. To search for the same string again, just @kbd{s} followed
  834. by @key{RET} will do. The file's nodes are scanned in the order
  835. they are in the file, which has no necessary relationship to the
  836. order that they may be in the tree structure of menus and @samp{next}
  837. pointers. But normally the two orders are not very different. In any
  838. case, you can always look at the mode line to find out what node you have
  839. reached, if the header is not visible (this can happen, because @kbd{s}
  840. puts your cursor at the occurrence of the string, not at the beginning
  841. of the node).
  842. @kindex C-s @r{(Info mode)}
  843. @kindex C-r @r{(Info mode)}
  844. @findex isearch
  845. Instead of using @kbd{s} in Emacs Info and in the stand-alone Info,
  846. you can use an incremental search started with @kbd{C-s} or @kbd{C-r}.
  847. It can search through multiple Info nodes. @xref{Incremental Search,,,
  848. emacs, The GNU Emacs Manual}. In Emacs, you can disable this behavior
  849. by setting the variable @code{Info-isearch-search} to @code{nil}
  850. (@pxref{Emacs Info Variables}).
  851. @node Search Index
  852. @section @kbd{i} searches the indices for specific subjects
  853. @cindex searching Info indices
  854. @kindex i @r{(Info mode)}
  855. @findex Info-index
  856. Since most topics in the manual should be indexed, you should try
  857. the index search first before the text search. The @kbd{i} command
  858. prompts you for a subject and then looks up that subject in the
  859. indices. If it finds an index entry with the subject you typed, it
  860. goes to the node to which that index entry points. You should browse
  861. through that node to see whether the issue you are looking for is
  862. described there. If it isn't, type @kbd{,} one or more times to go
  863. through additional index entries which match your subject.
  864. The @kbd{i} command and subsequent @kbd{,} commands find all index
  865. entries which include the string you typed @emph{as a substring}.
  866. For each match, Info shows in the echo area the full index entry it
  867. found. Often, the text of the full index entry already gives you
  868. enough information to decide whether it is relevant to what you are
  869. looking for, so we recommend that you read what Info shows in the echo
  870. area before looking at the node it displays.
  871. Since @kbd{i} looks for a substring, you can search for subjects even
  872. if you are not sure how they are spelled in the index. For example,
  873. suppose you want to find something that is pertinent to commands which
  874. complete partial input (e.g., when you type @key{TAB}). If you want
  875. to catch index entries that refer to ``complete,'' ``completion,'' and
  876. ``completing,'' you could type @kbd{icomplet@key{RET}}.
  877. Info documents which describe programs should index the commands,
  878. options, and key sequences that the program provides. If you are
  879. looking for a description of a command, an option, or a key, just type
  880. their names when @kbd{i} prompts you for a topic. For example, if you
  881. want to read the description of what the @kbd{C-l} key does, type
  882. @kbd{iC-l@key{RET}} literally.
  883. @findex Info-virtual-index
  884. @kindex I @r{(Info mode)}
  885. Emacs provides the command @code{Info-virtual-index}, bound to the
  886. @kbd{I} key. This behaves like @kbd{i}, but constructs a virtual
  887. info node displaying the results of an index search, making it easier
  888. to select the one you want.
  889. @findex info-apropos
  890. @findex index-apropos
  891. If you aren't sure which manual documents the topic you are looking
  892. for, try the @kbd{M-x info-apropos} command in Emacs, or the @kbd{M-x
  893. index-apropos} command in the stand-alone reader. It prompts for
  894. a string and then looks up that string in all the indices of all the
  895. Info documents installed on your system.
  896. @node Go to node
  897. @section @kbd{g} goes to a node by name
  898. @kindex g @r{(Info mode)}
  899. @findex Info-goto-node
  900. @cindex go to a node by name
  901. If you know a node's name, you can go there by typing @kbd{g}, the
  902. name, and @key{RET}. Thus, @kbd{gTop@key{RET}} would go to the node
  903. called @samp{Top} in this file. (This is equivalent to @kbd{t}, see
  904. @ref{Help-Int}.) @kbd{gGo to node@key{RET}} would come back here.
  905. Unlike @kbd{m}, @kbd{g} does not allow the use of abbreviations.
  906. But it does allow completion, so you can type @key{TAB} to complete a
  907. partial node name.
  908. @cindex go to another Info file
  909. To go to a node in another file, you can include the file name in the
  910. node name by putting it at the front, in parentheses. Thus,
  911. @kbd{g(dir)Top@key{RET}} would go to the Info Directory node, which is
  912. the node @samp{Top} in the Info file @file{dir}. Likewise,
  913. @kbd{g(emacs)Top@key{RET}} (or just @kbd{g(emacs)@key{RET}}) goes to the
  914. top node of the Emacs manual.
  915. The node name @samp{*} specifies the whole file. So you can look at
  916. all of the current file by typing @kbd{g*@key{RET}} or all of any
  917. other file with @kbd{g(@var{filename})*@key{RET}}.
  918. @node Choose menu subtopic
  919. @section @kbd{1}--@kbd{9} choose a menu subtopic by its number
  920. @kindex 1 @r{through} 9 @r{(Info mode)}
  921. @findex Info-nth-menu-item
  922. @cindex select @var{n}'th menu item
  923. If you begrudge each character of type-in which your system requires,
  924. you might like to use the commands @kbd{1}, @kbd{2}, @kbd{3}, @kbd{4},
  925. @dots{}, @kbd{9}. They are short for the @kbd{m} command together
  926. with a name of a menu subtopic. @kbd{1} goes through the first item
  927. in the current node's menu; @kbd{2} goes through the second item, etc.
  928. In the stand-alone reader, @kbd{0} goes through the last menu item;
  929. this is so you need not count how many entries are there.
  930. If your display supports multiple fonts, colors or underlining, and
  931. you are using Emacs's Info mode to read Info files, the third, sixth
  932. and ninth menu items have a @samp{*} that stands out, either in color
  933. or in some other attribute, such as underline; this makes it easy to
  934. see at a glance which number to use for an item.
  935. Some terminals don't support either multiple fonts, colors or
  936. underlining. If you need to actually count items, it is better to use
  937. @kbd{m} instead, and specify the name, or use @key{TAB} to quickly
  938. move between menu items.
  939. @node Create Info buffer
  940. @section @kbd{M-n} creates a new independent Info buffer in Emacs
  941. @kindex M-n @r{(Info mode)}
  942. @findex clone-buffer
  943. @cindex multiple Info buffers
  944. If you are reading Info in Emacs, you can select a new independent
  945. Info buffer in a new Emacs window by typing @kbd{M-n}. The new buffer
  946. starts out as an exact copy of the old one, but you will be able to
  947. move independently between nodes in the two buffers. (In Info mode,
  948. @kbd{M-n} runs the Emacs command @code{clone-buffer}.)
  949. In Emacs Info, you can also produce new Info buffers by giving a
  950. numeric prefix argument to the @kbd{m} and @kbd{g} commands. @kbd{C-u
  951. m} and @kbd{C-u g} go to a new node in exactly the same way that
  952. @kbd{m} and @kbd{g} do, but they do so in a new Info buffer which they
  953. select in another window.
  954. Another way to produce new Info buffers in Emacs is to use a numeric
  955. prefix argument for the @kbd{C-h i} command (@code{info}) which
  956. switches to the Info buffer with that number. Thus, @kbd{C-u 2 C-h i}
  957. switches to the buffer @file{*info*<2>}, creating it if necessary.
  958. @findex info-display-manual
  959. If you have created many Info buffers in Emacs, you might find it
  960. difficult to remember which buffer is showing which manual. You can
  961. use the command @kbd{M-x info-display-manual} to show an Info manual
  962. by name, reusing an existing buffer if there is one. When given a
  963. prefix argument, this command limits the completion alternatives to
  964. currently visited info files, thus giving a convenient way to switch
  965. between several manuals.
  966. @node Emacs Info Variables
  967. @section Emacs Info-mode Variables
  968. The following variables may modify the behavior of Info-mode in Emacs;
  969. you may wish to set one or several of these variables interactively,
  970. or in your init file. @xref{Examining, Examining and Setting
  971. Variables, Examining and Setting Variables, emacs, The GNU Emacs
  972. Manual}. The stand-alone Info reader program has its own set of
  973. variables, described in @ref{Variables,, Manipulating Variables,
  974. info-stnd, GNU Info}.
  975. @vtable @code
  976. @item Info-directory-list
  977. The list of directories to search for Info files. Each element is a
  978. string (directory name) or @code{nil} (try default directory). If not
  979. initialized Info uses the environment variable @env{INFOPATH} to
  980. initialize it, or @code{Info-default-directory-list} if there is no
  981. @env{INFOPATH} variable in the environment.
  982. If you wish to customize the Info directory search list for both Emacs
  983. Info and stand-alone Info, it is best to set the @env{INFOPATH}
  984. environment variable, since that applies to both programs.
  985. @item Info-additional-directory-list
  986. A list of additional directories to search for Info documentation files.
  987. These directories are not searched for merging the @file{dir} file.
  988. @item Info-mode-hook
  989. Hooks run when @code{Info-mode} is called. By default, it contains
  990. the hook @code{turn-on-font-lock} which enables highlighting of Info
  991. files. You can change how the highlighting looks by customizing the
  992. faces @code{info-node}, @code{info-xref}, @code{info-xref-visited},
  993. @code{info-header-xref}, @code{info-header-node}, @code{info-menu-header},
  994. @code{info-menu-star}, and @code{info-title-@var{n}} (where @var{n}
  995. is the level of the section, a number between 1 and 4). To customize
  996. a face, type @kbd{M-x customize-face @key{RET} @var{face} @key{RET}},
  997. where @var{face} is one of the face names listed here.
  998. @item Info-fontify-maximum-menu-size
  999. Maximum size of menu to fontify if @code{font-lock-mode} is non-@code{nil}.
  1000. @item Info-fontify-visited-nodes
  1001. If non-@code{nil}, menu items and cross-references pointing to visited
  1002. nodes are displayed in the @code{info-xref-visited} face.
  1003. @item Info-use-header-line
  1004. If non-@code{nil}, Emacs puts in the Info buffer a header line showing
  1005. the @samp{Next}, @samp{Prev}, and @samp{Up} links. A header line does
  1006. not scroll with the rest of the buffer, making these links always
  1007. visible.
  1008. @item Info-hide-note-references
  1009. As explained in earlier nodes, the Emacs version of Info normally
  1010. hides some text in menus and cross-references. You can completely
  1011. disable this feature, by setting this option to @code{nil}. Setting
  1012. it to a value that is neither @code{nil} nor @code{t} produces an
  1013. intermediate behavior, hiding a limited amount of text, but showing
  1014. all text that could potentially be useful.
  1015. @item Info-scroll-prefer-subnodes
  1016. If set to a non-@code{nil} value, @key{SPC} and @key{BACKSPACE} (or
  1017. @key{DEL}, or @kbd{S-@key{SPC}}) keys in a menu visit subnodes of the
  1018. current node before scrolling to its end or beginning, respectively.
  1019. For example, if the node's menu appears on the screen, the next
  1020. @key{SPC} moves to a subnode indicated by the following menu item.
  1021. Setting this option to @code{nil} results in behavior similar to the
  1022. stand-alone Info reader program, which visits the first subnode from
  1023. the menu only when you hit the end of the current node. The default
  1024. is @code{nil}.
  1025. @item Info-isearch-search
  1026. If non-@code{nil}, isearch in Info searches through multiple nodes.
  1027. @item Info-enable-active-nodes
  1028. When set to a non-@code{nil} value, allows Info to execute Lisp code
  1029. associated with nodes. The Lisp code is executed when the node is
  1030. selected. The Lisp code to be executed should follow the node
  1031. delimiter (the @samp{DEL} character) and an @samp{execute: } tag, like
  1032. this:
  1033. @example
  1034. ^_execute: (message "This is an active node!")
  1035. @end example
  1036. @end vtable
  1037. @node Further Reading
  1038. @chapter Further Reading
  1039. @cindex Texinfo
  1040. Info files are created from Texinfo source files. You can use the
  1041. same source file to make a printed manual or produce other formats,
  1042. such as HTML and DocBook.
  1043. The @code{makeinfo} command converts a Texinfo file into an Info file;
  1044. @code{texinfo-format-region} and @code{texinfo-format-buffer} are GNU
  1045. Emacs functions that do the same.
  1046. @xref{Top,, Overview of Texinfo, texinfo, Texinfo: The GNU
  1047. Documentation Format}, for how to write a Texinfo file.
  1048. @xref{Creating an Info File,,, texinfo, Texinfo: The GNU Documentation
  1049. Format}, for how to create an Info file from a Texinfo file.
  1050. @xref{Installing an Info File,,, texinfo, Texinfo: The GNU
  1051. Documentation Format}, for how to install an Info file after you
  1052. have created one.
  1053. @node GNU Free Documentation License
  1054. @appendix GNU Free Documentation License
  1055. @include doclicense.texi
  1056. @node Index
  1057. @unnumbered Index
  1058. This is an alphabetical listing of all the commands, variables, and
  1059. topics discussed in this document.
  1060. @printindex cp
  1061. @bye