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