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