Remove string.h hack.
[bpt/emacs.git] / man / help.texi
CommitLineData
6bf7aab6 1@c This is part of the Emacs manual.
7d291226
DL
2@c Copyright (C) 1985, 86, 87, 93, 94, 95, 97, 2000
3@c Free Software Foundation, Inc.
6bf7aab6
DL
4@c See file emacs.texi for copying conditions.
5@node Help, Mark, M-x, Top
6@chapter Help
7@kindex Help
8@cindex help
9@cindex self-documentation
10@findex help-command
11@kindex C-h
12@kindex F1
13
14 Emacs provides extensive help features accessible through a single
15character, @kbd{C-h}. @kbd{C-h} is a prefix key that is used only for
16documentation-printing commands. The characters that you can type after
17@kbd{C-h} are called @dfn{help options}. One help option is @kbd{C-h};
18that is how you ask for help about using @kbd{C-h}. To cancel, type
19@kbd{C-g}. The function key @key{F1} is equivalent to @kbd{C-h}.
20
21@kindex C-h C-h
22@findex help-for-help
23 @kbd{C-h C-h} (@code{help-for-help}) displays a list of the possible
24help options, each with a brief description. Before you type a help
25option, you can use @key{SPC} or @key{DEL} to scroll through the list.
26
27 @kbd{C-h} or @key{F1} means ``help'' in various other contexts as
28well. For example, in the middle of @code{query-replace}, it describes
29the options available for how to operate on the current match. After a
30prefix key, it displays a list of the alternatives that can follow the
31prefix key. (A few prefix keys don't support @kbd{C-h}, because they
32define other meanings for it, but they all support @key{F1}.)
33
34 Most help buffers use a special major mode, Help mode, which lets you
7d291226
DL
35scroll conveniently with @key{SPC} and @key{DEL}. It also offers
36hyperlinks to more help on cross-referenced names, Info nodes,
37customization buffers and the like. @xref{Help Mode}.
6bf7aab6
DL
38
39@menu
40* Help Summary:: Brief list of all Help commands.
41* Key Help:: Asking what a key does in Emacs.
42* Name Help:: Asking about a command, variable or function name.
43* Apropos:: Asking what pertains to a given topic.
44* Library Keywords:: Finding Lisp libraries by keywords (topics).
45* Language Help:: Help relating to international language support.
46* Help Mode:: Special features of Help mode and Help buffers.
47* Misc Help:: Other help commands.
7d291226 48* Help Echo:: Help on active text and tooltips (`balloon help')
6bf7aab6
DL
49@end menu
50
51@iftex
52@node Help Summary
53@end iftex
54@ifinfo
55@node Help Summary
56@section Help Summary
57@end ifinfo
58
59 Here is a summary of the defined help commands.
60
61@table @kbd
62@item C-h a @var{regexp} @key{RET}
63Display a list of commands whose names match @var{regexp}
64(@code{apropos-command}).
65@item C-h b
66Display a table of all key bindings in effect now, in this order: minor
67mode bindings, major mode bindings, and global bindings
68(@code{describe-bindings}).
69@item C-h c @var{key}
70Print the name of the command that @var{key} runs
71(@code{describe-key-briefly}). Here @kbd{c} stands for `character'. For more
72extensive information on @var{key}, use @kbd{C-h k}.
73@item C-h f @var{function} @key{RET}
74Display documentation on the Lisp function named @var{function}
75(@code{describe-function}). Since commands are Lisp functions,
76a command name may be used.
77@item C-h h
78Display the @file{hello} file, which shows examples of various character
79sets.
80@item C-h i
81Run Info, the program for browsing documentation files (@code{info}).
82The complete Emacs manual is available on-line in Info.
83@item C-h k @var{key}
84Display the name and documentation of the command that @var{key} runs
85(@code{describe-key}).
86@item C-h l
87Display a description of the last 100 characters you typed
88(@code{view-lossage}).
89@item C-h m
90Display documentation of the current major mode (@code{describe-mode}).
91@item C-h n
92Display documentation of Emacs changes, most recent first
93(@code{view-emacs-news}).
9888e890
DL
94@item C-h P
95Display info on known problems with Emacs and possible workarounds
96(@code{view-emacs-problems}).
6bf7aab6
DL
97@item C-h p
98Find packages by topic keyword (@code{finder-by-keyword}).
99@item C-h s
100Display current contents of the syntax table, plus an explanation of
101what they mean (@code{describe-syntax}). @xref{Syntax}.
102@item C-h t
103Enter the Emacs interactive tutorial (@code{help-with-tutorial}).
104@item C-h v @var{var} @key{RET}
105Display the documentation of the Lisp variable @var{var}
106(@code{describe-variable}).
107@item C-h w @var{command} @key{RET}
108Print which keys run the command named @var{command} (@code{where-is}).
109@item C-h C @var{coding} @key{RET}
110Describe coding system @var{coding}
111(@code{describe-coding-system}).
112@item C-h C @key{RET}
113Describe the coding systems currently in use.
114@item C-h I @var{method} @key{RET}
115Describe an input method (@code{describe-input-method}).
116@item C-h L @var{language-env} @key{RET}
117Describe information on the character sets, coding systems and input
118methods used for language environment @var{language-env}
119(@code{describe-language-environment}).
120@item C-h C-c
121Display the copying conditions for GNU Emacs.
122@item C-h C-d
123Display information about getting new versions of GNU Emacs.
124@item C-h C-f @var{function} @key{RET}
125Enter Info and go to the node documenting the Emacs function @var{function}
126(@code{Info-goto-emacs-command-node}).
127@item C-h C-k @var{key}
128Enter Info and go to the node where the key sequence @var{key} is
129documented (@code{Info-goto-emacs-key-command-node}).
130@item C-h C-p
131Display information about the GNU Project.
132@item C-h @key{TAB} @var{symbol} @key{RET}
133Display the Info documentation on symbol @var{symbol} according to the
134programming language you are editing (@code{info-lookup-symbol}).
135@end table
136
137@node Key Help
138@section Documentation for a Key
139
140@kindex C-h c
141@findex describe-key-briefly
142 The most basic @kbd{C-h} options are @kbd{C-h c}
143(@code{describe-key-briefly}) and @w{@kbd{C-h k}} (@code{describe-key}).
144@kbd{C-h c @var{key}} prints in the echo area the name of the command
145that @var{key} is bound to. For example, @kbd{C-h c C-f} prints
146@samp{forward-char}. Since command names are chosen to describe what
147the commands do, this is a good way to get a very brief description of
148what @var{key} does.
149
150@kindex C-h k
151@findex describe-key
152 @kbd{C-h k @var{key}} is similar but gives more information: it
153displays the documentation string of the command as well as its name.
154This is too big for the echo area, so a window is used for the display.
155
156 @kbd{C-h c} and @kbd{C-h k} work for any sort of key sequences,
157including function keys and mouse events.
158
159@node Name Help
160@section Help by Command or Variable Name
161
162@kindex C-h f
163@findex describe-function
164 @kbd{C-h f} (@code{describe-function}) reads the name of a Lisp function
165using the minibuffer, then displays that function's documentation string
166in a window. Since commands are Lisp functions, you can use this to get
167the documentation of a command that you know by name. For example,
168
169@example
170C-h f auto-fill-mode @key{RET}
171@end example
172
173@noindent
174displays the documentation of @code{auto-fill-mode}. This is the only
175way to get the documentation of a command that is not bound to any key
176(one which you would normally run using @kbd{M-x}).
177
178 @kbd{C-h f} is also useful for Lisp functions that you are planning to
179use in a Lisp program. For example, if you have just written the
180expression @code{(make-vector len)} and want to check that you are using
181@code{make-vector} properly, type @kbd{C-h f make-vector @key{RET}}.
182Because @kbd{C-h f} allows all function names, not just command names,
183you may find that some of your favorite abbreviations that work in
184@kbd{M-x} don't work in @kbd{C-h f}. An abbreviation may be unique
185among command names yet fail to be unique when other function names are
186allowed.
187
188 The function name for @kbd{C-h f} to describe has a default which is
189used if you type @key{RET} leaving the minibuffer empty. The default is
190the function called by the innermost Lisp expression in the buffer around
191point, @emph{provided} that is a valid, defined Lisp function name. For
192example, if point is located following the text @samp{(make-vector (car
193x)}, the innermost list containing point is the one that starts with
194@samp{(make-vector}, so the default is to describe the function
195@code{make-vector}.
196
197 @kbd{C-h f} is often useful just to verify that you have the right
198spelling for the function name. If @kbd{C-h f} mentions a name from the
199buffer as the default, that name must be defined as a Lisp function. If
200that is all you want to know, just type @kbd{C-g} to cancel the @kbd{C-h
201f} command, then go on editing.
202
203@kindex C-h w
204@findex where-is
205 @kbd{C-h w @var{command} @key{RET}} tells you what keys are bound to
206@var{command}. It prints a list of the keys in the echo area. If it
207says the command is not on any key, you must use @kbd{M-x} to run it.
208@kbd{C-h w} runs the command @code{where-is}.
209
210 @kbd{C-h v} (@code{describe-variable}) is like @kbd{C-h f} but describes
211Lisp variables instead of Lisp functions. Its default is the Lisp symbol
212around or before point, but only if that is the name of a known Lisp
213variable. @xref{Variables}.@refill
214
7d291226
DL
215Help buffers describing variables or functions defined in Lisp
216normally have hyperlinks to their definitions using the @code{find-func}
217package if you have the Lisp source files installed. If you can read
218Lisp, this provides the ultimate documentation.
219
6bf7aab6
DL
220@node Apropos
221@section Apropos
222
223@kindex C-h a
224@findex apropos-command
225@cindex apropos
226 A more sophisticated sort of question to ask is, ``What are the
227commands for working with files?'' To ask this question, type @kbd{C-h
228a file @key{RET}}, which displays a list of all command names that
229contain @samp{file}, including @code{copy-file}, @code{find-file}, and
230so on. With each command name appears a brief description of how to use
231the command, and what keys you can currently invoke it with. For
232example, it would say that you can invoke @code{find-file} by typing
233@kbd{C-x C-f}. The @kbd{a} in @kbd{C-h a} stands for `Apropos';
234@kbd{C-h a} runs the command @code{apropos-command}. This command
235normally checks only commands (interactive functions); if you specify a
236prefix argument, it checks noninteractive functions as well.
237
238 Because @kbd{C-h a} looks only for functions whose names contain the
239string you specify, you must use ingenuity in choosing the
240string. If you are looking for commands for killing backwards and
241@kbd{C-h a kill-backwards @key{RET}} doesn't reveal any, don't give up.
242Try just @kbd{kill}, or just @kbd{backwards}, or just @kbd{back}. Be
243persistent. Also note that you can use a regular expression as the
244argument, for more flexibility (@pxref{Regexps}).
245
246 Here is a set of arguments to give to @kbd{C-h a} that covers many
247classes of Emacs commands, since there are strong conventions for naming
248the standard Emacs commands. By giving you a feel for the naming
249conventions, this set should also serve to aid you in developing a
250technique for picking @code{apropos} strings.
251
252@quotation
253char, line, word, sentence, paragraph, region, page, sexp, list, defun,
254rect, buffer, frame, window, face, file, dir, register, mode, beginning, end,
255forward, backward, next, previous, up, down, search, goto, kill, delete,
256mark, insert, yank, fill, indent, case, change, set, what, list, find,
257view, describe, default.
258@end quotation
259
260@findex apropos-variable
261 To list all user variables that match a regexp, use the command
262@kbd{M-x apropos-variable}. This command shows only user variables and
263customization options by default; if you specify a prefix argument, it
264checks all variables.
265
266@findex apropos
267 To list all Lisp symbols that contain a match for a regexp, not just
268the ones that are defined as commands, use the command @kbd{M-x apropos}
269instead of @kbd{C-h a}. This command does not check key bindings by
270default; specify a numeric argument if you want it to check them.
271
272@findex apropos-documentation
273 The @code{apropos-documentation} command is like @code{apropos} except
274that it searches documentation strings as well as symbol names for
275matches for the specified regular expression.
276
277@findex apropos-value
278 The @code{apropos-value} command is like @code{apropos} except that it
279searches symbols' values for matches for the specified regular
280expression. This command does not check function definitions or
281property lists by default; specify a numeric argument if you want it to
282check them.
283
284@vindex apropos-do-all
285 If the variable @code{apropos-do-all} is non-@code{nil}, the commands
286above all behave as if they had been given a prefix argument.
287
288 If you want more information about a function definition, variable or
289symbol property listed in the Apropos buffer, you can click on it with
290@kbd{Mouse-2} or move there and type @key{RET}.
291
292@node Library Keywords
293@section Keyword Search for Lisp Libraries
294
295@kindex C-h p
296@findex finder-by-keyword
297The @kbd{C-h p} command lets you search the standard Emacs Lisp
298libraries by topic keywords. Here is a partial list of keywords you can
299use:
300
301@display
302abbrev --- abbreviation handling, typing shortcuts, macros.
303bib --- support for the bibliography processor @code{bib}.
304c --- C and C++ language support.
305calendar --- calendar and time management support.
306comm --- communications, networking, remote access to files.
307data --- support for editing files of data.
308docs --- support for Emacs documentation.
309emulations --- emulations of other editors.
310extensions --- Emacs Lisp language extensions.
311faces --- support for using faces (fonts and colors; @pxref{Faces}).
312frames --- support for Emacs frames and window systems.
313games --- games, jokes and amusements.
314hardware --- support for interfacing with exotic hardware.
315help --- support for on-line help systems.
316hypermedia --- support for links within text, or other media types.
317i18n --- internationalization and alternate character-set support.
318internal --- code for Emacs internals, build process, defaults.
319languages --- specialized modes for editing programming languages.
320lisp --- support for using Lisp (including Emacs Lisp).
321local --- libraries local to your site.
322maint --- maintenance aids for the Emacs development group.
323mail --- modes for electronic-mail handling.
324matching --- searching and matching.
325news --- support for netnews reading and posting.
326non-text --- support for editing files that are not ordinary text.
327oop --- support for object-oriented programming.
328outlines --- hierarchical outlining.
329processes --- process, subshell, compilation, and job control support.
330terminals --- support for terminal types.
331tex --- support for the @TeX{} formatter.
332tools --- programming tools.
333unix --- front-ends/assistants for, or emulators of, Unix features.
334vms --- support code for VMS.
335wp --- word processing.
336@end display
337
338@node Language Help
339@section Help for International Language Support
340
341 You can use the command @kbd{C-h L}
342(@code{describe-language-environment}) to find out the support for a
343specific language environment. @xref{Language Environments}. This
344tells you which languages this language environment is useful for, and
345lists the character sets, coding systems, and input methods that go with
346it. It also shows some sample text to illustrate scripts.
347
348 The command @kbd{C-h h} (@code{view-hello-file}) displays the file
349@file{etc/HELLO}, which shows how to say ``hello'' in many languages.
350
351 The command @kbd{C-h I} (@code{describe-input-method}) describes
352information about input methods---either a specified input method, or by
353default the input method in use. @xref{Input Methods}.
354
355 The command @kbd{C-h C} (@code{describe-coding-system}) describes
356information about coding systems---either a specified coding system, or
357the ones currently in use. @xref{Coding Systems}.
358
359@node Help Mode
360@section Help Mode Commands
361
362 Help buffers provide the commands of View mode (@pxref{Misc File
363Ops}), plus a few special commands of their own.
364
365@table @kbd
366@item @key{SPC}
367Scroll forward.
368@item @key{DEL}
369Scroll backward.
370@item @key{RET}
371Follow a cross reference at point.
372@item @key{TAB}
373Move point forward to the next cross reference.
374@item S-@key{TAB}
375Move point back to the previous cross reference.
376@item Mouse-2
377Follow a cross reference that you click on.
378@end table
379
380 When a command name (@pxref{M-x,, Running Commands by Name}) or
381variable name (@pxref{Variables}) appears in the documentation, it
382normally appears inside paired single-quotes. You can click on the name
383with @kbd{Mouse-2}, or move point there and type @key{RET}, to view the
384documentation of that command or variable. Use @kbd{C-c C-b} to retrace
385your steps.
386
387@kindex @key{TAB} @r{(Help mode)}
388@findex help-next-ref
389@kindex S-@key{TAB} @r{(Help mode)}
390@findex help-previous-ref
391 There are convenient commands for moving point to cross references in
392the help text. @key{TAB} (@code{help-next-ref}) moves point down to the
393next cross reference. Use @kbd{S-@key{TAB}} to move point up to the
394previous cross reference (@code{help-previous-ref}).
395
396@node Misc Help
397@section Other Help Commands
398
399@kindex C-h i
400@findex info
401@cindex Info
402@cindex manuals, on-line
403@cindex on-line manuals
404 @kbd{C-h i} (@code{info}) runs the Info program, which is used for
405browsing through structured documentation files. The entire Emacs manual
406is available within Info. Eventually all the documentation of the GNU
407system will be available. Type @kbd{h} after entering Info to run
408a tutorial on using Info.
409
410 If you specify a numeric argument, @kbd{C-h i} prompts for the name of
411a documentation file. This way, you can browse a file which doesn't
412have an entry in the top-level Info menu. It is also handy when you
413need to get to the documentation quickly, and you know the exact name of
414the file.
415
416@kindex C-h C-f
417@kindex C-h C-k
418@findex Info-goto-emacs-key-command-node
419@findex Info-goto-emacs-command-node
420 There are two special help commands for accessing Emacs documentation
421through Info. @kbd{C-h C-f @var{function} @key{RET}} enters Info and
422goes straight to the documentation of the Emacs function
423@var{function}. @kbd{C-h C-k @var{key}} enters Info and goes straight
424to the documentation of the key @var{key}. These two keys run the
425commands @code{Info-goto-emacs-command-node} and
426@code{Info-goto-emacs-key-command-node}.
427
428 When editing a program, if you have an Info version of the manual for
429the programming language, you can use the command @kbd{C-h C-i} to refer
430to the manual documentation for a symbol (keyword, function or
431variable). The details of how this command works depend on the major
432mode.
433
434@kindex C-h l
435@findex view-lossage
436 If something surprising happens, and you are not sure what commands you
437typed, use @kbd{C-h l} (@code{view-lossage}). @kbd{C-h l} prints the last
438100 command characters you typed in. If you see commands that you don't
439know, you can use @kbd{C-h c} to find out what they do.
440
441@kindex C-h m
442@findex describe-mode
443 Emacs has numerous major modes, each of which redefines a few keys and
444makes a few other changes in how editing works. @kbd{C-h m}
445(@code{describe-mode}) prints documentation on the current major mode,
446which normally describes all the commands that are changed in this
447mode.
448
449@kindex C-h b
450@findex describe-bindings
451 @kbd{C-h b} (@code{describe-bindings}) and @kbd{C-h s}
452(@code{describe-syntax}) present other information about the current
453Emacs mode. @kbd{C-h b} displays a list of all the key bindings now in
454effect; the local bindings defined by the current minor modes first,
455then the local bindings defined by the current major mode, and finally
456the global bindings (@pxref{Key Bindings}). @kbd{C-h s} displays the
457contents of the syntax table, with explanations of each character's
458syntax (@pxref{Syntax}).
459
460 You can get a similar list for a particular prefix key by typing
461@kbd{C-h} after the prefix key. (There are a few prefix keys for which
462this does not work---those that provide their own bindings for
463@kbd{C-h}. One of these is @key{ESC}, because @kbd{@key{ESC} C-h} is
464actually @kbd{C-M-h}, which marks a defun.)
465
466@kindex C-h F
467@findex view-emacs-FAQ
468@kindex C-h n
469@findex view-emacs-news
470@kindex C-h C-c
471@findex describe-copying
472@kindex C-h C-d
473@findex describe-distribution
474@kindex C-h C-w
475@findex describe-no-warranty
476@kindex C-h C-p
477@findex describe-project
9888e890
DL
478@kindex C-h P
479@findex view-emacs-problems
6bf7aab6
DL
480 The other @kbd{C-h} options display various files of useful
481information. @kbd{C-h C-w} displays the full details on the complete
482absence of warranty for GNU Emacs. @kbd{C-h n} (@code{view-emacs-news})
483displays the file @file{emacs/etc/NEWS}, which contains documentation on
484Emacs changes arranged chronologically. @kbd{C-h F}
485(@code{view-emacs-FAQ}) displays the Emacs frequently-answered-questions
486list. @kbd{C-h t} (@code{help-with-tutorial}) displays the
487learn-by-doing Emacs tutorial. @kbd{C-h C-c} (@code{describe-copying})
488displays the file @file{emacs/etc/COPYING}, which tells you the
489conditions you must obey in distributing copies of Emacs. @kbd{C-h C-d}
490(@code{describe-distribution}) displays the file
491@file{emacs/etc/DISTRIB}, which tells you how you can order a copy of
492the latest version of Emacs. @kbd{C-h C-p} (@code{describe-project})
9888e890
DL
493displays general information about the GNU Project. @kbd{C-h P}
494(@code{view-emacs-problems}) displays the file
495@file{emacs/etc/PROBLEMS}, which lists known problems with Emacs in
496various situations with solutions or workarounds in many cases.
7d291226
DL
497
498@node Help Echo
499@section Help on Active Text and Tooltips
500
501@cindex tooltips
502@cindex ballon help
503Often when a region of text is `active' so that you can select it with
504the mouse or a key like @kbd{RET}, it has associated help text. Areas
505of the mode line are examples. This help will normally be printed in
506the echo area when you move point into the active text. In a window
507system you can display the help text as `tooltips'. @xref{Tooltips}.