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