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