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