]> code.delx.au - gnu-emacs/blob - man/faq.texi
Set VER to `22.1'.
[gnu-emacs] / man / faq.texi
1 \input texinfo @c -*- coding: latin-1; mode: texinfo; -*-
2 @c %**start of header
3 @setfilename ../info/efaq
4 @settitle GNU Emacs FAQ
5 @c %**end of header
6
7 @setchapternewpage odd
8
9 @c This is used in many places
10 @set VER 22.1
11
12 @copying
13 Copyright (C) 2001, 2002, 2003, 2004, 2005 Free Software Foundation, Inc.
14 Copyright 1994,1995,1996,1997,1998,1999,2000 Reuven M. Lerner@*
15 Copyright 1992,1993 Steven Byrnes@*
16 Copyright 1990,1991,1992 Joseph Brian Wells@*
17
18 @quotation
19 This list of frequently asked questions about GNU Emacs with answers
20 (``FAQ'') may be translated into other languages, transformed into other
21 formats (e.g. Texinfo, Info, WWW, WAIS), and updated with new information.
22
23 The same conditions apply to any derivative of the FAQ as apply to the FAQ
24 itself. Every copy of the FAQ must include this notice or an approved
25 translation, information on who is currently maintaining the FAQ and how to
26 contact them (including their e-mail address), and information on where the
27 latest version of the FAQ is archived (including FTP information).
28
29 The FAQ may be copied and redistributed under these conditions, except that
30 the FAQ may not be embedded in a larger literary work unless that work
31 itself allows free copying and redistribution.
32
33 [This version has been heavily edited since it was included in the Emacs
34 distribution.]
35 @end quotation
36 @end copying
37
38 @dircategory Emacs
39 @direntry
40 * Emacs FAQ: (efaq). Frequently Asked Questions about Emacs.
41 @end direntry
42
43 @c The @titlepage stuff only appears in the printed version
44 @titlepage
45 @sp 10
46 @center @titlefont{GNU Emacs FAQ}
47
48 @c The following two commands start the copyright page.
49 @page
50 @vskip 0pt plus 1filll
51 @insertcopying
52 @end titlepage
53
54 @node Top, FAQ notation, (dir), (dir)
55
56 This is the GNU Emacs FAQ, last updated on @today{}.
57
58 The FAQ is maintained as a Texinfo document, allowing us to create HTML,
59 Info, and TeX documents from a single source file, and is slowly but
60 surely being improved. Please bear with us as we improve on this
61 format. This FAQ is maintained as a part of GNU Emacs. If you find
62 any errors, or have any suggestions, please use @kbd{M-x report-emacs-bug}
63 to report them.
64
65 @menu
66 * FAQ notation::
67 * General questions::
68 * Getting help::
69 * Status of Emacs::
70 * Common requests::
71 * Bugs and problems::
72 * Compiling and installing Emacs::
73 * Finding Emacs and related packages::
74 * Major packages and programs::
75 * Key bindings::
76 * Alternate character sets::
77 * Mail and news::
78 * Concept index::
79 @end menu
80
81 @c ------------------------------------------------------------
82 @node FAQ notation, General questions, Top, Top
83 @chapter FAQ notation
84 @cindex FAQ notation
85
86 This chapter describes notation used in the GNU Emacs FAQ, as well as in
87 the Emacs documentation. Consult this section if this is the first time
88 you are reading the FAQ, or if you are confused by notation or terms
89 used in the FAQ.
90
91 @menu
92 * Basic keys::
93 * Extended commands::
94 * On-line manual::
95 * File-name conventions::
96 * Common acronyms::
97 @end menu
98
99 @node Basic keys, Extended commands, FAQ notation, FAQ notation
100 @section What do these mean: @kbd{C-h}, @kbd{C-M-a}, @key{RET}, @kbd{@key{ESC} a}, etc.?
101 @cindex Basic keys
102 @cindex Control key, notation for
103 @cindex @key{Meta} key, notation for
104 @cindex Control-Meta characters, notation for
105 @cindex @kbd{C-h}, definition of
106 @cindex @kbd{C-M-h}, definition of
107 @cindex @key{DEL}, definition of
108 @cindex @key{ESC}, definition of
109 @cindex @key{LFD}, definition of
110 @cindex @key{RET}, definition of
111 @cindex @key{SPC}, definition of
112 @cindex @key{TAB}, definition of
113 @cindex Notation for keys
114
115 @itemize @bullet
116
117 @item
118 @kbd{C-x}: press the @key{x} key while holding down the @key{Control} key
119
120 @item
121 @kbd{M-x}: press the @key{x} key while holding down the @key{Meta} key
122 (if your computer doesn't have a @key{Meta} key, @pxref{No Meta key})
123
124 @item
125 @kbd{M-C-x}: press the @key{x} key while holding down both @key{Control}
126 and @key{Meta}
127
128 @item
129 @kbd{C-M-x}: a synonym for the above
130
131 @item
132 @key{LFD}: Linefeed or Newline; same as @kbd{C-j}
133
134 @item
135 @key{RET}: @key{Return}, sometimes marked @key{Enter}; same as @kbd{C-m}
136
137 @item
138 @key{DEL}: @key{Delete}, usually @strong{not} the same as
139 @key{Backspace}; same as @kbd{C-?} (see @ref{Backspace invokes help}, if
140 deleting invokes Emacs help)
141
142 @item
143 @key{ESC}: Escape; same as @kbd{C-[}
144
145 @item
146 @key{TAB}: Tab; same as @kbd{C-i}
147
148 @item
149 @key{SPC}: Space bar
150
151 @end itemize
152
153 Key sequences longer than one key (and some single-key sequences) are
154 written inside quotes or on lines by themselves, like this:
155
156 @display
157 @kbd{M-x frobnicate-while-foo RET}
158 @end display
159
160 @noindent
161 Any real spaces in such a key sequence should be ignored; only @key{SPC}
162 really means press the space key.
163
164 The @acronym{ASCII} code sent by @kbd{C-x} (except for @kbd{C-?}) is the value
165 that would be sent by pressing just @key{x} minus 96 (or 64 for
166 upper-case @key{X}) and will be from 0 to 31. On Unix and GNU/Linux
167 terminals, the @acronym{ASCII} code sent by @kbd{M-x} is the sum of 128 and the
168 @acronym{ASCII} code that would be sent by pressing just @key{x}. Essentially,
169 @key{Control} turns off bits 5 and 6 and @key{Meta} turns on bit
170 7@footnote{
171 DOS and Windows terminals don't set bit 7 when the @key{Meta} key is
172 pressed.}.
173
174 @kbd{C-?} (aka @key{DEL}) is @acronym{ASCII} code 127. It is a misnomer to call
175 @kbd{C-?} a ``control'' key, since 127 has both bits 5 and 6 turned ON.
176 Also, on very few keyboards does @kbd{C-?} generate @acronym{ASCII} code 127.
177
178 @inforef{Text Characters, Text Characters, emacs}, and @inforef{Keys,
179 Keys, emacs}, for more information. (@xref{On-line manual}, for more
180 information about Info.)
181
182 @node Extended commands, On-line manual, Basic keys, FAQ notation
183 @section What does @file{M-x @var{command}} mean?
184 @cindex Extended commands
185 @cindex Commands, extended
186 @cindex M-x, meaning of
187
188 @kbd{M-x @var{command}} means type @kbd{M-x}, then type the name of the
189 command, then type @key{RET}. (@xref{Basic keys}, if you're not sure
190 what @kbd{M-x} and @key{RET} mean.)
191
192 @kbd{M-x} (by default) invokes the command
193 @code{execute-extended-command}. This command allows you to run any
194 Emacs command if you can remember the command's name. If you can't
195 remember the command's name, you can type @key{TAB} and @key{SPC} for
196 completion, @key{?} for a list of possibilities, and @kbd{M-p} and
197 @kbd{M-n} (or up-arrow and down-arrow on terminals that have these
198 editing keys) to see previous commands entered. An Emacs @dfn{command}
199 is an @dfn{interactive} Emacs function.
200
201 @cindex @key{Do} key
202 Your system administrator may have bound other key sequences to invoke
203 @code{execute-extended-command}. A function key labeled @kbd{Do} is a
204 good candidate for this, on keyboards that have such a key.
205
206 If you need to run non-interactive Emacs functions, see @ref{Evaluating
207 Emacs Lisp code}.
208
209 @node On-line manual, File-name conventions, Extended commands, FAQ notation
210 @section How do I read topic XXX in the on-line manual?
211 @cindex On-line manual, reading topics in
212 @cindex Reading topics in the on-line manual
213 @cindex Finding topics in the on-line manual
214 @cindex Info, finding topics in
215
216 When we refer you to some @var{topic} in the on-line manual, you can
217 read this manual node inside Emacs (assuming nothing is broken) by
218 typing @kbd{C-h i m emacs @key{RET} m @var{topic} @key{RET}}.
219
220 This invokes Info, the GNU hypertext documentation browser. If you don't
221 already know how to use Info, type @key{?} from within Info.
222
223 If we refer to @var{topic}:@var{subtopic}, type @kbd{C-h i m emacs
224 @key{RET} m @var{topic} @key{RET} m @var{subtopic} @key{RET}}.
225
226 If these commands don't work as expected, your system administrator may
227 not have installed the Info files, or may have installed them
228 improperly. In this case you should complain.
229
230 @xref{Getting a printed manual}, if you would like a paper copy of the
231 Emacs manual.
232
233 @node File-name conventions, Common acronyms, On-line manual, FAQ notation
234 @section What are @file{etc/SERVICE}, @file{src/config.h}, and @file{lisp/default.el}?
235 @cindex File-name conventions
236 @cindex Conventions for file names
237 @cindex Directories and files that come with Emacs
238
239 These are files that come with Emacs. The Emacs distribution is divided
240 into subdirectories; the important ones are @file{etc}, @file{lisp}, and
241 @file{src}.
242
243 If you use Emacs, but don't know where it is kept on your system, start
244 Emacs, then type @kbd{C-h v data-directory @key{RET}}. The directory
245 name displayed by this will be the full pathname of the installed
246 @file{etc} directory. (This full path is recorded in the Emacs variable
247 @code{data-directory}, and @kbd{C-h v} displays the value and the
248 documentation of a variable.)
249
250 The location of your Info directory (i.e., where on-line documentation
251 is stored) is kept in the variable @code{Info-default-directory-list}. Use
252 @kbd{C-h v Info-default-directory-list @key{RET}} to see the value of
253 this variable, which will be a list of directory names. The last
254 directory in that list is probably where most Info files are stored. By
255 default, Info documentation is placed in @file{/usr/local/info}.
256
257 Some of these files are available individually via FTP or e-mail; see
258 @ref{Informational files for Emacs}. They all are available in the
259 source distribution. Many of the files in the @file{etc} directory are
260 also available via the Emacs @samp{Help} menu, or by typing @kbd{C-h ?}
261 (@kbd{M-x help-for-help}).
262
263 Your system administrator may have removed the @file{src} directory and
264 many files from the @file{etc} directory.
265
266 @node Common acronyms, , File-name conventions, FAQ notation
267 @section What are FSF, LPF, OSF, GNU, RMS, FTP, and GPL?
268 @cindex FSF, definition of
269 @cindex LPF, definition of
270 @cindex OSF, definition of
271 @cindex GNU, definition of
272 @cindex RMS, definition of
273 @cindex Stallman, Richard, acronym for
274 @cindex Richard Stallman, acronym for
275 @cindex FTP, definition of
276 @cindex GPL, definition of
277 @cindex Acronyms, definitions for
278 @cindex Common acronyms, definitions for
279
280 @table @asis
281
282 @item FSF
283 Free Software Foundation
284
285 @item LPF
286 League for Programming Freedom
287
288 @item OSF
289 Open Software Foundation
290
291 @item GNU
292 GNU's Not Unix
293
294 @item RMS
295 Richard Matthew Stallman
296
297 @item FTP
298 File Transfer Protocol
299
300 @item GPL
301 GNU General Public License
302
303 @end table
304
305 Avoid confusing the FSF, the LPF, and the OSF. The LPF opposes
306 look-and-feel copyrights and software patents. The FSF aims to make
307 high quality free software available for everyone. The OSF is a
308 consortium of computer vendors which develops commercial software for
309 Unix systems.
310
311 The word ``free'' in the title of the Free Software Foundation refers to
312 ``freedom,'' not ``zero dollars.'' Anyone can charge any price for
313 GPL-covered software that they want to. However, in practice, the
314 freedom enforced by the GPL leads to low prices, because you can always
315 get the software for less money from someone else, since everyone has
316 the right to resell or give away GPL-covered software.
317
318 @c ------------------------------------------------------------
319 @node General questions, Getting help, FAQ notation, Top
320 @chapter General questions
321 @cindex General questions
322
323 This chapter contains general questions having to do with Emacs, the
324 Free Software Foundation, and related organizations.
325
326 @menu
327 * The LPF::
328 * Real meaning of copyleft::
329 * Guidelines for newsgroup postings::
330 * Newsgroup archives::
331 * Reporting bugs::
332 * Unsubscribing from Emacs lists::
333 * Contacting the FSF::
334 @end menu
335
336 @node The LPF, Real meaning of copyleft, General questions, General questions
337 @section What is the LPF?
338 @cindex LPF, description of
339 @cindex League for Programming Freedom
340 @cindex Software patents, opposition to
341 @cindex Patents for software, opposition to
342
343 The LPF opposes the expanding danger of software patents and
344 look-and-feel copyrights. To get more information, feel free to contact
345 the LPF via e-mail or otherwise. You may also contact
346 @email{jbw@@cs.bu.edu, Joe Wells}; he will be happy to talk to you
347 about the LPF.
348
349 You can find more information about the LPF in the file @file{etc/LPF}.
350 More papers describing the LPF's views are available on the Internet and
351 also from @uref{http://lpf.ai.mit.edu/, the LPF home page}.
352
353 @node Real meaning of copyleft, Guidelines for newsgroup postings, The LPF, General questions
354 @section What is the real legal meaning of the GNU copyleft?
355 @cindex Copyleft, real meaning of
356 @cindex GPL, real meaning of
357 @cindex General Public License, real meaning of
358 @cindex Discussion of the GPL
359
360 The real legal meaning of the GNU General Public License (copyleft) will
361 only be known if and when a judge rules on its validity and scope.
362 There has never been a copyright infringement case involving the GPL to
363 set any precedents. Please take any discussion regarding this issue to
364 the newsgroup @uref{news:gnu.misc.discuss}, which was created to hold the
365 extensive flame wars on the subject.
366
367 RMS writes:
368
369 @quotation
370 The legal meaning of the GNU copyleft is less important than the spirit,
371 which is that Emacs is a free software project and that work pertaining
372 to Emacs should also be free software. ``Free'' means that all users
373 have the freedom to study, share, change and improve Emacs. To make
374 sure everyone has this freedom, pass along source code when you
375 distribute any version of Emacs or a related program, and give the
376 recipients the same freedom that you enjoyed.
377 @end quotation
378
379 @node Guidelines for newsgroup postings, Newsgroup archives, Real meaning of copyleft, General questions
380 @section What are appropriate messages for @uref{news:gnu.emacs.help}, @uref{news:gnu.emacs.bug}, @uref{news:comp.emacs}, etc.?
381 @cindex Newsgroups, appropriate messages for
382 @cindex GNU newsgroups, appropriate messages for
383 @cindex Usenet groups, appropriate messages for
384 @cindex Mailing lists, appropriate messages for
385 @cindex Posting messages to newsgroups
386
387 @cindex GNU mailing lists
388 The file @file{etc/MAILINGLISTS} describes the purpose of each GNU
389 mailing list. (@xref{Informational files for Emacs}, if you want a copy
390 of the file.) For those lists which are gatewayed with newsgroups, it
391 lists both the newsgroup name and the mailing list address.
392
393 The newsgroup @uref{news:comp.emacs} is for discussion of Emacs programs
394 in general. This includes Emacs along with various other
395 implementations, such as XEmacs, JOVE, MicroEmacs, Freemacs, MG,
396 Unipress, CCA, and Epsilon.
397
398 Many people post Emacs questions to @uref{news:comp.emacs} because they
399 don't receive any of the @code{gnu.*} newsgroups. Arguments have been
400 made both for and against posting GNU-Emacs-specific material to
401 @uref{news:comp.emacs}. You have to decide for yourself.
402
403 Messages advocating ``non-free'' software are considered unacceptable on
404 any of the @code{gnu.*} newsgroups except for @uref{news:gnu.misc.discuss},
405 which was created to hold the extensive flame-wars on the subject.
406 ``Non-free'' software includes any software for which the end user can't
407 freely modify the source code and exchange enhancements. Be careful to
408 remove the @code{gnu.*} groups from the @samp{Newsgroups:} line when
409 posting a followup that recommends such software.
410
411 @uref{news:gnu.emacs.bug} is a place where bug reports appear, but avoid
412 posting bug reports to this newsgroup directly (@pxref{Reporting bugs}).
413
414 @node Newsgroup archives, Reporting bugs, Guidelines for newsgroup postings, General questions
415 @section Where can I get old postings to @uref{news:gnu.emacs.help} and other GNU groups?
416 @cindex Archived postings from @code{gnu.emacs.help}
417 @cindex Usenet archives for GNU groups
418 @cindex Old Usenet postings for GNU groups
419
420 The FSF has maintained archives of all of the GNU mailing lists for many
421 years, although there may be some unintentional gaps in coverage. The
422 archive is not particularly well organized or easy to retrieve
423 individual postings from, but pretty much everything is there.
424
425 The archive is at @uref{ftp://ftp-mailing-list-archives.gnu.org}.
426
427 The archive can be browsed over the web at
428 @uref{http://mail.gnu.org/archive/html/, the GNU mail archive}.
429
430 Web-based Usenet search services, such as
431 @uref{http://groups.google.com, Google}, also archive the
432 @code{gnu.*} groups.
433
434 @node Reporting bugs, Unsubscribing from Emacs lists, Newsgroup archives, General questions
435 @section Where should I report bugs and other problems with Emacs?
436 @cindex Bug reporting
437 @cindex Good bug reports
438 @cindex How to submit a bug report
439 @cindex Reporting bugs
440
441 The correct way to report Emacs bugs is by e-mail to
442 @email{bug-gnu-emacs@@gnu.org}. Anything sent here also appears in the
443 newsgroup @uref{news:gnu.emacs.bug}, but please use e-mail instead of
444 news to submit the bug report. This ensures a reliable return address
445 so you can be contacted for further details.
446
447 Be sure to read the ``Bugs'' section of the Emacs manual before reporting
448 a bug to bug-gnu-emacs! The manual describes in detail how to submit a
449 useful bug report. (@xref{On-line manual}, if you don't know how to read the
450 manual.)
451
452 RMS says:
453
454 @quotation
455 Sending bug reports to @email{help-gnu-emacs@@gnu.org} (which has the
456 effect of posting on @uref{news:gnu.emacs.help}) is undesirable because
457 it takes the time of an unnecessarily large group of people, most of
458 whom are just users and have no idea how to fix these problem.
459 @email{bug-gnu-emacs@@gnu.org} reaches a much smaller group of people
460 who are more likely to know what to do and have expressed a wish to
461 receive more messages about Emacs than the others.
462 @end quotation
463
464 RMS says it is sometimes fine to post to @uref{news:gnu.emacs.help}:
465
466 @quotation
467 If you have reported a bug and you don't hear about a possible fix,
468 then after a suitable delay (such as a week) it is okay to post on
469 @code{gnu.emacs.help} asking if anyone can help you.
470 @end quotation
471
472 If you are unsure whether you have found a bug, consider the following
473 non-exhaustive list, courtesy of RMS:
474
475 @quotation
476 If Emacs crashes, that is a bug. If Emacs gets compilation errors
477 while building, that is a bug. If Emacs crashes while building, that
478 is a bug. If Lisp code does not do what the documentation says it
479 does, that is a bug.
480 @end quotation
481
482 @node Unsubscribing from Emacs lists, Contacting the FSF, Reporting bugs, General questions
483 @section How do I unsubscribe from this mailing list?
484 @cindex Unsubscribing from GNU mailing lists
485 @cindex Removing yourself from GNU mailing lists
486
487 If you are receiving a GNU mailing list named @var{list}, you might be
488 able to unsubscribe from it by sending a request to the address
489 @email{@var{list}-request@@gnu.org}. However, this will not work if you are
490 not listed on the main mailing list, but instead receive the mail from a
491 distribution point. In that case, you will have to track down at which
492 distribution point you are listed. Inspecting the @samp{Received} headers
493 on the mail messages may help, along with liberal use of the @samp{EXPN} or
494 @samp{VRFY} sendmail commands through @samp{telnet @var{site-address}
495 smtp}. Ask your postmaster for help, if you cannot figure out these
496 details.
497
498 @node Contacting the FSF, , Unsubscribing from Emacs lists, General questions
499 @section What is the current address of the FSF?
500 @cindex Snail mail address of the FSF
501 @cindex Postal address of the FSF
502 @cindex Contracting the FSF
503 @cindex Free Software Foundation, contacting
504
505 @table @asis
506
507 @item E-mail
508 gnu@@gnu.org
509
510 @item Telephone
511 +1-617-542-5942
512
513 @item Fax
514 +1-617-542-2652
515
516 @item World Wide Web
517 @uref{http://www.gnu.org/}
518
519 @item Postal address
520 Free Software Foundation@*
521 51 Franklin Street, Fifth Floor@*
522 Boston, MA 02110-1301@*
523 USA@*
524
525 @end table
526
527 @cindex Ordering GNU software
528 For details on how to order items directly from the FSF, see the
529 @uref{http://www.gnu.org/order/order.html, GNU Web site}.
530
531 @c ------------------------------------------------------------
532 @node Getting help, Status of Emacs, General questions, Top
533 @chapter Getting help
534 @cindex Getting help
535
536 This chapter tells you how to get help with Emacs
537
538 @menu
539 * Basic editing::
540 * Learning how to do something::
541 * Getting a printed manual::
542 * Emacs Lisp documentation::
543 * Installing Texinfo documentation::
544 * Printing a Texinfo file::
545 * Viewing Info files outside of Emacs::
546 * Informational files for Emacs::
547 * Help installing Emacs::
548 * Obtaining the FAQ::
549 @end menu
550
551 @node Basic editing, Learning how to do something, Getting help, Getting help
552 @section I'm just starting Emacs; how do I do basic editing?
553 @cindex Basic editing with Emacs
554 @cindex Beginning editing
555 @cindex Tutorial, invoking the
556 @cindex Self-paced tutorial, invoking the
557 @cindex Help system, entering the
558
559 Type @kbd{C-h t} to invoke the self-paced tutorial. Just typing
560 @kbd{C-h} enters the help system. Starting with Emacs 22, the tutorial
561 is available in many foreign languages such as French, German, Japanese,
562 Russian, etc. Use @kbd{M-x help-with-tutorial-spec-language @key{RET}}
563 to choose your language and start the tutorial.
564
565 Your system administrator may have changed @kbd{C-h} to act like
566 @key{DEL} to deal with local keyboards. You can use @kbd{M-x
567 help-for-help} instead to invoke help. To discover what key (if any)
568 invokes help on your system, type @kbd{M-x where-is @key{RET}
569 help-for-help @key{RET}}. This will print a comma-separated list of key
570 sequences in the echo area. Ignore the last character in each key
571 sequence listed. Each of the resulting key sequences invokes help.
572
573 Emacs help works best if it is invoked by a single key whose value
574 should be stored in the variable @code{help-char}.
575
576 @node Learning how to do something, Getting a printed manual, Basic editing, Getting help
577 @section How do I find out how to do something in Emacs?
578 @cindex Help for Emacs
579 @cindex Learning to do something in Emacs
580 @cindex Reference card for Emacs
581 @cindex Overview of help systems
582
583 There are several methods for finding out how to do things in Emacs.
584
585 @itemize @bullet
586
587 @cindex Reading the Emacs manual
588 @item
589 The complete text of the Emacs manual is available on-line via the Info
590 hypertext reader. Type @kbd{C-h r} to display the manual in Info mode.
591 Typing @key{h} immediately after entering Info will provide a short
592 tutorial on how to use it.
593
594 @cindex Lookup a subject in a manual
595 @cindex Index search in a manual
596 @item
597 To quickly locate the section of the manual which discusses a certain
598 issue, or describes a command or a variable, type @kbd{C-h i m emacs
599 @key{RET} i @var{topic} @key{RET}}, where @var{topic} is the name of the
600 topic, the command, or the variable which you are looking for. If this
601 does not land you on the right place in the manual, press @kbd{,}
602 (comma) repeatedly until you find what you need. (The @kbd{i} and
603 @kbd{,} keys invoke the index-searching functions, which look for the
604 @var{topic} you type in all the indices of the Emacs manual.)
605
606 @cindex Apropos
607 @item
608 You can list all of the commands whose names contain a certain word
609 (actually which match a regular expression) using @kbd{C-h a} (@kbd{M-x
610 command-apropos}).
611
612 @cindex Command description in the manual
613 @item
614 The command @kbd{C-h F} (@code{Info-goto-emacs-command-node}) prompts
615 for the name of a command, and then attempts to find the section in the
616 Emacs manual where that command is described.
617
618 @cindex Finding commands and variables
619 @item
620 You can list all of the functions and variables whose names contain a
621 certain word using @kbd{M-x apropos}.
622
623 @item
624 You can list all of the functions and variables whose documentation
625 matches a regular expression or a string, using @kbd{M-x
626 apropos-documentation}.
627
628 @item
629 You can order a hardcopy of the manual from the FSF. @xref{Getting a
630 printed manual}.
631
632 @cindex Reference cards, in other languages
633 @item
634 You can get a printed reference card listing commands and keys to
635 invoke them. You can order one from the FSF for $1 (or 10 for $5),
636 or you can print your own from the @file{etc/refcard.tex} or
637 @file{etc/refcard.ps} files in the Emacs distribution. Beginning with
638 version 21.1, the Emacs distribution comes with translations of the
639 reference card into several languages; look for files named
640 @file{etc/@var{lang}-refcard.*}, where @var{lang} is a two-letter code
641 of the language. For example, the German version of the reference card
642 is in the files @file{etc/de-refcard.tex} and @file{etc/de-refcard.ps}.
643
644 @item
645 There are many other commands in Emacs for getting help and
646 information. To get a list of these commands, type @samp{?} after
647 @kbd{C-h}.
648
649 @end itemize
650
651 @node Getting a printed manual, Emacs Lisp documentation, Learning how to do something, Getting help
652 @section How do I get a printed copy of the Emacs manual?
653 @cindex Printed Emacs manual, obtaining
654 @cindex Manual, obtaining a printed or HTML copy of
655 @cindex Emacs manual, obtaining a printed or HTML copy of
656
657 You can order a printed copy of the Emacs manual from the FSF. For
658 details see the @uref{http://www.gnu.org/order/order.html, GNU Web site}.
659
660 @c The number 620 below is version-dependent!
661 The full Texinfo source for the manual also comes in the @file{man}
662 directory of the Emacs distribution, if you're daring enough to try to
663 print out this 620-page manual yourself (@pxref{Printing a Texinfo
664 file}).
665
666 If you absolutely have to print your own copy, and you don't have @TeX{},
667 you can get a PostScript version from
668
669 @uref{http://www.gnu.org/software/emacs/manual/emacs.ps.gz}
670
671 @cindex HTML version of Emacs manual, obtaining
672 An HTML version of the manual is at
673
674 @uref{http://www.gnu.org/software/emacs/manual/emacs.html}
675
676 @xref{Learning how to do something}, for how to view the manual on-line.
677
678 @node Emacs Lisp documentation, Installing Texinfo documentation, Getting a printed manual, Getting help
679 @section Where can I get documentation on Emacs Lisp?
680 @cindex Documentation on Emacs Lisp
681 @cindex Function documentation
682 @cindex Variable documentation
683 @cindex Emacs Lisp Reference Manual
684 @cindex Reference manual for Emacs Lisp
685
686 Within Emacs, you can type @kbd{C-h f} to get the documentation for a
687 function, @kbd{C-h v} for a variable.
688
689 For more information, the Emacs Lisp Reference Manual is available
690 on-line, in Info format. @xref{Top, Emacs Lisp,, elisp, The
691 Emacs Lisp Reference Manual}.
692
693 You can also order a hardcopy of the manual, details on ordering it from
694 FSF are on the @uref{http://www.gnu.org/order/order.html, GNU Web site}.
695
696 An HTML version of the Emacs Lisp Reference Manual is available at
697
698 @uref{http://www.gnu.org/software/emacs/elisp-manual/elisp.html}
699
700 @node Installing Texinfo documentation, Printing a Texinfo file, Emacs Lisp documentation, Getting help
701 @section How do I install a piece of Texinfo documentation?
702 @cindex Texinfo documentation, installing
703 @cindex Installing Texinfo documentation
704 @cindex New Texinfo files, installing
705 @cindex Documentation, installing new Texinfo files
706 @cindex Info files, how to install
707
708 First, you must turn the Texinfo files into Info files. You may do this
709 using the stand-alone @file{makeinfo} program, available as part of the latest
710 Texinfo package at
711
712 @uref{ftp://ftp.gnu.org/pub/gnu/texinfo/texinfo-4.8.tar.gz}
713
714 and all mirrors of @samp{ftp.gnu.org} (for a list, @pxref{Current GNU
715 distributions}).
716
717 For information about the Texinfo format, read the Texinfo manual which
718 comes with the Texinfo package. This manual also comes installed in
719 Info format, so you can read it on-line; type @kbd{C-h i m texinfo
720 @key{RET}}.
721
722 Alternatively, you could use the Emacs command @kbd{M-x
723 texinfo-format-buffer}, after visiting the Texinfo source file of the
724 manual you want to convert.
725
726 Neither @code{texinfo-format-buffer} nor @file{makeinfo} installs the
727 resulting Info files in Emacs's Info tree. To install Info files,
728 perform these steps:
729
730 @enumerate
731 @item
732 Move the files to the @file{info} directory in the installed Emacs
733 distribution. @xref{File-name conventions}, if you don't know where that
734 is.
735
736 @item
737 Run the @code{install-info} command, which is part of the Texinfo
738 distribution, to update the main Info directory menu, like this:
739
740 @example
741 install-info --info-dir=@var{dir-path} @var{dir-path}/@var{file}
742 @end example
743
744 @noindent
745 where @var{dir-path} is the full path to the directory where you copied
746 the produced Info file(s), and @var{file} is the name of the Info file
747 you produced and want to install.
748
749 If you don't have the @code{install-info} command installed, you can
750 edit the file @file{info/dir} in the installed Emacs distribution, and
751 add a line for the top level node in the Info package that you are
752 installing. Follow the examples already in this file. The format is:
753
754 @example
755 * Topic: (relative-pathname). Short description of topic.
756 @end example
757
758 @end enumerate
759
760 If you want to install Info files and you don't have the necessary
761 privileges, you have several options:
762
763 @itemize @bullet
764 @item
765 Info files don't actually need to be installed before being used. You
766 can feed a file name to the @code{Info-goto-node} command (invoked by
767 pressing @key{g} in Info mode) by typing the name of the file in
768 parentheses. This goes to the node named ``Top'' in that file. For
769 example, to view a Info file named @file{@var{info-file}} in your home
770 directory, you can type this:
771
772 @example
773 @kbd{C-h i g (~/@var{info-file}) @key{RET}}
774 @end example
775
776 @item
777 You can create your own Info directory. You can tell Emacs where that
778 Info directory is by adding its pathname to the value of the variable
779 @code{Info-default-directory-list}. For example, to use a private Info
780 directory which is a subdirectory of your home directory named @file{Info},
781 you could put this in your @file{.emacs} file:
782
783 @lisp
784 (setq Info-default-directory-list
785 (cons "~/Info" Info-default-directory-list))
786 @end lisp
787
788 You will need a top-level Info file named @file{dir} in this directory
789 which has everything the system @file{dir} file has in it, except it should
790 list only entries for Info files in that directory. You might not need
791 it if all files in this directory were referenced by other @file{dir}
792 files. The node lists from all @file{dir} files in
793 @code{Info-default-directory-list} are merged by the Info system.
794
795 @end itemize
796
797 @node Printing a Texinfo file, Viewing Info files outside of Emacs, Installing Texinfo documentation, Getting help
798 @section How do I print a Texinfo file?
799 @cindex Printing a Texinfo file
800 @cindex Texinfo file, printing
801 @cindex Printing documentation
802
803 You can't get nicely printed output from Info files; you must still have
804 the original Texinfo source file for the manual you want to print.
805
806 Assuming you have @TeX{} installed on your system, follow these steps:
807
808 @enumerate
809
810 @item
811 Make sure the first line of the Texinfo file looks like this:
812
813 @example
814 \input texinfo
815 @end example
816
817 You may need to change @samp{texinfo} to the full pathname of the
818 @file{texinfo.tex} file, which comes with Emacs as
819 @file{man/texinfo.tex} (or copy or link it into the current directory).
820
821 @item
822 Type @kbd{texi2dvi @var{texinfo-source}}, where @var{texinfo-source} is
823 the name of the Texinfo source file for which you want to produce a
824 printed copy.
825
826 The @samp{texi2dvi} script is part of the GNU Texinfo distribution
827 (@pxref{Installing Texinfo documentation}).
828
829 @item
830 Print the DVI file @file{@var{texinfo-source}.dvi} in the normal way for
831 printing DVI files at your site. For example, if you have a PostScript
832 printer, run the @code{dvips} program to print the DVI file on that
833 printer.
834
835 @end enumerate
836
837 To get more general instructions, retrieve the latest Texinfo package
838 (@pxref{Installing Texinfo documentation}).
839
840 @node Viewing Info files outside of Emacs, Informational files for Emacs, Printing a Texinfo file, Getting help
841 @section Can I view Info files without using Emacs?
842 @cindex Viewing Info files
843 @cindex Info file viewers
844 @cindex Alternative Info file viewers
845
846 Yes. Here are some alternative programs:
847
848 @itemize @bullet
849
850 @item
851 @code{info}, a stand-alone version of the Info program, comes as part of
852 the Texinfo package. @xref{Installing Texinfo documentation}, for
853 details.
854
855 @item
856 Xinfo, a stand-alone version of the Info program that runs under X
857 Window system. You can get it at
858 @uref{ftp://ftp.gnu.org/pub/gnu/xinfo/xinfo-1.01.01.tar.gz} and all
859 mirrors of @samp{ftp.gnu.org} (see @ref{Current GNU distributions}, for a
860 list of mirrors).
861
862 @item
863 Tkinfo, an Info viewer that runs under X Window system and uses Tcl/Tk.
864 You can get Tkinfo at
865 @uref{http://math-www.uni-paderborn.de/~axel/tkinfo/}.
866
867 @end itemize
868
869 @node Informational files for Emacs, Help installing Emacs, Viewing Info files outside of Emacs, Getting help
870 @section What informational files are available for Emacs?
871 @cindex Informational files included with Emacs
872 @cindex Files included with Emacs
873 @cindex @file{COPYING}, description of file
874 @cindex @file{DISTRIB}, description of file
875 @cindex @file{FTP}, description of file
876 @cindex @file{GNU}, description of file
877 @cindex @file{INTERVIEW}, description of file
878 @cindex @file{LPF}, description of file
879 @cindex @file{MACHINES}, description of file
880 @cindex @file{MAILINGLISTS}, description of file
881 @cindex @file{NEWS}, description of file
882 @cindex @file{SERVICE}, description of file
883 @cindex @file{SUN-SUPPORT}, description of file
884
885 This isn't a frequently asked question, but it should be! A variety of
886 informational files about Emacs and relevant aspects of the GNU project
887 are available for you to read.
888
889 The following files are available in the @file{etc} directory of the
890 Emacs distribution (see @ref{File-name conventions}, if you're not sure
891 where that is).
892
893 @table @file
894
895 @item COPYING
896 GNU General Public License
897
898 @item DISTRIB
899 Emacs Availability Information, including the popular Free Software
900 Foundation Order Form
901
902 @item FTP
903 How to get GNU Software by Internet FTP or by UUCP
904
905 @item GNU
906 The GNU Manifesto
907
908 @item INTERVIEW
909 Richard Stallman discusses his public-domain UNIX-compatible software
910 system with BYTE editors
911
912 @item LPF
913 Why you should join the League for Programming Freedom
914
915 @item MACHINES
916 Status of Emacs on Various Machines and Systems
917
918 @item MAILINGLISTS
919 GNU Project Electronic Mailing Lists
920
921 @item NEWS
922 Emacs news, a history of recent user-visible changes
923
924 @item SERVICE
925 GNU Service Directory
926
927 @item SUN-SUPPORT
928 including ``Using Emacstool with GNU Emacs''
929
930 @end table
931
932 More GNU information, including back issues of the @cite{GNU's
933 Bulletin}, are at
934
935 @uref{http://www.gnu.org/bulletins/bulletins.html} and
936
937 @uref{http://www.cs.pdx.edu/~trent/gnu/gnu.html}
938
939 @node Help installing Emacs, Obtaining the FAQ, Informational files for Emacs, Getting help
940 @section Where can I get help in installing Emacs?
941 @cindex Installation help
942 @cindex Help installing Emacs
943
944 @xref{Installing Emacs}, for some basic installation hints, and see
945 @ref{Problems building Emacs}, or @ref{Linking with -lX11 fails}, if you
946 have problems with the installation.
947
948 The file @file{etc/SERVICE} (see @ref{File-name conventions}, if you're
949 not sure where that is) lists companies and individuals willing to sell
950 you help in installing or using Emacs. An up-to-date version this file
951 is available on @samp{ftp.gnu.org} (@pxref{Informational files for
952 Emacs}).
953
954 @node Obtaining the FAQ, , Help installing Emacs, Getting help
955 @section Where can I get the latest version of this FAQ?
956 @cindex FAQ, obtaining the
957 @cindex Latest FAQ version, obtaining the
958 @cindex Retrieving the latest FAQ version
959 @cindex E-mail, retrieving the FAQ via
960 @cindex Web, reading the FAQ on the
961
962 The Emacs FAQ is available in several ways:
963
964 @itemize @bullet
965
966 @item
967 Inside of Emacs itself. You can get it from selecting the @samp{Emacs
968 FAQ} option from the @samp{Help} menu of the Emacs menu bar at the top
969 of any Emacs frame, or by typing @kbd{C-h C-f} (@kbd{M-x view-emacs-FAQ}).
970
971 @item
972 Via USENET. If you can read news, the FAQ should be available in your
973 news spool, in both the @uref{news:gnu.emacs.help} and
974 @uref{news:comp.emacs} newsgroups. Every news reader should allow you
975 to read any news article that is still in the news spool, even if you
976 have read the article before. You may need to read the instructions for
977 your news reader to discover how to do this. In @file{rn}, this command
978 will do this for you at the article selection level:
979
980 @example
981 ?GNU Emacs Frequently Asked Questions?rc:m
982 @end example
983
984 In Gnus, you should type @kbd{C-u C-x C-s} from the @file{*Summary*}
985 buffer or @kbd{C-u @key{SPC}} from the @file{*Newsgroup*} buffer to view
986 all articles in a newsgroup.
987
988 If the FAQ articles have expired and have been deleted from your news
989 spool, it might (or might not) do some good to complain to your news
990 administrator, because the most recent FAQ should not expire for a
991 while.
992
993 @item
994 In the Emacs distribution. Since Emacs 18.56, the FAQ at the time
995 of release has been part of the Emacs distribution as either
996 @file{etc/FAQ} or @file{man/faq.texi} (@pxref{File-name conventions}).
997
998 @item
999 Via anonymous ftp and e-mail from @file{rtfm.mit.edu} (and its mirror in
1000 Europe), the main repository for FAQs and other items posted to
1001 news.answers. The Emacs FAQs are available at
1002
1003 @uref{ftp://rtfm.mit.edu/pub/usenet/comp.emacs/} and
1004
1005 @uref{ftp://ftp.uni-paderborn.de/pub/doc/FAQ/comp/emacs/}
1006
1007 If you do not have access to anonymous FTP, you can access the archives
1008 using the @file{rtfm.mit.edu} mail server. The Emacs FAQ can be
1009 retrieved by sending mail to @email{mail-server@@rtfm.mit.edu} with a
1010 blank subject and containing
1011
1012 @example
1013 send usenet/news.answers/GNU-Emacs-FAQ/diffs
1014 send usenet/news.answers/GNU-Emacs-FAQ/part1
1015 send usenet/news.answers/GNU-Emacs-FAQ/part2
1016 send usenet/news.answers/GNU-Emacs-FAQ/part3
1017 send usenet/news.answers/GNU-Emacs-FAQ/part4
1018 send usenet/news.answers/GNU-Emacs-FAQ/part5
1019 @end example
1020
1021 For more information, send email to @email{mail-server@@rtfm.mit.edu}
1022 with @samp{help} and @samp{index} in the body on separate lines.
1023 @end itemize
1024
1025 @c ------------------------------------------------------------
1026 @node Status of Emacs, Common requests, Getting help, Top
1027 @chapter Status of Emacs
1028 @cindex Status of Emacs
1029
1030 This chapter gives you basic information about Emacs, including its
1031 latest version status.
1032
1033 @menu
1034 * Origin of the term Emacs::
1035 * Latest version of Emacs::
1036 * New in Emacs 20::
1037 * New in Emacs 21::
1038 * New in Emacs 22::
1039 @end menu
1040
1041 @node Origin of the term Emacs, Latest version of Emacs, Status of Emacs, Status of Emacs
1042 @section Where does the name ``Emacs'' come from?
1043 @cindex Origin of the term ``Emacs''
1044 @cindex Emacs name origin
1045 @cindex TECO
1046 @cindex Original version of Emacs
1047
1048 Emacs originally was an acronym for Editor MACroS. RMS says he ``picked
1049 the name Emacs because @key{E} was not in use as an abbreviation on ITS at
1050 the time.'' The first Emacs was a set of macros written in 1976 at MIT
1051 by RMS for the editor TECO (Text Editor and COrrector, originally Tape
1052 Editor and COrrector) under ITS on a PDP-10. RMS had already extended
1053 TECO with a ``real-time'' full-screen mode with reprogrammable keys.
1054 Emacs was started by @email{gls@@east.sun.com, Guy Steele} as a project
1055 to unify the many divergent TECO command sets and key bindings at MIT,
1056 and completed by RMS.
1057
1058 Many people have said that TECO code looks a lot like line noise; you
1059 can read more at @uref{news:alt.lang.teco}. Someone has written a TECO
1060 implementation in Emacs Lisp (to find it, see @ref{Packages that do not
1061 come with Emacs}); it would be an interesting project to run the
1062 original TECO Emacs inside of Emacs.
1063
1064 @cindex Why Emacs?
1065 For some not-so-serious alternative reasons for Emacs to have that
1066 name, check out the file @file{etc/JOKES} (@pxref{File-name
1067 conventions}).
1068
1069 @node Latest version of Emacs, New in Emacs 20, Origin of the term Emacs, Status of Emacs
1070 @section What is the latest version of Emacs?
1071 @cindex Version, latest
1072 @cindex Latest version of Emacs
1073
1074 Emacs @value{VER} is the current version as of this writing.
1075
1076 @node New in Emacs 20, New in Emacs 21, Latest version of Emacs, Status of Emacs
1077 @section What is different about Emacs 20?
1078 @cindex Differences between Emacs 19 and Emacs 20
1079 @cindex Emacs 20, new features in
1080
1081 To find out what has changed in recent versions, type @kbd{C-h C-n}
1082 (@kbd{M-x view-emacs-news}). The oldest changes are at the bottom of
1083 the file, so you might want to read it starting there, rather than at
1084 the top.
1085
1086 The differences between Emacs versions 18 and 19 was rather dramatic;
1087 the introduction of frames, faces, and colors on windowing systems was
1088 obvious to even the most casual user.
1089
1090 There are differences between Emacs versions 19 and 20 as well, but many
1091 are more subtle or harder to find. Among the changes are the inclusion
1092 of MULE code for languages that use non-Latin characters and for mixing
1093 several languages in the same document; the ``Customize'' facility for
1094 modifying variables without having to use Lisp; and automatic conversion
1095 of files from Macintosh, Microsoft, and Unix platforms.
1096
1097 A number of older Lisp packages, such as Gnus, Supercite and the
1098 calendar/diary, have been updated and enhanced to work with Emacs 20,
1099 and are now included with the standard distribution.
1100
1101
1102 @node New in Emacs 21, New in Emacs 22, New in Emacs 20, Status of Emacs
1103 @section What is different about Emacs 21?
1104 @cindex Differences between Emacs 20 and Emacs 21
1105 @cindex Emacs 21, new features in
1106 @cindex Recently introduced features
1107
1108 @cindex Variable-size fonts
1109 @cindex Toolbar support
1110 Emacs 21 features a thorough rewrite of the display engine. The new
1111 display engine supports variable-size fonts, images, and can play sounds
1112 on platforms which support that. As a result, the visual appearance of
1113 Emacs, when it runs on a windowed display, is much more reminiscent of
1114 modern GUI programs, and includes 3D widgets (used for the mode line and
1115 the scroll bars), a configurable and extensible toolbar, tooltips
1116 (a.k.a.@: balloon help), and other niceties.
1117
1118 @cindex Colors on text-only terminals
1119 @cindex TTY colors
1120 In addition, Emacs 21 supports faces on text-only terminals. This means
1121 that you can now have colors when you run Emacs on a GNU/Linux console
1122 and on @code{xterm} with @kbd{emacs -nw}.
1123
1124 @node New in Emacs 22, , New in Emacs 21, Status of Emacs
1125 @section What is different about Emacs 22?
1126 @cindex Differences between Emacs 21 and Emacs 22
1127 @cindex Emacs 22, new features in
1128 @cindex Recently introduced features
1129
1130 @c FIXME: Improve this node before the 22.1 release.
1131 @cindex Default features
1132 Font-lock mode, auto-compression mode, and file name shadow mode are now
1133 enabled by default. It is now possible to follow links with
1134 @kbd{mouse-1}.
1135
1136 @cindex Supported systems
1137 Emacs 22 features support for GNU/Linux systems on S390 and X86-64
1138 machines, as well as support for the Mac OS X and Cygwin operating
1139 systems.
1140
1141 @cindex GTK+ Toolkit
1142 @cindex Drag-and-drop
1143 @cindex Mouse wheel
1144 Emacs can now be built with GTK+ widgets, and supports drag-and-drop
1145 operation on X. Mouse wheel support is now enabled by default.
1146
1147 @cindex New modes
1148 Many new modes and packages have been included in Emacs, such as Leim,
1149 Calc, Tramp and URL, as well as IDO, CUA, rcirc, conf-mode,
1150 python-mode, table, tumme, SES, ruler, Flymake, Org, etc.
1151
1152 @cindex Documentation
1153 @cindex Emacs Lisp Manual
1154 In addition, Emacs 22 now includes the Emacs Lisp Reference Manual
1155 (@pxref{Emacs Lisp documentation}) and the Emacs Lisp Intro.
1156
1157 @c ------------------------------------------------------------
1158 @node Common requests, Bugs and problems, Status of Emacs, Top
1159 @chapter Common requests
1160 @cindex Common requests
1161
1162 @menu
1163 * Setting up a customization file::
1164 * Debugging a customization file::
1165 * Colors on a TTY::
1166 * Displaying the current line or column::
1167 * Displaying the current file name in the titlebar::
1168 * Turning on abbrevs by default::
1169 * Turning on auto-fill by default::
1170 * Associating modes with files::
1171 * Working with unprintable characters::
1172 * Highlighting a region::
1173 * Controlling case sensitivity::
1174 * Wrapping words automatically::
1175 * Spell-checkers::
1176 * Checking TeX and *roff documents::
1177 * Changing load-path::
1178 * Using an already running Emacs process::
1179 * Compiler error messages::
1180 * Indenting switch statements::
1181 * Customizing C and C++ indentation::
1182 * Horizontal scrolling::
1183 * Overwrite mode::
1184 * Turning off beeping::
1185 * Turning the volume down::
1186 * Automatic indentation::
1187 * Matching parentheses::
1188 * Hiding #ifdef lines::
1189 * Repeating commands::
1190 * Valid X resources::
1191 * Evaluating Emacs Lisp code::
1192 * Changing the length of a Tab::
1193 * Inserting > at the beginning of each line::
1194 * Underlining paragraphs::
1195 * Repeating a command as many times as possible::
1196 * Forcing the cursor to remain in the same column::
1197 * Forcing Emacs to iconify itself::
1198 * Using regular expressions::
1199 * Replacing text across multiple files::
1200 * Documentation for etags::
1201 * Disabling backups::
1202 * Disabling auto-save-mode::
1203 * Going to a line by number::
1204 * Modifying pull-down menus::
1205 * Deleting menus and menu options::
1206 * Turning on syntax highlighting::
1207 * Scrolling only one line::
1208 * Replacing highlighted text::
1209 * Editing MS-DOS files::
1210 * Filling paragraphs with a single space::
1211 * Escape sequences in shell output::
1212 @end menu
1213
1214 @node Setting up a customization file, Colors on a TTY, Common requests, Common requests
1215 @section How do I set up a @file{.emacs} file properly?
1216 @cindex @file{.emacs} file, setting up
1217 @cindex @file{.emacs} file, locating
1218 @cindex Init file, setting up
1219 @cindex Customization file, setting up
1220
1221 @inforef{Init File, Init File, emacs}.
1222
1223 In general, new Emacs users should not have @file{.emacs} files, because
1224 it causes confusing non-standard behavior. Then they send questions to
1225 @email{help-gnu-emacs@@gnu.org} asking why Emacs isn't behaving as
1226 documented.
1227
1228 Beginning with version 20.1, Emacs includes the new Customize facility,
1229 which can be invoked using @kbd{M-x customize @key{RET}}. This allows
1230 users who are unfamiliar with Emacs Lisp to modify their @file{.emacs}
1231 files in a relatively straightforward way, using menus rather than Lisp
1232 code. Most packages support Customize as of this writing.
1233
1234 While Customize might indeed make it easier to configure Emacs,
1235 consider taking a bit of time to learn Emacs Lisp and modifying your
1236 @file{.emacs} directly. Simple configuration options are described
1237 rather completely in @inforef{Init File, Init File, emacs}, for users
1238 interested in performing frequently requested, basic tasks.
1239
1240 Sometimes users are unsure as to where their @file{.emacs} file should
1241 be found. Visiting the file as @file{~/.emacs} from Emacs will find
1242 the correct file.
1243
1244 @node Colors on a TTY, Debugging a customization file, Setting up a customization file, Common requests
1245 @section How do I get colors and syntax highlighting on a TTY?
1246 @cindex Colors on a TTY
1247 @cindex Syntax highlighting on a TTY
1248 @cindex Console, colors
1249
1250 In Emacs 21.1 and later, colors and faces are supported in non-windowed mode,
1251 i.e.@: on Unix and GNU/Linux text-only terminals and consoles, and when
1252 invoked as @samp{emacs -nw} on X and MS-Windows. (Colors and faces were
1253 supported in the MS-DOS port since Emacs 19.29.) Emacs automatically
1254 detects color support at startup and uses it if available. If you think
1255 that your terminal supports colors, but Emacs won't use them, check the
1256 @code{termcap} entry for your display type for color-related
1257 capabilities.
1258
1259 The command @kbd{M-x list-colors-display} pops up a window which
1260 exhibits all the colors Emacs knows about on the current display.
1261
1262 Syntax highlighting is on by default since version 22.1.
1263
1264 @node Debugging a customization file, Displaying the current line or column, Colors on a TTY, Common requests
1265 @section How do I debug a @file{.emacs} file?
1266 @cindex Debugging @file{.emacs} file
1267 @cindex @file{.emacs} debugging
1268 @cindex Init file debugging
1269 @cindex @samp{-debug-init} option
1270
1271 Start Emacs with the @samp{-debug-init} command-line option. This
1272 enables the Emacs Lisp debugger before evaluating your @file{.emacs}
1273 file, and places you in the debugger if something goes wrong. The top
1274 line in the @file{trace-back} buffer will be the error message, and the
1275 second or third line of that buffer will display the Lisp code from your
1276 @file{.emacs} file that caused the problem.
1277
1278 You can also evaluate an individual function or argument to a function
1279 in your @file{.emacs} file by moving the cursor to the end of the
1280 function or argument and typing @kbd{C-x C-e} (@kbd{M-x
1281 eval-last-sexp}).
1282
1283 Use @kbd{C-h v} (@kbd{M-x describe-variable}) to check the value of
1284 variables which you are trying to set or use.
1285
1286 @node Displaying the current line or column, Displaying the current file name in the titlebar, Debugging a customization file, Common requests
1287 @section How do I make Emacs display the current line (or column) number?
1288 @cindex @code{line-number-mode}
1289 @cindex Displaying the current line or column
1290 @cindex Line number, displaying the current
1291 @cindex Column, displaying the current
1292 @cindex @code{mode-line-format}
1293
1294 To have Emacs automatically display the current line number of the point
1295 in the mode line, do @kbd{M-x line-number-mode}. You can also put the
1296 form
1297
1298 @lisp
1299 (setq line-number-mode t)
1300 @end lisp
1301
1302 @noindent
1303 in your @file{.emacs} file to achieve this whenever you start Emacs.
1304 (Line number display is on by default, unless your site-specific
1305 initialization disables it.) Note that Emacs will not display the line
1306 number if the buffer's size in bytes is larger than the value of the
1307 variable @code{line-number-display-limit}.
1308
1309 As of Emacs 20, you can similarly display the current column with
1310 @kbd{M-x column-number-mode}, or by putting the form
1311
1312 @lisp
1313 (setq column-number-mode t)
1314 @end lisp
1315
1316 @noindent
1317 in your @file{.emacs} file.
1318
1319 The @code{"%c"} format specifier in the variable @code{mode-line-format}
1320 will insert the current column's value into the mode line. See the
1321 documentation for @code{mode-line-format} (using @kbd{C-h v
1322 mode-line-format @key{RET}}) for more information on how to set and use
1323 this variable.
1324
1325 Users of all Emacs versions can display the current column using the
1326 @samp{column} package written by @email{abraham@@dina.kvl.dk, Per
1327 Abrahamsen}. @xref{Packages that do not come with Emacs}, for
1328 instructions on how to get it.
1329
1330 @cindex Set number capability in @code{vi} emulators
1331 None of the @code{vi} emulation modes provide the ``set number''
1332 capability of @code{vi} (as far as we know). The @samp{setnu} package
1333 written by @email{kyle@@wonderworks.com, Kyle Jones} provides this
1334 feature. So too does @samp{wb-line-number}, written by
1335 @email{naoki.y.nakamura@@nifty.com, Naoki Nakamura}.
1336
1337 @node Displaying the current file name in the titlebar, Turning on abbrevs by default, Displaying the current line or column, Common requests
1338 @section How can I modify the titlebar to contain the current file name?
1339 @cindex Titlebar, displaying the current file name in
1340 @cindex File name, displaying in the titlebar
1341 @cindex @code{frame-title-format}
1342
1343 The contents of an Emacs frame's titlebar is controlled by the variable
1344 @code{frame-title-format}, which has the same structure as the variable
1345 @code{mode-line-format}. (Use @kbd{C-h v} or @kbd{M-x
1346 describe-variable} to get information about one or both of these
1347 variables.)
1348
1349 By default, the titlebar for a frame does contain the name of the buffer
1350 currently being visited, except if there is a single frame. In such a
1351 case, the titlebar contains Emacs invocation name and the name of the
1352 machine at which Emacs was invoked. This is done by setting
1353 @code{frame-title-format} to the default value of
1354
1355 @lisp
1356 (multiple-frames "%b" ("" invocation-name "@@" system-name))
1357 @end lisp
1358
1359 To modify the behavior such that frame titlebars contain the buffer's
1360 name regardless of the number of existing frames, include the following
1361 in your @file{.emacs}:
1362
1363 @lisp
1364 (setq frame-title-format "%b")
1365 @end lisp
1366
1367 @node Turning on abbrevs by default, Turning on auto-fill by default, Displaying the current file name in the titlebar, Common requests
1368 @section How do I turn on abbrevs by default just in mode @var{mymode}?
1369 @cindex Abbrevs, turning on by default
1370
1371 Put this in your @file{.emacs} file:
1372
1373 @lisp
1374 (condition-case ()
1375 (quietly-read-abbrev-file)
1376 (file-error nil))
1377
1378 (add-hook '@var{mymode}-mode-hook
1379 (lambda ()
1380 (setq abbrev-mode t)))
1381 @end lisp
1382
1383 Starting with Emacs 22, the standard abbrevs file is read automatically
1384 at startup, so the first of these two forms becomes unnecessary.
1385
1386 @node Turning on auto-fill by default, Associating modes with files, Turning on abbrevs by default, Common requests
1387 @section How do I turn on @code{auto-fill-mode} by default?
1388 @cindex @code{auto-fill-mode}, activating automatically
1389 @cindex Filling automatically
1390 @cindex Automatic entry to @code{auto-fill-mode}
1391
1392 To turn on @code{auto-fill-mode} just once for one buffer, use @kbd{M-x
1393 auto-fill-mode}.
1394
1395 To turn it on for every buffer in a certain mode, you must use the hook
1396 for that mode. For example, to turn on @code{auto-fill} mode for all
1397 text buffers, including the following in your @file{.emacs} file:
1398
1399 @lisp
1400 (add-hook 'text-mode-hook 'turn-on-auto-fill)
1401 @end lisp
1402
1403 If you want @code{auto-fill} mode on in all major modes, do this:
1404
1405 @lisp
1406 (setq-default auto-fill-function 'do-auto-fill)
1407 @end lisp
1408
1409 @node Associating modes with files, Working with unprintable characters, Turning on auto-fill by default, Common requests
1410 @section How do I make Emacs use a certain major mode for certain files?
1411 @cindex Associating modes with files
1412 @cindex File extensions and modes
1413 @cindex @code{auto-mode-alist}, modifying
1414 @cindex Modes, associating with file extensions
1415
1416 If you want to use a certain mode @var{foo} for all files whose names end
1417 with the extension @file{.@var{bar}}, this will do it for you:
1418
1419 @lisp
1420 (setq auto-mode-alist (cons '("\\.@var{bar}\\'" . @var{foo}-mode) auto-mode-alist))
1421 @end lisp
1422
1423 Otherwise put this somewhere in the first line of any file you want to
1424 edit in the mode @var{foo} (in the second line, if the first line begins
1425 with @samp{#!}):
1426
1427 @example
1428 -*- @var{foo} -*-
1429 @end example
1430
1431 @cindex Major mode for shell scripts
1432 Beginning with Emacs 19, the variable @code{interpreter-mode-alist}
1433 specifies which mode to use when loading a shell script. (Emacs
1434 determines which interpreter you're using by examining the first line of
1435 the script.) This feature only applies when the file name doesn't
1436 indicate which mode to use. Use @kbd{C-h v} (or @kbd{M-x
1437 describe-variable}) on @code{interpreter-mode-alist} to learn more.
1438
1439 @node Working with unprintable characters, Highlighting a region, Associating modes with files, Common requests
1440 @section How do I search for, delete, or replace unprintable (eight-bit or control) characters?
1441 @cindex Unprintable characters, working with
1442 @cindex Working with unprintable characters
1443 @cindex Control characters, working with
1444 @cindex Eight-bit characters, working with
1445 @cindex Searching for unprintable characters
1446 @cindex Regexps and unprintable characters
1447
1448 To search for a single character that appears in the buffer as, for
1449 example, @samp{\237}, you can type @kbd{C-s C-q 2 3 7}. (This assumes
1450 the value of @code{search-quote-char} is 17 (i.e., @kbd{C-q}).)
1451 Searching for @strong{all} unprintable characters is best done with a
1452 regular expression (@dfn{regexp}) search. The easiest regexp to use for
1453 the unprintable chars is the complement of the regexp for the printable
1454 chars.
1455
1456 @itemize @bullet
1457
1458 @item
1459 Regexp for the printable chars: @samp{[\t\n\r\f -~]}
1460
1461 @item
1462 Regexp for the unprintable chars: @samp{[^\t\n\r\f -~]}
1463
1464 @end itemize
1465
1466 To type these special characters in an interactive argument to
1467 @code{isearch-forward-regexp} or @code{re-search-forward}, you need to
1468 use @kbd{C-q}. (@samp{\t}, @samp{\n}, @samp{\r}, and @samp{\f} stand
1469 respectively for @key{TAB}, @key{LFD}, @key{RET}, and @kbd{C-l}.) So,
1470 to search for unprintable characters using @code{re-search-forward}:
1471
1472 @kbd{M-x re-search-forward @key{RET} [^ @key{TAB} C-q @key{LFD} C-q @key{RET} C-q C-l @key{SPC} -~] @key{RET}}
1473
1474 Using @code{isearch-forward-regexp}:
1475
1476 @kbd{C-M-s [^ @key{TAB} @key{LFD} C-q @key{RET} C-q C-l @key{SPC} -~]}
1477
1478 To delete all unprintable characters, simply use replace-regexp:
1479
1480 @kbd{M-x replace-regexp @key{RET} [^ @key{TAB} C-q @key{LFD} C-q @key{RET} C-q C-l @key{SPC} -~] @key{RET} @key{RET}}
1481
1482 Replacing is similar to the above. To replace all unprintable
1483 characters with a colon, use:
1484
1485 M-x replace-regexp @key{RET} [^ @key{TAB} C-q @key{LFD} C-q @key{RET} C-q C-l @key{SPC} -~] @key{RET} : @key{RET}
1486
1487 @itemize @bullet
1488
1489 @item
1490 You don't need to quote @key{TAB} with either isearch or typing
1491 something in the minibuffer.
1492
1493 @end itemize
1494
1495 @node Highlighting a region, Controlling case sensitivity, Working with unprintable characters, Common requests
1496 @section How can I highlight a region of text in Emacs?
1497 @cindex Highlighting text
1498 @cindex Text, highlighting
1499 @cindex @code{transient-mark-mode}
1500 @cindex Region, highlighting a
1501
1502 You can cause the region to be highlighted when the mark is active by
1503 including
1504
1505 @lisp
1506 (transient-mark-mode t)
1507 @end lisp
1508
1509 @noindent
1510 in your @file{.emacs} file. (Also see @ref{Turning on syntax
1511 highlighting}.)
1512
1513 @node Controlling case sensitivity, Wrapping words automatically, Highlighting a region, Common requests
1514 @section How do I control Emacs's case-sensitivity when searching/replacing?
1515 @cindex @code{case-fold-search}
1516 @cindex Case sensitivity of searches
1517 @cindex Searching without case sensitivity
1518 @cindex Ignoring case in searches
1519
1520 For searching, the value of the variable @code{case-fold-search}
1521 determines whether they are case sensitive:
1522
1523 @lisp
1524 (setq case-fold-search nil) ; make searches case sensitive
1525 (setq case-fold-search t) ; make searches case insensitive
1526 @end lisp
1527
1528 @cindex Case sensitivity in replacements
1529 @cindex Replacing, and case sensitivity
1530 @cindex @code{case-replace}
1531 Similarly, for replacing, the variable @code{case-replace} determines
1532 whether replacements preserve case.
1533
1534 You can also toggle case sensitivity at will in isearch with @kbd{M-c}.
1535
1536 To change the case sensitivity just for one major mode, use the major
1537 mode's hook. For example:
1538
1539 @lisp
1540 (add-hook '@var{foo}-mode-hook
1541 (lambda ()
1542 (setq case-fold-search nil)))
1543 @end lisp
1544
1545 @node Wrapping words automatically, Spell-checkers, Controlling case sensitivity, Common requests
1546 @section How do I make Emacs wrap words for me?
1547 @cindex Wrapping word automatically
1548 @cindex Wrapping lines
1549 @cindex Line wrap
1550 @cindex @code{auto-fill-mode}, introduction to
1551 @cindex Maximum line width, default value
1552 @cindex @code{fill-column}, default value
1553
1554 Use @code{auto-fill-mode}, activated by typing @kbd{M-x auto-fill-mode}.
1555 The default maximum line width is 70, determined by the variable
1556 @code{fill-column}. To learn how to turn this on automatically, see
1557 @ref{Turning on auto-fill by default}.
1558
1559 @node Spell-checkers, Checking TeX and *roff documents, Wrapping words automatically, Common requests
1560 @section Where can I get a better spelling checker for Emacs?
1561 @cindex Checking spelling
1562 @cindex Spelling, checking text documents
1563
1564 Use Ispell. @xref{Ispell}.
1565
1566 @node Checking TeX and *roff documents, Changing load-path, Spell-checkers, Common requests
1567 @section How can I spell-check @TeX{} or *roff documents?
1568 @cindex Spelling, checking @TeX{} documents
1569 @cindex @TeX{} documents, checking spelling in
1570
1571 Use Ispell. Ispell can handle @TeX{} and *roff documents.
1572 @xref{Ispell}.
1573
1574 @node Changing load-path, Using an already running Emacs process, Checking TeX and *roff documents, Common requests
1575 @section How do I change @code{load-path}?
1576 @cindex @code{load-path}, modifying
1577 @cindex Modifying @code{load-path}
1578 @cindex Adding to @code{load-path}
1579
1580 In general, you should only add to the @code{load-path}. You can add
1581 directory @var{/dir/subdir} to the load path like this:
1582
1583 @lisp
1584 (setq load-path (cons "/dir/subdir/" load-path))
1585 @end lisp
1586
1587 To do this relative to your home directory:
1588
1589 @lisp
1590 (setq load-path (cons "~/mysubdir/" load-path))
1591 @end lisp
1592
1593 @node Using an already running Emacs process, Compiler error messages, Changing load-path, Common requests
1594 @section How do I use an already running Emacs from another window?
1595 @cindex @code{emacsclient}
1596 @cindex Emacs server functions
1597 @cindex Using an existing Emacs process
1598
1599 @code{emacsclient}, which comes with Emacs, is for editing a file using
1600 an already running Emacs rather than starting up a new Emacs. It does
1601 this by sending a request to the already running Emacs, which must be
1602 expecting the request.
1603
1604 @itemize @bullet
1605
1606 @item
1607 Setup:
1608
1609 Emacs must have executed the @code{server-start} function for
1610 @samp{emacsclient} to work. This can be done either by a command line
1611 option:
1612
1613 @example
1614 emacs -f server-start
1615 @end example
1616
1617 or by invoking @code{server-start} from @file{.emacs}:
1618
1619 @lisp
1620 (if (@var{some conditions are met}) (server-start))
1621 @end lisp
1622
1623 When this is done, Emacs creates a Unix domain socket named
1624 @file{server} in @file{/tmp/emacs@var{userid}}. See
1625 @code{server-socket-dir}.
1626
1627 To get your news reader, mail reader, etc., to invoke
1628 @samp{emacsclient}, try setting the environment variable @code{EDITOR}
1629 (or sometimes @code{VISUAL}) to the value @samp{emacsclient}. You may
1630 have to specify the full pathname of the @samp{emacsclient} program
1631 instead. Examples:
1632
1633 @example
1634 # csh commands:
1635 setenv EDITOR emacsclient
1636
1637 # using full pathname
1638 setenv EDITOR /usr/local/emacs/etc/emacsclient
1639
1640 # sh command:
1641 EDITOR=emacsclient ; export EDITOR
1642 @end example
1643
1644 @item
1645 Normal use:
1646
1647 When @samp{emacsclient} is run, it connects to the socket and passes its
1648 command line options to Emacs, which at the next opportunity will visit
1649 the files specified. (Line numbers can be specified just like with
1650 Emacs.) The user will have to switch to the Emacs window by hand. When
1651 the user is done editing a file, the user can type @kbd{C-x #} (or
1652 @kbd{M-x server-edit}) to indicate this. If there is another buffer
1653 requested by @code{emacsclient}, Emacs will switch to it; otherwise
1654 @code{emacsclient} will exit, signaling the calling program to continue.
1655
1656 @cindex @code{gnuserv}
1657 There is an enhanced version of @samp{emacsclient} called
1658 @samp{gnuserv}, written by @email{ange@@hplb.hpl.hp.com, Andy Norman}
1659 (@pxref{Packages that do not come with Emacs}). @samp{gnuserv} uses
1660 Internet domain sockets, so it can work across most network connections.
1661
1662 The most recent @samp{gnuserv} package is available at
1663
1664 @uref{http://meltin.net/hacks/emacs/}
1665
1666 @end itemize
1667
1668 @node Compiler error messages, Indenting switch statements, Using an already running Emacs process, Common requests
1669 @section How do I make Emacs recognize my compiler's funny error messages?
1670 @cindex Compiler error messages, recognizing
1671 @cindex Recognizing non-standard compiler errors
1672 @cindex Regexps for recognizing compiler errors
1673 @cindex Errors, recognizing compiler
1674
1675 Customize the @code{compilation-error-regexp-alist} variable.
1676
1677 @node Indenting switch statements, Customizing C and C++ indentation, Compiler error messages, Common requests
1678 @section How do I change the indentation for @code{switch}?
1679 @cindex @code{switch}, indenting
1680 @cindex Indenting of @code{switch}
1681
1682 Many people want to indent their @code{switch} statements like this:
1683
1684 @example
1685 f()
1686 @{
1687 switch(x) @{
1688 case A:
1689 x1;
1690 break;
1691 case B:
1692 x2;
1693 break;
1694 default:
1695 x3;
1696 @}
1697 @}
1698 @end example
1699
1700 The solution at first appears to be: set @code{c-indent-level} to 4 and
1701 @code{c-label-offset} to -2. However, this will give you an indentation
1702 spacing of four instead of two.
1703
1704 The @emph{real} solution is to use @code{cc-mode} (the default mode for
1705 C programming in Emacs 20 and later) and add the following line to your
1706 @file{.emacs}:
1707
1708 @lisp
1709 (c-set-offset 'case-label '+)
1710 @end lisp
1711
1712 There appears to be no way to do this with the old @code{c-mode}.
1713
1714 @node Customizing C and C++ indentation, Horizontal scrolling, Indenting switch statements, Common requests
1715 @section How to customize indentation in C, C@t{++}, and Java buffers?
1716 @cindex Indentation, how to customize
1717 @cindex Customize indentation
1718
1719 The Emacs @code{cc-mode} features an interactive procedure for
1720 customizing the indentation style, which is fully explained in the
1721 @cite{CC Mode} manual that is part of the Emacs distribution, see
1722 @ref{Customizing Indentation, , Customization Indentation, ccmode,
1723 The CC Mode Manual}. Here's a short summary of the procedure:
1724
1725 @enumerate
1726 @item
1727 Go to the beginning of the first line where you don't like the
1728 indentation and type @kbd{C-c C-o}. Emacs will prompt you for the
1729 syntactic symbol; type @key{RET} to accept the default it suggests.
1730
1731 @item
1732 Emacs now prompts for the offset of this syntactic symbol, showing the
1733 default (the current definition) inside parentheses. You can choose
1734 one of these:
1735
1736 @table @code
1737 @item 0
1738 No extra indentation.
1739 @item +
1740 Indent one basic offset.
1741 @item -
1742 Outdent one basic offset.
1743 @item ++
1744 Indent two basic offsets
1745 @item --
1746 Outdent two basic offsets.
1747 @item *
1748 Indent half basic offset.
1749 @item /
1750 Outdent half basic offset.
1751 @end table
1752
1753 @item
1754 After choosing one of these symbols, type @kbd{C-c C-q} to reindent
1755 the line or the block according to what you just specified.
1756
1757 @item
1758 If you don't like the result, go back to step 1. Otherwise, add the
1759 following line to your @file{.emacs}:
1760
1761 @lisp
1762 (c-set-offset '@var{syntactic-symbol} @var{offset})
1763 @end lisp
1764
1765 @noindent
1766 where @var{syntactic-symbol} is the name Emacs shows in the minibuffer
1767 when you type @kbd{C-c C-o} at the beginning of the line, and
1768 @var{offset} is one of the indentation symbols listed above (@code{+},
1769 @code{/}, @code{0}, etc.) that you've chosen during the interactive
1770 procedure.
1771
1772 @item
1773 Go to the next line whose indentation is not to your liking and repeat
1774 the process there.
1775 @end enumerate
1776
1777 It is recommended to put all the resulting @code{(c-set-offset ...)}
1778 customizations inside a C mode hook, like this:
1779
1780 @lisp
1781 (defun my-c-mode-hook ()
1782 (c-set-offset ...)
1783 (c-set-offset ...))
1784 (add-hook 'c-mode-hook 'my-c-mode-hook)
1785 @end lisp
1786
1787 @noindent
1788 Using @code{c-mode-hook} avoids the need to put a @w{@code{(require
1789 'cc-mode)}} into your @file{.emacs} file, because @code{c-set-offset}
1790 might be unavailable when @code{cc-mode} is not loaded.
1791
1792 Note that @code{c-mode-hook} runs for C source files only; use
1793 @code{c++-mode-hook} for C@t{++} sources, @code{java-mode-hook} for
1794 Java sources, etc. If you want the same customizations to be in
1795 effect in @emph{all} languages supported by @code{cc-mode}, use
1796 @code{c-mode-common-hook}.
1797
1798 @node Horizontal scrolling, Overwrite mode, Customizing C and C++ indentation, Common requests
1799 @section How can I make Emacs automatically scroll horizontally?
1800 @cindex @code{hscroll-mode}
1801 @cindex Horizontal scrolling
1802 @cindex Scrolling horizontally
1803
1804 In Emacs 21 and later, this is on by default: if the variable
1805 @code{truncate-lines} is non-@code{nil} in the current buffer, Emacs
1806 automatically scrolls the display horizontally when point moves off the
1807 left or right edge of the window.
1808
1809 In Emacs 20, use the @code{hscroll-mode}. Here is some information from
1810 the documentation, available by typing @kbd{C-h f hscroll-mode @key{RET}}:
1811
1812 Automatically scroll horizontally when the point moves off the
1813 left or right edge of the window.
1814
1815 @itemize @minus
1816 @item
1817 Type @kbd{M-x hscroll-mode} to enable it in the current buffer.
1818
1819 @item
1820 Type @kbd{M-x hscroll-global-mode} to enable it in every buffer.
1821
1822 @item
1823 @code{turn-on-hscroll} is useful in mode hooks as in:
1824
1825 @lisp
1826 (add-hook 'text-mode-hook 'turn-on-hscroll)
1827 @end lisp
1828
1829 @item
1830 @code{hscroll-margin} controls how close the cursor can get to the
1831 edge of the window.
1832
1833 @item
1834 @code{hscroll-step-percent} controls how far to jump once we decide to do so.
1835 @end itemize
1836
1837 @node Overwrite mode, Turning off beeping, Horizontal scrolling, Common requests
1838 @section How do I make Emacs ``typeover'' or ``overwrite'' instead of inserting?
1839 @cindex @key{Insert}
1840 @cindex @code{overwrite-mode}
1841 @cindex Overwriting existing text
1842 @cindex Toggling @code{overwrite-mode}
1843
1844 @kbd{M-x overwrite-mode} (a minor mode). This toggles
1845 @code{overwrite-mode} on and off, so exiting from @code{overwrite-mode}
1846 is as easy as another @kbd{M-x overwrite-mode}.
1847
1848 On some systems, @key{Insert} toggles @code{overwrite-mode} on and off.
1849
1850 @node Turning off beeping, Turning the volume down, Overwrite mode, Common requests
1851 @section How do I stop Emacs from beeping on a terminal?
1852 @cindex Beeping, turning off
1853 @cindex Visible bell
1854 @cindex Bell, visible
1855
1856 @email{martin@@cc.gatech.edu, Martin R. Frank} writes:
1857
1858 Tell Emacs to use the @dfn{visible bell} instead of the audible bell,
1859 and set the visible bell to nothing.
1860
1861 That is, put the following in your @code{TERMCAP} environment variable
1862 (assuming you have one):
1863
1864 @example
1865 ... :vb=: ...
1866 @end example
1867
1868 And evaluate the following Lisp form:
1869
1870 @example
1871 (setq visible-bell t)
1872 @end example
1873
1874 @node Turning the volume down, Automatic indentation, Turning off beeping, Common requests
1875 @section How do I turn down the bell volume in Emacs running under X?
1876 @cindex Bell, volume of
1877 @cindex Volume of bell
1878
1879 On X Window system, you can adjust the bell volume and duration for all
1880 programs with the shell command @code{xset}.
1881
1882 Invoking @code{xset} without any arguments produces some basic
1883 information, including the following:
1884
1885 @example
1886 usage: xset [-display host:dpy] option ...
1887 To turn bell off:
1888 -b b off b 0
1889 To set bell volume, pitch and duration:
1890 b [vol [pitch [dur]]] b on
1891 @end example
1892
1893 @node Automatic indentation, Matching parentheses, Turning the volume down, Common requests
1894 @section How do I tell Emacs to automatically indent a new line to the indentation of the previous line?
1895 @cindex Indenting new lines
1896 @cindex New lines, indenting of
1897 @cindex Previous line, indenting according to
1898 @cindex Text indentation
1899
1900 Such behavior is automatic in Emacs 20 and later. From the
1901 @file{etc/NEWS} file for Emacs 20.2:
1902
1903 @example
1904 ** In Text mode, now only blank lines separate paragraphs. This makes
1905 it possible to get the full benefit of Adaptive Fill mode in Text mode,
1906 and other modes derived from it (such as Mail mode). @key{TAB} in Text
1907 mode now runs the command @code{indent-relative}; this makes a practical
1908 difference only when you use indented paragraphs.
1909
1910 As a result, the old Indented Text mode is now identical to Text mode,
1911 and is an alias for it.
1912
1913 If you want spaces at the beginning of a line to start a paragraph, use
1914 the new mode, Paragraph Indent Text mode.
1915 @end example
1916
1917 @cindex Prefixing lines
1918 @cindex Fill prefix
1919 If you have @code{auto-fill-mode} turned on (@pxref{Turning on auto-fill
1920 by default}), you can tell Emacs to prefix every line with a certain
1921 character sequence, the @dfn{fill prefix}. Type the prefix at the
1922 beginning of a line, position point after it, and then type @kbd{C-x .}
1923 (@code{set-fill-prefix}) to set the fill prefix. Thereafter,
1924 auto-filling will automatically put the fill prefix at the beginning of
1925 new lines, and @kbd{M-q} (@code{fill-paragraph}) will maintain any fill
1926 prefix when refilling the paragraph.
1927
1928 If you have paragraphs with different levels of indentation, you will
1929 have to set the fill prefix to the correct value each time you move to a
1930 new paragraph. There are many packages available to deal with this
1931 (@pxref{Packages that do not come with Emacs}). Look for ``fill'' and
1932 ``indent'' keywords for guidance.
1933
1934 @node Matching parentheses, Hiding #ifdef lines, Automatic indentation, Common requests
1935 @section How do I show which parenthesis matches the one I'm looking at?
1936 @cindex Parentheses, matching
1937 @cindex @file{paren.el}
1938 @cindex Highlighting matching parentheses
1939 @cindex Pairs of parentheses, highlighting
1940 @cindex Matching parentheses
1941
1942 Call @code{show-paren-mode} in your @file{.emacs} file:
1943
1944 @lisp
1945 (show-paren-mode 1)
1946 @end lisp
1947
1948 You can also enable this mode by selecting the @samp{Paren Match
1949 Highlighting} option from the @samp{Options} menu of the Emacs menu bar
1950 at the top of any Emacs frame.
1951
1952 Alternatives to this mode include:
1953
1954 @itemize @bullet
1955
1956 @item
1957 If you're looking at a right parenthesis (or brace or bracket) you can
1958 delete it and reinsert it. Emacs will momentarily move the cursor to
1959 the matching parenthesis.
1960
1961 @item
1962 @kbd{C-M-f} (@code{forward-sexp}) and @kbd{C-M-b} (@code{backward-sexp})
1963 will skip over one set of balanced parentheses, so you can see which
1964 parentheses match. (You can train it to skip over balanced brackets
1965 and braces at the same time by modifying the syntax table.)
1966
1967 @cindex Show matching paren as in @code{vi}
1968 @item
1969 Here is some Emacs Lisp that will make the @key{%} key show the matching
1970 parenthesis, like in @code{vi}. In addition, if the cursor isn't over a
1971 parenthesis, it simply inserts a % like normal.
1972
1973 @lisp
1974 ;; By an unknown contributor
1975
1976 (global-set-key "%" 'match-paren)
1977
1978 (defun match-paren (arg)
1979 "Go to the matching paren if on a paren; otherwise insert %."
1980 (interactive "p")
1981 (cond ((looking-at "\\s\(") (forward-list 1) (backward-char 1))
1982 ((looking-at "\\s\)") (forward-char 1) (backward-list 1))
1983 (t (self-insert-command (or arg 1)))))
1984 @end lisp
1985
1986 @end itemize
1987
1988 @node Hiding #ifdef lines, Repeating commands, Matching parentheses, Common requests
1989 @section In C mode, can I show just the lines that will be left after @code{#ifdef} commands are handled by the compiler?
1990 @cindex @code{#ifdef}, selective display of
1991 @cindex @code{hide-ifdef-mode}
1992 @cindex Hiding @code{#ifdef} text
1993 @cindex Selectively displaying @code{#ifdef} code
1994
1995 @kbd{M-x hide-ifdef-mode}. (This is a minor mode.) You might also want
1996 to investigate @file{cpp.el}, which is distributed with Emacs.
1997
1998 @node Repeating commands, Valid X resources, Hiding #ifdef lines, Common requests
1999 @section Is there an equivalent to the @code{.} (dot) command of vi?
2000 @cindex Repeating commands as with @code{vi}
2001 @cindex Command, repeat last
2002 @cindex @code{.}, equivalent to @code{vi} command
2003
2004 (@code{.} is the redo command in @code{vi}. It redoes the last
2005 insertion/deletion.)
2006
2007 As of Emacs 20.3, there is indeed a @code{repeat} command (@kbd{C-x z})
2008 that repeats the last command. If you preface it with a prefix
2009 argument, the prefix arg is applied to the command.
2010
2011 You can also type @kbd{C-x @key{ESC} @key{ESC}}
2012 (@code{repeat-complex-command}) to reinvoke commands that used the
2013 minibuffer to get arguments. In @code{repeat-complex-command} you can
2014 type @kbd{M-p} and @kbd{M-n} (and also up-arrow and down-arrow, if your
2015 keyboard has these keys) to scan through all the different complex
2016 commands you've typed.
2017
2018 To repeat a set of commands, use keyboard macros. (@inforef{Keyboard
2019 Macros, Keyboard Macros, emacs}.)
2020
2021 If you're really desperate for the @code{.} command, use VIPER, a
2022 @code{vi} emulation mode which comes with Emacs, and which appears to
2023 support it. (@xref{VIPER}.)
2024
2025 @node Valid X resources, Evaluating Emacs Lisp code, Repeating commands, Common requests
2026 @section What are the valid X resource settings (i.e., stuff in .Xdefaults)?
2027 @cindex Resources, X
2028 @cindex X resources
2029 @cindex Setting X resources
2030
2031 @inforef{X Resources, X Resources, emacs}.
2032
2033 You can also use a resource editor, such as editres (for X11R5 and
2034 onwards), to look at the resource names for the menu bar, assuming Emacs
2035 was compiled with the X toolkit.
2036
2037 @node Evaluating Emacs Lisp code, Changing the length of a Tab, Valid X resources, Common requests
2038 @section How do I execute (``evaluate'') a piece of Emacs Lisp code?
2039 @cindex Evaluating Lisp code
2040 @cindex Lisp forms, evaluating
2041
2042 There are a number of ways to execute (@dfn{evaluate}, in Lisp lingo) an
2043 Emacs Lisp @dfn{form}:
2044
2045 @itemize @bullet
2046
2047 @item
2048 If you want it evaluated every time you run Emacs, put it in a file
2049 named @file{.emacs} in your home directory. This is known as ``your
2050 @file{.emacs} file,'' and contains all of your personal customizations.
2051
2052 @item
2053 You can type the form in the @file{*scratch*} buffer, and then type
2054 @key{LFD} (or @kbd{C-j}) after it. The result of evaluating the form
2055 will be inserted in the buffer.
2056
2057 @item
2058 In @code{emacs-lisp-mode}, typing @kbd{C-M-x} evaluates a top-level form
2059 before or around point.
2060
2061 @item
2062 Typing @kbd{C-x C-e} in any buffer evaluates the Lisp form immediately
2063 before point and prints its value in the echo area.
2064
2065 @item
2066 Typing @kbd{M-:} or @kbd{M-x eval-expression} allows you to type a Lisp
2067 form in the minibuffer which will be evaluated once you press @key{RET}.
2068
2069 @item
2070 You can use @kbd{M-x load-file} to have Emacs evaluate all the Lisp
2071 forms in a file. (To do this from Lisp use the function @code{load}
2072 instead.)
2073
2074 The functions @code{load-library}, @code{eval-region},
2075 @code{eval-current-buffer}, @code{require}, and @code{autoload} are also
2076 useful; see @ref{Emacs Lisp documentation}, if you want to learn more
2077 about them.
2078
2079 @end itemize
2080
2081 @node Changing the length of a Tab, Inserting > at the beginning of each line, Evaluating Emacs Lisp code, Common requests
2082 @section How do I change Emacs's idea of the @key{TAB} character's length?
2083 @cindex Tab length
2084 @cindex Length of tab character
2085 @cindex @code{default-tab-width}
2086
2087 Set the variable @code{default-tab-width}. For example, to set
2088 @key{TAB} stops every 10 characters, insert the following in your
2089 @file{.emacs} file:
2090
2091 @lisp
2092 (setq default-tab-width 10)
2093 @end lisp
2094
2095 Do not confuse variable @code{tab-width} with variable
2096 @code{tab-stop-list}. The former is used for the display of literal
2097 @key{TAB} characters. The latter controls what characters are inserted
2098 when you press the @key{TAB} character in certain modes.
2099
2100 @node Inserting > at the beginning of each line, Underlining paragraphs, Changing the length of a Tab, Common requests
2101 @section How do I insert @samp{>} at the beginning of every line?
2102 @cindex Prefix character, inserting in mail/news replies
2103 @cindex Replies to mail/news, inserting a prefix character
2104 @cindex @code{mail-yank-prefix}
2105 @cindex Mail replies, inserting a prefix character
2106 @cindex News replies, inserting a prefix character
2107
2108 To do this to an entire buffer, type @kbd{M-< M-x replace-regexp
2109 @key{RET} ^ @key{RET} > @key{RET}}.
2110
2111 To do this to a region, use @code{string-insert-rectangle}.
2112 Set the mark (@kbd{C-@key{SPC}}) at the beginning of the first line you
2113 want to prefix, move the cursor to last line to be prefixed, and type
2114 @kbd{M-x string-insert-rectangle @key{RET}}. To do this for the whole
2115 buffer, type @kbd{C-x h M-x string-insert-rectangle @key{RET}}.
2116
2117 If you are trying to prefix a yanked mail message with @samp{>}, you
2118 might want to set the variable @code{mail-yank-prefix}. Better yet, use
2119 the Supercite package (@pxref{Supercite}), which provides flexible
2120 citation for yanked mail and news messages; it is included in Emacs
2121 since version 19.20. @xref{Changing the included text prefix}, for
2122 additional information.
2123
2124 @node Underlining paragraphs, Repeating a command as many times as possible, Inserting > at the beginning of each line, Common requests
2125 @section How do I insert @samp{_^H} before each character in a region to get an underlined paragraph?
2126 @cindex Underlining a region of text
2127 @cindex @code{underline-region}
2128
2129 Mark the region and then type @kbd{M-x underline-region @key{RET}}.
2130
2131 @node Repeating a command as many times as possible, Forcing the cursor to remain in the same column, Underlining paragraphs, Common requests
2132 @section How do I repeat a command as many times as possible?
2133 @cindex Repeating commands many times
2134 @cindex Commands, repeating many times
2135
2136 Use @kbd{C-x (} and @kbd{C-x )} to make a keyboard macro that invokes
2137 the command and then type @kbd{M-0 C-x e}.
2138
2139 Any messages your command prints in the echo area will be suppressed.
2140
2141 If you need to repeat a command a small number of times, you can use
2142 @kbd{C-x z} (@pxref{Repeating commands}) or @kbd{C-x e}.
2143
2144 @node Forcing the cursor to remain in the same column, Forcing Emacs to iconify itself, Repeating a command as many times as possible, Common requests
2145 @section How do I make Emacs behave like this: when I go up or down, the cursor should stay in the same column even if the line is too short?
2146 @cindex @code{picture-mode}
2147 @cindex Remaining in the same column, regardless of contents
2148 @cindex Vertical movement in empty documents
2149
2150 @kbd{M-x picture-mode}.
2151
2152 @node Forcing Emacs to iconify itself, Using regular expressions, Forcing the cursor to remain in the same column, Common requests
2153 @section How do I tell Emacs to iconify itself?
2154 @cindex Iconification under the X Window System
2155 @cindex X Window System and iconification
2156 @cindex Suspending Emacs
2157
2158 @kbd{C-z} iconifies Emacs when running under X and suspends Emacs
2159 otherwise. @inforef{Frame Commands, Frame Commands, emacs}.
2160
2161 @node Using regular expressions, Replacing text across multiple files, Forcing Emacs to iconify itself, Common requests
2162 @section How do I use regexps (regular expressions) in Emacs?
2163 @cindex Regexps
2164 @cindex Regular expressions
2165 @cindex Differences between Unix and Emacs regexps
2166 @cindex Unix regeps, differences from Emacs
2167 @cindex Text strings, putting regexps in
2168
2169 @inforef{Regexp Backslash, Regexp Backslash, emacs}.
2170
2171 The @code{or} operator is @samp{\|}, not @samp{|}, and the grouping operators
2172 are @samp{\(} and @samp{\)}. Also, the string syntax for a backslash is
2173 @samp{\\}. To specify a regular expression like @samp{xxx\(foo\|bar\)}
2174 in a Lisp string, use @samp{xxx\\(foo\\|bar\\)}.
2175
2176 Note the doubled backslashes!
2177
2178 @itemize @bullet
2179
2180 @item
2181 Unlike in Unix @file{grep}, @file{sed}, etc., a complement character set
2182 (@samp{[^...]}) can match a newline character (@key{LFD} a.k.a.@:
2183 @kbd{C-j} a.k.a.@: @samp{\n}), unless newline is mentioned as one of the
2184 characters not to match.
2185
2186 @item
2187 The character syntax regexps (e.g., @samp{\sw}) are not
2188 meaningful inside character set regexps (e.g., @samp{[aeiou]}). (This
2189 is actually typical for regexp syntax.)
2190
2191 @end itemize
2192
2193 @node Replacing text across multiple files, Documentation for etags, Using regular expressions, Common requests
2194 @section How do I perform a replace operation across more than one file?
2195 @cindex Replacing strings across files
2196 @cindex Multiple files, replacing across
2197 @cindex Files, replacing strings across multiple
2198
2199 The ``tags'' feature of Emacs includes the command
2200 @code{tags-query-replace} which performs a query-replace across all the
2201 files mentioned in the @file{TAGS} file. @inforef{Tags Search, Tags Search,
2202 emacs}.
2203
2204 As of Emacs 19.29, Dired mode (@kbd{M-x dired @key{RET}}, or @kbd{C-x
2205 d}) supports the command @code{dired-do-query-replace}, which allows
2206 users to replace regular expressions in multiple files.
2207
2208 @node Documentation for etags, Disabling backups, Replacing text across multiple files, Common requests
2209 @section Where is the documentation for @code{etags}?
2210 @cindex Documentation for @code{etags}
2211 @cindex @code{etags}, documentation for
2212
2213 The @code{etags} man page should be in the same place as the
2214 @code{emacs} man page.
2215
2216 Quick command-line switch descriptions are also available. For example,
2217 @samp{etags -H}.
2218
2219 @node Disabling backups, Disabling auto-save-mode, Documentation for etags, Common requests
2220 @section How do I disable backup files?
2221 @cindex Backups, disabling
2222 @cindex Disabling backups
2223
2224 You probably don't want to do this, since backups are useful, especially
2225 when something goes wrong.
2226
2227 To avoid seeing backup files (and other ``uninteresting'' files) in Dired,
2228 load @code{dired-x} by adding the following to your @file{.emacs} file:
2229
2230 @lisp
2231 (add-hook 'dired-load-hook
2232 (lambda ()
2233 (load "dired-x")))
2234 @end lisp
2235
2236 With @code{dired-x} loaded, @kbd{M-o} toggles omitting in each dired buffer.
2237 You can make omitting the default for new dired buffers by putting the
2238 following in your @file{.emacs}:
2239
2240 @lisp
2241 (add-hook 'dired-mode-hook 'dired-omit-toggle)
2242 @end lisp
2243
2244 If you're tired of seeing backup files whenever you do an @samp{ls} at
2245 the Unix shell, try GNU @code{ls} with the @samp{-B} option. GNU
2246 @code{ls} is part of the GNU Fileutils package, available from
2247 @samp{ftp.gnu.org} and its mirrors (@pxref{Current GNU distributions}).
2248
2249 To disable or change the way backups are made, @inforef{Backup Names, ,
2250 emacs}.
2251
2252 @cindex Backup files in a single directory
2253 Beginning with Emacs 21.1, you can control where Emacs puts backup files
2254 by customizing the variable @code{backup-directory-alist}. This
2255 variable's value specifies that files whose names match specific patters
2256 should have their backups put in certain directories. A typical use is
2257 to add the element @code{("." . @var{dir})} to force Emacs to put
2258 @strong{all} backup files in the directory @file{dir}.
2259
2260 @node Disabling auto-save-mode, Going to a line by number, Disabling backups, Common requests
2261 @section How do I disable @code{auto-save-mode}?
2262 @cindex Disabling @code{auto-save-mode}
2263 @cindex Auto-saving
2264 @cindex Saving at frequent intervals
2265
2266 You probably don't want to do this, since auto-saving is useful,
2267 especially when Emacs or your computer crashes while you are editing a
2268 document.
2269
2270 Instead, you might want to change the variable
2271 @code{auto-save-interval}, which specifies how many keystrokes Emacs
2272 waits before auto-saving. Increasing this value forces Emacs to wait
2273 longer between auto-saves, which might annoy you less.
2274
2275 You might also want to look into Sebastian Kremer's @code{auto-save}
2276 package (@pxref{Packages that do not come with Emacs}). This
2277 package also allows you to place all auto-save files in one directory,
2278 such as @file{/tmp}.
2279
2280 To disable or change how @code{auto-save-mode} works, @inforef{Auto
2281 Save, , emacs}.
2282
2283 @node Going to a line by number, Modifying pull-down menus, Disabling auto-save-mode, Common requests
2284 @section How can I go to a certain line given its number?
2285 @cindex Going to a line by number
2286 @cindex Compilation error messages
2287 @cindex Recompilation
2288
2289 Are you sure you indeed need to go to a line by its number? Perhaps all
2290 you want is to display a line in your source file for which a compiler
2291 printed an error message? If so, compiling from within Emacs using the
2292 @kbd{M-x compile} and @kbd{M-x recompile} commands is a much more
2293 effective way of doing that. Emacs automatically intercepts the compile
2294 error messages, inserts them into a special buffer called
2295 @code{*compilation*}, and lets you visit the locus of each message in
2296 the source. Type @kbd{C-x `} to step through the offending lines one by
2297 one (starting with Emacs 22, you can also use @kbd{M-g M-p} and
2298 @kbd{M-g M-n} to go to the previous and next matches directly). Click
2299 @kbd{Mouse-2} or press @key{RET} on a message text in the
2300 @code{*compilation*} buffer to go to the line whose number is mentioned
2301 in that message.
2302
2303 But if you indeed need to go to a certain text line, type @kbd{M-g M-g}
2304 (which is the default binding of the @code{goto-line} function starting
2305 with Emacs 22). Emacs will prompt you for the number of the line and go
2306 to that line.
2307
2308 You can do this faster by invoking @code{goto-line} with a numeric
2309 argument that is the line's number. For example, @kbd{C-u 286 M-g M-g}
2310 will jump to line number 286 in the current buffer.
2311
2312 @node Modifying pull-down menus, Deleting menus and menu options, Going to a line by number, Common requests
2313 @section How can I create or modify new pull-down menu options?
2314 @cindex Pull-down menus, creating or modifying
2315 @cindex Menus, creating or modifying
2316 @cindex Creating new menu options
2317 @cindex Modifying pull-down menus
2318 @cindex Menus and keymaps
2319 @cindex Keymaps and menus
2320
2321 Each menu title (e.g., @samp{File}, @samp{Edit}, @samp{Buffers})
2322 represents a local or global keymap. Selecting a menu title with the
2323 mouse displays that keymap's non-@code{nil} contents in the form of a menu.
2324
2325 So to add a menu option to an existing menu, all you have to do is add a
2326 new definition to the appropriate keymap. Adding a @samp{Forward Word}
2327 item to the @samp{Edit} menu thus requires the following Lisp code:
2328
2329 @lisp
2330 (define-key global-map
2331 [menu-bar edit forward]
2332 '("Forward word" . forward-word))
2333 @end lisp
2334
2335 @noindent
2336 The first line adds the entry to the global keymap, which includes
2337 global menu bar entries. Replacing the reference to @code{global-map}
2338 with a local keymap would add this menu option only within a particular
2339 mode.
2340
2341 The second line describes the path from the menu-bar to the new entry.
2342 Placing this menu entry underneath the @samp{File} menu would mean
2343 changing the word @code{edit} in the second line to @code{file}.
2344
2345 The third line is a cons cell whose first element is the title that will
2346 be displayed, and whose second element is the function that will be
2347 called when that menu option is invoked.
2348
2349 To add a new menu, rather than a new option to an existing menu, we must
2350 define an entirely new keymap:
2351
2352 @lisp
2353 (define-key global-map [menu-bar words]
2354 (cons "Words" (make-sparse-keymap "Words")))
2355 @end lisp
2356
2357 The above code creates a new sparse keymap, gives it the name
2358 @samp{Words}, and attaches it to the global menu bar. Adding the
2359 @samp{Forward Word} item to this new menu would thus require the
2360 following code:
2361
2362 @lisp
2363 (define-key global-map
2364 [menu-bar words forward]
2365 '("Forward word" . forward-word))
2366 @end lisp
2367
2368 @noindent
2369 Note that because of the way keymaps work, menu options are displayed
2370 with the more recently defined items at the top. Thus if you were to
2371 define menu options @samp{foo}, @samp{bar}, and @samp{baz} (in that
2372 order), the menu option @samp{baz} would appear at the top, and
2373 @samp{foo} would be at the bottom.
2374
2375 One way to avoid this problem is to use the function @code{define-key-after},
2376 which works the same as @code{define-key}, but lets you modify where items
2377 appear. The following Lisp code would insert the @samp{Forward Word}
2378 item in the @samp{Edit} menu immediately following the @samp{Undo} item:
2379
2380 @lisp
2381 (define-key-after
2382 (lookup-key global-map [menu-bar edit])
2383 [forward]
2384 '("Forward word" . forward-word)
2385 'undo)
2386 @end lisp
2387
2388 Note how the second and third arguments to @code{define-key-after} are
2389 different from those of @code{define-key}, and that we have added a new
2390 (final) argument, the function after which our new key should be
2391 defined.
2392
2393 To move a menu option from one position to another, simply evaluate
2394 @code{define-key-after} with the appropriate final argument.
2395
2396 More detailed information---and more examples of how to create and
2397 modify menu options---are in the @cite{Emacs Lisp Reference Manual}, under
2398 ``Menu Keymaps''. (@xref{Emacs Lisp documentation}, for information on
2399 this manual.)
2400
2401 @node Deleting menus and menu options, Turning on syntax highlighting, Modifying pull-down menus, Common requests
2402 @section How do I delete menus and menu options?
2403 @cindex Deleting menus and menu options
2404 @cindex Menus, deleting
2405
2406 The simplest way to remove a menu is to set its keymap to @samp{nil}.
2407 For example, to delete the @samp{Words} menu (@pxref{Modifying pull-down
2408 menus}), use:
2409
2410 @lisp
2411 (define-key global-map [menu-bar words] nil)
2412 @end lisp
2413
2414 Similarly, removing a menu option requires redefining a keymap entry to
2415 @code{nil}. For example, to delete the @samp{Forward word} menu option
2416 from the @samp{Edit} menu (we added it in @ref{Modifying pull-down
2417 menus}), use:
2418
2419 @lisp
2420 (define-key global-map [menu-bar edit forward] nil)
2421 @end lisp
2422
2423 @node Turning on syntax highlighting, Scrolling only one line, Deleting menus and menu options, Common requests
2424 @section How do I turn on syntax highlighting?
2425 @cindex Syntax highlighting
2426 @cindex @code{font-lock-mode}
2427 @cindex Highlighting based on syntax
2428 @cindex Colorizing text
2429 @cindex FAQ, @code{font-lock-mode}
2430
2431 @code{font-lock-mode} is the standard way to have Emacs perform syntax
2432 highlighting in the current buffer. It is enabled by default in Emacs
2433 22.1 and later.
2434
2435 With @code{font-lock-mode} turned on, different types of text will
2436 appear in different colors. For instance, in a programming mode,
2437 variables will appear in one face, keywords in a second, and comments in
2438 a third.
2439
2440 @cindex hilit19 is deprecated
2441 Earlier versions of Emacs supported hilit19, a similar package. Use of
2442 hilit19 is now considered non-standard, although @file{hilit19.el} comes
2443 with the stock Emacs distribution. It is no longer maintained.
2444
2445 To turn @code{font-lock-mode} off within an existing buffer, use
2446 @kbd{M-x font-lock-mode @key{RET}}.
2447
2448 In Emacs 21 and earlier versions, you could use the following code in
2449 your @file{.emacs} file to turn on @code{font-lock-mode} globally:
2450
2451 @lisp
2452 (global-font-lock-mode 1)
2453 @end lisp
2454
2455 Highlighting a buffer with @code{font-lock-mode} can take quite a while,
2456 and cause an annoying delay in display, so several features exist to
2457 work around this.
2458
2459 @cindex Just-In-Time syntax highlighting
2460 In Emacs 21 and later, turning on @code{font-lock-mode} automatically
2461 activates the new @dfn{Just-In-Time fontification} provided by
2462 @code{jit-lock-mode}. @code{jit-lock-mode} defers the fontification of
2463 portions of buffer until you actually need to see them, and can also
2464 fontify while Emacs is idle. This makes display of the visible portion
2465 of a buffer almost instantaneous. For details about customizing
2466 @code{jit-lock-mode}, type @kbd{C-h f jit-lock-mode @key{RET}}.
2467
2468 @cindex Levels of syntax highlighting
2469 @cindex Decoration level, in @code{font-lock-mode}
2470 In versions of Emacs before 21, different levels of decoration are
2471 available, from slight to gaudy. More decoration means you need to wait
2472 more time for a buffer to be fontified (or a faster machine). To
2473 control how decorated your buffers should become, set the value of
2474 @code{font-lock-maximum-decoration} in your @file{.emacs} file, with a
2475 @code{nil} value indicating default (usually minimum) decoration, and a
2476 @code{t} value indicating the maximum decoration. For the gaudiest
2477 possible look, then, include the line
2478
2479 @lisp
2480 (setq font-lock-maximum-decoration t)
2481 @end lisp
2482
2483 @noindent
2484 in your @file{.emacs} file. You can also set this variable such that
2485 different modes are highlighted in a different ways; for more
2486 information, see the documentation for
2487 @code{font-lock-maximum-decoration} with @kbd{C-h v} (or @kbd{M-x
2488 describe-variable @key{RET}}).
2489
2490 Also see the documentation for the function @code{font-lock-mode},
2491 available by typing @kbd{C-h f font-lock-mode} (@kbd{M-x
2492 describe-function @key{RET} font-lock-mode @key{RET}}).
2493
2494 To print buffers with the faces (i.e., colors and fonts) intact, use
2495 @kbd{M-x ps-print-buffer-with-faces} or @kbd{M-x
2496 ps-print-region-with-faces}. You will need a way to send text to a
2497 PostScript printer, or a PostScript interpreter such as Ghostscript;
2498 consult the documentation of the variables @code{ps-printer-name},
2499 @code{ps-lpr-command}, and @code{ps-lpr-switches} for more details.
2500
2501 @node Scrolling only one line, Replacing highlighted text, Turning on syntax highlighting, Common requests
2502 @section How can I force Emacs to scroll only one line when I move past the bottom of the screen?
2503 @cindex Scrolling only one line
2504 @cindex Reducing the increment when scrolling
2505
2506 Place the following Lisp form in your @file{.emacs} file:
2507
2508 @lisp
2509 (setq scroll-step 1)
2510 @end lisp
2511
2512 @inforef{Scrolling, Scrolling, emacs}.
2513
2514 @node Replacing highlighted text, Editing MS-DOS files, Scrolling only one line, Common requests
2515 @section How can I replace highlighted text with what I type?
2516 @cindex @code{delete-selection-mode}
2517 @cindex Replacing highlighted text
2518 @cindex Highlighting and replacing text
2519
2520 Use @code{delete-selection-mode}, which you can start automatically by
2521 placing the following Lisp form in your @file{.emacs} file:
2522
2523 @lisp
2524 (delete-selection-mode 1)
2525 @end lisp
2526
2527 According to the documentation string for @code{delete-selection-mode}
2528 (which you can read using @kbd{M-x describe-function @key{RET}
2529 delete-selection-mode @key{RET}}):
2530
2531 @quotation
2532 When ON, typed text replaces the selection if the selection is active.
2533 When OFF, typed text is just inserted at point.
2534 @end quotation
2535
2536 This mode also allows you to delete (not kill) the highlighted region by
2537 pressing @key{DEL}.
2538
2539 @node Editing MS-DOS files, Filling paragraphs with a single space, Replacing highlighted text, Common requests
2540 @section How can I edit MS-DOS files using Emacs?
2541 @cindex Editing MS-DOS files
2542 @cindex MS-DOS files, editing
2543 @cindex Microsoft files, editing
2544 @cindex Windows files, editing
2545
2546 As of Emacs 20, detection and handling of MS-DOS (and Windows) files is
2547 performed transparently. You can open MS-DOS files on a Unix system,
2548 edit it, and save it without having to worry about the file format.
2549
2550 When editing an MS-DOS style file, the mode line will indicate that it
2551 is a DOS file. On Unix and GNU/Linux systems, and also on a Macintosh,
2552 the string @samp{(DOS)} will appear near the left edge of the mode line;
2553 on DOS and Windows, where the DOS end-of-line (EOL) format is the
2554 default, a backslash (@samp{\}) will appear in the mode line.
2555
2556 If you are running a version of Emacs before 20.1, get @code{crypt++}
2557 (@pxref{Packages that do not come with Emacs}). Among other things,
2558 @code{crypt++} transparently modifies MS-DOS files as they are loaded
2559 and saved, allowing you to ignore the different conventions that Unix
2560 and MS-DOS have for delineating the end of a line.
2561
2562 @node Filling paragraphs with a single space, Escape sequences in shell output, Editing MS-DOS files, Common requests
2563 @section How can I tell Emacs to fill paragraphs with a single space after each period?
2564 @cindex One space following periods
2565 @cindex Single space following periods
2566 @cindex Periods, one space following
2567
2568 @email{ulm@@vsnhd1.cern.ch, Ulrich Mueller} suggests adding the
2569 following two lines to your @file{.emacs} file:
2570
2571 @lisp
2572 (setq sentence-end "[.?!][]\"')@}]*\\($\\|[ \t]\\)[ \t\n]*")
2573 (setq sentence-end-double-space nil)
2574 @end lisp
2575
2576 @node Escape sequences in shell output, , Filling paragraphs with a single space, Common requests
2577 @section Why these strange escape sequences from @code{ls} from the Shell mode?
2578 @cindex Escape sequences in @code{ls} output
2579 @cindex @code{ls} in Shell mode
2580
2581 This happens because @code{ls} is aliased to @samp{ls --color} in your
2582 shell init file. You have two alternatives to solve this:
2583
2584 @itemize @bullet
2585 @item
2586 Make the alias conditioned on the @code{EMACS} variable in the
2587 environment. When Emacs runs a subsidiary shell, it exports the
2588 @code{EMACS} variable with the value @code{t} to that shell. You can
2589 unalias @code{ls} when that happens, thus limiting the alias to your
2590 interactive sessions.
2591
2592 @item
2593 Install the @code{ansi-color} package (bundled with Emacs 21.1 and
2594 later), which converts these ANSI escape sequences into colors.
2595 @end itemize
2596
2597 @c ------------------------------------------------------------
2598 @node Bugs and problems, Compiling and installing Emacs, Common requests, Top
2599 @chapter Bugs and problems
2600 @cindex Bugs and problems
2601
2602 The Emacs manual lists some common kinds of trouble users could get
2603 into, see @ref{Lossage, , Dealing with Emacs Trouble, emacs, The GNU
2604 Emacs Manual}, so you might look there if the problem you encounter
2605 isn't described in this chapter. If you decide you've discovered a bug,
2606 see @ref{Bugs, , Reporting Bugs, emacs, The GNU Emacs Manual}, for
2607 instructions how to do that.
2608
2609 The file @file{etc/PROBLEMS} in the Emacs distribution lists various
2610 known problems with building and using Emacs on specific platforms;
2611 type @kbd{C-h C-e} to read it.
2612
2613 @menu
2614 * Problems with very large files::
2615 * ^M in the shell buffer::
2616 * Shell process exits abnormally::
2617 * Problems with Shell Mode on MS-Windows::
2618 * Termcap/Terminfo entries for Emacs::
2619 * Spontaneous entry into isearch-mode::
2620 * Problems talking to certain hosts::
2621 * Errors with init files::
2622 * Emacs ignores X resources::
2623 * Emacs ignores frame parameters::
2624 * Emacs takes a long time to visit files::
2625 * Editing files with $ in the name::
2626 * Shell mode loses the current directory::
2627 * Security risks with Emacs::
2628 * Dired claims that no file is on this line::
2629 @end menu
2630
2631 @node Problems with very large files, ^M in the shell buffer, Bugs and problems, Bugs and problems
2632 @section Does Emacs have problems with files larger than 8 megabytes?
2633 @cindex Very large files, opening
2634 @cindex Large files, opening
2635 @cindex Opening very large files
2636 @cindex Maximum file size
2637 @cindex Files, maximum size
2638
2639 Old versions (i.e., anything before 19.29) of Emacs had problems editing
2640 files larger than 8 megabytes. In versions 19.29 and later, the maximum
2641 buffer size is at least 2^27-1, or 134,217,727 bytes, or 132 MBytes.
2642 And in Emacs 22, the maximum buffer size has been increased to
2643 268,435,455 bytes (or 256 MBytes) on 32-bit machines.
2644
2645 @node ^M in the shell buffer, Shell process exits abnormally, Problems with very large files, Bugs and problems
2646 @section How do I get rid of @samp{^M} or echoed commands in my shell buffer?
2647 @cindex Shell buffer, echoed commands and @samp{^M} in
2648 @cindex Echoed commands in @code{shell-mode}
2649
2650 Try typing @kbd{M-x shell-strip-ctrl-m @key{RET}} while in @code{shell-mode} to
2651 make them go away. If that doesn't work, you have several options:
2652
2653 For @code{tcsh}, put this in your @file{.cshrc} (or @file{.tcshrc})
2654 file:
2655
2656 @example
2657 if ($?EMACS) then
2658 if ("$EMACS" == t) then
2659 if ($?tcsh) unset edit
2660 stty nl
2661 endif
2662 endif
2663 @end example
2664
2665 Or put this in your @file{.emacs_tcsh} file:
2666
2667 @example
2668 unset edit
2669 stty nl
2670 @end example
2671
2672 Alternatively, use @code{csh} in your shell buffers instead of
2673 @code{tcsh}. One way is:
2674
2675 @lisp
2676 (setq explicit-shell-file-name "/bin/csh")
2677 @end lisp
2678
2679 @noindent
2680 and another is to do this in your @file{.cshrc} (or @file{.tcshrc})
2681 file:
2682
2683 @example
2684 setenv ESHELL /bin/csh
2685 @end example
2686
2687 @noindent
2688 (You must start Emacs over again with the environment variable properly
2689 set for this to take effect.)
2690
2691 You can also set the @code{ESHELL} environment variable in Emacs Lisp
2692 with the following Lisp form,
2693
2694 @lisp
2695 (setenv "ESHELL" "/bin/csh")
2696 @end lisp
2697
2698 The above solutions try to prevent the shell from producing the
2699 @samp{^M} characters in the first place. If this is not possible
2700 (e.g., if you use a Windows shell), you can get Emacs to remove these
2701 characters from the buffer by adding this to your @file{.emacs} init
2702 file:
2703
2704 @smalllisp
2705 (add-hook 'comint-output-filter-functions 'shell-strip-ctrl-m)
2706 @end smalllisp
2707
2708 On a related note: if your shell is echoing your input line in the shell
2709 buffer, you might want to customize the @code{comint-process-echoes}
2710 variable in your shell buffers, or try the following command in your
2711 shell start-up file:
2712
2713 @example
2714 stty -icrnl -onlcr -echo susp ^Z
2715 @end example
2716
2717 @node Shell process exits abnormally, Problems with Shell Mode on MS-Windows, ^M in the shell buffer, Bugs and problems
2718 @section Why do I get ``Process shell exited abnormally with code 1''?
2719 @cindex Abnormal exits from @code{shell-mode}
2720 @cindex @code{shell-mode} exits
2721 @cindex Process shell exited
2722
2723 The most likely reason for this message is that the @samp{env} program
2724 is not properly installed. Compile this program for your architecture,
2725 and install it with @samp{a+x} permission in the architecture-dependent
2726 Emacs program directory. (You can find what this directory is at your
2727 site by inspecting the value of the variable @code{exec-directory} by
2728 typing @kbd{C-h v exec-directory @key{RET}}.)
2729
2730 You should also check for other programs named @samp{env} in your path
2731 (e.g., SunOS has a program named @file{/usr/bin/env}). We don't
2732 understand why this can cause a failure and don't know a general
2733 solution for working around the problem in this case.
2734
2735 The @samp{make clean} command will remove @samp{env} and other vital
2736 programs, so be careful when using it.
2737
2738 It has been reported that this sometimes happened when Emacs was started
2739 as an X client from an xterm window (i.e., had a controlling tty) but the
2740 xterm was later terminated.
2741
2742 See also @samp{PROBLEMS} (in the @file{etc} subdirectory of the
2743 top-level directory when you unpack the Emacs source) for other
2744 possible causes of this message.
2745
2746 @node Problems with Shell Mode on MS-Windows, Termcap/Terminfo entries for Emacs, Shell process exits abnormally, Bugs and problems
2747 @section Why do I get an error message when I try to run @kbd{M-x shell}?
2748
2749 @cindex Shell Mode, and MS-Windows
2750 @cindex @code{explicit-shell-file-name}
2751 On MS-Windows, this might happen because Emacs tries to look for the
2752 shell in a wrong place. The default file name @file{/bin/sh} is
2753 usually incorrect for non-Unix systems. If you know where your shell
2754 executable is, set the variable @code{explicit-shell-file-name} in
2755 your @file{.emacs} file to point to its full file name, like this:
2756
2757 @lisp
2758 (setq explicit-shell-file-name "d:/shells/bash.exe")
2759 @end lisp
2760
2761 If you don't know what shell does Emacs use, try the @kbd{M-!}
2762 command; if that works, put the following line into your
2763 @file{.emacs}:
2764
2765 @lisp
2766 (setq explicit-shell-file-name shell-file-name)
2767 @end lisp
2768
2769 @cindex Antivirus programs, and Shell Mode
2770 Some people have trouble with Shell Mode because of intrusive
2771 antivirus software; disabling the resident antivirus program solves
2772 the problems in those cases.
2773
2774 @node Termcap/Terminfo entries for Emacs, Spontaneous entry into isearch-mode, Problems with Shell Mode on MS-Windows, Bugs and problems
2775 @section Where is the termcap/terminfo entry for terminal type @samp{emacs}?
2776 @cindex Termcap
2777 @cindex Terminfo
2778 @cindex Emacs entries for termcap/terminfo
2779
2780 The termcap entry for terminal type @samp{emacs} is ordinarily put in
2781 the @samp{TERMCAP} environment variable of subshells. It may help in
2782 certain situations (e.g., using rlogin from shell buffer) to add an
2783 entry for @samp{emacs} to the system-wide termcap file. Here is a
2784 correct termcap entry for @samp{emacs}:
2785
2786 @example
2787 emacs:tc=unknown:
2788 @end example
2789
2790 To make a terminfo entry for @samp{emacs}, use @code{tic} or
2791 @code{captoinfo}. You need to generate
2792 @file{/usr/lib/terminfo/e/emacs}. It may work to simply copy
2793 @file{/usr/lib/terminfo/d/dumb} to @file{/usr/lib/terminfo/e/emacs}.
2794
2795 Having a termcap/terminfo entry will not enable the use of full screen
2796 programs in shell buffers. Use @kbd{M-x terminal-emulator} for that
2797 instead.
2798
2799 A workaround to the problem of missing termcap/terminfo entries is to
2800 change terminal type @samp{emacs} to type @samp{dumb} or @samp{unknown}
2801 in your shell start up file. @code{csh} users could put this in their
2802 @file{.cshrc} files:
2803
2804 @example
2805 if ("$term" == emacs) set term=dumb
2806 @end example
2807
2808 @node Spontaneous entry into isearch-mode, Problems talking to certain hosts, Termcap/Terminfo entries for Emacs, Bugs and problems
2809 @section Why does Emacs spontaneously start displaying @samp{I-search:} and beeping?
2810 @cindex Spontaneous entry into isearch-mode
2811 @cindex isearch-mode, spontaneous entry into
2812 @cindex Beeping without obvious reason
2813
2814 Your terminal (or something between your terminal and the computer) is
2815 sending @kbd{C-s} and @kbd{C-q} for flow control, and Emacs is receiving
2816 these characters and interpreting them as commands. (The @kbd{C-s}
2817 character normally invokes the @code{isearch-forward} command.) For
2818 possible solutions, see @ref{Handling C-s and C-q with flow control}.
2819
2820 @node Problems talking to certain hosts, Errors with init files, Spontaneous entry into isearch-mode, Bugs and problems
2821 @section Why can't Emacs talk to certain hosts (or certain hostnames)?
2822 @cindex Hosts, Emacs cannot talk to
2823 @cindex @code{gethostbyname}, problematic version
2824
2825 The problem may be that Emacs is linked with a wimpier version of
2826 @code{gethostbyname} than the rest of the programs on the machine. This
2827 is often manifested as a message on startup of ``X server not responding.
2828 Check your @samp{DISPLAY} environment variable.'' or a message of
2829 ``Unknown host'' from @code{open-network-stream}.
2830
2831 On a Sun, this may be because Emacs had to be linked with the static C
2832 library. The version of @code{gethostbyname} in the static C library
2833 may only look in @file{/etc/hosts} and the NIS (YP) maps, while the
2834 version in the dynamic C library may be smart enough to check DNS in
2835 addition to or instead of NIS. On a Motorola Delta running System V
2836 R3.6, the version of @code{gethostbyname} in the standard library works,
2837 but the one that works with NIS doesn't (the one you get with -linet).
2838 Other operating systems have similar problems.
2839
2840 Try these options:
2841
2842 @itemize @bullet
2843
2844 @item
2845 Explicitly add the host you want to communicate with to @file{/etc/hosts}.
2846
2847 @item
2848 Relink Emacs with this line in @file{src/config.h}:
2849
2850 @example
2851 #define LIBS_SYSTEM -lresolv
2852 @end example
2853
2854 @item
2855 Replace @code{gethostbyname} and friends in @file{libc.a} with more
2856 useful versions such as the ones in @file{libresolv.a}. Then relink
2857 Emacs.
2858
2859 @item
2860 If you are actually running NIS, make sure that @code{ypbind} is
2861 properly told to do DNS lookups with the correct command line switch.
2862
2863 @end itemize
2864
2865 @node Errors with init files, Emacs ignores X resources, Problems talking to certain hosts, Bugs and problems
2866 @section Why does Emacs say @samp{Error in init file}?
2867 @cindex Error in @file{.emacs}
2868 @cindex Error in init file
2869 @cindex Init file, errors in
2870 @cindex @file{.emacs} file, errors in
2871 @cindex Debugging @file{.emacs} file
2872
2873 An error occurred while loading either your @file{.emacs} file or the
2874 system-wide file @file{lisp/default.el}. Emacs 21.1 and later pops the
2875 @file{*Messages*} buffer, and puts there some additional information
2876 about the error, to provide some hints for debugging.
2877
2878 For information on how to debug your @file{.emacs} file, see
2879 @ref{Debugging a customization file}.
2880
2881 It may be the case that you need to load some package first, or use a
2882 hook that will be evaluated after the package is loaded. A common case
2883 of this is explained in @ref{Terminal setup code works after Emacs has
2884 begun}.
2885
2886 @node Emacs ignores X resources, Emacs ignores frame parameters, Errors with init files, Bugs and problems
2887 @section Why does Emacs ignore my X resources (my .Xdefaults file)?
2888 @cindex X resources being ignored
2889 @cindex Ignored X resources
2890 @cindex @file{.Xdefaults}
2891
2892 As of version 19, Emacs searches for X resources in the files specified
2893 by the following environment variables:
2894
2895 @itemize @bullet
2896
2897 @item @code{XFILESEARCHPATH}
2898 @item @code{XUSERFILESEARCHPATH}
2899 @item @code{XAPPLRESDIR}
2900
2901 @end itemize
2902
2903 This emulates the functionality provided by programs written using the
2904 Xt toolkit.
2905
2906 @code{XFILESEARCHPATH} and @code{XUSERFILESEARCHPATH} should be a list
2907 of file names separated by colons. @code{XAPPLRESDIR} should be a list
2908 of directory names separated by colons.
2909
2910 Emacs searches for X resources:
2911
2912 @enumerate
2913
2914 @item
2915 specified on the command line, with the @samp{-xrm RESOURCESTRING} option,
2916
2917 @item
2918 then in the value of the @samp{XENVIRONMENT} environment variable,
2919
2920 @itemize @minus
2921
2922 @item
2923 or if that is unset, in the file named
2924 @file{~/.Xdefaults-@var{hostname}} if it exists (where @var{hostname} is
2925 the name of the machine Emacs is running on),
2926
2927 @end itemize
2928
2929 @item
2930 then in the screen-specific and server-wide resource properties provided
2931 by the server,
2932
2933 @itemize @minus
2934
2935 @item
2936 or if those properties are unset, in the file named @file{~/.Xdefaults}
2937 if it exists,
2938
2939 @end itemize
2940
2941 @item
2942 then in the files listed in @samp{XUSERFILESEARCHPATH},
2943
2944 @itemize @minus
2945
2946 @item
2947 or in files named @file{@var{lang}/Emacs} in directories listed in
2948 @samp{XAPPLRESDIR} (where @var{lang} is the value of the @code{LANG}
2949 environment variable), if the @samp{LANG} environment variable is set,
2950 @item
2951 or in files named Emacs in the directories listed in @samp{XAPPLRESDIR}
2952 @item
2953 or in @file{~/@var{lang}/Emacs} (if the @code{LANG} environment variable
2954 is set),
2955 @item
2956 or in @file{~/Emacs},
2957
2958 @end itemize
2959
2960 @item
2961 then in the files listed in @code{XFILESEARCHPATH}.
2962
2963 @end enumerate
2964
2965 @node Emacs ignores frame parameters, Emacs takes a long time to visit files, Emacs ignores X resources, Bugs and problems
2966 @section Why don't my customizations of the frame parameters work?
2967 @cindex Frame parameters
2968
2969 This probably happens because you have set the frame parameters in the
2970 variable @code{initial-frame-alist}. That variable holds parameters
2971 used only for the first frame created when Emacs starts. To customize
2972 the parameters of all frames, change the variable
2973 @code{default-frame-alist} instead.
2974
2975 These two variables exist because many users customize the initial frame
2976 in a special way. For example, you could determine the position and
2977 size of the initial frame, but would like to control the geometry of the
2978 other frames by individually positioning each one of them.
2979
2980
2981 @node Emacs takes a long time to visit files, Editing files with $ in the name, Emacs ignores frame parameters, Bugs and problems
2982 @section Why does Emacs take 20 seconds to visit a file?
2983 @cindex Visiting files takes a long time
2984 @cindex Delay when visiting files
2985 @cindex Files, take a long time to visit
2986
2987 Old versions of Emacs (i.e., versions before Emacs 20.x) often
2988 encountered this when the master lock file, @file{!!!SuperLock!!!}, has
2989 been left in the lock directory somehow. Delete it.
2990
2991 @email{meuer@@geom.umn.edu, Mark Meuer} says that NeXT NFS has a bug
2992 where an exclusive create succeeds but returns an error status. This
2993 can cause the same problem. Since Emacs's file locking doesn't work
2994 over NFS anyway, the best solution is to recompile Emacs with
2995 @code{CLASH_DETECTION} undefined.
2996
2997 @node Editing files with $ in the name, Shell mode loses the current directory, Emacs takes a long time to visit files, Bugs and problems
2998 @section How do I edit a file with a @samp{$} in its name?
2999 @cindex Editing files with @samp{$} in the name
3000 @cindex @samp{$} in file names
3001 @cindex File names containing @samp{$}, editing
3002
3003 When entering a file name in the minibuffer, Emacs will attempt to expand
3004 a @samp{$} followed by a word as an environment variable. To suppress
3005 this behavior, type @kbd{$$} instead.
3006
3007 @node Shell mode loses the current directory, Security risks with Emacs, Editing files with $ in the name, Bugs and problems
3008 @section Why does shell mode lose track of the shell's current directory?
3009 @cindex Current directory and @code{shell-mode}
3010 @cindex @code{shell-mode} and current directory
3011 @cindex Directory, current in @code{shell-mode}
3012
3013 Emacs has no way of knowing when the shell actually changes its
3014 directory. This is an intrinsic limitation of Unix. So it tries to
3015 guess by recognizing @samp{cd} commands. If you type @kbd{cd} followed
3016 by a directory name with a variable reference (@kbd{cd $HOME/bin}) or
3017 with a shell metacharacter (@kbd{cd ../lib*}), Emacs will fail to
3018 correctly guess the shell's new current directory. A huge variety of
3019 fixes and enhancements to shell mode for this problem have been written
3020 to handle this problem (@pxref{Finding a package with particular
3021 functionality}).
3022
3023 You can tell Emacs the shell's current directory with the command
3024 @kbd{M-x dirs}.
3025
3026 @node Security risks with Emacs, Dired claims that no file is on this line, Shell mode loses the current directory, Bugs and problems
3027 @section Are there any security risks in Emacs?
3028 @cindex Security with Emacs
3029 @cindex @samp{movemail} and security
3030 @cindex @code{file-local-variable} and security
3031 @cindex Synthetic X events and security
3032 @cindex X events and security
3033
3034 @itemize @bullet
3035
3036 @item
3037 The @file{movemail} incident. (No, this is not a risk.)
3038
3039 In his book @cite{The Cuckoo's Egg}, Cliff Stoll describes this in
3040 chapter 4. The site at LBL had installed the @file{/etc/movemail}
3041 program setuid root. (As of version 19, @file{movemail} is in your
3042 architecture-specific directory; type @kbd{C-h v exec-directory
3043 @key{RET}} to see what it is.) Since @code{movemail} had not been
3044 designed for this situation, a security hole was created and users could
3045 get root privileges.
3046
3047 @code{movemail} has since been changed so that this security hole will
3048 not exist, even if it is installed setuid root. However,
3049 @code{movemail} no longer needs to be installed setuid root, which
3050 should eliminate this particular risk.
3051
3052 We have heard unverified reports that the 1988 Internet worm took
3053 advantage of this configuration problem.
3054
3055 @item
3056 The @code{file-local-variable} feature. (Yes, a risk, but easy to
3057 change.)
3058
3059 There is an Emacs feature that allows the setting of local values for
3060 variables when editing a file by including specially formatted text near
3061 the end of the file. This feature also includes the ability to have
3062 arbitrary Emacs Lisp code evaluated when the file is visited.
3063 Obviously, there is a potential for Trojan horses to exploit this
3064 feature.
3065
3066 Emacs 18 allowed this feature by default; users could disable it by
3067 setting the variable @code{inhibit-local-variables} to a non-@code{nil} value.
3068
3069 As of Emacs 19, Emacs has a list of local variables that create a
3070 security risk. If a file tries to set one of them, it asks the user to
3071 confirm whether the variables should be set. You can also tell Emacs
3072 whether to allow the evaluation of Emacs Lisp code found at the bottom
3073 of files by setting the variable @code{enable-local-eval}.
3074
3075 For more information, @inforef{File Variables, File Variables, emacs}.
3076
3077 @item
3078 Synthetic X events. (Yes, a risk; use @samp{MIT-MAGIC-COOKIE-1} or
3079 better.)
3080
3081 Emacs accepts synthetic X events generated by the @code{SendEvent}
3082 request as though they were regular events. As a result, if you are
3083 using the trivial host-based authentication, other users who can open X
3084 connections to your X workstation can make your Emacs process do
3085 anything, including run other processes with your privileges.
3086
3087 The only fix for this is to prevent other users from being able to open
3088 X connections. The standard way to prevent this is to use a real
3089 authentication mechanism, such as @samp{MIT-MAGIC-COOKIE-1}. If using
3090 the @code{xauth} program has any effect, then you are probably using
3091 @samp{MIT-MAGIC-COOKIE-1}. Your site may be using a superior
3092 authentication method; ask your system administrator.
3093
3094 If real authentication is not a possibility, you may be satisfied by
3095 just allowing hosts access for brief intervals while you start your X
3096 programs, then removing the access. This reduces the risk somewhat by
3097 narrowing the time window when hostile users would have access, but
3098 @emph{does not eliminate the risk}.
3099
3100 On most computers running Unix and X, you enable and disable
3101 access using the @code{xhost} command. To allow all hosts access to
3102 your X server, use
3103
3104 @example
3105 xhost +
3106 @end example
3107
3108 @noindent
3109 at the shell prompt, which (on an HP machine, at least) produces the
3110 following message:
3111
3112 @example
3113 access control disabled, clients can connect from any host
3114 @end example
3115
3116 To deny all hosts access to your X server (except those explicitly
3117 allowed by name), use
3118
3119 @example
3120 xhost -
3121 @end example
3122
3123 On the test HP computer, this command generated the following message:
3124
3125 @example
3126 access control enabled, only authorized clients can connect
3127 @end example
3128
3129 @end itemize
3130
3131 @node Dired claims that no file is on this line, , Security risks with Emacs, Bugs and problems
3132 @section Dired says, @samp{no file on this line} when I try to do something.
3133 @cindex Dired does not see a file
3134
3135 @c FIXME: I think this is fixed in Emacs 21, but I didn't have time to
3136 @c check.
3137 Chances are you're using a localized version of Unix that doesn't use US
3138 date format in dired listings. You can check this by looking at dired
3139 listings or by typing @kbd{ls -l} to a shell and looking at the dates that
3140 come out.
3141
3142 Dired uses a regular expression to find the beginning of a file name.
3143 In a long Unix-style directory listing (@samp{ls -l}), the file name
3144 starts after the date. The regexp has thus been written to look for the
3145 date, the format of which can vary on non-US systems.
3146
3147 There are two approaches to solving this. The first one involves
3148 setting things up so that @samp{ls -l} outputs US date format. This can
3149 be done by setting the locale. See your OS manual for more information.
3150
3151 The second approach involves changing the regular expression used by
3152 dired, @code{directory-listing-before-filename-regexp}.
3153
3154 @c ------------------------------------------------------------
3155 @node Compiling and installing Emacs, Finding Emacs and related packages, Bugs and problems, Top
3156 @chapter Compiling and installing Emacs
3157 @cindex Compiling and installing Emacs
3158
3159 @menu
3160 * Installing Emacs::
3161 * Updating Emacs::
3162 * Problems building Emacs::
3163 * Linking with -lX11 fails::
3164 @end menu
3165
3166 @node Installing Emacs, Updating Emacs, Compiling and installing Emacs, Compiling and installing Emacs
3167 @section How do I install Emacs?
3168 @cindex Installing Emacs
3169 @cindex Unix systems, installing Emacs on
3170 @cindex Downloading and installing Emacs
3171 @cindex Retrieving and installing Emacs
3172 @cindex Building Emacs from source
3173 @cindex Source code, building Emacs from
3174 @cindex Unpacking and installing Emacs
3175
3176 This answer is meant for users of Unix and Unix-like systems. Users of
3177 other operating systems should see the series of questions beginning
3178 with @ref{Emacs for MS-DOS}, which describe where to get non-Unix source
3179 and binaries, and how to install Emacs on those systems.
3180
3181 For Unix and Unix-like systems, the easiest way is often to compile it
3182 from scratch. You will need:
3183
3184 @itemize @bullet
3185
3186 @item
3187 Emacs sources. @xref{Current GNU distributions}, for a list of ftp sites
3188 that make them available. On @file{ftp.gnu.org}, the main GNU
3189 distribution site, sources are available as
3190
3191 @uref{ftp://ftp.gnu.org/pub/gnu/emacs/emacs-@value{VER}.tar.gz}
3192
3193 The above will obviously change as new versions of Emacs come out. For
3194 instance, when Emacs 22.42 is released, it will most probably be
3195 available as
3196
3197 @uref{ftp://ftp.gnu.org/pub/gnu/emacs/emacs-22.42.tar.gz}
3198
3199 Again, you should use one of the GNU mirror sites (see @ref{Current GNU
3200 distributions}, and adjust the URL accordingly) so as to reduce load on
3201 @file{ftp.gnu.org}.
3202
3203 @item
3204 @code{gzip}, the GNU compression utility. You can get @code{gzip} via
3205 anonymous ftp at mirrors of @file{ftp.gnu.org} sites; it should compile
3206 and install without much trouble on most systems. Once you have
3207 retrieved the Emacs sources, you will probably be able to uncompress
3208 them with the command
3209
3210 @example
3211 gunzip --verbose emacs-@value{VER}.tar.gz
3212 @end example
3213
3214 @noindent
3215 changing the Emacs version (@value{VER}), as necessary. Once
3216 @code{gunzip} has finished doing its job, a file by the name of
3217 @file{emacs-@value{VER}.tar} should be in your build directory.
3218
3219 @item
3220 @code{tar}, the @dfn{tape archiving} program, which moves multiple files
3221 into and out of archive files, or @dfn{tarfiles}. All of the files
3222 comprising the Emacs source come in a single tarfile, and must be
3223 extracted using @code{tar} before you can build Emacs. Typically, the
3224 extraction command would look like
3225
3226 @example
3227 tar -xvvf emacs-@value{VER}.tar
3228 @end example
3229
3230 @noindent
3231 The @samp{x} indicates that we want to extract files from this tarfile,
3232 the two @samp{v}s force verbose output, and the @samp{f} tells
3233 @code{tar} to use a disk file, rather than one on the tape drive.
3234
3235 If you're using GNU @code{tar} (available at mirrors of
3236 @file{ftp.gnu.org}), you can combine this step and the previous one by
3237 using the command
3238
3239 @example
3240 tar -zxvvf emacs-@value{VER}.tar.gz
3241 @end example
3242
3243 @noindent
3244 The additional @samp{z} at the beginning of the options list tells GNU
3245 @code{tar} to uncompress the file with @code{gunzip} before extracting
3246 the tarfile's components.
3247
3248 @end itemize
3249
3250 At this point, the Emacs sources (all 70+ megabytes of them) should be
3251 sitting in a directory called @file{emacs-@value{VER}}. On most common
3252 Unix and Unix-like systems, you should be able to compile Emacs (with X
3253 Window system support) with the following commands:
3254
3255 @example
3256 cd emacs-@value{VER} # change directory to emacs-@value{VER}
3257 ./configure # configure Emacs for your particular system
3258 make # use Makefile to build components, then Emacs
3259 @end example
3260
3261 If the @code{make} completes successfully, the odds are fairly good that
3262 the build has gone well. (@xref{Problems building Emacs}, if you weren't
3263 successful.)
3264
3265 By default, Emacs is installed in the following directories:
3266
3267 @table @file
3268 @item /usr/local/bin
3269 binaries.
3270
3271 @item /usr/local/share/emacs/@value{VER}
3272 Lisp code and support files.
3273
3274 @item /usr/local/info
3275 Info documentation.
3276 @end table
3277
3278 To install files in those default directories, become the superuser and
3279 type
3280
3281 @example
3282 make install
3283 @end example
3284
3285 Note that @samp{make install} will overwrite @file{/usr/local/bin/emacs}
3286 and any Emacs Info files that might be in @file{/usr/local/info}.
3287
3288 Much more verbose instructions (with many more hints and suggestions)
3289 come with the Emacs sources, in the file @file{INSTALL}.
3290
3291 @node Updating Emacs, Problems building Emacs, Installing Emacs, Compiling and installing Emacs
3292 @section How do I update Emacs to the latest version?
3293 @cindex Updating Emacs
3294
3295 @xref{Installing Emacs}, and follow the instructions there for
3296 installation.
3297
3298 Most files are placed in version-specific directories. Emacs
3299 @value{VER}, for instance, places files in
3300 @file{/usr/local/share/emacs/@value{VER}}.
3301
3302 Upgrading should overwrite only, @file{/usr/local/bin/emacs} (the Emacs
3303 binary) and documentation in @file{/usr/local/info}. Back up these
3304 files before you upgrade, and you shouldn't have too much trouble.
3305
3306 @node Problems building Emacs, Linking with -lX11 fails, Updating Emacs, Compiling and installing Emacs
3307 @section What should I do if I have trouble building Emacs?
3308 @cindex Problems building Emacs
3309 @cindex Errors when building Emacs
3310
3311 First look in the file @file{etc/PROBLEMS} (where you unpack the Emacs
3312 source) to see if there is already a solution for your problem. Next,
3313 look for other questions in this FAQ that have to do with Emacs
3314 installation and compilation problems.
3315
3316 If you'd like to have someone look at your problem and help solve it,
3317 see @ref{Help installing Emacs}.
3318
3319 If you cannot find a solution in the documentation, send a message to
3320 @email{bug-gnu-emacs@@gnu.org}.
3321
3322 Please don't post it to @uref{news:gnu.emacs.help} or send e-mail to
3323 @email{help-gnu-emacs@@gnu.org}. For further guidelines, see
3324 @ref{Guidelines for newsgroup postings} and @ref{Reporting bugs}.
3325
3326 @node Linking with -lX11 fails, , Problems building Emacs, Compiling and installing Emacs
3327 @section Why does linking Emacs with -lX11 fail?
3328 @cindex Linking with -lX11 fails
3329 @cindex lX11, linking fails with
3330
3331 Emacs needs to be linked with the static version of the X11 library,
3332 @file{libX11.a}. This may be missing.
3333
3334 On OpenWindows, you may need to use @code{add_services} to add the
3335 ``OpenWindows Programmers'' optional software category from the CD-ROM.
3336
3337 On HP-UX 8.0, you may need to run @code{update} again to load the
3338 X11-PRG ``fileset''. This may be missing even if you specified ``all
3339 filesets'' the first time. If @file{libcurses.a} is missing, you may
3340 need to load the ``Berkeley Development Option.''
3341
3342 @email{zoo@@armadillo.com, David Zuhn} says that MIT X builds shared
3343 libraries by default, and only shared libraries, on those platforms that
3344 support them. These shared libraries can't be used when undumping
3345 @code{temacs} (the last stage of the Emacs build process). To get
3346 regular libraries in addition to shared libraries, add this to
3347 @file{site.cf}:
3348
3349 @example
3350 #define ForceNormalLib YES
3351 @end example
3352
3353 Other systems may have similar problems. You can always define
3354 @code{CANNOT_DUMP} and link with the shared libraries instead.
3355
3356 @cindex X Menus don't work
3357 To get the Xmenu stuff to work, you need to find a copy of MIT's
3358 @file{liboldX.a}.
3359
3360 @c ------------------------------------------------------------
3361 @node Finding Emacs and related packages, Major packages and programs, Compiling and installing Emacs, Top
3362 @chapter Finding Emacs and related packages
3363 @cindex Finding Emacs and related packages
3364
3365 @menu
3366 * Finding Emacs on the Internet::
3367 * Finding a package with particular functionality::
3368 * Packages that do not come with Emacs::
3369 * Current GNU distributions::
3370 * Difference between Emacs and XEmacs::
3371 * Emacs for MS-DOS::
3372 * Emacs for Windows::
3373 * Emacs for OS/2::
3374 * Emacs for Atari ST::
3375 * Emacs for the Amiga ::
3376 * Emacs for NeXTSTEP::
3377 * Emacs for Apple computers::
3378 * Emacs for VMS and DECwindows::
3379 * Modes for various languages::
3380 @end menu
3381
3382 @node Finding Emacs on the Internet, Finding a package with particular functionality, Finding Emacs and related packages, Finding Emacs and related packages
3383 @section Where can I get Emacs on the net (or by snail mail)?
3384 @cindex Finding Emacs on the Internet
3385 @cindex Snail mail, ordering Emacs via
3386 @cindex Postal service, ordering Emacs via
3387 @cindex Distribution, retrieving Emacs
3388 @cindex Internet, retrieving from
3389
3390 Look in the files @file{etc/DISTRIB} and @file{etc/FTP} for
3391 information on nearby archive sites. If you don't already have Emacs,
3392 see @ref{Informational files for Emacs}, for how to get these files.
3393
3394 @xref{Installing Emacs}, for information on how to obtain and build the latest
3395 version of Emacs, and see @ref{Current GNU distributions}, for a list of
3396 archive sites that make GNU software available.
3397
3398 @node Finding a package with particular functionality, Packages that do not come with Emacs, Finding Emacs on the Internet, Finding Emacs and related packages
3399 @section How do I find a Emacs Lisp package that does XXX?
3400 @cindex Package, finding
3401 @cindex Finding an Emacs Lisp package
3402 @cindex Functionality, finding a particular package
3403
3404 First of all, you should check to make sure that the package isn't
3405 already available. For example, typing @kbd{M-x apropos @key{RET}
3406 wordstar @key{RET}} lists all functions and variables containing the
3407 string @samp{wordstar}.
3408
3409 It is also possible that the package is on your system, but has not been
3410 loaded. To see which packages are available for loading, look through
3411 your computer's lisp directory (@pxref{File-name conventions}). The Lisp
3412 source to most packages contains a short description of how they
3413 should be loaded, invoked, and configured---so before you use or
3414 modify a Lisp package, see if the author has provided any hints in the
3415 source code.
3416
3417 The command @kbd{C-h p} (@code{finder-by-keyword}) allows you to browse
3418 the constituent Emacs packages.
3419
3420 For advice on how to find extra packages that are not part of Emacs,
3421 see @ref{Packages that do not come with Emacs}.
3422
3423 @node Packages that do not come with Emacs, Current GNU distributions, Finding a package with particular functionality, Finding Emacs and related packages
3424 @section Where can I get Emacs Lisp packages that don't come with Emacs?
3425 @cindex Unbundled packages
3426 @cindex Finding other packages
3427 @cindex Lisp packages that do not come with Emacs
3428 @cindex Packages, those that do not come with Emacs
3429 @cindex Emacs Lisp List
3430 @cindex Emacs Lisp Archive
3431
3432 @uref{http://www.anc.ed.ac.uk/~stephen/emacs/ell.html, The Emacs Lisp
3433 List (ELL)}, maintained by @email{stephen@@anc.ed.ac.uk, Stephen Eglen},
3434 aims to provide one compact list with links to all of the current Emacs
3435 Lisp files on the internet. The ELL can be browsed over the web, or
3436 from Emacs with @uref{http://www.anc.ed.ac.uk/~stephen/emacs/ell.el,
3437 the @file{ell} package}.
3438
3439 Many authors post their packages to the @uref{news:gnu.emacs.sources,
3440 Emacs sources newsgroup}. You can search the archives of this
3441 group with @uref{http://groups.google.com, Google}, for example.
3442
3443 Several packages are stored in
3444 @uref{http://emacswiki.org/elisp/, the Lisp area of the Emacs Wiki}.
3445
3446 For a long time, the Emacs Lisp Archive provided a central repository
3447 for Emacs packages. Sadly, it has not been active for some time,
3448 although you can still access the old files at
3449
3450 @uref{ftp://ftp.cis.ohio-state.edu/pub/emacs-lisp/WWW/index.html}
3451
3452 @node Current GNU distributions, Difference between Emacs and XEmacs, Packages that do not come with Emacs, Finding Emacs and related packages
3453 @section Where can I get other up-to-date GNU stuff?
3454 @cindex Current GNU distributions
3455 @cindex Sources for current GNU distributions
3456 @cindex Stuff, current GNU
3457 @cindex Up-to-date GNU stuff
3458 @cindex Finding current GNU software
3459 @cindex Official GNU software sites
3460
3461 The most up-to-date official GNU software is normally kept at
3462
3463 @uref{ftp://ftp.gnu.org/pub/gnu}
3464
3465 Read the files @file{etc/DISTRIB} and @file{etc/FTP} for more
3466 information.
3467
3468 A list of sites mirroring @samp{ftp.gnu.org} can be found at
3469
3470 @uref{http://www.gnu.org/order/ftp.html}
3471
3472 @node Difference between Emacs and XEmacs, Emacs for MS-DOS, Current GNU distributions, Finding Emacs and related packages
3473 @section What is the difference between Emacs and XEmacs (formerly Lucid Emacs)?
3474 @cindex XEmacs
3475 @cindex Difference Emacs and XEmacs
3476 @cindex Lucid Emacs
3477 @cindex Epoch
3478
3479 XEmacs is a branch version of Emacs. It was first called Lucid Emacs,
3480 and was initially derived from a prerelease version of Emacs 19. In
3481 this FAQ, we use the name ``Emacs'' only for the official version.
3482
3483 Emacs and XEmacs each come with Lisp packages that are lacking in the
3484 other. The two versions have some significant differences at the Lisp
3485 programming level. Their current features are roughly comparable,
3486 though the support for some operating systems, character sets and
3487 specific packages might be quite different.
3488
3489 Some XEmacs code has been contributed to Emacs, and we would like to
3490 use other parts, but the earlier XEmacs maintainers did not always
3491 keep track of the authors of contributed code, which makes it
3492 impossible for the FSF to get copyright papers signed for that code.
3493 (The FSF requires these papers for all the code included in the Emacs
3494 release, aside from generic C support packages that retain their
3495 separate identity and are not integrated into the code of Emacs
3496 proper.)
3497
3498 If you want to talk about these two versions and distinguish them,
3499 please call them ``Emacs'' and ``XEmacs.'' To contrast ``XEmacs''
3500 with ``GNU Emacs'' would be misleading, since XEmacs too has its
3501 origin in the work of the GNU Project. Terms such as ``Emacsen'' and
3502 ``(X)Emacs'' are not wrong, but they are not very clear, so it
3503 is better to write ``Emacs and XEmacs.''
3504
3505 @node Emacs for MS-DOS, Emacs for Windows, Difference between Emacs and XEmacs, Finding Emacs and related packages
3506 @section Where can I get Emacs for my PC running MS-DOS?
3507 @cindex MS-DOS, Emacs for
3508 @cindex DOS, Emacs for
3509 @cindex Compiling Emacs for DOS
3510 @cindex Emacs for MS-DOS
3511 @cindex Tools needed to compile Emacs under DOS
3512
3513 A pre-built binary distribution of Emacs is available from the
3514 SimTel.NET archives. This version apparently works under MS-DOS and
3515 Windows (3.X, 9X, ME, NT, and 2000) and supports long file names under
3516 Windows 9X, Windows ME, and Windows 2000. More information is available
3517 from
3518
3519 @uref{ftp://ftp.delorie.com/pub/djgpp/current/v2gnu/emacs.README}
3520
3521 The binary itself is available in the files @file{em*.zip} in the
3522 directory
3523
3524 @uref{ftp://ftp.delorie.com/pub/djgpp/current/v2gnu/}
3525
3526 If you prefer to compile Emacs for yourself, you can do so with the
3527 current distribution directly. You will need a 386 (or
3528 better) processor, and to be running MS-DOS 3.0 or later. According to
3529 @email{eliz@@gnu.org, Eli Zaretskii} and
3530 @email{hankedr@@dms.auburn.edu, Darrel Hankerson}, you will need the
3531 following:
3532
3533 @table @emph
3534
3535 @item Compiler
3536 DJGPP version 1.12 maint 1 or later. Djgpp 2.0 or later is
3537 recommended, since 1.x is very old an unmaintained. Djgpp 2 supports
3538 long file names on Windows 9X/ME/2K.
3539
3540 You can get the latest release of DJGPP by retrieving all of
3541 the files in
3542
3543 @uref{ftp://ftp.delorie.com/pub/djgpp/current/v2*}
3544
3545 @item Unpacking program
3546 The easiest way is to use @code{djtar} which comes with DJGPP v2.x,
3547 because it can open gzip'ed tarfiles (i.e., those ending with
3548 @file{.tar.gz}) in one step. @code{Djtar} comes in
3549 @file{djdev@var{nnn}.zip} archive (where @var{nnn} is the DJGPP version
3550 number), from the URL mentioned above.
3551
3552 @strong{Warning!} Do @strong{not} use the popular WinZip program to
3553 unpack the Emacs distribution! WinZip is known to corrupt some of the
3554 files by converting them to the DOS CR-LF format, it doesn't always
3555 preserve the directory structure recorded in the compressed Emacs
3556 archive, and commits other atrocities. Some of these problems could
3557 actually prevent Emacs from building successfully!
3558
3559 @item make, mv, sed, and rm
3560 All of these utilities are available at
3561
3562 @uref{ftp://ftp.delorie.com/pub/djgpp/current/v2gnu}
3563
3564 16-bit utilities can be found in GNUish, at
3565
3566 @uref{http://www.simtel.net/pub/gnuish/}
3567
3568 @noindent
3569 (@code{mv} and @code{rm} are in the Fileutils package, @code{sed} and
3570 @code{make} are each one in a separate package named after them.)
3571
3572 @end table
3573
3574 The files @file{INSTALL} (near its end) and @file{etc/PROBLEMS} in the
3575 directory of the Emacs sources contains some additional information
3576 regarding Emacs under MS-DOS.
3577
3578 For a list of other MS-DOS implementations of Emacs (and Emacs
3579 look-alikes), consult the list of ``Emacs implementations and literature,''
3580 available at
3581
3582 @uref{ftp://rtfm.mit.edu/pub/usenet/comp.emacs/}
3583
3584 Note that while many of these programs look similar to Emacs, they often
3585 lack certain features, such as the Emacs Lisp extension language.
3586
3587 @node Emacs for Windows, Emacs for OS/2, Emacs for MS-DOS, Finding Emacs and related packages
3588 @section Where can I get Emacs for Microsoft Windows?
3589 @cindex FAQ for NT Emacs
3590 @cindex Emacs for MS-Windows
3591 @cindex Microsoft Windows, Emacs for
3592 @cindex Windows 9X, ME, NT, 2K, and CE, Emacs for
3593
3594 For information on Emacs for Windows 95 and NT, read the FAQ produced by
3595 @email{voelker@@cs.washington.edu, Geoff Voelker}, available at
3596
3597 @uref{http://www.gnu.org/software/emacs/windows/ntemacs.html}
3598
3599 @xref{Emacs for MS-DOS}, for Windows 3.1.
3600
3601 A port of Emacs 20.7 for Windows CE, based on NTEmacs, is available at
3602
3603 @uref{http://www.rainer-keuchel.de/software.html}
3604
3605 @noindent
3606 This port was done by @email{coyxc@@rainer-keuchel.de, Rainer Keuchel},
3607 and supports all Emacs features except async subprocesses and menus.
3608 You will need MSVC 6.0 and a Windows CE SDK to build this port.
3609
3610 @node Emacs for OS/2, Emacs for Atari ST, Emacs for Windows, Finding Emacs and related packages
3611 @section Where can I get Emacs for my PC running OS/2?
3612 @cindex OS/2, Emacs for
3613
3614 Emacs 20.6 is ported for emx on OS/2 2.0 or 2.1, and is available at
3615
3616 @uref{ftp://hobbes.nmsu.edu/pub/os2/apps/editors/emacs/e206*.zip}
3617
3618 @noindent
3619 and also at
3620
3621 @uref{http://archiv.leo.org/pub/comp/os/os2/leo/gnu/emacs%2d20/}
3622
3623 Instructions for installation, basic setup, and other useful information
3624 for OS/2 users of Emacs can be found at
3625
3626 @uref{http://userpage.fu-berlin.de/~oheiabbd/emacs/emacs206-os2.html}
3627
3628 @node Emacs for Atari ST, Emacs for the Amiga , Emacs for OS/2, Finding Emacs and related packages
3629 @section Where can I get Emacs for my Atari ST?
3630 @cindex Atari ST, Emacs for
3631 @cindex TOS, Emacs for
3632
3633 Roland Schäuble reports that Emacs 18.58 running on plain TOS and MiNT
3634 is available at
3635 @uref{ftp://atari.archive.umich.edu/Editors/Emacs-18-58/1858b-d3.zoo}.
3636
3637 @node Emacs for the Amiga , Emacs for NeXTSTEP, Emacs for Atari ST, Finding Emacs and related packages
3638 @section Where can I get Emacs for my Amiga?
3639 @cindex Amiga, Emacs for
3640
3641 The files you need are available at
3642
3643 @uref{ftp://ftp.wustl.edu/pub/aminet/util/gnu/}
3644
3645 @email{dgilbert@@gamiga.guelphnet.dweomer.org, David Gilbert} has released a
3646 beta version of Emacs 19.25 for the Amiga. You can get the binary at
3647
3648 @uref{ftp://ftp.wustl.edu/pub/aminet/util/gnu/a2.0bEmacs-bin.lha}
3649
3650 @node Emacs for NeXTSTEP, Emacs for Apple computers, Emacs for the Amiga , Finding Emacs and related packages
3651 @section Where can I get Emacs for NeXTSTEP?
3652 @cindex NeXTSTEP, Emacs for
3653
3654 Emacs.app is a NeXTSTEP version of Emacs 19.34 which supports colors,
3655 menus, and multiple frames. You can get it from
3656
3657 @uref{ftp://next-ftp.peak.org/pub/next/apps/emacs/Emacs_for_NeXTstep.4.20a1.NIHS.b.tar.gz}
3658
3659 @node Emacs for Apple computers, Emacs for VMS and DECwindows, Emacs for NeXTSTEP, Finding Emacs and related packages
3660 @section Where can I get Emacs for my Apple computer?
3661 @cindex Apple computers, Emacs for
3662 @cindex Macintosh, Emacs for
3663
3664 Beginning with version 21.1, the Macintosh is supported in the official
3665 Emacs distribution; see the files @file{mac/README} and
3666 @file{mac/INSTALL} in the Emacs distribution for build instructions.
3667
3668 Beginning with version 22.1, Emacs supports Mac OS X natively.
3669
3670 @node Emacs for VMS and DECwindows, Modes for various languages, Emacs for Apple computers, Finding Emacs and related packages
3671 @section Where do I get Emacs that runs on VMS under DECwindows?
3672 @cindex DECwindows, Emacs for
3673 @cindex VMS, Emacs for
3674
3675 Up-to-date information about GNU software (including Emacs) for VMS is
3676 available at @uref{http://vms.gnu.org/}.
3677
3678 @node Modes for various languages, , Emacs for VMS and DECwindows, Finding Emacs and related packages
3679 @section Where can I get modes for Lex, Yacc/Bison, Bourne shell, csh, C@t{++}, Objective-C, Pascal, Java, and Awk?
3680 @cindex Awk, mode for
3681 @cindex @code{awk-mode}
3682 @cindex Bison, mode for
3683 @cindex Bourne Shell, mode for
3684 @cindex C@t{++}, mode for
3685 @cindex Java, mode for
3686 @cindex Lex mode
3687 @cindex Objective-C, mode for
3688 @cindex @code{pascal-mode}
3689 @cindex Shell mode
3690 @cindex Yacc mode
3691 @cindex @file{csh} mode
3692 @cindex @code{sh-mode}
3693 @cindex @code{cc-mode}
3694
3695 Most of these modes are now available in standard Emacs distribution.
3696 To get additional modes, see @ref{Finding a package with particular
3697 functionality}.
3698
3699 Barry Warsaw's @code{cc-mode} now works for C, C@t{++}, Objective-C, and
3700 Java code. It is distributed with Emacs, but has
3701 @uref{http://cc-mode.sourceforge.net/, its own homepage}.
3702
3703 @c ------------------------------------------------------------
3704 @node Major packages and programs, Key bindings, Finding Emacs and related packages, Top
3705 @chapter Major packages and programs
3706 @cindex Major packages and programs
3707
3708 @menu
3709 * VM::
3710 * Supercite::
3711 * Calc::
3712 * VIPER::
3713 * AUCTeX::
3714 * BBDB::
3715 * Ispell::
3716 * w3-mode::
3717 * EDB::
3718 * Mailcrypt::
3719 * JDE::
3720 * Patch::
3721 @end menu
3722
3723 @node VM, Supercite, Major packages and programs, Major packages and programs
3724 @section VM (View Mail) --- another mail reader within Emacs, with MIME support
3725 @cindex VM
3726 @cindex Alternative mail software
3727 @cindex View Mail
3728 @cindex E-mail reader, VM
3729
3730 @table @b
3731
3732 @item Author
3733 @email{kyle_jones@@wonderworks.com, Kyle Jones}
3734
3735 @item Latest version
3736 7.15
3737
3738 @item Distribution
3739 @uref{ftp://ftp.wonderworks.com/pub/vm/vm.tar.gz}
3740
3741 @item Informational newsgroup
3742 @uref{news:gnu.emacs.vm.info}@*
3743
3744 @item Bug reports newsgroup
3745 @uref{news:gnu.emacs.vm.bug}@*
3746 Or send reports to @email{bug-vm@@wonderworks.com}
3747 @end table
3748
3749 VM 7 works well with Emacs 21. Older versions of VM suitable for use
3750 with older versions of Emacs are available from
3751 @uref{ftp://ftp.wonderworks.com/pub/vm/, the same FTP site}.
3752
3753
3754 @node Supercite, Calc, VM, Major packages and programs
3755 @section Supercite --- mail and news citation package within Emacs
3756 @cindex Supercite
3757 @cindex Superyank
3758 @cindex Mail and news citations
3759 @cindex News and mail citations
3760 @cindex Citations in mail and news
3761
3762 @table @b
3763
3764 @item Author
3765 @email{barry@@python.org, Barry Warsaw}
3766
3767 @item Latest version
3768 3.54 (comes bundled with Emacs since version 20)
3769
3770 @item Distribution
3771 @uref{http://www.python.org/emacs/supercite.tar.gz}
3772
3773 @item Mailing list
3774 Subscription requests to @email{supercite-request@@python.org}@*
3775 Submissions @email{supercite@@python.org}
3776
3777 @end table
3778
3779 Superyank is an old version of Supercite.
3780
3781 @node Calc, VIPER, Supercite, Major packages and programs
3782 @section Calc --- poor man's Mathematica within Emacs
3783 @cindex Programmable calculator
3784 @cindex Calc
3785 @cindex Mathematical package
3786
3787 @table @b
3788
3789 @item Author
3790 @email{daveg@@csvax.cs.caltech.edu, Dave Gillespie}
3791
3792 @item Latest version
3793 2.02g (part of Emacs since version 22.1)
3794
3795 @item Distribution
3796 No separate distribution outside of Emacs. Older versions
3797 are available at @uref{ftp://ftp.gnu.org/pub/gnu/calc/}.
3798
3799 @end table
3800
3801 Note that Calc 2.02f needs patching to work with Emacs 21 and later.
3802
3803 @cindex @code{calculator}, a package
3804 Emacs 21.1 and later comes with a package called @file{calculator.el}.
3805 It doesn't support all the mathematical wizardry offered by Calc, such
3806 as matrices, special functions, and statistics, but is more than
3807 adequate as a replacement for @code{xcalc} and similar programs.
3808
3809 @node VIPER, AUCTeX, Calc, Major packages and programs
3810 @section VIPER --- @code{vi} emulation for Emacs
3811 @cindex @code{vi} emulation
3812 @cindex VIPER
3813 @cindex Emulation of @code{vi}
3814
3815 Since Emacs 19.29, the preferred @code{vi} emulation in Emacs is VIPER
3816 (@kbd{M-x viper-mode @key{RET}}), which comes with Emacs. It extends
3817 and supersedes VIP (including VIP 4.3) and provides @code{vi} emulation
3818 at several levels, from one that closely follows @code{vi} to one that
3819 departs from @code{vi} in several significant ways.
3820
3821 For Emacs 19.28 and earlier, the following version of VIP is generally
3822 better than the one distributed with Emacs:
3823
3824 @table @b
3825 @item Author
3826 @email{sane@@cs.uiuc.edu, Aamod Sane}
3827
3828 @item Latest version
3829 4.3
3830
3831 @item Distribution
3832 @uref{ftp://archive.cis.ohio-state.edu/pub/emacs-lisp/old-archive/modes/vip-mode.tar.Z}
3833
3834 @end table
3835
3836 @node AUCTeX, BBDB, VIPER, Major packages and programs
3837 @section AUC@TeX{} --- enhanced @TeX{} modes with debugging facilities
3838 @cindex Mode for @TeX{}
3839 @cindex @TeX{} mode
3840 @cindex AUC@TeX{} mode for editing @TeX{}
3841 @cindex Writing and debugging @TeX{}
3842
3843 AUC@TeX{} is a set of sophisticated major modes for @TeX{}, LaTeX,
3844 ConTeXt, and Texinfo offering context-sensitive syntax highlighting,
3845 indentation, formatting and folding, macro completion, @TeX{} shell
3846 functionality, and debugging. Some important supplemental packages are
3847 described in @ref{Introduction, RefTeX, Introduction, reftex, Ref@TeX{}
3848 User Manual}, and
3849 @uref{http://preview-latex.sourceforge.net,preview-latex}.
3850
3851 @table @b
3852
3853 @item Authors
3854 @email{krab@@iesd.auc.dk, Kresten Krab Thorup}, @*
3855 @email{abraham@@dina.kvl.dk, Per Abrahamsen}, @* and others.
3856
3857 @item Maintainer
3858 @email{dak@@gnu.org, David Kastrup}
3859
3860 @item Latest version
3861 11.54
3862
3863 @item Distribution
3864 @uref{ftp://ftp.gnu.org/pub/gnu/auctex/}
3865
3866 @item Web site
3867 @uref{http://www.gnu.org/software/auctex/}
3868
3869 @item Mailing list:
3870 Subscription requests to @email{auc-tex-subscribe@@sunsite.dk}@*
3871 Submissions to @email{auc-tex@@sunsite.dk}
3872
3873 @end table
3874
3875 @node BBDB, Ispell, AUCTeX, Major packages and programs
3876 @section BBDB --- personal Info Rolodex integrated with mail/news readers
3877 @cindex BBDB
3878 @cindex Rolodex-like functionality
3879 @cindex Integrated contact database
3880 @cindex Contact database
3881 @cindex Big Brother Database
3882 @cindex Address book
3883
3884 @table @b
3885
3886 @item Maintainer
3887 @email{waider@@waider.ie, Ronan Waide}
3888
3889 @item Latest version
3890 2.34
3891
3892 @item Distribution
3893 @uref{http://bbdb.sourceforge.net/}
3894
3895 @item Mailing lists
3896 Subscription requests to @email{bbdb-info-request@@lists.sourceforge.net}@*
3897 Submissions to @email{bbdb-info@@lists.sourceforge.net}@*
3898 Release announcements: @email{bbdb-announce-request@@lists.sourceforge.net}
3899
3900 @end table
3901
3902 @node Ispell, w3-mode, BBDB, Major packages and programs
3903 @section Ispell --- spell checker in C with interface for Emacs
3904 @cindex Spell-checker
3905 @cindex Checking spelling
3906 @cindex Ispell
3907
3908 @table @b
3909
3910 @item Author
3911 @email{geoff@@itcorp.com, Geoff Kuenning}
3912
3913 @item Latest version
3914 3.1.20
3915
3916 @item Distribution
3917 @uref{ftp://ftp.cs.ucla.edu/pub/ispell/ispell-3.1.20.tar.gz}@*
3918
3919 @item Web site
3920 @uref{http://fmg-www.cs.ucla.edu/geoff/ispell.html}
3921
3922 @end table
3923
3924 @itemize @bullet
3925
3926 @item
3927 Do not ask Geoff to send you the latest version of Ispell. He does not
3928 have free e-mail.
3929
3930 @item
3931 This Ispell program is distinct from GNU Ispell 4.0. GNU Ispell 4.0 is
3932 no longer a supported product.
3933
3934 @end itemize
3935
3936 @node w3-mode, EDB, Ispell, Major packages and programs
3937 @section w3-mode --- A World Wide Web browser inside of Emacs
3938 @cindex WWW browser
3939 @cindex Web browser
3940 @cindex HTML browser in Emacs
3941 @cindex @code{w3-mode}
3942
3943 @table @b
3944
3945 @item Author
3946 @email{wmperry@@spry.com, Bill Perry}
3947
3948 @item Latest version
3949 4.0pre.39
3950
3951 @item Distribution
3952 @uref{ftp://ftp.cs.indiana.edu/pub/elisp/w3/w3.tar.gz}
3953
3954 @item Mailing lists
3955 Receive announcements from @email{w3-announce-request@@indiana.edu}@*
3956 Become a beta tester at @email{w3-beta-request@@indiana.edu}@*
3957 Help to develop @code{w3-mode} at @email{w3-dev@@indiana.edu}
3958
3959 @end table
3960
3961 @node EDB, Mailcrypt, w3-mode, Major packages and programs
3962 @section EDB --- Database program for Emacs; replaces forms editing modes
3963 @cindex EDB
3964 @cindex Database
3965 @cindex Forms mode
3966
3967 @table @b
3968 @item Author
3969 @email{mernst@@theory.lcs.mit.edu, Michael Ernst}
3970
3971 @item Latest version
3972 1.21
3973
3974 @item Distribution
3975 @uref{ftp://theory.lcs.mit.edu/pub/emacs/edb}
3976
3977 @end table
3978
3979 @node Mailcrypt, JDE, EDB, Major packages and programs
3980 @section Mailcrypt --- PGP interface within Emacs mail and news
3981 @cindex PGP
3982 @cindex GPG
3983 @cindex Interface to PGP from Emacs mail and news
3984 @cindex News, interface to PGP from
3985 @cindex Mail, interface to PGP from
3986 @cindex Encryption software, interface to
3987
3988 @table @b
3989
3990 @item Authors
3991 @email{patl@@lcs.mit.edu, Patrick J. LoPresti} and
3992 @email{jin@@atype.com, Jin S. Choi}
3993
3994 @item Maintainer
3995 @email{warner-mailcrypt@@lothar.com, Brian Warner}
3996
3997 @item Latest version
3998 3.5.8
3999
4000 @item Distribution
4001 @uref{http://dl.sourceforge.net/sourceforge/mailcrypt/mailcrypt-3.5.8.tar.gz}
4002
4003 @item Web site
4004 @uref{http://mailcrypt.sourceforge.net/}
4005
4006 @end table
4007
4008 @node JDE, Patch, Mailcrypt, Major packages and programs
4009 @section JDE --- Integrated development environment for Java
4010 @cindex Java development environment
4011 @cindex Integrated Java development environment
4012 @cindex JDE
4013
4014 @table @b
4015
4016 @item Author
4017 @email{paulk@@mathworks.com, Paul Kinnucan}
4018
4019 @item Mailing list
4020 jde-subscribe@@sunsite.auc.dk
4021
4022 @item Latest version
4023 2.1.1
4024
4025 @item Web site
4026 @uref{http://sunsite.auc.dk/jde/}
4027
4028 @end table
4029
4030 @node Patch, , JDE, Major packages and programs
4031 @section Patch --- program to apply ``diffs'' for updating files
4032 @cindex Updating files with diffs
4033 @cindex Patching source files with diffs
4034 @cindex Diffs and patching
4035 @cindex @file{patch}
4036
4037 @table @b
4038
4039 @item Author
4040 @email{lwall@@wall.org, Larry Wall} (with GNU modifications)
4041
4042 @item Latest version
4043 2.5.4
4044
4045 @item Distribution
4046 @xref{Current GNU distributions}.
4047
4048 @end table
4049
4050 @c ------------------------------------------------------------
4051 @node Key bindings, Alternate character sets, Major packages and programs, Top
4052 @chapter Key bindings
4053 @cindex Key bindings
4054
4055 @menu
4056 * Binding keys to commands::
4057 * Invalid prefix characters::
4058 * Terminal setup code works after Emacs has begun::
4059 * Using function keys under X::
4060 * Working with function and arrow keys::
4061 * X key translations for Emacs::
4062 * Handling C-s and C-q with flow control::
4063 * Binding C-s and C-q::
4064 * Backspace invokes help::
4065 * stty and Backspace key::
4066 * Swapping keys::
4067 * Producing C-XXX with the keyboard::
4068 * No Meta key::
4069 * No Escape key::
4070 * Compose Character::
4071 * Binding combinations of modifiers and function keys::
4072 * Meta key does not work in xterm::
4073 * ExtendChar key does not work as Meta::
4074 * SPC no longer completes file names::
4075 @end menu
4076
4077 @node Binding keys to commands, Invalid prefix characters, Key bindings, Key bindings
4078 @section How do I bind keys (including function keys) to commands?
4079 @cindex Binding keys to commands
4080 @cindex Keys, binding to commands
4081 @cindex Commands, binding keys to
4082
4083 Keys can be bound to commands either interactively or in your
4084 @file{.emacs} file. To interactively bind keys for all modes, type
4085 @kbd{M-x global-set-key @key{RET} @var{key} @var{cmd} @key{RET}}.
4086
4087 To bind a key just in the current major mode, type @kbd{M-x
4088 local-set-key @key{RET} @var{key} @var{cmd} @key{RET}}.
4089
4090 @inforef{Key Bindings, Key Bindings, emacs}, for further details.
4091
4092 To make the process of binding keys interactively easier, use the
4093 following ``trick'': First bind the key interactively, then immediately
4094 type @kbd{C-x @key{ESC} @key{ESC} C-a C-k C-g}. Now, the command needed
4095 to bind the key is in the kill ring, and can be yanked into your
4096 @file{.emacs} file. If the key binding is global, no changes to the
4097 command are required. For example,
4098
4099 @lisp
4100 (global-set-key (quote [f1]) (quote help-for-help))
4101 @end lisp
4102
4103 @noindent
4104 can be placed directly into the @file{.emacs} file. If the key binding is
4105 local, the command is used in conjunction with the @samp{add-hook} function.
4106 For example, in TeX mode, a local binding might be
4107
4108 @lisp
4109 (add-hook 'tex-mode-hook
4110 (lambda ()
4111 (local-set-key (quote [f1]) (quote help-for-help))))
4112 @end lisp
4113
4114
4115 @itemize @bullet
4116
4117 @item
4118 Control characters in key sequences, in the form yanked from the kill
4119 ring are given in their graphic form---i.e., @key{CTRL} is shown as
4120 @samp{^}, @key{TAB} as a set of spaces (usually 8), etc. You may want
4121 to convert these into their vector or string forms.
4122
4123 @item
4124 If a prefix key of the character sequence to be bound is already
4125 bound as a complete key, then you must unbind it before the new
4126 binding. For example, if @kbd{ESC @{} is previously bound:
4127
4128 @lisp
4129 (global-unset-key [?\e ?@{]) ;; or
4130 (local-unset-key [?\e ?@{])
4131 @end lisp
4132
4133 @item
4134 Aside from commands and ``lambda lists,'' a vector or string also
4135 can be bound to a key and thus treated as a macro. For example:
4136
4137 @lisp
4138 (global-set-key [f10] [?\C-x?\e?\e?\C-a?\C-k?\C-g]) ;; or
4139 (global-set-key [f10] "\C-x\e\e\C-a\C-k\C-g")
4140 @end lisp
4141
4142 @end itemize
4143
4144 @node Invalid prefix characters, Terminal setup code works after Emacs has begun, Binding keys to commands, Key bindings
4145 @section Why does Emacs say @samp{Key sequence XXX uses invalid prefix characters}?
4146 @cindex Prefix characters, invalid
4147 @cindex Invalid prefix characters
4148 @cindex Misspecified key sequences
4149
4150 Usually, one of two things has happened. In one case, the control
4151 character in the key sequence has been misspecified (e.g. @samp{C-f}
4152 used instead of @samp{\C-f} within a Lisp expression). In the other
4153 case, a @dfn{prefix key} in the keystroke sequence you were trying to bind
4154 was already bound as a @dfn{complete key}. Historically, the @samp{ESC [}
4155 prefix was usually the problem, in which case you should evaluate either
4156 of these forms before attempting to bind the key sequence:
4157
4158 @lisp
4159 (global-unset-key [?\e ?[]) ;; or
4160 (global-unset-key "\e[")
4161 @end lisp
4162
4163 @node Terminal setup code works after Emacs has begun, Using function keys under X, Invalid prefix characters, Key bindings
4164 @section Why doesn't this [terminal or window-system setup] code work in my @file{.emacs} file, but it works just fine after Emacs starts up?
4165 @cindex Terminal setup code in @file{.emacs}
4166
4167 During startup, Emacs initializes itself according to a given code/file
4168 order. If some of the code executed in your @file{.emacs} file needs to
4169 be postponed until the initial terminal or window-system setup code has
4170 been executed but is not, then you will experience this problem (this
4171 code/file execution order is not enforced after startup).
4172
4173 To postpone the execution of Emacs Lisp code until after terminal or
4174 window-system setup, treat the code as a @dfn{lambda list} and set the
4175 value of either the @code{term-setup-hook} or @code{window-setup-hook}
4176 variable to this lambda function. For example,
4177
4178 @lisp
4179 (add-hook 'term-setup-hook
4180 (lambda ()
4181 (when (string-match "\\`vt220" (or (getenv "TERM") ""))
4182 ;; Make vt220's "Do" key behave like M-x:
4183 (global-set-key [do] 'execute-extended-command))))
4184 @end lisp
4185
4186 For information on what Emacs does every time it is started, see the
4187 @file{lisp/startup.el} file.
4188
4189 @node Using function keys under X, Working with function and arrow keys, Terminal setup code works after Emacs has begun, Key bindings
4190 @section How do I use function keys under X?
4191 @cindex Function keys
4192 @cindex X Window System and function keys
4193 @cindex Binding function keys
4194
4195 With Emacs 19, functions keys under X are bound like any other key. @xref{Binding keys to commands}, for details.
4196
4197 @node Working with function and arrow keys, X key translations for Emacs, Using function keys under X, Key bindings
4198 @section How do I tell what characters or symbols my function or arrow keys emit?
4199 @cindex Working with arrow keys
4200 @cindex Arrow keys, symbols generated by
4201 @cindex Working with function keys
4202 @cindex Function keys, symbols generated by
4203 @cindex Symbols generated by function keys
4204
4205 Type @kbd{C-h c} then the function or arrow keys. The command will
4206 return either a function key symbol or character sequence (see the
4207 Emacs on-line documentation for an explanation). This works for other
4208 keys as well.
4209
4210 @node X key translations for Emacs, Handling C-s and C-q with flow control, Working with function and arrow keys, Key bindings
4211 @section How do I set the X key ``translations'' for Emacs?
4212 @cindex X key translations
4213 @cindex Key translations under X
4214 @cindex Translations for keys under X
4215
4216 Emacs is not written using the Xt library by default, so there are no
4217 ``translations'' to be set. (We aren't sure how to set such translations
4218 if you do build Emacs with Xt; please let us know if you've done this!)
4219
4220 The only way to affect the behavior of keys within Emacs is through
4221 @code{xmodmap} (outside Emacs) or @code{define-key} (inside Emacs). The
4222 @code{define-key} command should be used in conjunction with the
4223 @code{function-key-map} map. For instance,
4224
4225 @lisp
4226 (define-key function-key-map [M-@key{TAB}] [?\M-\t])
4227 @end lisp
4228
4229 @noindent
4230 defines the @kbd{M-@key{TAB}} key sequence.
4231
4232 @node Handling C-s and C-q with flow control, Binding C-s and C-q, X key translations for Emacs, Key bindings
4233 @section How do I handle @kbd{C-s} and @kbd{C-q} being used for flow control?
4234 @cindex Flow control, @kbd{C-s} and @kbd{C-q} with
4235 @cindex @kbd{C-s} and @kbd{C-q} with flow control
4236
4237 @kbd{C-s} and @kbd{C-q} are used in the XON/XOFF flow control protocol.
4238 This messes things up when you're using Emacs over a serial line,
4239 because Emacs binds these keys to commands by default. Because Emacs
4240 won't honor them as flow control characters, too many of these
4241 characters are not passed on and overwhelm output buffers. Sometimes,
4242 intermediate software using XON/XOFF flow control will prevent Emacs
4243 from ever seeing @kbd{C-s} and @kbd{C-q}.
4244
4245 Possible solutions:
4246
4247 @itemize @bullet
4248
4249 @item
4250 Disable the use of @kbd{C-s} and @kbd{C-q} for flow control.
4251
4252 You need to determine the cause of the flow control.
4253
4254 @itemize @minus
4255
4256 @item
4257 your terminal
4258
4259 Your terminal may use XON/XOFF flow control to have time to display
4260 all the characters it receives. For example, VT series terminals do
4261 this. It may be possible to turn this off from a setup menu. For
4262 example, on a VT220 you may select ``No XOFF'' in the setup menu. This
4263 is also true for some terminal emulation programs on PCs.
4264
4265 When you turn off flow control at the terminal, you will also need to
4266 turn it off at the other end, which might be at the computer you are
4267 logged in to or at some terminal server in between.
4268
4269 If you turn off flow control, characters may be lost; using a printer
4270 connected to the terminal may fail. You may be able to get around
4271 this problem by modifying the @samp{termcap} entry for your terminal to
4272 include extra NUL padding characters.
4273
4274 @item
4275 a modem
4276
4277 If you are using a dialup connection, the modems may be using
4278 XON/XOFF flow control. It's not clear how to get around this.
4279
4280 @item
4281 a router or terminal server
4282
4283 Some network box between the terminal and your computer may be using
4284 XON/XOFF flow control. It may be possible to make it use some other
4285 kind of flow control. You will probably have to ask your local
4286 network experts for help with this.
4287
4288 @item
4289 @code{tty} and/or @code{pty} devices
4290
4291 If your connection to Emacs goes through multiple @code{tty} and/or
4292 @code{pty} devices, they may be using XON/XOFF flow control even when it
4293 is not necessary.
4294
4295 @email{eirik@@theory.tn.cornell.edu, Eirik Fuller} writes:
4296
4297 @quotation
4298 Some versions of @code{rlogin} (and possibly @code{telnet}) do not pass
4299 flow control characters to the remote system to which they connect. On
4300 such systems, Emacs on the remote system cannot disable flow control on
4301 the local system. Sometimes @samp{rlogin -8} will avoid this problem.
4302
4303 One way to cure this is to disable flow control on the local host (the
4304 one running @code{rlogin}, not the one running @code{rlogind}) using the
4305 @code{stty} command, before starting the @code{rlogin} process. On many
4306 systems, @samp{stty start u stop u} will do this.
4307
4308 Some versions of @samp{tcsh} will prevent even this from working. One
4309 way around this is to start another shell before starting rlogin,
4310 and issue the @samp{stty} command to disable flow control from that shell.
4311 @end quotation
4312
4313 Use @samp{stty -ixon} instead of @samp{stty start u stop u} on some systems.
4314
4315 @end itemize
4316
4317 @item
4318 Make Emacs speak the XON/XOFF flow control protocol.
4319
4320 You can make Emacs treat @kbd{C-s} and @kbd{C-q} as flow control characters by
4321 evaluating the form
4322
4323 @lisp
4324 (enable-flow-control)
4325 @end lisp
4326
4327 @noindent
4328 to unconditionally enable flow control or
4329
4330 @lisp
4331 (enable-flow-control-on "vt100" "h19")
4332 @end lisp
4333
4334 @noindent
4335 (using your terminal names instead of @samp{vt100} or @samp{h19}) to
4336 enable selectively. These commands will automatically swap @kbd{C-s}
4337 and @kbd{C-q} to @kbd{C-\} and @kbd{C-^}. Variables can be used to
4338 change the default swap keys (@code{flow-control-c-s-replacement} and
4339 @code{flow-control-c-q-replacement}).
4340
4341 If you are fixing this for yourself, simply put the form in your
4342 @file{.emacs} file. If you are fixing this for your entire site, the
4343 best place to put it is in the @file{site-lisp/site-start.el} file.
4344 (Here @file{site-lisp} is actually a subdirectory of your Emacs
4345 installation directory, typically @file{/usr/local/share/emacs}.)
4346 Putting this form in @file{site-lisp/default.el} has the problem that
4347 if the user's @file{.emacs} file has an error, this will prevent
4348 @file{default.el} from being loaded and Emacs may be unusable for the
4349 user, even for correcting their @file{.emacs} file (unless they're
4350 smart enough to move it to another name).
4351
4352 @code{enable-flow-control} can be invoked interactively as well:
4353 @kbd{M-x enable-flow-control @key{RET}}.
4354
4355 @end itemize
4356
4357 For further discussion of this issue, read the file @file{etc/PROBLEMS}
4358 (in the Emacs source directory when you unpack the Emacs distribution).
4359
4360 @node Binding C-s and C-q, Backspace invokes help, Handling C-s and C-q with flow control, Key bindings
4361 @section How do I bind @kbd{C-s} and @kbd{C-q} (or any key) if these keys are filtered out?
4362 @cindex Binding @kbd{C-s} and @kbd{C-q}
4363 @cindex @kbd{C-s} and @kbd{C-q}, binding
4364
4365 To bind @kbd{C-s} and @kbd{C-q}, use either @code{enable-flow-control}
4366 or @code{enable-flow-control-on}. @xref{Handling C-s and C-q with flow
4367 control}, for usage and implementation details.
4368
4369 To bind other keys, use @code{keyboard-translate}. @xref{Swapping
4370 keys}, for usage details. To do this for an entire site, you should
4371 swap the keys in @file{site-lisp/site-start.el}. @xref{Handling C-s
4372 and C-q with flow control}, for an explanation of why
4373 @file{site-lisp/default.el} should not be used.
4374
4375 @itemize @bullet
4376
4377 @item
4378 If you do this for an entire site, the users will be confused by
4379 the disparity between what the documentation says and how Emacs
4380 actually behaves.
4381
4382 @end itemize
4383
4384 @node Backspace invokes help, stty and Backspace key, Binding C-s and C-q, Key bindings
4385 @section Why does the @key{Backspace} key invoke help?
4386 @cindex Backspace key invokes help
4387 @cindex Help invoked by Backspace
4388 @cindex DEL key does not delete
4389
4390 The @key{Backspace} key (on most keyboards) generates @acronym{ASCII} code 8.
4391 @kbd{C-h} sends the same code. In Emacs by default @kbd{C-h} invokes
4392 help-command. This is intended to be easy to remember since the first
4393 letter of @samp{help} is @samp{h}. The easiest solution to this problem
4394 is to use @kbd{C-h} (and @key{Backspace}) for help and @key{DEL} (the
4395 @key{Delete} key) for deleting the previous character.
4396
4397 For many people this solution may be problematic:
4398
4399 @itemize @bullet
4400
4401 @item
4402 They normally use @key{Backspace} outside of Emacs for deleting the
4403 previous character. This can be solved by making @key{DEL} the command
4404 for deleting the previous character outside of Emacs. On many Unix
4405 systems, this command will remap @key{DEL}:
4406
4407 @example
4408 stty erase `^?'
4409 @end example
4410
4411 @item
4412 The user may prefer the @key{Backspace} key for deleting the
4413 previous character because it is more conveniently located on their
4414 keyboard or because they don't even have a separate @key{Delete} key.
4415 In this case, the @key{Backspace} key should be made to behave like
4416 @key{Delete}. There are several methods.
4417
4418 @itemize @minus
4419 @item
4420 Some terminals (e.g., VT3## terminals) and terminal emulators (e.g.,
4421 TeraTerm) allow the character generated by the @key{Backspace} key to be
4422 changed from a setup menu.
4423
4424 @item
4425 You may be able to get a keyboard that is completely programmable, or a
4426 terminal emulator that supports remapping of any key to any other key.
4427
4428 @item
4429 With Emacs 21.1 and later, you can control the effect of the
4430 @key{Backspace} and @key{Delete} keys, on both dumb terminals and a
4431 windowed displays, by customizing the option
4432 @code{normal-erase-is-backspace-mode}, or by invoking @kbd{M-x
4433 normal-erase-is-backspace}. See the documentation of these symbols
4434 (@pxref{Emacs Lisp documentation}) for more info.
4435
4436 @item
4437 It is possible to swap the @key{Backspace} and @key{DEL} keys inside
4438 Emacs:
4439
4440 @lisp
4441 (keyboard-translate ?\C-h ?\C-?)
4442 @end lisp
4443
4444 @noindent
4445 This is the recommended method of forcing @key{Backspace} to act as
4446 @key{DEL}, because it works even in modes which bind @key{DEL} to
4447 something other than @code{delete-backward-char}.
4448
4449 Similarly, you could remap @key{DEL} to act as @kbd{C-d}, which by
4450 default deletes forward:
4451
4452 @lisp
4453 (keyboard-translate ?\C-? ?\C-d)
4454 @end lisp
4455
4456 @xref{Swapping keys}, for further details about @code{keyboard-translate}.
4457
4458 @item
4459 Another approach is to switch key bindings and put help on @kbd{C-x h}
4460 instead:
4461
4462 @lisp
4463 (global-set-key "\C-h" 'delete-backward-char)
4464
4465 ;;; overrides mark-whole-buffer
4466 (global-set-key "\C-xh" 'help-command)
4467 @end lisp
4468
4469 @noindent
4470 This method is not recommended, though: it only solves the problem for
4471 those modes which bind @key{DEL} to @code{delete-backward-char}. Modes
4472 which bind @key{DEL} to something else, such as @code{view-mode}, will
4473 not work as you expect when you press the @key{Backspace} key. For this
4474 reason, we recommend the @code{keyboard-translate} method, shown
4475 above.
4476
4477 Other popular key bindings for help are @kbd{M-?} and @kbd{C-x ?}.
4478 @end itemize
4479
4480 Don't try to bind @key{DEL} to @code{help-command}, because there are
4481 many modes that have local bindings of @key{DEL} that will interfere.
4482
4483 @end itemize
4484
4485 When Emacs 21 or later runs on a windowed display, it binds the
4486 @key{Delete} key to a command which deletes the character at point, to
4487 make Emacs more consistent with keyboard operation on these systems.
4488
4489 For more information about troubleshooting this problem, see @ref{DEL
4490 Does Not Delete, , If @key{DEL} Fails to Delete, emacs, The GNU Emacs
4491 Manual}.
4492
4493 @node stty and Backspace key, Swapping keys, Backspace invokes help, Key bindings
4494 @section Why doesn't Emacs look at the @file{stty} settings for @key{Backspace} vs. @key{Delete}?
4495 @cindex @file{stty} and Emacs
4496 @cindex Backspace and @file{stty}
4497 @cindex Delete and @file{stty}
4498
4499 Good question!
4500
4501 @c FIXME: RMS explained the reasons for this on emacs-hackers. It's
4502 @c probably worth putting that explanation here.
4503
4504 @node Swapping keys, Producing C-XXX with the keyboard, stty and Backspace key, Key bindings
4505 @section How do I swap two keys?
4506 @cindex Swapping keys
4507 @cindex Keys, swapping
4508 @cindex @code{keyboard-translate}
4509
4510 You can swap two keys (or key sequences) by using the
4511 @code{keyboard-translate} function. For example, to turn @kbd{C-h}
4512 into @key{DEL} and @key{DEL} to @kbd{C-h}, use
4513
4514 @lisp
4515 (keyboard-translate ?\C-h ?\C-?) ; translate `C-h' to DEL
4516 (keyboard-translate ?\C-? ?\C-h) ; translate DEL to `C-h'.
4517 @end lisp
4518
4519 @noindent
4520 The first key sequence of the pair after the function identifies what is
4521 produced by the keyboard; the second, what is matched for in the
4522 keymaps.
4523
4524 However, in the specific case of @kbd{C-h} and @key{DEL}, you should
4525 toggle @code{normal-erase-is-backspace-mode} instead of calling
4526 @code{keyboard-translate}. @inforef{DEL Does Not Delete, DEL Does Not Delete,
4527 emacs}.
4528
4529 Keyboard translations are not the same as key bindings in keymaps.
4530 Emacs contains numerous keymaps that apply in different situations, but
4531 there is only one set of keyboard translations, and it applies to every
4532 character that Emacs reads from the terminal. Keyboard translations
4533 take place at the lowest level of input processing; the keys that are
4534 looked up in keymaps contain the characters that result from keyboard
4535 translation.
4536
4537 @node Producing C-XXX with the keyboard, No Meta key, Swapping keys, Key bindings
4538 @section How do I produce C-XXX with my keyboard?
4539 @cindex Producing control characters
4540 @cindex Generating control characters
4541 @cindex Control characters, generating
4542
4543 On terminals (but not under X), some common ``aliases'' are:
4544
4545 @table @asis
4546
4547 @item @kbd{C-2} or @kbd{C-@key{SPC}}
4548 @kbd{C-@@}
4549
4550 @item @kbd{C-6}
4551 @kbd{C-^}
4552
4553 @item @kbd{C-7} or @kbd{C-S--}
4554 @kbd{C-_}
4555
4556 @item @kbd{C-4}
4557 @kbd{C-\}
4558
4559 @item @kbd{C-5}
4560 @kbd{C-]}
4561
4562 @item @kbd{C-/}
4563 @kbd{C-?}
4564
4565 @end table
4566
4567 Often other aliases exist; use the @kbd{C-h c} command and try
4568 @key{CTRL} with all of the digits on your keyboard to see what gets
4569 generated. You can also try the @kbd{C-h w} command if you know the
4570 name of the command.
4571
4572 @node No Meta key, No Escape key, Producing C-XXX with the keyboard, Key bindings
4573 @section What if I don't have a @key{Meta} key?
4574 @cindex No @key{Meta} key
4575 @cindex @key{Meta} key, what to do if you lack it
4576
4577 On many keyboards, the @key{Alt} key acts as @key{Meta}, so try it.
4578
4579 Instead of typing @kbd{M-a}, you can type @kbd{@key{ESC} a}. In fact,
4580 Emacs converts @kbd{M-a} internally into @kbd{@key{ESC} a} anyway
4581 (depending on the value of @code{meta-prefix-char}). Note that you
4582 press @key{Meta} and @key{a} together, but with @key{ESC}, you press
4583 @key{ESC}, release it, and then press @key{a}.
4584
4585 @node No Escape key, Compose Character, No Meta key, Key bindings
4586 @section What if I don't have an @key{Escape} key?
4587 @cindex No Escape key
4588 @cindex Lacking an Escape key
4589 @cindex Escape key, lacking
4590
4591 Type @kbd{C-[} instead. This should send @acronym{ASCII} code 27 just like an
4592 Escape key would. @kbd{C-3} may also work on some terminal (but not
4593 under X). For many terminals (notably DEC terminals) @key{F11}
4594 generates @key{ESC}. If not, the following form can be used to bind it:
4595
4596 @lisp
4597 ;;; F11 is the documented ESC replacement on DEC terminals.
4598 (define-key function-key-map [f11] [?\e])
4599 @end lisp
4600
4601 @node Compose Character, Binding combinations of modifiers and function keys, No Escape key, Key bindings
4602 @section Can I make my @key{Compose Character} key behave like a @key{Meta} key?
4603 @cindex @key{Compose Character} key, using as @key{Meta}
4604 @cindex @key{Meta}, using @key{Compose Character} for
4605
4606 On a dumb terminal such as a VT220, no. It is rumored that certain
4607 VT220 clones could have their @key{Compose} key configured this way. If
4608 you're using X, you might be able to do this with the @code{xmodmap}
4609 command.
4610
4611 @node Binding combinations of modifiers and function keys, Meta key does not work in xterm, Compose Character, Key bindings
4612 @section How do I bind a combination of modifier key and function key?
4613 @cindex Modifiers and function keys
4614 @cindex Function keys and modifiers
4615 @cindex Binding modifiers and function keys
4616
4617 With Emacs 19 and later, you can represent modified function keys in
4618 vector format by adding prefixes to the function key symbol. For
4619 example (from the on-line documentation):
4620
4621 @lisp
4622 (global-set-key [?\C-x right] 'forward-page)
4623 @end lisp
4624
4625 @noindent
4626 where @samp{?\C-x} is the Lisp character constant for the character @kbd{C-x}.
4627
4628 You can use the modifier keys @key{Control}, @key{Meta}, @key{Hyper},
4629 @key{Super}, @key{Alt}, and @key{Shift} with function keys. To
4630 represent these modifiers, prepend the strings @samp{C-}, @samp{M-},
4631 @samp{H-}, @samp{s-}, @samp{A-}, and @samp{S-} to the symbol name. Here
4632 is how to make @kbd{H-M-RIGHT} move forward a word:
4633
4634 @lisp
4635 (global-set-key [H-M-right] 'forward-word)
4636 @end lisp
4637
4638 @itemize @bullet
4639
4640 @item
4641 Not all modifiers are permitted in all situations. @key{Hyper},
4642 @key{Super}, and @key{Alt} are not available on Unix character
4643 terminals. Non-@acronym{ASCII} keys and mouse events (e.g. @kbd{C-=} and
4644 @kbd{Mouse-1}) also fall under this category.
4645
4646 @end itemize
4647
4648 @xref{Binding keys to commands}, for general key binding instructions.
4649
4650 @node Meta key does not work in xterm, ExtendChar key does not work as Meta, Binding combinations of modifiers and function keys, Key bindings
4651 @section Why doesn't my @key{Meta} key work in an @code{xterm} window?
4652 @cindex @key{Meta} key and @code{xterm}
4653 @cindex Xterm and @key{Meta} key
4654
4655 @inforef{Single-Byte Character Support, Single-Byte Character Set
4656 Support, emacs}.
4657
4658 If the advice in the Emacs manual fails, try all of these methods before
4659 asking for further help:
4660
4661 @itemize @bullet
4662
4663 @item
4664 You may have big problems using @code{mwm} as your window manager.
4665 (Does anyone know a good generic solution to allow the use of the
4666 @key{Meta} key in Emacs with @file{mwm}?)
4667
4668 @item
4669 For X11: Make sure it really is a @key{Meta} key. Use @code{xev} to
4670 find out what keysym your @key{Meta} key generates. It should be either
4671 @code{Meta_L} or @code{Meta_R}. If it isn't, use @file{xmodmap} to fix
4672 the situation. If @key{Meta} does generate @code{Meta_L} or
4673 @code{Meta_R}, but @kbd{M-x} produces a non-@acronym{ASCII} character, put this in
4674 your @file{~/.Xdefaults} file:
4675
4676 @example
4677 XTerm*eightBitInput: false
4678 XTerm*eightBitOutput: true
4679 @end example
4680
4681 @item
4682 Make sure the @code{pty} the @code{xterm} is using is passing 8 bit
4683 characters. @samp{stty -a} (or @samp{stty everything}) should show
4684 @samp{cs8} somewhere. If it shows @samp{cs7} instead, use @samp{stty
4685 cs8 -istrip} (or @samp{stty pass8}) to fix it.
4686
4687 @item
4688 If there is an @code{rlogin} connection between @code{xterm} and Emacs, the
4689 @samp{-8} argument may need to be given to rlogin to make it pass all 8 bits
4690 of every character.
4691
4692 @item
4693 If Emacs is running on Ultrix, it is reported that evaluating
4694 @code{(set-input-mode t nil)} helps.
4695
4696 @item
4697 If all else fails, you can make @code{xterm} generate @kbd{@key{ESC} W} when
4698 you type @kbd{M-W}, which is the same conversion Emacs would make if it
4699 got the @kbd{M-W} anyway. In X11R4, the following resource
4700 specification will do this:
4701
4702 @example
4703 XTerm.VT100.EightBitInput: false
4704 @end example
4705
4706 @noindent
4707 (This changes the behavior of the @code{insert-eight-bit} action.)
4708
4709 With older @code{xterm}s, you can specify this behavior with a translation:
4710
4711 @example
4712 XTerm.VT100.Translations: #override \
4713 Meta<KeyPress>: string(0x1b) insert()
4714 @end example
4715
4716 @noindent
4717 You might have to replace @samp{Meta} with @samp{Alt}.
4718
4719 @end itemize
4720
4721 @node ExtendChar key does not work as Meta, SPC no longer completes file names, Meta key does not work in xterm, Key bindings
4722 @section Why doesn't my @key{ExtendChar} key work as a @key{Meta} key under HP-UX 8.0 and 9.x?
4723 @cindex @key{ExtendChar} key as @key{Meta}
4724 @cindex @key{Meta}, using @key{ExtendChar} for
4725 @cindex HP-UX, the @key{ExtendChar} key
4726
4727 This is a result of an internationalization extension in X11R4 and the
4728 fact that HP is now using this extension. Emacs assumes that the
4729 @code{XLookupString} function returns the same result regardless of the
4730 @key{Meta} key state which is no longer necessarily true. Until Emacs
4731 is fixed, the temporary kludge is to run this command after each time
4732 the X server is started but preferably before any xterm clients are:
4733
4734 @example
4735 xmodmap -e 'remove mod1 = Mode_switch'
4736 @end example
4737
4738 @c FIXME: Emacs 21 supports I18N in X11; does that mean that this bug is
4739 @c solved?
4740
4741 This will disable the use of the extra keysyms systemwide, which may be
4742 undesirable if you actually intend to use them.
4743
4744 @node SPC no longer completes file names, , ExtendChar key does not work as Meta, Key bindings
4745 @section Why doesn't SPC complete file names anymore?
4746 @cindex @kbd{SPC} file name completion
4747
4748 Starting with Emacs 22.1, @kbd{SPC} no longer completes file names in
4749 the minibuffer, so that file names with embedded spaces could be typed
4750 without the need to quote the spaces.
4751
4752 You can get the old behavior by binding @kbd{SPC} to
4753 @code{minibuffer-complete-word} in the minibuffer, as follows:
4754
4755 @lisp
4756 (define-key minibuffer-local-filename-completion-map (kbd "SPC")
4757 'minibuffer-complete-word)
4758
4759 (define-key minibuffer-local-must-match-filename-map (kbd "SPC")
4760 'minibuffer-complete-word)
4761 @end lisp
4762
4763 @c ------------------------------------------------------------
4764 @node Alternate character sets, Mail and news, Key bindings, Top
4765 @chapter Alternate character sets
4766 @cindex Alternate character sets
4767
4768 @menu
4769 * Emacs does not display 8-bit characters::
4770 * Inputting eight-bit characters::
4771 * Kanji and Chinese characters::
4772 * Right-to-left alphabets::
4773 @end menu
4774
4775 @node Emacs does not display 8-bit characters, Inputting eight-bit characters, Alternate character sets, Alternate character sets
4776 @section How do I make Emacs display 8-bit characters?
4777 @cindex Displaying eight-bit characters
4778 @cindex Eight-bit characters, displaying
4779
4780 @inforef{Single-Byte Character Support, Single-byte Character Set
4781 Support, emacs}. On a Unix, when Emacs runs on a text-only terminal
4782 display or is invoked with @samp{emacs -nw}, you typically need to use
4783 @code{set-terminal-coding-system} to tell Emacs what the terminal can
4784 display, even after setting the language environment; otherwise
4785 non-@acronym{ASCII} characters will display as @samp{?}. On other operating
4786 systems, such as MS-DOS and MS-Windows, Emacs queries the OS about the
4787 character set supported by the display, and sets up the required
4788 terminal coding system automatically.
4789
4790 @node Inputting eight-bit characters, Kanji and Chinese characters, Emacs does not display 8-bit characters, Alternate character sets
4791 @section How do I input eight-bit characters?
4792 @cindex Entering eight-bit characters
4793 @cindex Eight-bit characters, entering
4794 @cindex Input, 8-bit characters
4795
4796 Various methods are available for input of eight-bit characters. See
4797 @inforef{Single-Byte Character Support, Single-byte Character Set
4798 Support, emacs}. For more sophisticated methods, @inforef{Input
4799 Methods, Input Methods, emacs}.
4800
4801 @node Kanji and Chinese characters, Right-to-left alphabets, Inputting eight-bit characters, Alternate character sets
4802 @section Where can I get an Emacs that handles kanji, Chinese, or other Far-Eastern character sets?
4803 @cindex Kanji, handling with Emacs
4804 @cindex Chinese, handling with Emacs
4805 @cindex Japanese, handling with Emacs
4806 @cindex Korean, handling with Emacs
4807
4808 Emacs 20 and later includes many of the features of MULE, the MULtilingual
4809 Enhancement to Emacs. @xref{Installing Emacs}, for information on where
4810 to find and download the latest version of Emacs.
4811
4812 @node Right-to-left alphabets, , Kanji and Chinese characters, Alternate character sets
4813 @section Where is an Emacs that can handle Semitic (right-to-left) alphabets?
4814 @cindex Right-to-left alphabets
4815 @cindex Hebrew, handling with Emacs
4816 @cindex Semitic alphabets
4817 @cindex Arabic alphabets
4818
4819 Emacs 20 and later supports Hebrew characters (ISO 8859-8), but does not
4820 yet support right-to-left character entry and display.
4821
4822 @email{joel@@exc.com, Joel M. Hoffman} has written a Lisp package called
4823 @file{hebrew.el} that allows right-to-left editing of Hebrew. It
4824 reportedly works out of the box with Emacs 19, but requires patches for
4825 Emacs 18. Write to Joel if you want the patches or package.
4826
4827 @c FIXME: Should we mention Ehud Karni's package?
4828
4829 @file{hebrew.el} requires a Hebrew screen font, but no other hardware support.
4830 Joel has a screen font for PCs running MS-DOS or GNU/Linux.
4831
4832 You might also try to query archie for files named with @file{hebrew};
4833 several ftp sites in Israel may also have the necessary files.
4834
4835 @c ------------------------------------------------------------
4836 @node Mail and news, Concept index, Alternate character sets, Top
4837 @chapter Mail and news
4838 @cindex Mail and news
4839
4840 @menu
4841 * Changing the included text prefix::
4842 * Saving a copy of outgoing mail::
4843 * Expanding aliases when sending mail::
4844 * Rmail thinks all messages are one big one::
4845 * Sorting the messages in an Rmail folder::
4846 * Rmail writes to /usr/spool/mail::
4847 * Recovering mail files when Rmail munges them::
4848 * Replying to the sender of a message::
4849 * MIME with Emacs mail packages::
4850 * Automatically starting a mail or news reader::
4851 * Reading news with Emacs::
4852 * Gnus does not work with NNTP::
4853 * Viewing articles with embedded underlining::
4854 * Saving a multi-part Gnus posting::
4855 * Starting Gnus faster::
4856 * Catching up in all newsgroups::
4857 * Killing based on nonstandard headers::
4858 * Removing flashing messages::
4859 * Catch-up is slow in Gnus::
4860 * Gnus hangs for a long time::
4861 * Learning more about Gnus::
4862 @end menu
4863
4864 @node Changing the included text prefix, Saving a copy of outgoing mail, Mail and news, Mail and news
4865 @section How do I change the included text prefix in mail/news followups?
4866 @cindex Prefix in mail/news followups, changing
4867 @cindex Included text prefix, changing
4868 @cindex Setting the included text character
4869 @cindex Quoting in mail messages
4870
4871 If you read mail with Rmail or news with Gnus, set the variable
4872 @code{mail-yank-prefix}. For VM, set @code{vm-included-text-prefix}.
4873 For mh-e, set @code{mh-ins-buf-prefix}.
4874
4875 For fancier control of citations, use Supercite. @xref{Supercite}.
4876
4877 To prevent Emacs from including various headers of the replied-to
4878 message, set the value of @code{mail-yank-ignored-headers} to an
4879 appropriate regexp.
4880
4881 @node Saving a copy of outgoing mail, Expanding aliases when sending mail, Changing the included text prefix, Mail and news
4882 @section How do I save a copy of outgoing mail?
4883 @cindex Saving a copy of outgoing mail
4884 @cindex Copying outgoing mail to a file
4885 @cindex Filing outgoing mail
4886 @cindex Automatic filing of outgoing mail
4887 @cindex Mail, saving outgoing automatically
4888
4889 You can either mail yourself a copy by including a @samp{BCC} header in the
4890 mail message, or store a copy of the message directly to a file by
4891 including an @samp{FCC} header.
4892
4893 If you use standard mail, you can automatically create a @samp{BCC} to
4894 yourself by putting
4895
4896 @lisp
4897 (setq mail-self-blind t)
4898 @end lisp
4899
4900 @noindent
4901 in your @file{.emacs} file. You can automatically include an @samp{FCC}
4902 field by putting something like the following in your @file{.emacs}
4903 file:
4904
4905 @lisp
4906 (setq mail-archive-file-name (expand-file-name "~/outgoing"))
4907 @end lisp
4908
4909 The output file will be in Unix mail format, which can be read directly
4910 by VM, but not always by Rmail. @xref{Learning how to do something}.
4911
4912 If you use @code{mh-e}, add an @samp{FCC} or @samp{BCC} field to your
4913 components file.
4914
4915 It does not work to put @samp{set record filename} in the @file{.mailrc}
4916 file.
4917
4918 @node Expanding aliases when sending mail, Rmail thinks all messages are one big one, Saving a copy of outgoing mail, Mail and news
4919 @section Why doesn't Emacs expand my aliases when sending mail?
4920 @cindex Expanding aliases when sending mail
4921 @cindex Mail alias expansion
4922 @cindex Sending mail with aliases
4923
4924 @itemize @bullet
4925
4926 @item
4927 You must separate multiple addresses in the headers of the mail buffer
4928 with commas. This is because Emacs supports RFC822 standard addresses
4929 like this one:
4930
4931 @example
4932 To: Willy Smith <wks@@xpnsv.lwyrs.com>
4933 @end example
4934
4935 However, you do not need to---and probably should not, unless your
4936 system's version of @file{/usr/ucb/mail} (a.k.a.@: @code{mailx})
4937 supports RFC822---separate addresses with commas in your
4938 @file{~/.mailrc} file.
4939
4940 @item
4941 Emacs normally only reads the @file{.mailrc} file once per session,
4942 when you start to compose your first mail message. If you edit
4943 @file{.mailrc}, you can type @kbd{M-x rebuild-mail-abbrevs @key{RET}} to
4944 make Emacs reread @file{~/.mailrc}.
4945
4946 @item
4947 If you like, you can expand mail aliases as abbrevs, as soon as you
4948 type them in. To enable this feature, execute the following:
4949
4950 @lisp
4951 (add-hook 'mail-mode-hook 'mail-abbrevs-setup)
4952 @end lisp
4953
4954 Note that the aliases are expanded automatically only after you type
4955 @key{RET} or a punctuation character (e.g. @kbd{,}). You can force their
4956 expansion by moving point to the end of the alias and typing @kbd{C-x a e}
4957 (@kbd{M-x expand-abbrev}).
4958 @end itemize
4959
4960 @node Rmail thinks all messages are one big one, Sorting the messages in an Rmail folder, Expanding aliases when sending mail, Mail and news
4961 @section Why does Rmail think all my saved messages are one big message?
4962 @cindex Rmail thinks all messages are one large message
4963
4964 A file created through the @samp{FCC} field in a message is in Unix mail
4965 format, not the format that Rmail uses (BABYL format). Rmail will try
4966 to convert a Unix mail file into BABYL format on input, but sometimes it
4967 makes errors. For guaranteed safety, you can make the
4968 @file{saved-messages} file be an inbox for your Rmail file by using the
4969 function @code{set-rmail-inbox-list}.
4970
4971 @node Sorting the messages in an Rmail folder, Rmail writes to /usr/spool/mail, Rmail thinks all messages are one big one, Mail and news
4972 @section How can I sort the messages in my Rmail folder?
4973 @cindex Rmail, sorting messages in
4974 @cindex Folder, sorting messages in an Rmail
4975 @cindex Sorting messages in an Rmail folder
4976
4977 In Rmail, type @kbd{C-c C-s C-h} to get a list of sorting functions
4978 and their key bindings.
4979
4980 @node Rmail writes to /usr/spool/mail, Recovering mail files when Rmail munges them, Sorting the messages in an Rmail folder, Mail and news
4981 @section Why does Rmail need to write to @file{/usr/spool/mail}?
4982 @cindex Rmail and @file{/usr/spool/mail}
4983 @cindex @file{/usr/spool/mail} and Rmail
4984
4985 This is the behavior of the @code{movemail} program which Rmail uses.
4986 This indicates that @code{movemail} is configured to use lock files.
4987
4988 RMS writes:
4989
4990 @quotation
4991 Certain systems require lock files to interlock access to mail files.
4992 On these systems, @code{movemail} must write lock files, or you risk losing
4993 mail. You simply must arrange to let @code{movemail} write them.
4994
4995 Other systems use the @code{flock} system call to interlock access. On
4996 these systems, you should configure @code{movemail} to use @code{flock}.
4997 @end quotation
4998
4999 @node Recovering mail files when Rmail munges them, Replying to the sender of a message, Rmail writes to /usr/spool/mail, Mail and news
5000 @section How do I recover my mail files after Rmail munges their format?
5001 @cindex Recovering munged mail files
5002 @cindex Rmail munged my files
5003 @cindex Mail files, recovering those munged by Rmail
5004
5005 If you have just done @kbd{M-x rmail-input} on a file and you don't want
5006 to save it in Rmail's format (called BABYL), just kill the buffer (with
5007 @kbd{C-x k}).
5008
5009 @cindex Exporting messages as Unix mail files
5010 If you typed @kbd{M-x rmail} and it read some messages out of your inbox
5011 and you want to put them in a Unix mail file, use @kbd{C-o} on each
5012 message.
5013
5014 @cindex Converting from BABYL to Unix mail format
5015 @cindex @code{unrmail} command
5016 If you want to convert an existing file from BABYL format to Unix mail
5017 format, use the command @kbd{M-x unrmail}: it will prompt you for the
5018 input and output file names.
5019
5020 @pindex b2m
5021 Alternatively, you could use the @code{b2m} program supplied with
5022 Emacs. @code{b2m} is a filter, and is used like this:
5023
5024 @example
5025 b2m < @var{babyl-file} > @var{mbox-file}
5026 @end example
5027
5028 @noindent
5029 where @var{babyl-file} is the name of the BABYL file, and
5030 @var{mbox-file} is the name of the file where the converted mail will
5031 be written.
5032
5033 @node Replying to the sender of a message, MIME with Emacs mail packages, Recovering mail files when Rmail munges them, Mail and news
5034 @section How can I force Rmail to reply to the sender of a message, but not the other recipients?
5035 @cindex Replying only to the sender of a message
5036 @cindex Sender, replying only to
5037 @cindex Rmail, replying to the sender of a message in
5038
5039 @email{isaacson@@seas.upenn.edu, Ron Isaacson} says: When you hit
5040 @key{r} to reply in Rmail, by default it CCs all of the original
5041 recipients (everyone on the original @samp{To} and @samp{CC}
5042 lists). With a prefix argument (i.e., typing @kbd{C-u} before @key{r}),
5043 it replies only to the sender. However, going through the whole
5044 @kbd{C-u} business every time you want to reply is a pain. This is the
5045 best fix I've been able to come up with:
5046
5047 @lisp
5048 (defun rmail-reply-t ()
5049 "Reply only to the sender of the current message. (See rmail-reply.)"
5050 (interactive)
5051 (rmail-reply t))
5052
5053 (add-hook 'rmail-mode-hook
5054 (lambda ()
5055 (define-key rmail-mode-map "r" 'rmail-reply-t)
5056 (define-key rmail-mode-map "R" 'rmail-reply)))
5057 @end lisp
5058
5059 @node MIME with Emacs mail packages, Automatically starting a mail or news reader, Replying to the sender of a message, Mail and news
5060 @section How can I get my favorite Emacs mail package to support MIME?
5061 @cindex MIME and Emacs mail packages
5062 @cindex Mail packages and MIME
5063 @cindex FAQ for MIME and Emacs
5064
5065 Version 6.x of VM supports MIME. @xref{VM}. Gnus supports MIME in mail
5066 and news messages as of version 5.8.1 (Pterodactyl). Rmail has limited
5067 support for single-part MIME messages beginning with Emacs 20.3.
5068
5069 @node Automatically starting a mail or news reader, Reading news with Emacs, MIME with Emacs mail packages, Mail and news
5070 @section How do I make Emacs automatically start my mail/news reader?
5071 @cindex Mail reader, starting automatically
5072 @cindex News reader, starting automatically
5073 @cindex Starting mail/news reader automatically
5074
5075 To start Emacs in Gnus:
5076
5077 @example
5078 emacs -f gnus
5079 @end example
5080
5081 @noindent
5082 in Rmail:
5083
5084 @example
5085 emacs -f rmail
5086 @end example
5087
5088 A more convenient way to start with Gnus:
5089
5090 @example
5091 alias gnus 'emacs -f gnus'
5092 gnus
5093 @end example
5094
5095 It is probably unwise to automatically start your mail or news reader
5096 from your @file{.emacs} file. This would cause problems if you needed to run
5097 two copies of Emacs at the same time. Also, this would make it difficult for
5098 you to start Emacs quickly when you needed to.
5099
5100 @node Reading news with Emacs, Gnus does not work with NNTP, Automatically starting a mail or news reader, Mail and news
5101 @section How do I read news under Emacs?
5102 @cindex Reading news under Emacs
5103 @cindex Usenet reader in Emacs
5104 @cindex Gnus newsreader
5105
5106 Use @kbd{M-x gnus}. It is documented in Info (@pxref{Learning how to do
5107 something}).
5108
5109 @node Gnus does not work with NNTP, Viewing articles with embedded underlining, Reading news with Emacs, Mail and news
5110 @section Why doesn't Gnus work via NNTP?
5111 @cindex Gnus and NNTP
5112 @cindex NNTP, Gnus fails to work with
5113
5114 There is a bug in NNTP version 1.5.10, such that when multiple requests
5115 are sent to the NNTP server, the server only handles the first one
5116 before blocking waiting for more input which never comes. NNTP version
5117 1.5.11 claims to fix this.
5118
5119 You can work around the bug inside Emacs like this:
5120
5121 @lisp
5122 (setq nntp-maximum-request 1)
5123 @end lisp
5124
5125 You can find out what version of NNTP your news server is running by
5126 telnetting to the NNTP port (usually 119) on the news server machine
5127 (i.e., @kbd{telnet server-machine 119}). The server should give its
5128 version number in the welcome message. Type @kbd{quit} to get out.
5129
5130 @xref{Spontaneous entry into isearch-mode}, for some additional ideas.
5131
5132 @node Viewing articles with embedded underlining, Saving a multi-part Gnus posting, Gnus does not work with NNTP, Mail and news
5133 @section How do I view news articles with embedded underlining (e.g., ClariNews)?
5134 @cindex Underlining, embedded in news articles
5135 @cindex News articles with embedded underlining
5136 @cindex Embedded underlining in news articles
5137
5138 Underlining appears like this:
5139
5140 @example
5141 _^Hu_^Hn_^Hd_^He_^Hr_^Hl_^Hi_^Hn_^Hi_^Hn_^Hg
5142 @end example
5143
5144 @email{abraham@@dina.kvl.dk, Per Abrahamsen} suggests using the following
5145 code, which uses the underline face to turn such text into true
5146 underlining, inconjunction with Gnus:
5147
5148 @lisp
5149 (defun gnus-article-prepare-overstrike ()
5150 ;; Prepare article for overstrike commands.
5151 (save-excursion
5152 (set-buffer gnus-article-buffer)
5153 (let ((buffer-read-only nil))
5154 (goto-char (point-min))
5155 (while (search-forward "\b" nil t)
5156 (let ((next (following-char))
5157 (previous (char-after (- (point) 2))))
5158 (cond ((eq next previous)
5159 (delete-region (- (point) 2) (point))
5160 (put-text-property (point) (1+ (point))
5161 'face 'bold))
5162 ((eq next ?_)
5163 (delete-region (1- (point)) (1+ (point)))
5164 (put-text-property (1- (point)) (point)
5165 'face 'underline))
5166 ((eq previous ?_)
5167 (delete-region (- (point) 2) (point))
5168 (put-text-property (point) (1+ (point))
5169 'face 'underline))))))))
5170
5171 (add-hook 'gnus-article-prepare-hook 'gnus-article-prepare-overstrike)
5172 @end lisp
5173
5174 Latest versions of Gnus do such a conversion automatically.
5175
5176 If you prefer to do away with underlining altogether, you can
5177 destructively remove it with @kbd{M-x ununderline-region}; do this
5178 automatically via
5179
5180 @lisp
5181 (add-hook 'gnus-article-prepare-hook
5182 (lambda () (ununderline-region (point-min) (point-max))))
5183 @end lisp
5184
5185 @node Saving a multi-part Gnus posting, Starting Gnus faster, Viewing articles with embedded underlining, Mail and news
5186 @section How do I save all the items of a multi-part posting in Gnus?
5187 @cindex Multi-part postings in Gnus, saving
5188 @cindex Saving multi-part postings in Gnus
5189 @cindex Gnus, saving multi-part postings in
5190
5191 Use @code{gnus-uu}. Type @kbd{C-c C-v C-h} in the Gnus summary buffer
5192 to see a list of available commands.
5193
5194 @node Starting Gnus faster, Catching up in all newsgroups, Saving a multi-part Gnus posting, Mail and news
5195 @section How do I make Gnus start up faster?
5196 @cindex Faster, starting Gnus
5197 @cindex Starting Gnus faster
5198 @cindex Gnus, starting faster
5199
5200 From the Gnus FAQ (@pxref{Learning more about Gnus}):
5201
5202 @quotation
5203 @email{pktiwari@@eos.ncsu.edu, Pranav Kumar Tiwari} writes: I posted
5204 the same query recently and I got an answer to it. I am going to
5205 repeat the answer. What you need is a newer version of gnus, version
5206 5.0.4+. I am using 5.0.12 and it works fine with me with the
5207 following settings:
5208
5209 @lisp
5210 (setq gnus-check-new-newsgroups nil
5211 gnus-read-active-file 'some
5212 gnus-nov-is-evil nil
5213 gnus-select-method '(nntp gnus-nntp-server))
5214 @end lisp
5215 @end quotation
5216
5217 @node Catching up in all newsgroups, Killing based on nonstandard headers, Starting Gnus faster, Mail and news
5218 @section How do I catch up all newsgroups in Gnus?
5219 @cindex Catching up all newsgroups in Gnus
5220 @cindex Gnus, Catching up all newsgroups in
5221
5222 In the @file{*Newsgroup*} buffer, type @kbd{M-< C-x ( c y C-x ) M-0 C-x e}
5223
5224 Leave off the initial @kbd{M-<} if you only want to catch up from point
5225 to the end of the @file{*Newsgroup*} buffer.
5226
5227 @node Killing based on nonstandard headers, Removing flashing messages, Catching up in all newsgroups, Mail and news
5228 @section Why can't I kill in Gnus based on the Newsgroups/Keywords/Control headers?
5229 @cindex Killing articles based on nonstandard headers
5230 @cindex Newsgroups header, killing articles based on
5231 @cindex Keywords header, killing articles based on
5232 @cindex Control header, killing articles based on
5233
5234 Gnus will complain that the @samp{Newsgroups}, @samp{Keywords}, and
5235 @samp{Control} headers are ``Unknown header'' fields.
5236
5237 For the @samp{Newsgroups} header, there is an easy workaround: kill on the
5238 @samp{Xref} header instead, which will be present on any cross-posted article
5239 (as long as your site carries the cross-post group).
5240
5241 If you really want to kill on one of these headers, you can do it like
5242 this:
5243
5244 @lisp
5245 (gnus-kill nil "^Newsgroups: .*\\(bad\\.group\\|worse\\.group\\)")
5246 @end lisp
5247
5248 @node Removing flashing messages, Catch-up is slow in Gnus, Killing based on nonstandard headers, Mail and news
5249 @section How do I get rid of flashing messages in Gnus for slow connections?
5250 @cindex Flashing Gnus messages, removing
5251 @cindex Removing flashing Gnus messages
5252 @cindex Slow connections causing flashing messages in Gnus
5253 @cindex Gnus, flashing messages in
5254
5255 Set @code{nntp-debug-read} to @code{nil}.
5256
5257 @node Catch-up is slow in Gnus, Gnus hangs for a long time, Removing flashing messages, Mail and news
5258 @section Why is catch up slow in Gnus?
5259 @cindex Slow catch up in Gnus
5260 @cindex Gnus is slow when catching up
5261 @cindex Crosspostings make Gnus catching up slow
5262
5263 Because Gnus is marking crosspostings read. You can control this with
5264 the variable @code{gnus-use-cross-reference}.
5265
5266 @node Gnus hangs for a long time, Learning more about Gnus, Catch-up is slow in Gnus, Mail and news
5267 @section Why does Gnus hang for a long time when posting?
5268 @cindex Hangs in Gnus
5269 @cindex Gnus hangs while posting
5270 @cindex Posting, Gnus hangs wile
5271
5272 @email{tale@@uunet.uu.net, David Lawrence} explains:
5273
5274 @quotation
5275 The problem is almost always interaction between NNTP and C News. NNTP
5276 POST asks C News's @code{inews} to not background itself but rather hang
5277 around and give its exit status so it knows whether the post was successful.
5278 (That wait will on some systems not return the exit status of the
5279 waited for job is a different sort of problem.) It ends up taking a
5280 long time because @code{inews} is calling @code{relaynews}, which often
5281 waits for another @code{relaynews} to free the lock on the news system
5282 so it can file the article.
5283
5284 My preferred solution is to change @code{inews} to not call
5285 @code{relaynews}, but rather use @code{newsspool}. This loses some
5286 error-catching functionality, but is for the most part safe as
5287 @code{inews} will detect a lot of the errors on its own. The C News
5288 folks have sped up @code{inews}, too, so speed should look better to
5289 most folks as that update propagates around.
5290 @end quotation
5291
5292 @node Learning more about Gnus, , Gnus hangs for a long time, Mail and news
5293 @section Where can I find out more about Gnus?
5294 @cindex FAQ for Gnus
5295 @cindex Gnus FAQ
5296 @cindex Learning more about Gnus
5297
5298 For more information on Gnus, consult the Gnus manual and FAQ, which are
5299 part of the Gnus distribution.
5300
5301 @node Concept index, , Mail and news, Top
5302 @unnumbered Concept Index
5303 @printindex cp
5304
5305 @contents
5306 @bye
5307
5308 @ignore
5309 arch-tag: fee0d62d-06cf-43d8-ac21-123408eaf10f
5310 @end ignore