1 \input texinfo @c -*-texinfo-*- -*- coding: latin-1 -*-
3 @setfilename ../info/efaq
4 @settitle GNU Emacs FAQ
9 @c This is used in many places
12 @c The @ifinfo stuff only appears in the Info version
16 * Emacs FAQ: (efaq). Frequently Asked Questions about Emacs.
19 Copyright 1994,1995,1996,1997,1998,1999,2000 Reuven M. Lerner@*
20 Copyright 1992,1993 Steven Byrnes@*
21 Copyright 1990,1991,1992 Joseph Brian Wells@*
23 This list of frequently asked questions about GNU Emacs with answers
24 ("FAQ") may be translated into other languages, transformed into other
25 formats (e.g. Texinfo, Info, WWW, WAIS), and updated with new information.
27 The same conditions apply to any derivative of the FAQ as apply to the FAQ
28 itself. Every copy of the FAQ must include this notice or an approved
29 translation, information on who is currently maintaining the FAQ and how to
30 contact them (including their e-mail address), and information on where the
31 latest version of the FAQ is archived (including FTP information).
33 The FAQ may be copied and redistributed under these conditions, except that
34 the FAQ may not be embedded in a larger literary work unless that work
35 itself allows free copying and redistribution.
37 [This version has been somewhat edited from the last-posted version
38 (as of August 1999) for inclusion in the Emacs distribution.]
42 @c The @titlepage stuff only appears in the printed version
45 @center @titlefont{GNU Emacs FAQ}
47 @c The following two commands start the copyright page.
49 @vskip 0pt plus 1filll
50 Copyright @copyright{} 1994,1995,1996,1997,1998,1999,2000 Reuven M. Lerner@*
51 Copyright @copyright{} 1992,1993 Steven Byrnes@*
52 Copyright @copyright{} 1990,1991,1992 Joseph Brian Wells@*
54 This list of frequently asked questions about GNU Emacs with answers
55 ("FAQ") may be translated into other languages, transformed into other
56 formats (e.g. Texinfo, Info, WWW, WAIS), and updated with new information.
58 The same conditions apply to any derivative of the FAQ as apply to the FAQ
59 itself. Every copy of the FAQ must include this notice or an approved
60 translation, information on who is currently maintaining the FAQ and how to
61 contact them (including their e-mail address), and information on where the
62 latest version of the FAQ is archived (including FTP information).
64 The FAQ may be copied and redistributed under these conditions, except that
65 the FAQ may not be embedded in a larger literary work unless that work
66 itself allows free copying and redistribution.
68 [This version has been somewhat edited from the last-posted version
69 (as of August 1999) for inclusion in the Emacs distribution.]
72 @node Top, FAQ notation, (dir), (dir)
74 This is the GNU Emacs FAQ, last updated on @today{}.
76 The FAQ is maintained as a Texinfo document, allowing us to create HTML,
77 Info, and TeX documents from a single source file, and is slowly but
78 surely being improved. Please bear with us as we improve on this
79 format. If you have any suggestions or questions, please contact
80 @email{emacs-faq@@lerner.co.il, the FAQ maintainers}.
89 * Compiling and installing Emacs::
90 * Finding Emacs and related packages::
91 * Major packages and programs::
93 * Alternate character sets::
98 @c ------------------------------------------------------------
99 @node FAQ notation, General questions, Top, Top
100 @chapter FAQ notation
103 This chapter describes notation used in the GNU Emacs FAQ, as well as in
104 the Emacs documentation. Consult this section if this is the first time
105 you are reading the FAQ, or if you are confused by notation or terms
110 * Extended commands::
112 * File-name conventions::
116 @node Basic keys, Extended commands, FAQ notation, FAQ notation
117 @section What do these mean: @kbd{C-h}, @kbd{M-C-a}, @key{RET}, @kbd{@key{ESC} a}, etc.?
119 @cindex Control key, notation for
120 @cindex @key{Meta} key, notation for
121 @cindex Control-Meta characters, notation for
122 @cindex @kbd{C-h}, definition of
123 @cindex @kbd{M-C-h}, definition of
124 @cindex @key{DEL}, definition of
125 @cindex @key{ESC}, definition of
126 @cindex @key{LFD}, definition of
127 @cindex @key{RET}, definition of
128 @cindex @key{SPC}, definition of
129 @cindex @key{TAB}, definition of
130 @cindex Notation for keys
135 @kbd{C-x}: press the @key{x} key while holding down the @key{Control} key
138 @kbd{M-x}: press the @key{x} key while holding down the @key{Meta} key
139 (if your computer doesn't have a @key{Meta} key, @pxref{No Meta key})
142 @kbd{M-C-x}: press the @key{x} key while holding down both @key{Control}
146 @kbd{C-M-x}: a synonym for the above
149 @key{LFD}: Linefeed or Newline; same as @kbd{C-j}
152 @key{RET}: @key{Return}, sometimes marked @key{Enter}; same as @kbd{C-m}
155 @key{DEL}: @key{Delete}, usually @strong{not} the same as
156 @key{Backspace}; same as @kbd{C-?} (see @ref{Backspace invokes help}, if
157 deleting invokes Emacs help)
160 @key{ESC}: Escape; same as @kbd{C-[}
163 @key{TAB}: Tab; same as @kbd{C-i}
170 Key sequences longer than one key (and some single-key sequences) are
171 written inside quotes or on lines by themselves, like this:
174 @kbd{M-x frobnicate-while-foo RET}
178 Any real spaces in such a key sequence should be ignored; only @key{SPC}
179 really means press the space key.
181 The ASCII code sent by @kbd{C-x} (except for @kbd{C-?}) is the value
182 that would be sent by pressing just @key{x} minus 96 (or 64 for
183 upper-case @key{X}) and will be from 0 to 31. On Unix and GNU/Linux
184 terminals, the ASCII code sent by @kbd{M-x} is the sum of 128 and the
185 ASCII code that would be sent by pressing just @key{x}. Essentially,
186 @key{Control} turns off bits 5 and 6 and @key{Meta} turns on bit
188 DOS and Windows terminals don't set bit 7 when the @key{Meta} key is
191 @kbd{C-?} (aka @key{DEL}) is ASCII code 127. It is a misnomer to call
192 @kbd{C-?} a ``control'' key, since 127 has both bits 5 and 6 turned ON.
193 Also, on very few keyboards does @kbd{C-?} generate ASCII code 127.
195 @inforef{Text Characters, Text Characters, emacs}, and @inforef{Keys,
196 Keys, emacs}, for more information. (@xref{On-line manual}, for more
197 information about Info.)
199 @node Extended commands, On-line manual, Basic keys, FAQ notation
200 @section What does @file{M-x @var{command}} mean?
201 @cindex Extended commands
202 @cindex Commands, extended
203 @cindex M-x, meaning of
205 @kbd{M-x @var{command}} means type @kbd{M-x}, then type the name of the
206 command, then type @key{RET}. (@xref{Basic keys}, if you're not sure
207 what @kbd{M-x} and @key{RET} mean.)
209 @kbd{M-x} (by default) invokes the command
210 @code{execute-extended-command}. This command allows you to run any
211 Emacs command if you can remember the command's name. If you can't
212 remember the command's name, you can type @key{TAB} and @key{SPC} for
213 completion, @key{?} for a list of possibilities, and @kbd{M-p} and
214 @kbd{M-n} (or up-arrow and down-arrow on terminals that have these
215 editing keys) to see previous commands entered. An Emacs @dfn{command}
216 is an @dfn{interactive} Emacs function.
219 Your system administrator may have bound other key sequences to invoke
220 @code{execute-extended-command}. A function key labeled @kbd{Do} is a
221 good candidate for this, on keyboards that have such a key.
223 If you need to run non-interactive Emacs functions, see @ref{Evaluating
226 @node On-line manual, File-name conventions, Extended commands, FAQ notation
227 @section How do I read topic XXX in the on-line manual?
228 @cindex On-line manual, reading topics in
229 @cindex Reading topics in the on-line manual
230 @cindex Finding topics in the on-line manual
231 @cindex Info, finding topics in
233 When we refer you to some @var{topic} in the on-line manual, you can
234 read this manual node inside Emacs (assuming nothing is broken) by
235 typing @kbd{C-h i m emacs @key{RET} m @var{topic} @key{RET}}.
237 This invokes Info, the GNU hypertext documentation browser. If you don't
238 already know how to use Info, type @key{?} from within Info.
240 If we refer to @var{topic}:@var{subtopic}, type @kbd{C-h i m emacs
241 @key{RET} m @var{topic} @key{RET} m @var{subtopic} @key{RET}}.
243 If these commands don't work as expected, your system administrator may
244 not have installed the Info files, or may have installed them
245 improperly. In this case you should complain.
247 @xref{Getting a printed manual}, if you would like a paper copy of the
250 @node File-name conventions, Common acronyms, On-line manual, FAQ notation
251 @section What are @file{etc/SERVICE}, @file{src/config.h}, and @file{lisp/default.el}?
252 @cindex File-name conventions
253 @cindex Conventions for file names
254 @cindex Directories and files that come with Emacs
256 These are files that come with Emacs. The Emacs distribution is divided
257 into subdirectories; the important ones are @file{etc}, @file{lisp}, and
260 If you use Emacs, but don't know where it is kept on your system, start
261 Emacs, then type @kbd{C-h v data-directory @key{RET}}. The directory
262 name displayed by this will be the full pathname of the installed
263 @file{etc} directory. (This full path is recorded in the Emacs variable
264 @code{data-directory}, and @kbd{C-h v} displays the value and the
265 documentation of a variable.)
267 The location of your Info directory (i.e., where on-line documentation
268 is stored) is kept in the variable @code{Info-default-directory-list}. Use
269 @kbd{C-h v Info-default-directory-list @key{RET}} to see the value of
270 this variable, which will be a list of directory names. The last
271 directory in that list is probably where most Info files are stored. By
272 default, Info documentation is placed in @file{/usr/local/info}.
274 Some of these files are available individually via FTP or e-mail; see
275 @ref{Informational files for Emacs}. They all are available in the
276 source distribution. Many of the files in the @file{etc} directory are
277 also available via the Emacs @samp{Help} menu, or by typing @kbd{C-h ?}
278 (@kbd{M-x help-for-help}).
280 Your system administrator may have removed the @file{src} directory and
281 many files from the @file{etc} directory.
283 @node Common acronyms, , File-name conventions, FAQ notation
284 @section What are FSF, LPF, OSF, GNU, RMS, FTP, and GPL?
285 @cindex FSF, definition of
286 @cindex LPF, definition of
287 @cindex OSF, definition of
288 @cindex GNU, definition of
289 @cindex RMS, definition of
290 @cindex Stallman, Richard, acronym for
291 @cindex Richard Stallman, acronym for
292 @cindex FTP, definition of
293 @cindex GPL, definition of
294 @cindex Acronyms, definitions for
295 @cindex Common acronyms, definitions for
300 Free Software Foundation
303 League for Programming Freedom
306 Open Software Foundation
312 Richard Matthew Stallman
315 File Transfer Protocol
318 GNU General Public License
322 Avoid confusing the FSF, the LPF, and the OSF. The LPF opposes
323 look-and-feel copyrights and software patents. The FSF aims to make
324 high quality free software available for everyone. The OSF is a
325 consortium of computer vendors which develops commercial software for
328 The word ``free'' in the title of the Free Software Foundation refers to
329 ``freedom,'' not ``zero dollars.'' Anyone can charge any price for
330 GPL-covered software that they want to. However, in practice, the
331 freedom enforced by the GPL leads to low prices, because you can always
332 get the software for less money from someone else, since everyone has
333 the right to resell or give away GPL-covered software.
335 @c ------------------------------------------------------------
336 @node General questions, Getting help, FAQ notation, Top
337 @chapter General questions
338 @cindex General questions
340 This chapter contains general questions having to do with Emacs, the
341 Free Software Foundation, and related organizations.
345 * Real meaning of copyleft::
346 * Guidelines for newsgroup postings::
347 * Newsgroup archives::
349 * Unsubscribing from Emacs lists::
350 * Contacting the FSF::
353 @node The LPF, Real meaning of copyleft, General questions, General questions
354 @section What is the LPF?
355 @cindex LPF, description of
356 @cindex League for Programming Freedom
357 @cindex Software patents, opposition to
358 @cindex Patents for software, opposition to
360 The LPF opposes the expanding danger of software patents and
361 look-and-feel copyrights. To get more information, feel free to contact
362 the LPF via e-mail or otherwise. You may also contact
363 @email{jbw@@cs.bu.edu, Joe Wells}; he will be happy to talk to you
366 You can find more information about the LPF in the file @file{etc/LPF}.
367 More papers describing the LPF's views are available on the Internet and
368 also from @uref{http://lpf.ai.mit.edu/, the LPF home page}.
370 @node Real meaning of copyleft, Guidelines for newsgroup postings, The LPF, General questions
371 @section What is the real legal meaning of the GNU copyleft?
372 @cindex Copyleft, real meaning of
373 @cindex GPL, real meaning of
374 @cindex General Public License, real meaning of
375 @cindex Discussion of the GPL
377 The real legal meaning of the GNU General Public License (copyleft) will
378 only be known if and when a judge rules on its validity and scope.
379 There has never been a copyright infringement case involving the GPL to
380 set any precedents. Please take any discussion regarding this issue to
381 the newsgroup @uref{news:gnu.misc.discuss}, which was created to hold the
382 extensive flame wars on the subject.
387 The legal meaning of the GNU copyleft is less important than the spirit,
388 which is that Emacs is a free software project and that work pertaining
389 to Emacs should also be free software. ``Free'' means that all users
390 have the freedom to study, share, change and improve Emacs. To make
391 sure everyone has this freedom, pass along source code when you
392 distribute any version of Emacs or a related program, and give the
393 recipients the same freedom that you enjoyed.
396 @node Guidelines for newsgroup postings, Newsgroup archives, Real meaning of copyleft, General questions
397 @section What are appropriate messages for @uref{news:gnu.emacs.help}, @uref{news:gnu.emacs.bug}, @uref{news:comp.emacs}, etc.?
398 @cindex Newsgroups, appropriate messages for
399 @cindex GNU newsgroups, appropriate messages for
400 @cindex Usenet groups, appropriate messages for
401 @cindex Mailing lists, appropriate messages for
402 @cindex Posting messages to newsgroups
404 @cindex GNU mailing lists
405 The file @file{etc/MAILINGLISTS} describes the purpose of each GNU
406 mailing list. (@xref{Informational files for Emacs}, if you want a copy
407 of the file.) For those lists which are gatewayed with newsgroups, it
408 lists both the newsgroup name and the mailing list address.
410 The newsgroup @uref{news:comp.emacs} is for discussion of Emacs programs
411 in general. This includes Emacs along with various other
412 implementations, such as XEmacs, JOVE, MicroEmacs, Freemacs, MG,
413 Unipress, CCA, and Epsilon.
415 Many people post Emacs questions to @uref{news:comp.emacs} because they
416 don't receive any of the @code{gnu.*} newsgroups. Arguments have been
417 made both for and against posting GNU-Emacs-specific material to
418 @uref{news:comp.emacs}. You have to decide for yourself.
420 Messages advocating ``non-free'' software are considered unacceptable on
421 any of the @code{gnu.*} newsgroups except for @uref{news:gnu.misc.discuss},
422 which was created to hold the extensive flame-wars on the subject.
423 ``Non-free'' software includes any software for which the end user can't
424 freely modify the source code and exchange enhancements. Be careful to
425 remove the @code{gnu.*} groups from the @samp{Newsgroups:} line when
426 posting a followup that recommends such software.
428 @uref{news:gnu.emacs.bug} is a place where bug reports appear, but avoid
429 posting bug reports to this newsgroup directly (@pxref{Reporting bugs}).
431 @node Newsgroup archives, Reporting bugs, Guidelines for newsgroup postings, General questions
432 @section Where can I get old postings to @uref{news:gnu.emacs.help} and other GNU groups?
433 @cindex Archived postings from @uref{news:gnu.emacs.help}
434 @cindex Usenet archives for GNU groups
435 @cindex Old Usenet postings for GNU groups
437 The FSF has maintained archives of all of the GNU mailing lists for many
438 years, although there may be some unintentional gaps in coverage. The
439 archive is not particularly well organized or easy to retrieve
440 individual postings from, but pretty much everything is there.
442 The archive is at @uref{ftp://ftp-mailing-list-archives.gnu.org}.
444 As of this writing, the archives are not yet working.
446 Web-based Usenet search services, such as
447 @uref{http://www.dejanews.com, DejaNews}, also archive the
450 @node Reporting bugs, Unsubscribing from Emacs lists, Newsgroup archives, General questions
451 @section Where should I report bugs and other problems with Emacs?
452 @cindex Bug reporting
453 @cindex Good bug reports
454 @cindex How to submit a bug report
455 @cindex Reporting bugs
457 The correct way to report Emacs bugs is by e-mail to
458 @email{bug-gnu-emacs@@gnu.org}. Anything sent here also appears in the
459 newsgroup @uref{news:gnu.emacs.bug}, but please use e-mail instead of
460 news to submit the bug report. This ensures a reliable return address
461 so you can be contacted for further details.
463 Be sure to read the ``Bugs'' section of the Emacs manual before reporting
464 a bug to bug-gnu-emacs! The manual describes in detail how to submit a
465 useful bug report. (@xref{On-line manual}, if you don't know how to read the
471 Sending bug reports to @email{help-gnu-emacs@@gnu.org} (which has the
472 effect of posting on @uref{news:gnu.emacs.help}) is undesirable because
473 it takes the time of an unnecessarily large group of people, most of
474 whom are just users and have no idea how to fix these problem.
475 @email{bug-gnu-emacs@@gnu.org} reaches a much smaller group of people
476 who are more likely to know what to do and have expressed a wish to
477 receive more messages about Emacs than the others.
480 RMS says it is sometimes fine to post to @uref{news:gnu.emacs.help}:
483 If you have reported a bug and you don't hear about a possible fix,
484 then after a suitable delay (such as a week) it is okay to post on
485 @code{gnu.emacs.help} asking if anyone can help you.
488 If you are unsure whether you have found a bug, consider the following
489 non-exhaustive list, courtesy of RMS:
492 If Emacs crashes, that is a bug. If Emacs gets compilation errors
493 while building, that is a bug. If Emacs crashes while building, that
494 is a bug. If Lisp code does not do what the documentation says it
498 @node Unsubscribing from Emacs lists, Contacting the FSF, Reporting bugs, General questions
499 @section How do I unsubscribe from this mailing list?
500 @cindex Unsubscribing from GNU mailing lists
501 @cindex Removing yourself from GNU mailing lists
503 If you are receiving a GNU mailing list named @var{list}, you might be
504 able to unsubscribe from it by sending a request to the address
505 @email{@var{list}-request@@gnu.org}. However, this will not work if you are
506 not listed on the main mailing list, but instead receive the mail from a
507 distribution point. In that case, you will have to track down at which
508 distribution point you are listed. Inspecting the @samp{Received} headers
509 on the mail messages may help, along with liberal use of the @samp{EXPN} or
510 @samp{VRFY} sendmail commands through @samp{telnet @var{site-address}
511 smtp}. Ask your postmaster for help, if you cannot figure out these
514 @node Contacting the FSF, , Unsubscribing from Emacs lists, General questions
515 @section What is the current address of the FSF?
516 @cindex Snail mail address of the FSF
517 @cindex Postal address of the FSF
518 @cindex Contracting the FSF
519 @cindex Free Software Foundation, contacting
533 @uref{http://www.gnu.org/}
536 Free Software Foundation@*
537 59 Temple Place - Suite 330@*
538 Boston, MA 02111-1307@*
543 @cindex Ordering GNU software
544 For details on how to order items directly from the FSF, see the
545 @uref{http://www.gnu.org/order/order.html, GNU Web site}, and also the
546 files @file{etc/ORDERS}, @file{ORDERS.EUROPE}, and @file{ORDERS.JAPAN}.
548 @c ------------------------------------------------------------
549 @node Getting help, Status of Emacs, General questions, Top
550 @chapter Getting help
553 This chapter tells you how to get help with Emacs
557 * Learning how to do something::
558 * Getting a printed manual::
559 * Emacs Lisp documentation::
560 * Installing Texinfo documentation::
561 * Printing a Texinfo file::
562 * Viewing Info files outside of Emacs::
563 * Informational files for Emacs::
564 * Help installing Emacs::
565 * Obtaining the FAQ::
568 @node Basic editing, Learning how to do something, Getting help, Getting help
569 @section I'm just starting Emacs; how do I do basic editing?
570 @cindex Basic editing with Emacs
571 @cindex Beginning editing
572 @cindex Tutorial, invoking the
573 @cindex Self-paced tutorial, invoking the
574 @cindex Help system, entering the
576 Type @kbd{C-h t} to invoke the self-paced tutorial. Just typing @kbd{C-h}
577 enters the help system.
579 Your system administrator may have changed @kbd{C-h} to act like
580 @key{DEL} to deal with local keyboards. You can use @kbd{M-x
581 help-for-help} instead to invoke help. To discover what key (if any)
582 invokes help on your system, type @kbd{M-x where-is @key{RET}
583 help-for-help @key{RET}}. This will print a comma-separated list of key
584 sequences in the echo area. Ignore the last character in each key
585 sequence listed. Each of the resulting key sequences invokes help.
587 Emacs help works best if it is invoked by a single key whose value
588 should be stored in the variable @code{help-char}.
590 There is also a WWW-based tutorial for Emacs 18, much of which is also
591 relevant for later versions of Emacs, available at
593 @uref{http://kufacts.cc.ukans.edu/cwis/writeups/misc/emacsguide.html}
595 @node Learning how to do something, Getting a printed manual, Basic editing, Getting help
596 @section How do I find out how to do something in Emacs?
597 @cindex Help for Emacs
598 @cindex Learning to do something in Emacs
599 @cindex Reference card for Emacs
600 @cindex Overview of help systems
602 There are several methods for finding out how to do things in Emacs.
606 @cindex Reading the Emacs manual
608 The complete text of the Emacs manual is available on-line via the Info
609 hypertext reader. Type @kbd{C-h i} to invoke Info. Typing @key{h}
610 immediately after entering Info will provide a short tutorial on how to
613 @cindex Lookup a subject in a manual
614 @cindex Index search in a manual
616 To quickly locate the section of the manual which discusses a certain
617 issue, or describes a command or a variable, type @kbd{C-h i m emacs
618 @key{RET} i @var{topic} @key{RET}}, where @var{topic} is the name of the
619 topic, the command, or the variable which you are looking for. If this
620 does not land you on the right place in the manual, press @kbd{,}
621 (comma) repeatedly until you find what you need. (The @kbd{i} and
622 @kbd{,} keys invoke the index-searching functions, which look for the
623 @var{topic} you type in all the indices of the Emacs manual.)
627 You can list all of the commands whose names contain a certain word
628 (actually which match a regular expression) using @kbd{C-h a} (@kbd{M-x
631 @cindex Command description in the manual
633 The command @kbd{C-h C-f} (@code{Info-goto-emacs-command-node}) prompts
634 for the name of a command, and then attempts to find the section in the
635 Emacs manual where that command is described.
637 @cindex Finding commands and variables
639 You can list all of the functions and variables whose names contain a
640 certain word using @kbd{M-x apropos}.
643 You can list all of the functions and variables whose documentation
644 matches a regular expression or a string, using @kbd{M-x
645 apropos-documentation}.
648 You can order a hardcopy of the manual from the FSF. @xref{Getting a
651 @cindex Reference cards, in other languages
653 You can get a printed reference card listing commands and keys to
654 invoke them. You can order one from the FSF for $1 (or 10 for $5),
655 or you can print your own from the @file{etc/refcard.tex} or
656 @file{etc/refcard.ps} files in the Emacs distribution. Beginning with
657 version 21.1, the Emacs distribution comes with translations of the
658 reference card into several languages; look for files named
659 @file{etc/@var{lang}-refcard.*}, where @var{lang} is a two-letter code
660 of the language. For example, the German version of the reference card
661 is in the files @file{etc/de-refcard.tex} and @file{etc/de-refcard.ps}.
664 There are many other commands in Emacs for getting help and
665 information. To get a list of these commands, type @samp{?} after
670 @node Getting a printed manual, Emacs Lisp documentation, Learning how to do something, Getting help
671 @section How do I get a printed copy of the Emacs manual?
672 @cindex Printed Emacs manual, obtaining
673 @cindex Manual, obtaining a printed copy of
674 @cindex Emacs manual, obtaining a printed copy of
676 You can order a printed copy of the Emacs manual from the FSF. For
677 details see the @uref{http://www.gnu.org/order/order.html, GNU Web site}
678 and the file @file{etc/ORDERS}.
680 @c The number 620 below is version-dependent!
681 The full Texinfo source for the manual also comes in the @file{man}
682 directory of the Emacs distribution, if you're daring enough to try to
683 print out this 620-page manual yourself (@pxref{Printing a Texinfo
686 If you absolutely have to print your own copy, and you don't have @TeX{},
687 you can get a PostScript version from
689 @uref{http://www.gnu.org/manual/emacs/ps/emacs.ps.gz}
691 An HTML version of the manual is at
693 @uref{www.gnu.org/manual/emacs/index.html}
695 @xref{Learning how to do something}, for how to view the manual on-line.
697 @node Emacs Lisp documentation, Installing Texinfo documentation, Getting a printed manual, Getting help
698 @section Where can I get documentation on Emacs Lisp?
699 @cindex Documentation on Emacs Lisp
700 @cindex Function documentation
701 @cindex Variable documentation
702 @cindex Emacs Lisp Reference Manual
703 @cindex Reference manual for Emacs Lisp
705 Within Emacs, you can type @kbd{C-h f} to get the documentation for a
706 function, @kbd{C-h v} for a variable.
708 For more information, obtain the Emacs Lisp Reference Manual. Details
709 on ordering it from FSF are on the
710 @uref{http://www.gnu.org/order/order.html, GNU Web site} and in the file
713 The Emacs Lisp Reference Manual is also available on-line, in Info
714 format. Texinfo source for the manual (along with pregenerated Info
715 files) is available at
717 @uref{ftp://ftp.gnu.org/pub/gnu/emacs/elisp-manual-21-2.6.tar.gz}
719 and all mirrors of @samp{ftp.gnu.org} (for a list, @pxref{Current GNU
720 distributions}). @xref{Installing Texinfo documentation}, if you want
721 to install the Info files, or @ref{Printing a Texinfo file}, if you want
722 to use the Texinfo source to print the manual yourself.
724 An HTML version of the Emacs Lisp Reference Manual is available at
726 @uref{http://www.gnu.org/manual/elisp-manual-21-2.6/elisp.html}
728 @node Installing Texinfo documentation, Printing a Texinfo file, Emacs Lisp documentation, Getting help
729 @section How do I install a piece of Texinfo documentation?
730 @cindex Texinfo documentation, installing
731 @cindex Installing Texinfo documentation
732 @cindex New Texinfo files, installing
733 @cindex Documentation, installing new Texinfo files
734 @cindex Info files, how to install
736 First, you must turn the Texinfo files into Info files. You may do this
737 using the stand-alone @file{makeinfo} program, available as part of the latest
740 @uref{ftp://ftp.gnu.org/pub/gnu/texinfo/texinfo-4.0.tar.gz}
742 and all mirrors of @samp{ftp.gnu.org} (for a list, @pxref{Current GNU
745 For information about the Texinfo format, read the Texinfo manual which
746 comes with the Texinfo package. This manual also comes installed in
747 Info format, so you can read it on-line; type @kbd{C-h i m texinfo
750 Alternatively, you could use the Emacs command @kbd{M-x
751 texinfo-format-buffer}, after visiting the Texinfo source file of the
752 manual you want to convert.
754 Neither @code{texinfo-format-buffer} nor @file{makeinfo} installs the
755 resulting Info files in Emacs's Info tree. To install Info files,
760 Move the files to the @file{info} directory in the installed Emacs
761 distribution. @xref{File-name conventions}, if you don't know where that
765 Run the @code{install-info} command, which is part of the Texinfo
766 distribution, to update the main Info directory menu, like this:
769 install-info --info-dir=@var{dir-path} @var{dir-path}/@var{file}
773 where @var{dir-path} is the full path to the directory where you copied
774 the produced Info file(s), and @var{file} is the name of the Info file
775 you produced and want to install.
777 If you don't have the @code{install-info} command installed, you can
778 edit the file @file{info/dir} in the installed Emacs distribution, and
779 add a line for the top level node in the Info package that you are
780 installing. Follow the examples already in this file. The format is:
783 * Topic: (relative-pathname). Short description of topic.
788 If you want to install Info files and you don't have the necessary
789 privileges, you have several options:
793 Info files don't actually need to be installed before being used. You
794 can feed a file name to the @code{Info-goto-node} command (invoked by
795 pressing @key{g} in Info mode) by typing the name of the file in
796 parentheses. This goes to the node named ``Top'' in that file. For
797 example, to view a Info file named @file{@var{info-file}} in your home
798 directory, you can type this:
801 @kbd{C-h i g (~/@var{info-file}) @key{RET}}
805 You can create your own Info directory. You can tell Emacs where that
806 Info directory is by adding its pathname to the value of the variable
807 @code{Info-default-directory-list}. For example, to use a private Info
808 directory which is a subdirectory of your home directory named @file{Info},
809 you could put this in your @file{.emacs} file:
812 (setq Info-default-directory-list
813 (cons "~/Info" Info-default-directory-list))
816 You will need a top-level Info file named @file{dir} in this directory
817 which has everything the system @file{dir} file has in it, except it should
818 list only entries for Info files in that directory. You might not need
819 it if all files in this directory were referenced by other @file{dir}
820 files. The node lists from all @file{dir} files in
821 @code{Info-default-directory-list} are merged by the Info system.
825 @node Printing a Texinfo file, Viewing Info files outside of Emacs, Installing Texinfo documentation, Getting help
826 @section How do I print a Texinfo file?
827 @cindex Printing a Texinfo file
828 @cindex Texinfo file, printing
829 @cindex Printing documentation
831 You can't get nicely printed output from Info files; you must still have
832 the original Texinfo source file for the manual you want to print.
834 Assuming you have @TeX{} installed on your system, follow these steps:
839 Make sure the first line of the Texinfo file looks like this:
845 You may need to change @samp{texinfo} to the full pathname of the
846 @file{texinfo.tex} file, which comes with Emacs as
847 @file{man/texinfo.tex} (or copy or link it into the current directory).
850 Type @kbd{texi2dvi @var{texinfo-source}}, where @var{texinfo-source} is
851 the name of the Texinfo source file for which you want to produce a
854 The @samp{texi2dvi} script is part of the GNU Texinfo distribution
855 (@pxref{Installing Texinfo documentation}).
858 Print the DVI file @file{@var{texinfo-source}.dvi} in the normal way for
859 printing DVI files at your site. For example, if you have a PostScript
860 printer, run the @code{dvips} program to print the DVI file on that
865 To get more general instructions, retrieve the latest Texinfo package
866 (@pxref{Installing Texinfo documentation}).
868 @node Viewing Info files outside of Emacs, Informational files for Emacs, Printing a Texinfo file, Getting help
869 @section Can I view Info files without using Emacs?
870 @cindex Viewing Info files
871 @cindex Info file viewers
872 @cindex Alternative Info file viewers
874 Yes. Here are some alternative programs:
879 @code{info}, a stand-alone version of the Info program, comes as part of
880 the Texinfo package. @xref{Installing Texinfo documentation}, for
884 Xinfo, a stand-alone version of the Info program that runs under X
885 Window system. You can get it at
886 @uref{ftp://ftp.gnu.org/pub/gnu/xinfo/xinfo-1.01.01.tar.gz} and all
887 mirrors of @samp{ftp.gnu.org} (see @ref{Current GNU distributions}, for a
891 Tkinfo, an Info viewer that runs under X Window system and uses Tcl/Tk.
892 You can get Tkinfo at
893 @uref{http://math-www.uni-paderborn.de/~axel/tkinfo/}.
897 @node Informational files for Emacs, Help installing Emacs, Viewing Info files outside of Emacs, Getting help
898 @section What informational files are available for Emacs?
899 @cindex Informational files included with Emacs
900 @cindex Files included with Emacs
901 @cindex @file{COPYING}, description of file
902 @cindex @file{DISTRIB}, description of file
903 @cindex @file{FTP}, description of file
904 @cindex @file{GNU}, description of file
905 @cindex @file{INTERVIEW}, description of file
906 @cindex @file{LPF}, description of file
907 @cindex @file{MACHINES}, description of file
908 @cindex @file{MAILINGLISTS}, description of file
909 @cindex @file{NEWS}, description of file
910 @cindex @file{SERVICE}, description of file
911 @cindex @file{SUN-SUPPORT}, description of file
913 This isn't a frequently asked question, but it should be! A variety of
914 informational files about Emacs and relevant aspects of the GNU project
915 are available for you to read.
917 The following files are available in the @file{etc} directory of the
918 Emacs distribution (see @ref{File-name conventions}, if you're not sure
924 Emacs General Public License
927 Emacs Availability Information, including the popular "Free Software
928 Foundation Order Form"
931 How to get GNU Software by Internet FTP or by UUCP
937 Richard Stallman discusses his public-domain UNIX-compatible software
938 system with BYTE editors
941 Why you should join the League for Programming Freedom
944 Status of Emacs on Various Machines and Systems
947 GNU Project Electronic Mailing Lists
950 Emacs news, a history of recent user-visible changes
953 GNU Service Directory
956 including "Using Emacstool with GNU Emacs"
960 Latest versions of the above files also available at
962 @uref{ftp://ftp.gnu.org/pub/gnu/GNUinfo/}
964 More GNU information, including back issues of the @cite{GNU's
967 @uref{http://www.gnu.org/bulletins/bulletins.html} and
969 @uref{http://www.cs.pdx.edu/~trent/gnu/gnu.html}
971 @node Help installing Emacs, Obtaining the FAQ, Informational files for Emacs, Getting help
972 @section Where can I get help in installing Emacs?
973 @cindex Installation help
974 @cindex Help installing Emacs
976 @xref{Installing Emacs}, for some basic installation hints, and see
977 @ref{Problems building Emacs}, or @ref{Linking with -lX11 fails}, if you
978 have problems with the installation.
980 The file @file{etc/SERVICE} (see @ref{File-name conventions}, if you're
981 not sure where that is) lists companies and individuals willing to sell
982 you help in installing or using Emacs. An up-to-date version this file
983 is available on @samp{ftp.gnu.org} (@pxref{Informational files for
986 @node Obtaining the FAQ, , Help installing Emacs, Getting help
987 @section Where can I get the latest version of this FAQ?
988 @cindex FAQ, obtaining the
989 @cindex Latest FAQ version, obtaining the
990 @cindex Retrieving the latest FAQ version
991 @cindex E-mail, retrieving the FAQ via
992 @cindex Web, reading the FAQ on the
994 The Emacs FAQ is available in several ways:
999 Inside of Emacs itself. You can get it from selecting the @samp{Emacs
1000 FAQ} option from the @samp{Help} menu of the Emacs menu bar at the top
1001 of any Emacs frame, or by typing @kbd{C-h F} (@kbd{M-x view-emacs-FAQ}).
1004 Via USENET. If you can read news, the FAQ should be available in your
1005 news spool, in both the @uref{news:gnu.emacs.help} and
1006 @uref{news:comp.emacs} newsgroups. Every news reader should allow you
1007 to read any news article that is still in the news spool, even if you
1008 have read the article before. You may need to read the instructions for
1009 your news reader to discover how to do this. In @file{rn}, this command
1010 will do this for you at the article selection level:
1013 ?GNU Emacs Frequently Asked Questions?rc:m
1016 In Gnus, you should type @kbd{C-u C-x C-s} from the @file{*Summary*}
1017 buffer or @kbd{C-u @key{SPC}} from the @file{*Newsgroup*} buffer to view
1018 all articles in a newsgroup.
1020 If the FAQ articles have expired and have been deleted from your news
1021 spool, it might (or might not) do some good to complain to your news
1022 administrator, because the most recent FAQ should not expire for a
1026 Via HTTP or FTP. You can always fetch the latest FAQ from
1028 @uref{http://www.lerner.co.il/emacs/} and
1030 @uref{ftp://ftp.lerner.co.il/pub/emacs/}
1033 In the Emacs distribution. Since Emacs 18.56, the FAQ at the time
1034 of release has been part of the Emacs distribution as either
1035 @file{etc/FAQ} or @file{man/faq.texi} (@pxref{File-name conventions}).
1038 Via the World Wide Web. A hypertext version is available at
1040 @uref{http://www.lerner.co.il/emacs/}
1043 Via anonymous ftp and e-mail from @file{rtfm.mit.edu} (and its mirror in
1044 Europe), the main repository for FAQs and other items posted to
1045 news.answers. The Emacs FAQs are available at
1047 @uref{ftp://rtfm.mit.edu/pub/usenet/comp.emacs/} and
1049 @uref{ftp://ftp.uni-paderborn.de/pub/doc/FAQ/comp/emacs/}
1051 If you do not have access to anonymous FTP, you can access the archives
1052 using the @file{rtfm.mit.edu} mail server. The Emacs FAQ can be
1053 retrieved by sending mail to @email{mail-server@@rtfm.mit.edu} with a
1054 blank subject and containing
1057 send usenet/news.answers/GNU-Emacs-FAQ/diffs
1058 send usenet/news.answers/GNU-Emacs-FAQ/part1
1059 send usenet/news.answers/GNU-Emacs-FAQ/part2
1060 send usenet/news.answers/GNU-Emacs-FAQ/part3
1061 send usenet/news.answers/GNU-Emacs-FAQ/part4
1062 send usenet/news.answers/GNU-Emacs-FAQ/part5
1065 For more information, send email to @email{mail-server@@rtfm.mit.edu}
1066 with "help" and "index" in the body on separate lines.
1069 As the very last resort, you can e-mail a request to
1070 @email{emacs-faq@@lerner.co.il}. Don't do this unless you have made a
1071 good-faith effort to obtain the FAQ list via one of the methods listed
1076 @c ------------------------------------------------------------
1077 @node Status of Emacs, Common requests, Getting help, Top
1078 @chapter Status of Emacs
1079 @cindex Status of Emacs
1081 This chapter gives you basic information about Emacs, including its
1082 latest version status.
1085 * Origin of the term Emacs::
1086 * Latest version of Emacs::
1091 @node Origin of the term Emacs, Latest version of Emacs, Status of Emacs, Status of Emacs
1092 @section Where does the name ``Emacs'' come from?
1093 @cindex Origin of the term ``Emacs''
1094 @cindex Emacs name origin
1096 @cindex Original version of Emacs
1098 Emacs originally was an acronym for Editor MACroS. RMS says he ``picked
1099 the name Emacs because @key{E} was not in use as an abbreviation on ITS at
1100 the time.'' The first Emacs was a set of macros written in 1976 at MIT
1101 by RMS for the editor TECO (Text Editor and COrrector, originally Tape
1102 Editor and COrrector) under ITS on a PDP-10. RMS had already extended
1103 TECO with a ``real-time'' full-screen mode with reprogrammable keys.
1104 Emacs was started by @email{gls@@east.sun.com, Guy Steele} as a project
1105 to unify the many divergent TECO command sets and key bindings at MIT,
1106 and completed by RMS.
1108 Many people have said that TECO code looks a lot like line noise; you
1109 can read more at @uref{news:alt.lang.teco}. Someone has written a TECO
1110 implementation in Emacs Lisp (to find it, see @ref{Packages that do not
1111 come with Emacs}); it would be an interesting project to run the
1112 original TECO Emacs inside of Emacs.
1115 For some not-so-serious alternative reasons for Emacs to have that
1116 name, check out the file @file{etc/JOKES} (@pxref{File-name
1119 @node Latest version of Emacs, New in Emacs 20, Origin of the term Emacs, Status of Emacs
1120 @section What is the latest version of Emacs?
1121 @cindex Version, latest
1122 @cindex Latest version of Emacs
1124 Emacs @value{VER} is the current version as of this writing.
1126 @node New in Emacs 20, New in Emacs 21, Latest version of Emacs, Status of Emacs
1127 @section What is different about Emacs 20?
1128 @cindex Differences between Emacs 19 and Emacs 20
1129 @cindex Emacs 20, new features in
1131 To find out what has changed in recent versions, type @kbd{C-h n}
1132 (@kbd{M-x view-emacs-news}). The oldest changes are at the bottom of
1133 the file, so you might want to read it starting there, rather than at
1136 The differences between Emacs versions 18 and 19 was rather dramatic;
1137 the introduction of frames, faces, and colors on windowing systems was
1138 obvious to even the most casual user.
1140 There are differences between Emacs versions 19 and 20 as well, but many
1141 are more subtle or harder to find. Among the changes are the inclusion
1142 of MULE code for languages that use non-Latin characters and for mixing
1143 several languages in the same document; the ``Customize'' facility for
1144 modifying variables without having to use Lisp; and automatic conversion
1145 of files from Macintosh, Microsoft, and Unix platforms.
1147 A number of older Lisp packages, such as Gnus, Supercite and the
1148 calendar/diary, have been updated and enhanced to work with Emacs 20,
1149 and are now included with the standard distribution.
1152 @node New in Emacs 21, , New in Emacs 20, Status of Emacs
1153 @section What is different about Emacs 21?
1154 @cindex Differences between Emacs 20 and Emacs 21
1155 @cindex Emacs 21, new features in
1156 @cindex Recently introduced features
1158 @cindex Variable-size fonts
1159 @cindex Toolbar support
1160 Emacs 21 features a thorough rewrite of the display engine. The new
1161 display engine supports variable-size fonts, images, and can play sounds
1162 on platforms which support that. As a result, the visual appearence of
1163 Emacs, when it runs on a windowed display, is much more reminiscent of
1164 modern GUI programs, and includes 3D widgets (used for the mode line and
1165 the scroll bars), a configurable and extensible toolbar, tooltips
1166 (a.k.a.@: balloon help), and other niceties.
1168 @cindex Colors on text-only terminals
1170 In addition, Emacs 21 supports faces on text-only terminals. This means
1171 that you can now have colors when you run Emacs on a GNU/Linux console
1172 and on @code{xterm} with @kbd{emacs -nw}.
1174 @c ------------------------------------------------------------
1175 @node Common requests, Bugs and problems, Status of Emacs, Top
1176 @chapter Common requests
1177 @cindex Common requests
1180 * Setting up a customization file::
1181 * Debugging a customization file::
1183 * Displaying the current line or column::
1184 * Displaying the current file name in the titlebar::
1185 * Turning on abbrevs by default::
1186 * Turning on auto-fill by default::
1187 * Associating modes with files::
1188 * Working with unprintable characters::
1189 * Highlighting a region::
1190 * Controlling case sensitivity::
1191 * Wrapping words automatically::
1193 * Checking TeX and *roff documents::
1194 * Changing load-path::
1195 * Using an already running Emacs process::
1196 * Compiler error messages::
1197 * Indenting switch statements::
1198 * Customizing C and C++ indentation::
1199 * Horizontal scrolling::
1201 * Turning off beeping::
1202 * Turning the volume down::
1203 * Automatic indentation::
1204 * Matching parentheses::
1205 * Hiding #ifdef lines::
1206 * Repeating commands::
1207 * Valid X resources::
1208 * Evaluating Emacs Lisp code::
1209 * Changing the length of a Tab::
1210 * Inserting > at the beginning of each line::
1211 * Underlining paragraphs::
1212 * Repeating a command as many times as possible::
1213 * Forcing the cursor to remain in the same column::
1214 * Forcing Emacs to iconify itself::
1215 * Using regular expressions::
1216 * Replacing text across multiple files::
1217 * Documentation for etags::
1218 * Disabling backups::
1219 * Disabling auto-save-mode::
1220 * Going to a line by number::
1221 * Modifying pull-down menus::
1222 * Deleting menus and menu options::
1223 * Turning on syntax highlighting::
1224 * Scrolling only one line::
1225 * Replacing highlighted text::
1226 * Editing MS-DOS files::
1227 * Filling paragraphs with a single space::
1228 * Escape sequences in shell output::
1231 @node Setting up a customization file, Colors on a TTY, Common requests, Common requests
1232 @section How do I set up a @file{.emacs} file properly?
1233 @cindex @file{.emacs} file, setting up
1234 @cindex Init file, setting up
1235 @cindex Customization file, setting up
1237 @inforef{Init File, Init File, emacs}
1239 In general, new Emacs users should not have @file{.emacs} files, because
1240 it causes confusing non-standard behavior. Then they send questions to
1241 @email{help-gnu-emacs@@gnu.org} asking why Emacs isn't behaving as
1244 Beginning with version 20.1, Emacs includes the new Customize
1245 facility, which can be invoked using @kbd{M-x customize @key{RET}}.
1246 This allows users who are unfamiliar with Emacs Lisp to modify their
1247 @file{.emacs} files in a relatively straightforward way, using menus
1248 rather than Lisp code. Not all packages support Customize as of this
1249 writing, but the number is growing fairly steadily.
1251 While Customize might indeed make it easier to configure Emacs,
1252 consider taking a bit of time to learn Emacs Lisp and modifying your
1253 @file{.emacs} directly. Simple configuration options are described
1254 rather completely in @inforef{Init File, Init File, emacs}, for users
1255 interested in performing frequently requested, basic tasks.
1257 @node Colors on a TTY, Debugging a customization file, Setting up a customization file, Common requests
1258 @section How do I get colors and syntax highlighting on a TTY?
1259 @cindex Colors on a TTY
1260 @cindex Syntax highlighting on a TTY
1261 @cindex Console, colors
1263 As of Emacs 21.1, colors and faces are supported in non-windowed mode,
1264 i.e.@: on Unix and GNU/Linux text-only terminals and consoles, and when
1265 invoked as @samp{emacs -nw} on X and MS-Windows. (Colors and faces were
1266 supported in the MS-DOS port since Emacs 19.29.) Emacs automatically
1267 detects color support at startup and uses it if available. If you think
1268 that your terminal supports colors, but Emacs won't use them, check the
1269 @code{termcap} entry for your display type for color-related
1272 The command @kbd{M-x list-colors-display} pops up a window which
1273 exhibits all the colors Emacs knows about on the current display.
1275 Syntax highlighting is usually turned off by default; see @ref{Turning
1276 on syntax highlighting}, for instructions how to turn it on.
1278 @node Debugging a customization file, Displaying the current line or column, Colors on a TTY, Common requests
1279 @section How do I debug a @file{.emacs} file?
1280 @cindex Debugging @file{.emacs} file
1281 @cindex @file{.emacs} debugging
1282 @cindex Init file debugging
1283 @cindex @samp{-debug-init} option
1285 Start Emacs with the @samp{-debug-init} command-line option. This
1286 enables the Emacs Lisp debugger before evaluating your @file{.emacs}
1287 file, and places you in the debugger if something goes wrong. The top
1288 line in the @file{trace-back} buffer will be the error message, and the
1289 second or third line of that buffer will display the Lisp code from your
1290 @file{.emacs} file that caused the problem.
1292 You can also evaluate an individual function or argument to a function
1293 in your @file{.emacs} file by moving the cursor to the end of the
1294 function or argument and typing @kbd{C-x C-e} (@kbd{M-x
1297 Use @kbd{C-h v} (@kbd{M-x describe-variable}) to check the value of
1298 variables which you are trying to set or use.
1300 @node Displaying the current line or column, Displaying the current file name in the titlebar, Debugging a customization file, Common requests
1301 @section How do I make Emacs display the current line (or column) number?
1302 @cindex @code{line-number-mode}
1303 @cindex Displaying the current line or column
1304 @cindex Line number, displaying the current
1305 @cindex Column, displaying the current
1306 @cindex @code{mode-line-format}
1308 To have Emacs automatically display the current line number of the point
1309 in the mode line, do @kbd{M-x line-number-mode}. You can also put the
1313 (setq line-number-mode t)
1317 in your @file{.emacs} file to achieve this whenever you start Emacs.
1318 (Line number display is on by default, unless your site-specific
1319 initialization disables it.) Note that Emacs will not display the line
1320 number if the buffer's size in bytes is larger than the value of the
1321 variable @code{line-number-display-limit}.
1323 As of Emacs 20, you can similarly display the current column with
1324 @kbd{M-x column-number-mode}, or by putting the form
1327 (setq column-number-mode t)
1331 in your @file{.emacs} file.
1333 The @code{"%c"} format specifier in the variable @code{mode-line-format}
1334 will insert the current column's value into the mode line. See the
1335 documentation for @code{mode-line-format} (using @kbd{C-h v
1336 mode-line-format @key{RET}}) for more information on how to set and use
1339 Users of all Emacs versions can display the current column using the
1340 @samp{column} package written by @email{abraham@@dina.kvl.dk, Per
1341 Abrahamsen}. @xref{Packages that do not come with Emacs}, for
1342 instructions on how to get it.
1344 @cindex Set number capability in @code{vi} emulators
1345 None of the @code{vi} emulation modes provide the ``set number''
1346 capability of @code{vi} (as far as we know).
1348 @node Displaying the current file name in the titlebar, Turning on abbrevs by default, Displaying the current line or column, Common requests
1349 @section How can I modify the titlebar to contain the current file name?
1350 @cindex Titlebar, displaying the current file name in
1351 @cindex File name, displaying in the titlebar
1352 @cindex @code{frame-title-format}
1354 The contents of an Emacs frame's titlebar is controlled by the variable
1355 @code{frame-title-format}, which has the same structure as the variable
1356 @code{mode-line-format}. (Use @kbd{C-h v} or @kbd{M-x
1357 describe-variable} to get information about one or both of these
1360 By default, the titlebar for a frame does contain the name of the buffer
1361 currently being visited, except if there is a single frame. In such a
1362 case, the titlebar contains Emacs invocation name and the name of the
1363 machine at which Emacs was invoked. This is done by setting
1364 @code{frame-title-format} to the default value of
1367 (multiple-frames "%b" ("" invocation-name "@@" system-name))
1370 To modify the behavior such that frame titlebars contain the buffer's
1371 name regardless of the number of existing frames, include the following
1372 in your @file{.emacs}:
1375 (setq frame-title-format "%b")
1378 @node Turning on abbrevs by default, Turning on auto-fill by default, Displaying the current file name in the titlebar, Common requests
1379 @section How do I turn on abbrevs by default just in mode @var{mymode}?
1380 @cindex Abbrevs, turning on by default
1382 Put this in your @file{.emacs} file:
1386 (quietly-read-abbrev-file)
1389 (add-hook '@var{mymode}-mode-hook
1391 (setq abbrev-mode t)))
1394 @node Turning on auto-fill by default, Associating modes with files, Turning on abbrevs by default, Common requests
1395 @section How do I turn on @code{auto-fill-mode} by default?
1396 @cindex @code{auto-fill-mode}, activating automatically
1397 @cindex Filling automatically
1398 @cindex Automatic entry to @code{auto-fill-mode}
1400 To turn on @code{auto-fill-mode} just once for one buffer, use @kbd{M-x
1403 To turn it on for every buffer in a certain mode, you must use the hook
1404 for that mode. For example, to turn on @code{auto-fill} mode for all
1405 text buffers, including the following in your @file{.emacs} file:
1408 (add-hook 'text-mode-hook 'turn-on-auto-fill)
1411 If you want @code{auto-fill} mode on in all major modes, do this:
1414 (setq-default auto-fill-function 'do-auto-fill)
1417 @node Associating modes with files, Working with unprintable characters, Turning on auto-fill by default, Common requests
1418 @section How do I make Emacs use a certain major mode for certain files?
1419 @cindex Associating modes with files
1420 @cindex File extensions and modes
1421 @cindex @code{auto-mode-alist}, modifying
1422 @cindex Modes, associating with file extensions
1424 If you want to use a certain mode @var{foo} for all files whose names end
1425 with the extension @file{.@var{bar}}, this will do it for you:
1428 (setq auto-mode-alist (cons '("\\.@var{bar}\\'" . @var{foo}-mode) auto-mode-alist))
1431 Otherwise put this somewhere in the first line of any file you want to
1432 edit in the mode @var{foo} (in the second line, if the first line begins
1439 @cindex Major mode for shell scripts
1440 Beginning with Emacs 19, the variable @code{interpreter-mode-alist}
1441 specifies which mode to use when loading a shell script. (Emacs
1442 determines which interpreter you're using by examining the first line of
1443 the script.) This feature only applies when the file name doesn't
1444 indicate which mode to use. Use @kbd{C-h v} (or @kbd{M-x
1445 describe-variable}) on @code{interpreter-mode-alist} to learn more.
1447 @node Working with unprintable characters, Highlighting a region, Associating modes with files, Common requests
1448 @section How do I search for, delete, or replace unprintable (eight-bit or control) characters?
1449 @cindex Unprintable characters, working with
1450 @cindex Working with unprintable characters
1451 @cindex Control characters, working with
1452 @cindex Eight-bit characters, working with
1453 @cindex Searching for unprintable characters
1454 @cindex Regexps and unprintable characters
1456 To search for a single character that appears in the buffer as, for
1457 example, @samp{\237}, you can type @kbd{C-s C-q 2 3 7}. (This assumes
1458 the value of @code{search-quote-char} is 17 (i.e., @kbd{C-q}).)
1459 Searching for @strong{all} unprintable characters is best done with a
1460 regular expression (@dfn{regexp}) search. The easiest regexp to use for
1461 the unprintable chars is the complement of the regexp for the printable
1467 Regexp for the printable chars: @samp{[\t\n\r\f -~]}
1470 Regexp for the unprintable chars: @samp{[^\t\n\r\f -~]}
1474 To type these special characters in an interactive argument to
1475 @code{isearch-forward-regexp} or @code{re-search-forward}, you need to
1476 use @kbd{C-q}. (@samp{\t}, @samp{\n}, @samp{\r}, and @samp{\f} stand
1477 respectively for @key{TAB}, @key{LFD}, @key{RET}, and @kbd{C-l}.) So,
1478 to search for unprintable characters using @code{re-search-forward}:
1480 @kbd{M-x re-search-forward @key{RET} [^ @key{TAB} C-q @key{LFD} C-q @key{RET} C-q C-l @key{SPC} -~] @key{RET}}
1482 Using @code{isearch-forward-regexp}:
1484 @kbd{M-C-s [^ @key{TAB} @key{LFD} C-q @key{RET} C-q C-l @key{SPC} -~]}
1486 To delete all unprintable characters, simply use replace-regexp:
1488 @kbd{M-x replace-regexp @key{RET} [^ @key{TAB} C-q @key{LFD} C-q @key{RET} C-q C-l @key{SPC} -~] @key{RET} @key{RET}}
1490 Replacing is similar to the above. To replace all unprintable
1491 characters with a colon, use:
1493 M-x replace-regexp @key{RET} [^ @key{TAB} C-q @key{LFD} C-q @key{RET} C-q C-l @key{SPC} -~] @key{RET} : @key{RET}
1498 You don't need to quote @key{TAB} with either isearch or typing
1499 something in the minibuffer.
1503 @node Highlighting a region, Controlling case sensitivity, Working with unprintable characters, Common requests
1504 @section How can I highlight a region of text in Emacs?
1505 @cindex Highlighting text
1506 @cindex Text, highlighting
1507 @cindex @code{transient-mark-mode}
1508 @cindex Region, highlighting a
1510 You can cause the region to be highlighted when the mark is active by
1514 (transient-mark-mode t)
1518 in your @file{.emacs} file. (Also see @ref{Turning on syntax
1521 @node Controlling case sensitivity, Wrapping words automatically, Highlighting a region, Common requests
1522 @section How do I control Emacs's case-sensitivity when searching/replacing?
1523 @cindex @code{case-fold-search}
1524 @cindex Case sensitivity of searches
1525 @cindex Searching without case sensitivity
1526 @cindex Ignoring case in searches
1528 For searching, the value of the variable @code{case-fold-search}
1529 determines whether they are case sensitive:
1532 (setq case-fold-search nil) ; make searches case sensitive
1533 (setq case-fold-search t) ; make searches case insensitive
1536 @cindex Case sensitivity in replacements
1537 @cindex Replacing, and case sensitivity
1538 @cindex @code{case-replace}
1539 Similarly, for replacing, the variable @code{case-replace} determines
1540 whether replacements preserve case.
1542 To change the case sensitivity just for one major mode, use the major
1543 mode's hook. For example:
1546 (add-hook '@var{foo}-mode-hook
1548 (setq case-fold-search nil)))
1551 @node Wrapping words automatically, Spell-checkers, Controlling case sensitivity, Common requests
1552 @section How do I make Emacs wrap words for me?
1553 @cindex Wrapping word automatically
1554 @cindex Wrapping lines
1556 @cindex @code{auto-fill-mode}, introduction to
1557 @cindex Maximum line width, default value
1558 @cindex @code{fill-column}, default value
1560 Use @code{auto-fill-mode}, activated by typing @kbd{M-x auto-fill-mode}.
1561 The default maximum line width is 70, determined by the variable
1562 @code{fill-column}. To learn how to turn this on automatically, see
1563 @ref{Turning on auto-fill by default}.
1565 @node Spell-checkers, Checking TeX and *roff documents, Wrapping words automatically, Common requests
1566 @section Where can I get a better spelling checker for Emacs?
1567 @cindex Checking spelling
1568 @cindex Spelling, checking text documents
1570 Use Ispell. @xref{Ispell}.
1572 @node Checking TeX and *roff documents, Changing load-path, Spell-checkers, Common requests
1573 @section How can I spell-check @TeX{} or *roff documents?
1574 @cindex Spelling, checking @TeX{} documents
1575 @cindex @TeX{} documents, checking spelling in
1577 Use Ispell. Ispell can handle @TeX{} and *roff documents.
1580 @node Changing load-path, Using an already running Emacs process, Checking TeX and *roff documents, Common requests
1581 @section How do I change @code{load-path}?
1582 @cindex @code{load-path}, modifying
1583 @cindex Modifying @code{load-path}
1584 @cindex Adding to @code{load-path}
1586 In general, you should only add to the @code{load-path}. You can add
1587 directory @var{/dir/subdir} to the load path like this:
1590 (setq load-path (cons "/dir/subdir/" load-path))
1593 To do this relative to your home directory:
1596 (setq load-path (cons "~/mysubdir/" load-path)
1599 @node Using an already running Emacs process, Compiler error messages, Changing load-path, Common requests
1600 @section How do I use an already running Emacs from another window?
1601 @cindex @code{emacsclient}
1602 @cindex Emacs server functions
1603 @cindex Using an existing Emacs process
1605 @code{emacsclient}, which comes with Emacs, is for editing a file using
1606 an already running Emacs rather than starting up a new Emacs. It does
1607 this by sending a request to the already running Emacs, which must be
1608 expecting the request.
1615 Emacs must have executed the @code{server-start} function for
1616 @samp{emacsclient} to work. This can be done either by a command line
1620 emacs -f server-start
1623 or by invoking @code{server-start} from @file{.emacs}:
1626 (if (@var{some conditions are met}) (server-start))
1629 When this is done, Emacs starts a subprocess running a program called
1630 @samp{emacsserver}. @samp{emacsserver} creates a Unix domain socket.
1631 The socket is either named @file{.emacs_server}, in the user's home directory,
1632 or @file{esrv-@var{userid}-@var{systemname}}, in the @file{/tmp}
1633 directory, depending on how @samp{emacsserver} was compiled.
1635 To get your news reader, mail reader, etc., to invoke
1636 @samp{emacsclient}, try setting the environment variable @code{EDITOR}
1637 (or sometimes @code{VISUAL}) to the value @samp{emacsclient}. You may
1638 have to specify the full pathname of the @samp{emacsclient} program
1643 setenv EDITOR emacsclient
1645 # using full pathname
1646 setenv EDITOR /usr/local/emacs/etc/emacsclient
1649 EDITOR=emacsclient ; export EDITOR
1655 When @samp{emacsclient} is run, it connects to the @file{.emacs_server}
1656 socket and passes its command line options to @samp{server}. When
1657 @samp{server} receives these requests, it sends this information to the
1658 the Emacs process, which at the next opportunity will visit the files
1659 specified. (Line numbers can be specified just like with Emacs.) The
1660 user will have to switch to the Emacs window by hand. When the user is
1661 done editing a file, the user can type @kbd{C-x #} (or @kbd{M-x
1662 server-edit}) to indicate this. If there is another buffer requested by
1663 @code{emacsclient}, Emacs will switch to it; otherwise
1664 @code{emacsclient} will exit, signaling the calling program to continue.
1666 @samp{emacsclient} and @samp{server} must be running on machines which
1667 share the same filesystem for this to work. The pathnames that
1668 @samp{emacsclient} specifies should be correct for the filesystem that
1669 the Emacs process sees. The Emacs process should not be suspended at
1670 the time @samp{emacsclient} is invoked. On Unix and GNU/Linux systems,
1671 @samp{emacsclient} should either be invoked from another X window, or
1672 from a shell window inside Emacs itself, or from another interactive
1673 session, e.g., by means of a @code{screen} program.
1675 @cindex @code{gnuserv}
1676 There is an enhanced version of @samp{emacsclient}/server called
1677 @samp{gnuserv}, written by @email{ange@@hplb.hpl.hp.com, Andy Norman}
1678 which is available in the Emacs Lisp Archive (@pxref{Packages that do
1679 not come with Emacs}). @samp{gnuserv} uses Internet domain sockets, so
1680 it can work across most network connections. It also supports the
1681 execution of arbitrary Emacs Lisp forms and does not require the client
1682 program to wait for completion.
1684 The alpha version of an enhanced @samp{gnuserv} is available at
1686 @uref{ftp://ftp.wellfleet.com/netman/psmith/emacs/gnuserv-2.1alpha.tar.gz}
1690 @node Compiler error messages, Indenting switch statements, Using an already running Emacs process, Common requests
1691 @section How do I make Emacs recognize my compiler's funny error messages?
1692 @cindex Compiler error messages, recognizing
1693 @cindex Recognizing non-standard compiler errors
1694 @cindex Regexps for recognizing compiler errors
1695 @cindex Errors, recognizing compiler
1697 The variable @code{compilation-error-regexp-alist} helps control how
1698 Emacs parses your compiler output. It is a list of triplets of the form:
1699 @code{(@var{regexp} @var{file-idx} @var{line-idx})}, where @var{regexp},
1700 @var{file-idx} and @var{line-idx} are strings. To help determine what
1701 the constituent elements should be, load @file{compile.el} and then type
1702 @kbd{C-h v compilation-error-regexp-alist @key{RET}} to see the current
1703 value. A good idea is to look at @file{compile.el} itself as the
1704 comments included for this variable are quite useful---the regular
1705 expressions required for your compiler's output may be very close to one
1706 already provided. Once you have determined the proper regexps, use the
1707 following to inform Emacs of your changes:
1710 (setq compilation-error-regexp-alist
1711 (cons '(@var{regexp} @var{file-idx} @var{line-idx})
1712 compilation-error-regexp-alist))
1715 @node Indenting switch statements, Customizing C and C++ indentation, Compiler error messages, Common requests
1716 @section How do I change the indentation for @code{switch}?
1717 @cindex @code{switch}, indenting
1718 @cindex Indenting of @code{switch}
1720 Many people want to indent their @code{switch} statements like this:
1738 The solution at first appears to be: set @code{c-indent-level} to 4 and
1739 @code{c-label-offset} to -2. However, this will give you an indentation
1740 spacing of four instead of two.
1742 The @emph{real} solution is to use @code{cc-mode} (the default mode for
1743 C programming in Emacs 20 and later) and add the following line to yoyr
1747 (c-set-offset 'case-label '+)
1750 There appears to be no way to do this with the old @code{c-mode}.
1752 @node Customizing C and C++ indentation, Horizontal scrolling, Indenting switch statements, Common requests
1753 @section How to customize indentation in C, C@t{++}, and Java buffers?
1754 @cindex Indentation, how to customize
1755 @cindex Customize indentation
1757 The Emacs @code{cc-mode} features an interactive procedure for
1758 customizing the indentation style, which is fully explained in the
1759 @cite{CC Mode} manual that is part of the Emacs distribution, see
1760 @ref{Customizing Indentation, , Customization Indentation, ccmode,
1761 The CC Mode Manual}. Here's a short summary of the procedure:
1765 Go to the beginning of the first line where you don't like the
1766 indentation and type @kbd{C-c C-o}. Emacs will prompt you for the
1767 syntactic symbol; type @key{RET} to accept the default it suggests.
1770 Emacs now prompts for the offset of this syntactic symbol, showing the
1771 default (the current definition) inside parentheses. You can choose
1776 No extra indentation.
1778 Indent one basic offset.
1780 Outdent one basic offset.
1782 Indent two basic offsets
1784 Outdent two basic offsets.
1786 Indent half basic offset.
1788 Outdent half basic offset.
1792 After choosing one of these symbols, type @kbd{C-c C-q} to reindent
1793 the line or the block according to what you just specified.
1796 If you don't like the result, go back to step 1. Otherwise, add the
1797 following line to your @file{.emacs}:
1800 (c-set-offset '@var{syntactic-symbol} @var{offset})
1804 where @var{syntactic-symbol} is the name Emacs shows in the minibuffer
1805 when you type @kbd{C-c C-o} at the beginning of the line, and
1806 @var{offset} is one of the indentation symbols listed above (@code{+},
1807 @code{/}, @code{0}, etc.) that you've chosen during the interactive
1811 Go to the next line whose indentation is not to your liking and repeat
1815 It is recommended to put all the resulting @code{(c-set-offset ...)}
1816 customizations inside a C mode hook, like this:
1819 (defun my-c-mode-hook ()
1822 (add-hook 'c-mode-hook 'my-c-mode-hook)
1826 Using @code{c-mode-hook} avoids the need to put a @w{@code{(require
1827 'cc-mode)}} into your @file{.emacs} file, because @code{c-set-offset}
1828 might be unavailable when @code{cc-mode} is not loaded.
1830 Note that @code{c-mode-hook} runs for C source files only; use
1831 @code{c++-mode-hook} for C@t{++} sources, @code{java-mode-hook} for
1832 Java sources, etc. If you want the same customizations to be in
1833 effect in @emph{all} languages supported by @code{cc-mode}, use
1834 @code{c-mode-common-hook}.
1836 @node Horizontal scrolling, Overwrite mode, Customizing C and C++ indentation, Common requests
1837 @section How can I make Emacs automatically scroll horizontally?
1838 @cindex @code{hscroll-mode}
1839 @cindex Horizontal scrolling
1840 @cindex Scrolling horizontally
1842 In Emacs 21 and later, this is on by default: if the variable
1843 @code{truncate-lines} is non-@code{nil} in the current buffer, Emacs
1844 automatically scrolls the display horizontally when point moves off the
1845 left or right edge of the window.
1847 In Emacs 20, use the @code{hscroll-mode}. Here is some information from
1848 the documentation, available by typing @kbd{C-h f hscroll-mode @key{RET}}:
1850 Automatically scroll horizontally when the point moves off the
1851 left or right edge of the window.
1855 Type @kbd{M-x hscroll-mode} to enable it in the current buffer.
1858 Type @kbd{M-x hscroll-global-mode} to enable it in every buffer.
1861 @code{turn-on-hscroll} is useful in mode hooks as in:
1864 (add-hook 'text-mode-hook 'turn-on-hscroll)
1868 @code{hscroll-margin} controls how close the cursor can get to the
1872 @code{hscroll-step-percent} controls how far to jump once we decide to do so.
1875 @node Overwrite mode, Turning off beeping, Horizontal scrolling, Common requests
1876 @section How do I make Emacs "typeover" or "overwrite" instead of inserting?
1877 @cindex @key{Insert}
1878 @cindex @code{overwrite-mode}
1879 @cindex Overwriting existing text
1880 @cindex Toggling @code{overwrite-mode}
1882 @kbd{M-x overwrite-mode} (a minor mode). This toggles
1883 @code{overwrite-mode} on and off, so exiting from @code{overwrite-mode}
1884 is as easy as another @kbd{M-x overwrite-mode}.
1886 On some systems, @key{Insert} toggles @code{overwrite-mode} on and off.
1888 @node Turning off beeping, Turning the volume down, Overwrite mode, Common requests
1889 @section How do I stop Emacs from beeping on a terminal?
1890 @cindex Beeping, turning off
1891 @cindex Visible bell
1892 @cindex Bell, visible
1894 @email{martin@@cc.gatech.edu, Martin R. Frank} writes:
1896 Tell Emacs to use the @dfn{visible bell} instead of the audible bell,
1897 and set the visible bell to nothing.
1899 That is, put the following in your @code{TERMCAP} environment variable
1900 (assuming you have one):
1906 And evaluate the following Lisp form:
1909 (setq visible-bell t)
1912 @node Turning the volume down, Automatic indentation, Turning off beeping, Common requests
1913 @section How do I turn down the bell volume in Emacs running under X?
1914 @cindex Bell, volume of
1915 @cindex Volume of bell
1917 On X Window system, you can adjust the bell volume and duration for all
1918 programs with the shell command @code{xset}.
1920 Invoking @code{xset} without any arguments produces some basic
1921 information, including the following:
1924 usage: xset [-display host:dpy] option ...
1927 To set bell volume, pitch and duration:
1928 b [vol [pitch [dur]]] b on
1931 @node Automatic indentation, Matching parentheses, Turning the volume down, Common requests
1932 @section How do I tell Emacs to automatically indent a new line to the indentation of the previous line?
1933 @cindex Indenting new lines
1934 @cindex New lines, indenting of
1935 @cindex Previous line, indenting according to
1936 @cindex Text indentation
1938 Such behavior is automatic in Emacs 20 and later. From the
1939 @file{etc/NEWS} file for Emacs 20.2:
1942 ** In Text mode, now only blank lines separate paragraphs. This makes
1943 it possible to get the full benefit of Adaptive Fill mode in Text mode,
1944 and other modes derived from it (such as Mail mode). @key{TAB} in Text
1945 mode now runs the command @code{indent-relative}; this makes a practical
1946 difference only when you use indented paragraphs.
1948 As a result, the old Indented Text mode is now identical to Text mode,
1949 and is an alias for it.
1951 If you want spaces at the beginning of a line to start a paragraph, use
1952 the new mode, Paragraph Indent Text mode.
1955 @cindex Prefixing lines
1957 If you have @code{auto-fill-mode} turned on (@pxref{Turning on auto-fill
1958 by default}), you can tell Emacs to prefix every line with a certain
1959 character sequence, the @dfn{fill prefix}. Type the prefix at the
1960 beginning of a line, position point after it, and then type @kbd{C-x .}
1961 (@code{set-fill-prefix}) to set the fill prefix. Thereafter,
1962 auto-filling will automatically put the fill prefix at the beginning of
1963 new lines, and @kbd{M-q} (@code{fill-paragraph}) will maintain any fill
1964 prefix when refilling the paragraph.
1966 If you have paragraphs with different levels of indentation, you will
1967 have to set the fill prefix to the correct value each time you move to a
1968 new paragraph. To avoid this hassle, try one of the many packages
1969 available from the Emacs Lisp Archive (@pxref{Packages that do not come
1970 with Emacs}.) Look up ``fill'' and ``indent'' in the Lisp Code
1971 Directory for guidance.
1973 @node Matching parentheses, Hiding #ifdef lines, Automatic indentation, Common requests
1974 @section How do I show which parenthesis matches the one I'm looking at?
1975 @cindex Parentheses, matching
1976 @cindex @file{paren.el}
1977 @cindex Highlighting matching parentheses
1978 @cindex Pairs of parentheses, highlighting
1979 @cindex Matching parentheses
1981 As of version 19, Emacs comes with @file{paren.el}, which (when loaded)
1982 will automatically highlight matching parentheses whenever point (i.e.,
1983 the cursor) is located over one. To load @file{paren.el} automatically,
1990 in your @file{.emacs} file. @email{shutkoa@@ugsolutions.com, Alan Shutko}
1991 reports that as of version 20.1, you must also call @code{show-paren-mode} in
1992 your @file{.emacs} file:
1998 Customize will let you turn on @code{show-paren-mode}. Use @kbd{M-x
1999 customize-group @key{RET} paren-showing @key{RET}}. From within
2000 Customize, you can also go directly to the ``paren-showing'' group.
2002 Alternatives to paren include:
2007 If you're looking at a right parenthesis (or brace or bracket) you can
2008 delete it and reinsert it. Emacs will momentarily move the cursor to
2009 the matching parenthesis.
2012 @kbd{M-C-f} (@code{forward-sexp}) and @kbd{M-C-b} (@code{backward-sexp})
2013 will skip over one set of balanced parentheses, so you can see which
2014 parentheses match. (You can train it to skip over balanced brackets
2015 and braces at the same time by modifying the syntax table.)
2017 @cindex Show matching paren as in @code{vi}
2019 Here is some Emacs Lisp that will make the @key{%} key show the matching
2020 parenthesis, like in @code{vi}. In addition, if the cursor isn't over a
2021 parenthesis, it simply inserts a % like normal.
2024 ;; By an unknown contributor
2026 (global-set-key "%" 'match-paren)
2028 (defun match-paren (arg)
2029 "Go to the matching paren if on a paren; otherwise insert %."
2031 (cond ((looking-at "\\s\(") (forward-list 1) (backward-char 1))
2032 ((looking-at "\\s\)") (forward-char 1) (backward-list 1))
2033 (t (self-insert-command (or arg 1)))))
2038 @node Hiding #ifdef lines, Repeating commands, Matching parentheses, Common requests
2039 @section In C mode, can I show just the lines that will be left after @code{#ifdef} commands are handled by the compiler?
2040 @cindex @code{#ifdef}, selective display of
2041 @cindex @code{hide-ifdef-mode}
2042 @cindex Hiding @code{#ifdef} text
2043 @cindex Selectively displaying @code{#ifdef} code
2045 @kbd{M-x hide-ifdef-mode}. (This is a minor mode.) You might also want
2046 to try @file{cpp.el}, available at the Emacs Lisp Archive
2047 (@pxref{Packages that do not come with Emacs}).
2049 @node Repeating commands, Valid X resources, Hiding #ifdef lines, Common requests
2050 @section Is there an equivalent to the @code{.} (dot) command of vi?
2051 @cindex Repeating commands as with @code{vi}
2052 @cindex Command, repeat last
2053 @cindex @code{.}, equivalent to @code{vi} command
2055 (@code{.} is the redo command in @code{vi}. It redoes the last
2056 insertion/deletion.)
2058 As of Emacs 20.3, there is indeed a @code{repeat} command (@kbd{C-x z})
2059 that repeats the last command. If you preface it with a prefix
2060 argument, the prefix arg is applied to the command.
2062 You can also type @kbd{C-x @key{ESC} @key{ESC}}
2063 (@code{repeat-complex-command}) to reinvoke commands that used the
2064 minibuffer to get arguments. In @code{repeat-complex-command} you can
2065 type @kbd{M-p} and @kbd{M-n} (and also up-arrow and down-arrow, if your
2066 keyboard has these keys) to scan through all the different complex
2067 commands you've typed.
2069 To repeat a set of commands, use keyboard macros. (@inforef{Keyboard
2070 Macros, Keyboard Macros, emacs}.)
2072 If you're really desperate for the @code{.} command, use VIPER, a
2073 @code{vi} emulation mode which comes with Emacs, and which appears to
2074 support it. (@xref{VIPER}.)
2076 @node Valid X resources, Evaluating Emacs Lisp code, Repeating commands, Common requests
2077 @section What are the valid X resource settings (i.e., stuff in .Xdefaults)?
2078 @cindex Resources, X
2080 @cindex Setting X resources
2082 @inforef{Resources X, Resources X, emacs}.
2084 You can also use a resource editor, such as editres (for X11R5 and
2085 onwards), to look at the resource names for the menu bar, assuming Emacs
2086 was compiled with the X toolkit.
2088 @node Evaluating Emacs Lisp code, Changing the length of a Tab, Valid X resources, Common requests
2089 @section How do I execute ("evaluate") a piece of Emacs Lisp code?
2090 @cindex Evaluating Lisp code
2091 @cindex Lisp forms, evaluating
2093 There are a number of ways to execute (@dfn{evaluate}, in Lisp lingo) an
2094 Emacs Lisp @dfn{form}:
2099 If you want it evaluated every time you run Emacs, put it in a file
2100 named @file{.emacs} in your home directory. This is known as ``your
2101 @file{.emacs} file,'' and contains all of your personal customizations.
2104 You can type the form in the @file{*scratch*} buffer, and then type
2105 @key{LFD} (or @kbd{C-j}) after it. The result of evaluating the form
2106 will be inserted in the buffer.
2109 In @code{emacs-lisp-mode}, typing @kbd{M-C-x} evaluates a top-level form
2110 before or around point.
2113 Typing @kbd{C-x C-e} in any buffer evaluates the Lisp form immediately
2114 before point and prints its value in the echo area.
2117 Typing @kbd{M-:} or @kbd{M-x eval-expression} allows you to type a Lisp
2118 form in the minibuffer which will be evaluated once you press @key{RET}.
2121 You can use @kbd{M-x load-file} to have Emacs evaluate all the Lisp
2122 forms in a file. (To do this from Lisp use the function @code{load}
2125 The functions @code{load-library}, @code{eval-region},
2126 @code{eval-current-buffer}, @code{require}, and @code{autoload} are also
2127 useful; see @ref{Emacs Lisp documentation}, if you want to learn more
2132 @node Changing the length of a Tab, Inserting > at the beginning of each line, Evaluating Emacs Lisp code, Common requests
2133 @section How do I change Emacs's idea of the @key{TAB} character's length?
2135 @cindex Length of tab character
2136 @cindex @code{default-tab-width}
2138 Set the variable @code{default-tab-width}. For example, to set
2139 @key{TAB} stops every 10 characters, insert the following in your
2143 (setq default-tab-width 10)
2146 Do not confuse variable @code{tab-width} with variable
2147 @code{tab-stop-list}. The former is used for the display of literal
2148 @key{TAB} characters. The latter controls what characters are inserted
2149 when you press the @key{TAB} character in certain modes.
2151 @node Inserting > at the beginning of each line, Underlining paragraphs, Changing the length of a Tab, Common requests
2152 @section How do I insert @samp{>} at the beginning of every line?
2153 @cindex Prefix character, inserting in mail/news replies
2154 @cindex Replies to mail/news, inserting a prefix character
2155 @cindex @code{mail-yank-prefix}
2156 @cindex Mail replies, inserting a prefix character
2157 @cindex News replies, inserting a prefix character
2159 To do this to an entire buffer, type @kbd{M-< M-x replace-regexp
2160 @key{RET} ^ @key{RET} > @key{RET}}.
2162 To do this to a region, use @code{string-insert-rectangle}.
2163 Set the mark (@kbd{C-@key{SPC}}) at the beginning of the first line you
2164 want to prefix, move the cursor to last line to be prefixed, and type
2165 @kbd{M-x string-insert-rectangle @key{RET}}. To do this for the whole
2166 buffer, type @kbd{C-x h M-x string-insert-rectangle @key{RET}}.
2168 If you are trying to prefix a yanked mail message with @samp{>}, you
2169 might want to set the variable @code{mail-yank-prefix}. Better yet, use
2170 the Supercite package (@pxref{Supercite}), which provides flexible
2171 citation for yanked mail and news messages; it is included in Emacs
2172 since version 19.20. @xref{Changing the included text prefix}, for
2173 additional information.
2175 @node Underlining paragraphs, Repeating a command as many times as possible, Inserting > at the beginning of each line, Common requests
2176 @section How do I insert "_^H" before each character in a region to get an underlined paragraph?
2177 @cindex Underlining a region of text
2178 @cindex @code{underline-region}
2180 Mark the region and then type @kbd{M-x underline-region @key{RET}}.
2182 @node Repeating a command as many times as possible, Forcing the cursor to remain in the same column, Underlining paragraphs, Common requests
2183 @section How do I repeat a command as many times as possible?
2184 @cindex Repeating commands many times
2185 @cindex Commands, repeating many times
2187 Use @kbd{C-x (} and @kbd{C-x )} to make a keyboard macro that invokes
2188 the command and then type @kbd{M-0 C-x e}.
2190 Any messages your command prints in the echo area will be suppressed.
2192 If you need to repeat a command a small number of times, you can use
2193 @kbd{C-x z}, see @ref{Repeating commands}.
2195 @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
2196 @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?
2197 @cindex @code{picture-mode}
2198 @cindex Remaining in the same column, regardless of contents
2199 @cindex Vertical movement in empty documents
2201 @kbd{M-x picture-mode}.
2203 @node Forcing Emacs to iconify itself, Using regular expressions, Forcing the cursor to remain in the same column, Common requests
2204 @section How do I tell Emacs to iconify itself?
2205 @cindex Iconification under the X Window System
2206 @cindex X Window System and iconification
2207 @cindex Suspending Emacs
2209 @kbd{C-z} iconifies Emacs when running under X and suspends Emacs
2210 otherwise. @inforef{Misc X, Misc X, emacs}.
2212 @node Using regular expressions, Replacing text across multiple files, Forcing Emacs to iconify itself, Common requests
2213 @section How do I use regexps (regular expressions) in Emacs?
2215 @cindex Regular expressions
2216 @cindex Differences between Unix and Emacs regexps
2217 @cindex Unix regeps, differences from Emacs
2218 @cindex Text strings, putting regexps in
2220 @inforef{Regexps, Regexps, emacs}.
2222 The @code{or} operator is @samp{\|}, not @samp{|}, and the grouping operators
2223 are @samp{\(} and @samp{\)}. Also, the string syntax for a backslash is
2224 @samp{\\}. To specify a regular expression like @samp{xxx\(foo\|bar\)}
2225 in a Lisp string, use @samp{xxx\\(foo\\|bar\\)}.
2227 Note the doubled backslashes!
2232 Unlike in Unix @file{grep}, @file{sed}, etc., a complement character set
2233 (@samp{[^...]}) can match a newline character (@key{LFD} a.k.a.@:
2234 @kbd{C-j} a.k.a.@: @samp{\n}), unless newline is mentioned as one of the
2235 characters not to match.
2238 The character syntax regexps (e.g., @samp{\sw}) are not
2239 meaningful inside character set regexps (e.g., @samp{[aeiou]}). (This
2240 is actually typical for regexp syntax.)
2244 @node Replacing text across multiple files, Documentation for etags, Using regular expressions, Common requests
2245 @section How do I perform a replace operation across more than one file?
2246 @cindex Replacing strings across files
2247 @cindex Multiple files, replacing across
2248 @cindex Files, replacing strings across multiple
2250 The ``tags'' feature of Emacs includes the command
2251 @code{tags-query-replace} which performs a query-replace across all the
2252 files mentioned in the @file{TAGS} file. @inforef{Tags Search, Tags Search,
2255 As of Emacs 19.29, Dired mode (@kbd{M-x dired @key{RET}}, or @kbd{C-x
2256 d}) supports the command @code{dired-do-query-replace}, which allows
2257 users to replace regular expressions in multiple files.
2259 @node Documentation for etags, Disabling backups, Replacing text across multiple files, Common requests
2260 @section Where is the documentation for @code{etags}?
2261 @cindex Documentation for @code{etags}
2262 @cindex @code{etags}, documentation for
2264 The @code{etags} man page should be in the same place as the
2265 @code{emacs} man page.
2267 Quick command-line switch descriptions are also available. For example,
2270 @node Disabling backups, Disabling auto-save-mode, Documentation for etags, Common requests
2271 @section How do I disable backup files?
2272 @cindex Backups, disabling
2273 @cindex Disabling backups
2275 You probably don't want to do this, since backups are useful, especially
2276 when something goes wrong.
2278 To avoid seeing backup files (and other "uninteresting" files) in Dired,
2279 load @code{dired-x} by adding the following to your @file{.emacs} file:
2282 (add-hook 'dired-load-hook
2287 With @code{dired-x} loaded, @kbd{M-o} toggles omitting in each dired buffer.
2288 You can make omitting the default for new dired buffers by putting the
2289 following in your @file{.emacs}:
2292 (add-hook 'dired-mode-hook 'dired-omit-toggle)
2295 If you're tired of seeing backup files whenever you do an @samp{ls} at
2296 the Unix shell, try GNU @code{ls} with the @samp{-B} option. GNU
2297 @code{ls} is part of the GNU Fileutils package, available from
2298 @samp{ftp.gnu.org} and its mirrors (@pxref{Current GNU distributions}).
2300 To disable or change the way backups are made, @inforef{Backup Names, ,
2303 @cindex Backup files in a single directory
2304 Beginning with Emacs 21.1, you can control where Emacs puts backup files
2305 by customizing the variable @code{backup-directory-alist}. This
2306 variable's value specifies that files whose names match specific patters
2307 should have their backups put in certain directories. A typical use is
2308 to add the element @code{("." . @var{dir})} to force Emacs to put
2309 @strong{all} backup files in the directory @file{dir}.
2311 @node Disabling auto-save-mode, Going to a line by number, Disabling backups, Common requests
2312 @section How do I disable @code{auto-save-mode}?
2313 @cindex Disabling @code{auto-save-mode}
2315 @cindex Saving at frequent intervals
2317 You probably don't want to do this, since auto-saving is useful,
2318 especially when Emacs or your computer crashes while you are editing a
2321 Instead, you might want to change the variable
2322 @code{auto-save-interval}, which specifies how many keystrokes Emacs
2323 waits before auto-saving. Increasing this value forces Emacs to wait
2324 longer between auto-saves, which might annoy you less.
2326 You might also want to look into Sebastian Kremer's @code{auto-save}
2327 package, available from the Lisp Code Archive (@pxref{Packages that do not come
2329 package also allows you to place all auto-save files in one directory,
2330 such as @file{/tmp}.
2332 To disable or change how @code{auto-save-mode} works, @inforef{Auto
2335 @node Going to a line by number, Modifying pull-down menus, Disabling auto-save-mode, Common requests
2336 @section How can I go to a certain line given its number?
2337 @cindex Going to a line by number
2338 @cindex Compilation error messages
2339 @cindex Recompilation
2341 Are you sure you indeed need to go to a line by its number? Perhaps all
2342 you want is to display a line in your source file for which a compiler
2343 printed an error message? If so, compiling from within Emacs using the
2344 @kbd{M-x compile} and @kbd{M-x recompile} commands is a much more
2345 effective way of doing that. Emacs automatically intercepts the compile
2346 error messages, inserts them into a special buffer called
2347 @code{*compilation*}, and lets you visit the locus of each message in
2348 the source. Type @kbd{C-x `} to step through the offending lines one by
2349 one. Click @kbd{Mouse-2} or press @key{RET} on a message text in the
2350 @code{*compilation*} buffer to go to the line whose number is mentioned
2353 But if you indeed need to go to a certain text line, type @kbd{M-x
2354 goto-line @key{RET}}. Emacs will prompt you for the number of the line
2355 and go to that line.
2357 You can do this faster by invoking @code{goto-line} with a numeric
2358 argument that is the line's number. For example, @kbd{C-u 286 M-x
2359 goto-line @key{RET}} will jump to line number 286 in the current
2362 If you need to use this command frequently, you might consider binding
2363 it to a key. The following snippet, if added to your @file{~/.emacs}
2364 file, will bind the sequence @kbd{C-x g} to @code{goto-line}:
2367 (global-set-key "\C-xg" 'goto-line)
2371 @node Modifying pull-down menus, Deleting menus and menu options, Going to a line by number, Common requests
2372 @section How can I create or modify new pull-down menu options?
2373 @cindex Pull-down menus, creating or modifying
2374 @cindex Menus, creating or modifying
2375 @cindex Creating new menu options
2376 @cindex Modifying pull-down menus
2377 @cindex Menus and keymaps
2378 @cindex Keymaps and menus
2380 Each menu title (e.g., @samp{File}, @samp{Edit}, @samp{Buffers})
2381 represents a local or global keymap. Selecting a menu title with the
2382 mouse displays that keymap's non-nil contents in the form of a menu.
2384 So to add a menu option to an existing menu, all you have to do is add a
2385 new definition to the appropriate keymap. Adding a @samp{Forward Word}
2386 item to the @samp{Edit} menu thus requires the following Lisp code:
2389 (define-key global-map
2390 [menu-bar edit forward]
2391 '("Forward word" . forward-word))
2395 The first line adds the entry to the global keymap, which includes
2396 global menu bar entries. Replacing the reference to @code{global-map}
2397 with a local keymap would add this menu option only within a particular
2400 The second line describes the path from the menu-bar to the new entry.
2401 Placing this menu entry underneath the @samp{File} menu would mean
2402 changing the word @code{edit} in the second line to @code{file}.
2404 The third line is a cons cell whose first element is the title that will
2405 be displayed, and whose second element is the function that will be
2406 called when that menu option is invoked.
2408 To add a new menu, rather than a new option to an existing menu, we must
2409 define an entirely new keymap:
2412 (define-key global-map [menu-bar words]
2413 (cons "Words" (make-sparse-keymap "Words")))
2416 The above code creates a new sparse keymap, gives it the name
2417 @samp{Words}, and attaches it to the global menu bar. Adding the
2418 @samp{Forward Word} item to this new menu would thus require the
2422 (define-key global-map
2423 [menu-bar words forward]
2424 '("Forward word" . forward-word))
2428 Note that because of the way keymaps work, menu options are displayed
2429 with the more recently defined items at the top. Thus if you were to
2430 define menu options @samp{foo}, @samp{bar}, and @samp{baz} (in that
2431 order), the menu option @samp{baz} would appear at the top, and
2432 @samp{foo} would be at the bottom.
2434 One way to avoid this problem is to use the function @code{define-key-after},
2435 which works the same as @code{define-key}, but lets you modify where items
2436 appear. The following Lisp code would insert the @samp{Forward Word}
2437 item in the @samp{Edit} menu immediately following the @samp{Undo} item:
2441 (lookup-key global-map [menu-bar edit])
2443 '("Forward word" . forward-word)
2447 Note how the second and third arguments to @code{define-key-after} are
2448 different from those of @code{define-key}, and that we have added a new
2449 (final) argument, the function after which our new key should be
2452 To move a menu option from one position to another, simply evaluate
2453 @code{define-key-after} with the appropriate final argument.
2455 More detailed information---and more examples of how to create and
2456 modify menu options---are in the @cite{Emacs Lisp Reference Manual}, under
2457 ``Menu Keymaps''. (@xref{Emacs Lisp documentation}, for information on
2460 @node Deleting menus and menu options, Turning on syntax highlighting, Modifying pull-down menus, Common requests
2461 @section How do I delete menus and menu options?
2462 @cindex Deleting menus and menu options
2463 @cindex Menus, deleting
2465 The simplest way to remove a menu is to set its keymap to @samp{nil}.
2466 For example, to delete the @samp{Words} menu (@pxref{Modifying pull-down
2470 (define-key global-map [menu-bar words] nil)
2473 Similarly, removing a menu option requires redefining a keymap entry to
2474 @code{nil}. For example, to delete the @samp{Forward word} menu option
2475 from the @samp{Edit} menu (we added it in @ref{Modifying pull-down
2479 (define-key global-map [menu-bar edit forward] nil)
2482 @node Turning on syntax highlighting, Scrolling only one line, Deleting menus and menu options, Common requests
2483 @section How do I turn on syntax highlighting?
2484 @cindex Syntax highlighting
2485 @cindex @code{font-lock-mode}
2486 @cindex Highlighting based on syntax
2487 @cindex Colorizing text
2488 @cindex FAQ, @code{font-lock-mode}
2490 @code{font-lock-mode} is the standard way to have Emacs perform syntax
2491 highlighting in the current buffer. With @code{font-lock-mode} turned
2492 on, different types of text will appear in different colors. For
2493 instance, if you turn on @code{font-lock-mode} in a programming mode,
2494 variables will appear in one face, keywords in a second, and comments in
2497 @cindex hilit19 is deprecated
2498 Earlier versions of Emacs supported hilit19, a similar package. Use of
2499 hilit19 is now considered non-standard, although @file{hilit19.el} comes
2500 with the stock Emacs distribution. It is no longer maintained.
2502 To turn @code{font-lock-mode} on within an existing buffer, use @kbd{M-x
2503 font-lock-mode @key{RET}}.
2505 To automatically invoke @code{font-lock-mode} when a particular major
2506 mode is invoked, set the major mode's hook. For example, to fontify all
2507 @code{c-mode} buffers, add the following to your @file{.emacs} file:
2510 (add-hook 'c-mode-hook 'turn-on-font-lock)
2513 To automatically invoke @code{font-lock-mode} for all major modes, you
2514 can turn on @code{global-font-lock-mode} by including the following line
2515 in your @file{.emacs} file:
2518 (global-font-lock-mode 1)
2522 This instructs Emacs to turn on font-lock mode in those buffers for
2523 which a font-lock mode definition has been provided (in the variable
2524 @code{font-lock-global-modes}). If you edit a file in
2525 @code{pie-ala-mode}, and no font-lock definitions have been provided for
2526 @code{pie-ala} files, then the above setting will have no effect on that
2529 Highlighting a buffer with @code{font-lock-mode} can take quite a while,
2530 and cause an annoying delay in display, so several features exist to
2533 @cindex Just-In-Time syntax highlighting
2534 In Emacs 21 and later, turning on @code{font-lock-mode} automatically
2535 activates the new @dfn{Just-In-Time fontification} provided by
2536 @code{jit-lock-mode}. @code{jit-lock-mode} defers the fontification of
2537 portions of buffer until you actually need to see them, and can also
2538 fontify while Emacs is idle. This makes display of the visible portion
2539 of a buffer almost instantaneous. For details about customizing
2540 @code{jit-lock-mode}, type @kbd{C-h f jit-lock-mode @key{RET}}.
2542 @cindex Levels of syntax highlighting
2543 @cindex Decoration level, in @code{font-lock-mode}
2544 In versions of Emacs before 21, different levels of decoration are
2545 available, from slight to gaudy. More decoration means you need to wait
2546 more time for a buffer to be fontified (or a faster machine). To
2547 control how decorated your buffers should become, set the value of
2548 @code{font-lock-maximum-decoration} in your @file{.emacs} file, with a
2549 @code{nil} value indicating default (usually minimum) decoration, and a
2550 @code{t} value indicating the maximum decoration. For the gaudiest
2551 possible look, then, include the line
2554 (setq font-lock-maximum-decoration t)
2558 in your @file{.emacs} file. You can also set this variable such that
2559 different modes are highlighted in a different ways; for more
2560 information, see the documentation for
2561 @code{font-lock-maximum-decoration} with @kbd{C-h v} (or @kbd{M-x
2562 describe-variable @key{RET}}).
2564 @cindex Lazy font-lock
2565 You might also want to investigate @code{fast-lock-mode} and
2566 @code{lazy-lock-mode}, versions of @code{font-lock-mode} that speed up
2567 highlighting. These are the alternatives for @code{jit-lock-mode} in
2568 versions of Emacs before 21.1. The advantage of @code{lazy-lock-mode}
2569 is that it only fontifies buffers when certain conditions are met, such
2570 as after a certain amount of idle time, or after you have finished
2571 scrolling through text. See the documentation for @code{lazy-lock-mode}
2572 by typing @kbd{C-h f @code{lazy-lock-mode}} (@kbd{M-x describe-function
2573 @key{RET} lazy-lock-mode @key{RET}}).
2575 Also see the documentation for the function @code{font-lock-mode},
2576 available by typing @kbd{C-h f font-lock-mode} (@kbd{M-x
2577 describe-function @key{RET} font-lock-mode @key{RET}}).
2579 For more information on font-lock mode, take a look at the
2580 @code{font-lock-mode} FAQ, maintained by
2581 @email{jari.aalto@@ntc.nokia.com, Jari Aalto} at
2583 @uref{ftp://cs.uta.fi/pub/ssjaaa/ema-font.gui}
2585 To print buffers with the faces (i.e., colors and fonts) intact, use
2586 @kbd{M-x ps-print-buffer-with-faces} or @kbd{M-x
2587 ps-print-region-with-faces}. You will need a way to send text to a
2588 PostScript printer, or a PostScript interpreter such as Ghostscript;
2589 consult the documentation of the variables @code{ps-printer-name},
2590 @code{ps-lpr-command}, and @code{ps-lpr-switches} for more details.
2592 @node Scrolling only one line, Replacing highlighted text, Turning on syntax highlighting, Common requests
2593 @section How can I force Emacs to scroll only one line when I move past the bottom of the screen?
2594 @cindex Scrolling only one line
2595 @cindex Reducing the increment when scrollng
2597 Place the following Lisp form in your @file{.emacs} file:
2600 (setq scroll-step 1)
2603 @inforef{Scrolling, Scrolling, emacs}.
2605 @node Replacing highlighted text, Editing MS-DOS files, Scrolling only one line, Common requests
2606 @section How can I replace highlighted text with what I type?
2607 @cindex @code{delete-selection-mode}
2608 @cindex Replacing highlighted text
2609 @cindex Highlighing and replacing text
2611 Use @code{delete-selection-mode}, which you can start automatically by
2612 placing the following Lisp form in your @file{.emacs} file:
2615 (delete-selection-mode t)
2618 According to the documentation string for @code{delete-selection-mode}
2619 (which you can read using @kbd{M-x describe-function @key{RET}
2620 delete-selection-mode @key{RET}}):
2623 When ON, typed text replaces the selection if the selection is active.
2624 When OFF, typed text is just inserted at point.
2627 This mode also allows you to delete (not kill) the highlighted region by
2630 @node Editing MS-DOS files, Filling paragraphs with a single space, Replacing highlighted text, Common requests
2631 @section How can I edit MS-DOS files using Emacs?
2632 @cindex Editing MS-DOS files
2633 @cindex MS-DOS files, editing
2634 @cindex Microsoft files, editing
2635 @cindex Windows files, editing
2637 As of Emacs 20, detection and handling of MS-DOS (and Windows) files is
2638 performed transparently. You can open MS-DOS files on a Unix system,
2639 edit it, and save it without having to worry about the file format.
2641 When editing an MS-DOS style file, the mode line will indicate that it
2642 is a DOS file. On Unix and GNU/Linux systems, and also on a Macintosh,
2643 the string @samp{(DOS)} will appear near the left edge of the mode line;
2644 on DOS and Windows, where the DOS end-of-line (EOL) format is the
2645 default, a backslash (@samp{\}) will appear in the mode line.
2647 If you are running a version of Emacs before 20.1, get @code{crypt++}
2648 from the Emacs Lisp Archive (@pxref{Packages that do not come with
2649 Emacs}). Among other things, @code{crypt++} transparently modifies
2650 MS-DOS files as they are loaded and saved, allowing you to ignore the
2651 different conventions that Unix and MS-DOS have for delineating the end
2654 @node Filling paragraphs with a single space, Escape sequences in shell output, Editing MS-DOS files, Common requests
2655 @section How can I tell Emacs to fill paragraphs with a single space after each period?
2656 @cindex One space following periods
2657 @cindex Single space following periods
2658 @cindex Periods, one space following
2660 @email{ulm@@vsnhd1.cern.ch, Ulrich Mueller} suggests adding the
2661 following two lines to your @file{.emacs} file:
2664 (setq sentence-end "[.?!][]\"')@}]*\\($\\|[ \t]\\)[ \t\n]*")
2665 (setq sentence-end-double-space nil)
2668 @node Escape sequences in shell output, , Filling paragraphs with a single space, Common requests
2669 @section Why do I get these strange escape sequences when I run
2670 @code{ls} from the Shell mode?
2671 @cindex Escape sequences in @code{ls} output
2672 @cindex @code{ls} in Shell mode
2674 This happens because @code{ls} is aliased to @samp{ls --color} in your
2675 shell init file. You have two alternatives to solve this:
2679 Make the alias conditioned on the @code{EMACS} variable in the
2680 environment. When Emacs runs a subsidiary shell, it exports the
2681 @code{EMACS} variable with the value @code{t} to that shell. You can
2682 unalias @code{ls} when that happens, thus limiting the alias to your
2683 interactive sessions.
2686 Install the @code{ansi-color} package (bundled with Emacs 21.1 and
2687 later), which converts these ANSI escape sequences into colors.
2690 @c ------------------------------------------------------------
2691 @node Bugs and problems, Compiling and installing Emacs, Common requests, Top
2692 @chapter Bugs and problems
2693 @cindex Bugs and problems
2696 * Problems with very large files::
2697 * ^M in the shell buffer::
2698 * Shell process exits abnormally::
2699 * Problems with Shell Mode on MS-Windows::
2700 * Termcap/Terminfo entries for Emacs::
2701 * Spontaneous entry into isearch-mode::
2702 * Problems talking to certain hosts::
2703 * Errors with init files::
2704 * Emacs ignores X resources::
2705 * Emacs ignores frame parameters::
2706 * Emacs takes a long time to visit files::
2707 * Editing files with $ in the name::
2708 * Shell mode loses the current directory::
2709 * Security risks with Emacs::
2710 * Dired claims that no file is on this line::
2713 @node Problems with very large files, ^M in the shell buffer, Bugs and problems, Bugs and problems
2714 @section Does Emacs have problems with files larger than 8 megabytes?
2715 @cindex Very large files, opening
2716 @cindex Large files, opening
2717 @cindex Opening very large files
2718 @cindex Maximum file size
2719 @cindex Files, maximum size
2721 Old versions (i.e., anything before 19.29) of Emacs had problems editing
2722 files larger than 8 megabytes. As of version 19.29, the maximum buffer
2723 size is at least 2^27-1, or 134,217,727 bytes, or 132 MBytes. Emacs 20
2724 can be compiled on some 64-bit systems in a way that enlarges the buffer
2725 size up to 576,460,752,303,423,487 bytes, or 549,755,813 GBytes.
2727 If you are using a version of Emacs older than 19.29 and cannot upgrade,
2728 you will have to recompile. @email{lnz@@lucid.com, Leonard N. Zubkoff}
2729 suggests putting the following two lines in @file{src/config.h} before
2730 compiling Emacs to allow for 26-bit integers and pointers (and thus file
2731 sizes of up to 33,554,431 bytes):
2735 #define GCTYPEBITS 5
2739 This method may result in "ILLEGAL DATATYPE" and other random errors on
2742 @email{daveg@@csvax.cs.caltech.edu, David Gillespie} explains how this
2743 problems crops up; while his numbers are true only for pre-19.29
2744 versions of Emacs, the theory remains the same with current versions.
2747 Emacs is largely written in a dialect of Lisp; Lisp is a freely-typed
2748 language in the sense that you can put any value of any type into any
2749 variable, or return it from a function, and so on. So each value
2750 must carry a @dfn{tag} along with it identifying what kind of thing it
2751 is, e.g., integer, pointer to a list, pointer to an editing buffer, and
2752 so on. Emacs uses standard 32-bit integers for data objects, taking the
2753 top 8 bits for the tag and the bottom 24 bits for the value. So
2754 integers (and pointers) are somewhat restricted compared to true C
2755 integers and pointers.
2758 @node ^M in the shell buffer, Shell process exits abnormally, Problems with very large files, Bugs and problems
2759 @section How do I get rid of @samp{^M} or echoed commands in my shell buffer?
2760 @cindex Shell buffer, echoed commands and @samp{^M} in
2761 @cindex Echoed commands in @code{shell-mode}
2763 Try typing @kbd{M-x shell-strip-ctrl-m @key{RET}} while in @code{shell-mode} to
2764 make them go away. If that doesn't work, you have several options:
2766 For @code{tcsh}, put this in your @file{.cshrc} (or @file{.tcshrc})
2771 if ("$EMACS" == t) then
2772 if ($?tcsh) unset edit
2778 Or put this in your @file{.emacs_tcsh} file:
2785 Alternatively, use @code{csh} in your shell buffers instead of
2786 @code{tcsh}. One way is:
2789 (setq explicit-shell-file-name "/bin/csh")
2793 and another is to do this in your @file{.cshrc} (or @file{.tcshrc})
2797 setenv ESHELL /bin/csh
2801 (You must start Emacs over again with the environment variable properly
2802 set for this to take effect.)
2804 You can also set the @code{ESHELL} environment variable in Emacs Lisp
2805 with the following Lisp form,
2808 (setenv "ESHELL" "/bin/csh")
2811 The above solutions try to prevent the shell from producing the
2812 @samp{^M} characters in the first place. If this is not possible
2813 (e.g., if you use a Windows shell), you can get Emacs to remove these
2814 characters from the buffer by adding this to your @file{.emacs} init
2818 (add-hook 'comint-output-filter-functions 'shell-strip-ctrl-m)
2821 On a related note: If your shell is echoing your input line in the shell
2822 buffer, you might want to try the following command in your shell
2826 stty -icrnl -onlcr -echo susp ^Z
2829 @node Shell process exits abnormally, Problems with Shell Mode on MS-Windows, ^M in the shell buffer, Bugs and problems
2830 @section Why do I get "Process shell exited abnormally with code 1"?
2831 @cindex Abnormal exits from @code{shell-mode}
2832 @cindex @code{shell-mode} exits
2833 @cindex Process shell exited
2835 The most likely reason for this message is that the @samp{env} program
2836 is not properly installed. Compile this program for your architecture,
2837 and install it with @samp{a+x} permission in the architecture-dependent
2838 Emacs program directory. (You can find what this directory is at your
2839 site by inspecting the value of the variable @code{exec-directory} by
2840 typing @kbd{C-h v exec-directory @key{RET}}.)
2842 You should also check for other programs named @samp{env} in your path
2843 (e.g., SunOS has a program named @file{/usr/bin/env}). We don't
2844 understand why this can cause a failure and don't know a general
2845 solution for working around the problem in this case.
2847 The @samp{make clean} command will remove @samp{env} and other vital
2848 programs, so be careful when using it.
2850 It has been reported that this sometimes happened when Emacs was started
2851 as an X client from an xterm window (i.e., had a controlling tty) but the
2852 xterm was later terminated.
2854 See also @samp{PROBLEMS} (in the @file{etc} subdirectory of the
2855 top-level directory when you unpack the Emacs source) for other
2856 possible causes of this message.
2858 @node Problems with Shell Mode on MS-Windows, Termcap/Terminfo entries for Emacs, Shell process exits abnormally, Bugs and problems
2859 @section Why do I get an error message when I try to run @kbd{M-x shell}?
2861 @cindex Shell Mode, and MS-Windows
2862 @cindex @code{explicit-shell-file-name}
2863 On MS-Windows, this might happen because Emacs tries to look for the
2864 shell in a wrong place. The default file name @file{/bin/sh} is
2865 usually incorrect for non-Unix systems. If you know where your shell
2866 executable is, set the variable @code{explicit-shell-file-name} in
2867 your @file{.emacs} file to point to its full file name, like this:
2870 (setq explicit-shell-file-name "d:/shells/bash.exe")
2873 If you don't know what shell does Emacs use, try the @kbd{M-!}
2874 command; if that works, put the following line into your
2878 (setq explicit-shell-file-name shell-file-name)
2881 @cindex Antivirus programs, and Shell Mode
2882 Some people have trouble with Shell Mode because of intrusive
2883 antivirus software; disabling the resident antivirus program solves
2884 the problems in those cases.
2886 @node Termcap/Terminfo entries for Emacs, Spontaneous entry into isearch-mode, Problems with Shell Mode on MS-Windows, Bugs and problems
2887 @section Where is the termcap/terminfo entry for terminal type "emacs"?
2890 @cindex Emacs entries for termcap/terminfo
2892 The termcap entry for terminal type @samp{emacs} is ordinarily put in
2893 the @samp{TERMCAP} environment variable of subshells. It may help in
2894 certain situations (e.g., using rlogin from shell buffer) to add an
2895 entry for @samp{emacs} to the system-wide termcap file. Here is a
2896 correct termcap entry for @samp{emacs}:
2902 To make a terminfo entry for @samp{emacs}, use @code{tic} or
2903 @code{captoinfo}. You need to generate
2904 @file{/usr/lib/terminfo/e/emacs}. It may work to simply copy
2905 @file{/usr/lib/terminfo/d/dumb} to @file{/usr/lib/terminfo/e/emacs}.
2907 Having a termcap/terminfo entry will not enable the use of full screen
2908 programs in shell buffers. Use @kbd{M-x terminal-emulator} for that
2911 A workaround to the problem of missing termcap/terminfo entries is to
2912 change terminal type @samp{emacs} to type @samp{dumb} or @samp{unknown}
2913 in your shell start up file. @code{csh} users could put this in their
2914 @file{.cshrc} files:
2917 if ("$term" == emacs) set term=dumb
2920 @node Spontaneous entry into isearch-mode, Problems talking to certain hosts, Termcap/Terminfo entries for Emacs, Bugs and problems
2921 @section Why does Emacs spontaneously start displaying "I-search:" and beeping?
2922 @cindex Spontaneous entry into isearch-mode
2923 @cindex isearch-mode, spontaneous entry into
2924 @cindex Beeping without obvious reason
2926 Your terminal (or something between your terminal and the computer) is
2927 sending @kbd{C-s} and @kbd{C-q} for flow control, and Emacs is receiving
2928 these characters and interpreting them as commands. (The @kbd{C-s}
2929 character normally invokes the @code{isearch-forward} command.) For
2930 possible solutions, see @ref{Handling C-s and C-q with flow control}.
2932 @node Problems talking to certain hosts, Errors with init files, Spontaneous entry into isearch-mode, Bugs and problems
2933 @section Why can't Emacs talk to certain hosts (or certain hostnames)?
2934 @cindex Hosts, Emacs cannot talk to
2935 @cindex @code{gethostbyname}, problematic version
2937 The problem may be that Emacs is linked with a wimpier version of
2938 @code{gethostbyname} than the rest of the programs on the machine. This
2939 is often manifested as a message on startup of ``X server not responding.
2940 Check your @samp{DISPLAY} environment variable.'' or a message of
2941 ``Unknown host'' from @code{open-network-stream}.
2943 On a Sun, this may be because Emacs had to be linked with the static C
2944 library. The version of @code{gethostbyname} in the static C library
2945 may only look in @file{/etc/hosts} and the NIS (YP) maps, while the
2946 version in the dynamic C library may be smart enough to check DNS in
2947 addition to or instead of NIS. On a Motorola Delta running System V
2948 R3.6, the version of @code{gethostbyname} in the standard library works,
2949 but the one that works with NIS doesn't (the one you get with -linet).
2950 Other operating systems have similar problems.
2957 Explicitly add the host you want to communicate with to @file{/etc/hosts}.
2960 Relink Emacs with this line in @file{src/config.h}:
2963 #define LIBS_SYSTEM -lresolv
2967 Replace @code{gethostbyname} and friends in @file{libc.a} with more
2968 useful versions such as the ones in @file{libresolv.a}. Then relink
2972 If you are actually running NIS, make sure that @code{ypbind} is
2973 properly told to do DNS lookups with the correct command line switch.
2977 @node Errors with init files, Emacs ignores X resources, Problems talking to certain hosts, Bugs and problems
2978 @section Why does Emacs say "Error in init file"?
2979 @cindex Error in @file{.emacs}
2980 @cindex Error in init file
2981 @cindex Init file, errors in
2982 @cindex @file{.emacs} file, errors in
2983 @cindex Debugging @file{.emacs} file
2985 An error occurred while loading either your @file{.emacs} file or the
2986 system-wide file @file{lisp/default.el}. Emacs 21.1 and later pops the
2987 @file{*Messages*} buffer, and puts there some additional information
2988 about the error, to provide some hints for debugging.
2990 For information on how to debug your @file{.emacs} file, see
2991 @ref{Debugging a customization file}.
2993 It may be the case that you need to load some package first, or use a
2994 hook that will be evaluated after the package is loaded. A common case
2995 of this is explained in @ref{Terminal setup code works after Emacs has
2998 @node Emacs ignores X resources, Emacs ignores frame parameters, Errors with init files, Bugs and problems
2999 @section Why does Emacs ignore my X resources (my .Xdefaults file)?
3000 @cindex X resources being ignored
3001 @cindex Ignored X resources
3002 @cindex @file{.Xdefaults}
3004 As of version 19, Emacs searches for X resources in the files specified
3005 by the following environment variables:
3009 @item @code{XFILESEARCHPATH}
3010 @item @code{XUSERFILESEARCHPATH}
3011 @item @code{XAPPLRESDIR}
3015 This emulates the functionality provided by programs written using the
3018 @code{XFILESEARCHPATH} and @code{XUSERFILESEARCHPATH} should be a list
3019 of file names separated by colons. @code{XAPPLRESDIR} should be a list
3020 of directory names separated by colons.
3022 Emacs searches for X resources:
3027 specified on the command line, with the @samp{-xrm RESOURCESTRING} option,
3030 then in the value of the @samp{XENVIRONMENT} environment variable,
3035 or if that is unset, in the file named
3036 @file{~/.Xdefaults-@var{hostname}} if it exists (where @var{hostname} is
3037 the name of the machine Emacs is running on),
3042 then in the screen-specific and server-wide resource properties provided
3048 or if those properties are unset, in the file named @file{~/.Xdefaults}
3054 then in the files listed in @samp{XUSERFILESEARCHPATH},
3059 or in files named @file{@var{lang}/Emacs} in directories listed in
3060 @samp{XAPPLRESDIR} (where @var{lang} is the value of the @code{LANG}
3061 environment variable), if the @samp{LANG} environment variable is set,
3063 or in files named Emacs in the directories listed in @samp{XAPPLRESDIR}
3065 or in @file{~/@var{lang}/Emacs} (if the @code{LANG} environment variable
3068 or in @file{~/Emacs},
3073 then in the files listed in @code{XFILESEARCHPATH}.
3077 @node Emacs ignores frame parameters, Emacs takes a long time to visit files, Emacs ignores X resources, Bugs and problems
3078 @section Why don't my customizations of the frame parameters work?
3079 @cindex Frame parameters
3081 This probably happens because you have set the frame parameters in the
3082 variable @code{initial-frame-alist}. That variable holds parameters
3083 used only for the first frame created when Emacs starts. To customize
3084 the parameters of all frames, change the variable
3085 @code{default-frame-alist} instead.
3087 These two variables exist because many users customize the initial frame
3088 in a special way. For example, you could determine the position and
3089 size of the initial frame, but would like to control the geometry of the
3090 other frames by individually positioning each one of them.
3093 @node Emacs takes a long time to visit files, Editing files with $ in the name, Emacs ignores frame parameters, Bugs and problems
3094 @section Why does Emacs take 20 seconds to visit a file?
3095 @cindex Visiting files takes a long time
3096 @cindex Delay when visiting files
3097 @cindex Files, take a long time to visit
3099 Old versions of Emacs (i.e., versions before Emacs 20.x) often
3100 encountered this when the master lock file, @file{!!!SuperLock!!!}, has
3101 been left in the lock directory somehow. Delete it.
3103 @email{meuer@@geom.umn.edu, Mark Meuer} says that NeXT NFS has a bug
3104 where an exclusive create succeeds but returns an error status. This
3105 can cause the same problem. Since Emacs's file locking doesn't work
3106 over NFS anyway, the best solution is to recompile Emacs with
3107 @code{CLASH_DETECTION} undefined.
3109 @node Editing files with $ in the name, Shell mode loses the current directory, Emacs takes a long time to visit files, Bugs and problems
3110 @section How do I edit a file with a @samp{$} in its name?
3111 @cindex Editing files with @samp{$} in the name
3112 @cindex @samp{$} in file names
3113 @cindex File names containing @samp{$}, editing
3115 When entering a file name in the minibuffer, Emacs will attempt to expand
3116 a @samp{$} followed by a word as an environment variable. To suppress
3117 this behavior, type @kbd{$$} instead.
3119 @node Shell mode loses the current directory, Security risks with Emacs, Editing files with $ in the name, Bugs and problems
3120 @section Why does shell mode lose track of the shell's current directory?
3121 @cindex Current directory and @code{shell-mode}
3122 @cindex @code{shell-mode} and current directory
3123 @cindex Directory, current in @code{shell-mode}
3125 Emacs has no way of knowing when the shell actually changes its
3126 directory. This is an intrinsic limitation of Unix. So it tries to
3127 guess by recognizing @samp{cd} commands. If you type @kbd{cd} followed
3128 by a directory name with a variable reference (@kbd{cd $HOME/bin}) or
3129 with a shell metacharacter (@kbd{cd ../lib*}), Emacs will fail to
3130 correctly guess the shell's new current directory. A huge variety of
3131 fixes and enhancements to shell mode for this problem have been written
3132 to handle this problem. Check the Lisp Code Directory (@pxref{Finding a
3133 package with particular functionality}).
3135 You can tell Emacs the shell's current directory with the command
3138 @node Security risks with Emacs, Dired claims that no file is on this line, Shell mode loses the current directory, Bugs and problems
3139 @section Are there any security risks in Emacs?
3140 @cindex Security with Emacs
3141 @cindex @samp{movemail} and security
3142 @cindex @code{file-local-variable} and security
3143 @cindex Synthetic X events and security
3144 @cindex X events and security
3149 The @file{movemail} incident. (No, this is not a risk.)
3151 In his book @cite{The Cuckoo's Egg}, Cliff Stoll describes this in
3152 chapter 4. The site at LBL had installed the @file{/etc/movemail}
3153 program setuid root. (As of version 19, @file{movemail} is in your
3154 architecture-specific directory; type @kbd{C-h v exec-directory
3155 @key{RET}} to see what it is.) Since @code{movemail} had not been
3156 designed for this situation, a security hole was created and users could
3157 get root privileges.
3159 @code{movemail} has since been changed so that this security hole will
3160 not exist, even if it is installed setuid root. However,
3161 @code{movemail} no longer needs to be installed setuid root, which
3162 should eliminate this particular risk.
3164 We have heard unverified reports that the 1988 Internet worm took
3165 advantage of this configuration problem.
3168 The @code{file-local-variable} feature. (Yes, a risk, but easy to
3171 There is an Emacs feature that allows the setting of local values for
3172 variables when editing a file by including specially formatted text near
3173 the end of the file. This feature also includes the ability to have
3174 arbitrary Emacs Lisp code evaluated when the file is visited.
3175 Obviously, there is a potential for Trojan horses to exploit this
3178 Emacs 18 allowed this feature by default; users could disable it by
3179 setting the variable @code{inhibit-local-variables} to a non-nil value.
3181 As of Emacs 19, Emacs has a list of local variables that create a
3182 security risk. If a file tries to set one of them, it asks the user to
3183 confirm whether the variables should be set. You can also tell Emacs
3184 whether to allow the evaluation of Emacs Lisp code found at the bottom
3185 of files by setting the variable @code{enable-local-eval}.
3187 For more information, @inforef{File Variables, File Variables, emacs}.
3190 Synthetic X events. (Yes, a risk; use @samp{MIT-MAGIC-COOKIE-1} or
3193 Emacs accepts synthetic X events generated by the @code{SendEvent}
3194 request as though they were regular events. As a result, if you are
3195 using the trivial host-based authentication, other users who can open X
3196 connections to your X workstation can make your Emacs process do
3197 anything, including run other processes with your privileges.
3199 The only fix for this is to prevent other users from being able to open
3200 X connections. The standard way to prevent this is to use a real
3201 authentication mechanism, such as @samp{MIT-MAGIC-COOKIE-1}. If using
3202 the @code{xauth} program has any effect, then you are probably using
3203 @samp{MIT-MAGIC-COOKIE-1}. Your site may be using a superior
3204 authentication method; ask your system administrator.
3206 If real authentication is not a possibility, you may be satisfied by
3207 just allowing hosts access for brief intervals while you start your X
3208 programs, then removing the access. This reduces the risk somewhat by
3209 narrowing the time window when hostile users would have access, but
3210 @emph{does not eliminate the risk}.
3212 On most computers running Unix and X, you enable and disable
3213 access using the @code{xhost} command. To allow all hosts access to
3221 at the shell prompt, which (on an HP machine, at least) produces the
3225 access control disabled, clients can connect from any host
3228 To deny all hosts access to your X server (except those explicitly
3229 allowed by name), use
3235 On the test HP computer, this command generated the following message:
3238 access control enabled, only authorized clients can connect
3243 @node Dired claims that no file is on this line, , Security risks with Emacs, Bugs and problems
3244 @section Dired says, "no file on this line" when I try to do something.
3245 @cindex Dired does not see a file
3247 @c FIXME: I think this is fixed in Emacs 21, but I didn't have time to
3249 Chances are you're using a localized version of Unix that doesn't use US
3250 date format in dired listings. You can check this by looking at dired
3251 listings or by typing @kbd{ls -l} to a shell and looking at the dates that
3254 Dired uses a regular expression to find the beginning of a file name.
3255 In a long Unix-style directory listing (@samp{ls -l}), the file name
3256 starts after the date. The regexp has thus been written to look for the
3257 date, the format of which can vary on non-US systems.
3259 There are two approaches to solving this. The first one involves
3260 setting things up so that @samp{ls -l} outputs US date format. This can
3261 be done by setting the locale. See your OS manual for more information.
3263 The second approach involves changing the regular expression used by
3264 dired, @code{dired-move-to-filename-regexp}.
3266 @c ------------------------------------------------------------
3267 @node Compiling and installing Emacs, Finding Emacs and related packages, Bugs and problems, Top
3268 @chapter Compiling and installing Emacs
3269 @cindex Compiling and installing Emacs
3272 * Installing Emacs::
3274 * Problems building Emacs::
3275 * Linking with -lX11 fails::
3278 @node Installing Emacs, Updating Emacs, Compiling and installing Emacs, Compiling and installing Emacs
3279 @section How do I install Emacs?
3280 @cindex Installing Emacs
3281 @cindex Unix systems, installing Emacs on
3282 @cindex Downloading and installing Emacs
3283 @cindex Retrieving and installing Emacs
3284 @cindex Building Emacs from source
3285 @cindex Source code, building Emacs from
3286 @cindex Unpacking and installing Emacs
3288 This answer is meant for users of Unix and Unix-like systems. Users of
3289 other operating systems should see the series of questions beginning
3290 with @ref{Emacs for MS-DOS}, which describe where to get non-Unix source
3291 and binaries, and how to install Emacs on those systems.
3293 For Unix and Unix-like systems, the easiest way is often to compile it
3294 from scratch. You will need:
3299 Emacs sources. @xref{Current GNU distributions}, for a list of ftp sites
3300 that make them available. On @file{ftp.gnu.org}, the main GNU
3301 distribution site, sources are available as
3303 @uref{ftp://ftp.gnu.org/pub/gnu/emacs/emacs-@value{VER}.tar.gz}
3305 The above will obviously change as new versions of Emacs come out. For
3306 instance, when Emacs 21.42 is released, it will most probably be
3309 @uref{ftp://ftp.gnu.org/pub/gnu/emacs/emacs-21.42.tar.gz}
3311 Again, you should use one of the GNU mirror sites (see @ref{Current GNU
3312 distributions}, and adjust the URL accordingly) so as to reduce load on
3316 @code{gzip}, the GNU compression utility. You can get @code{gzip} via
3317 anonymous ftp at mirrors of @file{ftp.gnu.org} sites; it should compile
3318 and install without much trouble on most systems. Once you have
3319 retrieved the Emacs sources, you will probably be able to uncompress
3320 them with the command
3323 gunzip --verbose emacs-@value{VER}.tar.gz
3327 changing the Emacs version (@value{VER}), as necessary. Once
3328 @code{gunzip} has finished doing its job, a file by the name of
3329 @file{emacs-@value{VER}.tar} should be in your build directory.
3332 @code{tar}, the @dfn{tape archiving} program, which moves multiple files
3333 into and out of archive files, or @dfn{tarfiles}. All of the files
3334 comprising the Emacs source come in a single tarfile, and must be
3335 extracted using @code{tar} before you can build Emacs. Typically, the
3336 extraction command would look like
3339 tar -xvvf emacs-@value{VER}.tar
3343 The @samp{x} indicates that we want to extract files from this tarfile,
3344 the two @samp{v}s force verbose output, and the @samp{f} tells
3345 @code{tar} to use a disk file, rather than one on the tape drive.
3347 If you're using GNU @code{tar} (available at mirrors of
3348 @file{ftp.gnu.org}), you can combine this step and the previous one by
3352 tar -zxvvf emacs-@value{VER}.tar.gz
3356 The additional @samp{z} at the beginning of the options list tells GNU
3357 @code{tar} to uncompress the file with @code{gunzip} before extracting
3358 the tarfile's components.
3362 At this point, the Emacs sources (all 70+ megabytes of them) should be
3363 sitting in a directory called @file{emacs-@value{VER}}. On most common
3364 Unix and Unix-like systems, you should be able to compile Emacs (with X
3365 Window system support) with the following commands:
3368 cd emacs-@value{VER} # change directory to emacs-@value{VER}
3369 ./configure # configure Emacs for your particular system
3370 make # use Makefile to build components, then Emacs
3373 If the @code{make} completes successfully, the odds are fairly good that
3374 the build has gone well. (@xref{Problems building Emacs}, if you weren't
3377 By default, Emacs is installed in the following directories:
3380 @item /usr/local/bin
3383 @item /usr/local/share/emacs/@value{VER}
3384 Lisp code and support files.
3386 @item /usr/local/info
3390 To install files in those default directories, become the superuser and
3397 Note that @samp{make install} will overwrite @file{/usr/local/bin/emacs}
3398 and any Emacs Info files that might be in @file{/usr/local/info}.
3400 Much more verbose instructions (with many more hints and suggestions)
3401 come with the Emacs sources, in the file @file{INSTALL}.
3403 @node Updating Emacs, Problems building Emacs, Installing Emacs, Compiling and installing Emacs
3404 @section How do I update Emacs to the latest version?
3405 @cindex Updating Emacs
3407 @xref{Installing Emacs}, and follow the instructions there for
3410 Most files are placed in version-specific directories. Emacs
3411 @value{VER}, for instance, places files in
3412 @file{/usr/local/share/emacs/@value{VER}}.
3414 Upgrading should overwrite only, @file{/usr/local/bin/emacs} (the Emacs
3415 binary) and documentation in @file{/usr/local/info}. Back up these
3416 files before you upgrade, and you shouldn't have too much trouble.
3418 @node Problems building Emacs, Linking with -lX11 fails, Updating Emacs, Compiling and installing Emacs
3419 @section What should I do if I have trouble building Emacs?
3420 @cindex Problems building Emacs
3421 @cindex Errors when building Emacs
3423 First look in the file @file{etc/PROBLEMS} (where you unpack the Emacs
3424 source) to see if there is already a solution for your problem. Next,
3425 look for other questions in this FAQ that have to do with Emacs
3426 installation and compilation problems.
3428 If you'd like to have someone look at your problem and help solve it,
3429 see @ref{Help installing Emacs}.
3431 If you cannot find a solution in the documentation, send a message to
3432 @email{bug-gnu-emacs@@gnu.org}.
3434 Please don't post it to @uref{news:gnu.emacs.help} or send e-mail to
3435 @email{help-gnu-emacs@@gnu.org}. For further guidelines, see
3436 @ref{Guidelines for newsgroup postings} and @ref{Reporting bugs}.
3438 @node Linking with -lX11 fails, , Problems building Emacs, Compiling and installing Emacs
3439 @section Why does linking Emacs with -lX11 fail?
3440 @cindex Linking with -lX11 fails
3441 @cindex lX11, linking fails with
3443 Emacs needs to be linked with the static version of the X11 library,
3444 @file{libX11.a}. This may be missing.
3446 On OpenWindows, you may need to use @code{add_services} to add the
3447 "OpenWindows Programmers" optional software category from the CD-ROM.
3449 On HP-UX 8.0, you may need to run @code{update} again to load the
3450 X11-PRG ``fileset''. This may be missing even if you specified ``all
3451 filesets'' the first time. If @file{libcurses.a} is missing, you may
3452 need to load the ``Berkeley Development Option.''
3454 @email{zoo@@armadillo.com, David Zuhn} says that MIT X builds shared
3455 libraries by default, and only shared libraries, on those platforms that
3456 support them. These shared libraries can't be used when undumping
3457 @code{temacs} (the last stage of the Emacs build process). To get
3458 regular libraries in addition to shared libraries, add this to
3462 #define ForceNormalLib YES
3465 Other systems may have similar problems. You can always define
3466 @code{CANNOT_DUMP} and link with the shared libraries instead.
3468 @cindex X Menus don't work
3469 To get the Xmenu stuff to work, you need to find a copy of MIT's
3472 @c ------------------------------------------------------------
3473 @node Finding Emacs and related packages, Major packages and programs, Compiling and installing Emacs, Top
3474 @chapter Finding Emacs and related packages
3475 @cindex Finding Emacs and related packages
3478 * Finding Emacs on the Internet::
3479 * Finding a package with particular functionality::
3480 * Packages that do not come with Emacs::
3481 * Submitting to the Emacs Lisp Archive::
3482 * Current GNU distributions::
3483 * Difference between Emacs and XEmacs::
3484 * Emacs for MS-DOS::
3485 * Emacs for Windows::
3487 * Emacs for Atari ST::
3488 * Emacs for the Amiga ::
3489 * Emacs for NeXTSTEP::
3490 * Emacs for Apple computers::
3491 * Emacs for VMS and DECwindows::
3492 * Modes for various languages::
3493 * Translating names to IP addresses::
3496 @node Finding Emacs on the Internet, Finding a package with particular functionality, Finding Emacs and related packages, Finding Emacs and related packages
3497 @section Where can I get Emacs on the net (or by snail mail)?
3498 @cindex Finding Emacs on the Internet
3499 @cindex Snail mail, ordering Emacs via
3500 @cindex Postal service, ordering Emacs via
3501 @cindex Distribution, retrieving Emacs
3502 @cindex Internet, retreiving from
3504 Look in the files @file{etc/DISTRIB} and @file{etc/FTP} for information
3505 on nearby archive sites and @file{etc/ORDERS} for mail orders. If you
3506 don't already have Emacs, see @ref{Informational files for Emacs}, for how
3509 @xref{Installing Emacs}, for information on how to obtain and build the latest
3510 version of Emacs, and see @ref{Current GNU distributions}, for a list of
3511 archive sites that make GNU software available.
3513 @node Finding a package with particular functionality, Packages that do not come with Emacs, Finding Emacs on the Internet, Finding Emacs and related packages
3514 @section How do I find a Emacs Lisp package that does XXX?
3515 @cindex Package, finding
3516 @cindex Finding an Emacs Lisp package
3517 @cindex Functionality, finding a particular package
3519 First of all, you should check to make sure that the package isn't
3520 already available. For example, typing @kbd{M-x apropos @key{RET}
3521 wordstar @key{RET}} lists all functions and variables containing the
3522 string @samp{wordstar}.
3524 It is also possible that the package is on your system, but has not been
3525 loaded. To see which packages are available for loading, look through
3526 your computer's lisp directory (@pxref{File-name conventions}). The Lisp
3527 source to most packages contains a short description of how they
3528 should be loaded, invoked, and configured---so before you use or
3529 modify a Lisp package, see if the author has provided any hints in the
3532 If a package does not come with Emacs, check the Lisp Code Directory.
3533 The LCD was originally maintained by @email{brennan@@hal.com, Dave
3534 Brennan}, but was recently taken over by @email{toby@@world.std.com,
3535 toby knudsen}, who maintains @uref{http://www.emacs.org}. The LCD is
3536 currently being reorganized and updated, but you can meanwhile find many
3537 packages at @uref{ftp://ftp.emacs.org/pub}.
3539 For now, you can search through the LCD with @file{lispdir.el}, which is
3540 in the process of being updated. Download it from the LCD, in the
3541 @file{emacs-lisp-attic/misc} directory, and then evaluate the following
3542 Lisp form (@pxref{Evaluating Emacs Lisp code}):
3545 (setq lisp-code-directory
3546 "/anonymous@@ftp.emacs.org:pub/emacs-lisp-attic/emacs-lisp/LCD-datafile.gz"
3547 elisp-archive-host "ftp.emacs.org"
3548 elisp-archive-directory "/pub/emacs-lisp-attic/emacs-lisp/")
3551 Once you have installed @file{lispdir.el}, you can use @kbd{M-x
3552 lisp-dir-apropos} to search the listing. For example, @kbd{M-x
3553 lisp-dir-apropos @key{RET} ange-ftp @key{RET}} produces this output:
3556 GNU Emacs Lisp Code Directory Apropos --- "ange-ftp"
3557 "~/" refers to archive.cis.ohio-state.edu:pub/elisp-archive/
3559 ange-ftp (4.18) 15-Jul-1992
3560 Andy Norman, <ange@@hplb.hpl.hp.com>
3561 ~/packages/ange-ftp.tar.Z
3562 transparent FTP Support for GNU Emacs
3563 auto-save (1.19) 01-May-1992
3564 Sebastian Kremer, <sk@@thp.uni-koeln.de>
3565 ~/misc/auto-save.el.Z
3566 Safer autosaving with support for ange-ftp and /tmp
3567 ftp-quik (1.0) 28-Jul-1993
3568 Terrence Brannon, <tb06@@pl122f.eecs.lehigh.edu>
3569 ~/modes/ftp-quik.el.Z
3570 Quik access to dired'ing of ange-ftp and normal paths
3573 @node Packages that do not come with Emacs, Submitting to the Emacs Lisp Archive, Finding a package with particular functionality, Finding Emacs and related packages
3574 @section Where can I get Emacs Lisp packages that don't come with Emacs?
3575 @cindex Unbundled packages
3576 @cindex Finding other packages
3577 @cindex Lisp packages that do not come with Emacs
3578 @cindex Packages, those that do not come with Emacs
3579 @cindex Emacs Lisp Archive, description of
3580 @cindex Archive, description of the Emacs Lisp
3582 First, check the Lisp Code Directory to find the name of the package you
3583 are looking for (@pxref{Finding a package with particular
3584 functionality}). Next, check local archives and the Emacs Lisp Archive
3585 to find a copy of the relevant files. If you still haven't found it,
3586 you can send e-mail to the author asking for a copy. If you find Emacs
3587 Lisp code that doesn't appear in the LCD, please submit a copy to the
3588 LCD (@pxref{Submitting to the Emacs Lisp Archive}).
3590 You can access the Emacs Lisp Archive at
3592 @uref{ftp://archive.cis.ohio-state.edu/pub/emacs-lisp/}
3597 @uref{http://www.cis.ohio-state.edu/emacs-lisp}
3600 Retrieve and read the file @file{README} first.
3605 The archive maintainers do not have time to answer individual
3606 requests for packages or the list of packages in the archive. If you
3607 cannot use FTP or UUCP to access the archive yourself, try to find a
3608 friend who can, but please don't ask the maintainers.
3611 Any files with names ending in @file{.Z}, @file{.z}, or @file{.gz} are
3612 compressed, so you should use "binary" mode in FTP to retrieve them.
3613 You should also use binary mode whenever you retrieve any files with
3614 names ending in @file{.elc}.
3618 @node Submitting to the Emacs Lisp Archive, Current GNU distributions, Packages that do not come with Emacs, Finding Emacs and related packages
3619 @section How do I submit code to the Emacs Lisp Archive?
3620 @cindex Submitting code to the Emacs Lisp Archive
3621 @cindex Emacs Lisp Archive, submissions to
3622 @cindex Lisp Archive, submissions to
3623 @cindex Archive, submitting to the Emacs Lisp
3625 Guidelines and procedures for submission to the archive can be found in
3626 the file @file{GUIDELINES} in the archive directory (@pxref{Packages that
3627 do not come with Emacs}). It covers documentation, copyrights,
3628 packaging, submission, and the Lisp Code Directory Record. Anonymous
3629 FTP uploads are not permitted. Instead, all submissions are mailed to
3630 @email{elisp-archive@@cis.ohio-state.edu}. The @file{lispdir.el}
3631 package has a function named @code{submit-lcd-entry} which will help you
3634 @node Current GNU distributions, Difference between Emacs and XEmacs, Submitting to the Emacs Lisp Archive, Finding Emacs and related packages
3635 @section Where can I get other up-to-date GNU stuff?
3636 @cindex Current GNU distributions
3637 @cindex Sources for current GNU distributions
3638 @cindex Stuff, current GNU
3639 @cindex Up-to-date GNU stuff
3640 @cindex Finding current GNU software
3641 @cindex Official GNU software sites
3643 The most up-to-date official GNU software is normally kept at
3645 @uref{ftp://ftp.gnu.org/pub/gnu}
3647 Read the files @file{etc/DISTRIB} and @file{etc/FTP} for more
3650 A list of sites mirroring @samp{ftp.gnu.org} can be found at
3652 @uref{http://www.gnu.org/order/ftp.html}
3654 @node Difference between Emacs and XEmacs, Emacs for MS-DOS, Current GNU distributions, Finding Emacs and related packages
3655 @section What is the difference between Emacs and XEmacs (formerly "Lucid Emacs")?
3657 @cindex Difference Emacs and XEmacs
3661 First of all, they're both GNU Emacs. XEmacs is just as much a later
3662 version of GNU Emacs as the FSF-distributed version. This FAQ refers to
3663 the latest version to be distributed by the FSF as ``Emacs,'' partly
3664 because the XEmacs maintainers now refer to their product using the
3665 ``XEmacs'' name, and partly because there isn't any accurate way to
3666 differentiate between the two without getting mired in paragraphs of
3667 legalese and history.
3669 XEmacs, which began life as Lucid Emacs, is based on an early version of
3670 Emacs 19 and Epoch, an X-aware version of Emacs 18.
3672 Emacs (i.e., the version distributed by the FSF) has a larger installed
3673 base and now always contains the MULE multilingual facilities.
3674 XEmacs can do some clever tricks with X and MS-Windows, such as
3675 putting arbitrary graphics in a buffer. Similar facilities have been
3676 implemented for Emacs as part of a new redisplay implementation for
3677 Emacs 21, and are available in the latest Emacs releases.
3678 Emacs and XEmacs each come with
3679 Lisp packages that are lacking in the other; RMS says that the FSF would
3680 include more packages that come with XEmacs, but that the XEmacs
3681 maintainers don't always keep track of the authors of contributed code,
3682 which makes it impossible for the FSF to have certain legal papers
3683 signed. (Without these legal papers, the FSF will not distribute Lisp
3684 packages with Emacs.) The two versions have some
3685 significant differences at the Lisp programming level.
3687 Many XEmacs features have found their way into recent versions of Emacs,
3688 and more features can be expected in the future, but there are still many
3689 differences between the two.
3691 The latest stable version of XEmacs as of this writing is 21.1; you can
3694 @uref{ftp://ftp.xemacs.org/pub/xemacs/current/xemacs-21.1.13.tar.gz}
3696 More information about XEmacs, including a list of frequently asked
3697 questions (FAQ), is available at
3699 @uref{http://www.xemacs.org/}
3701 @node Emacs for MS-DOS, Emacs for Windows, Difference between Emacs and XEmacs, Finding Emacs and related packages
3702 @section Where can I get Emacs for my PC running MS-DOS?
3703 @cindex MS-DOS, Emacs for
3704 @cindex DOS, Emacs for
3705 @cindex Compiling Emacs for DOS
3706 @cindex Emacs for MS-DOS
3707 @cindex Tools needed to compile Emacs under DOS
3709 A pre-built binary distribution of Emacs is available from the
3710 SimTel.NET archives. This version apparently works under MS-DOS and
3711 Windows (3.X, 9X, ME, NT, and 2000) and supports long file names under
3712 Windows 9X, Windows ME, and Windows 2000. More information is available
3715 @uref{ftp://ftp.simtel.net/pub/simtelnet/gnu/djgpp/v2gnu/emacs.README}
3717 The binary itself is available in the files @file{em*.zip} in the
3720 @uref{ftp://ftp.simtel.net/pub/simtelnet/gnu/djgpp/v2gnu/}
3722 If you prefer to compile Emacs for yourself, you can do so with the
3723 current distribution directly. You will need a 386 (or
3724 better) processor, and to be running MS-DOS 3.0 or later. According to
3725 @email{eliz@@is.elta.co.il, Eli Zaretskii} and
3726 @email{hankedr@@dms.auburn.edu, Darrel Hankerson}, you will need the
3732 DJGPP version 1.12 maint 1 or later. Djgpp 2.0 or later is
3733 recommended, since 1.x is very old an unmaintained. Djgpp 2 supports
3734 long file names on Windows 9X/ME/2K.
3736 You can get the latest release of DJGPP by retrieving all of
3739 @uref{ftp://ftp.simtel.net/pub/simtelnet/gnu/djgpp/v2*}
3741 @item Unpacking program
3742 The easiest way is to use @code{djtar} which comes with DJGPP v2.x,
3743 because it can open gzip'ed tarfiles (i.e., those ending with
3744 @file{.tar.gz}) in one step. @code{Djtar} comes in
3745 @file{djdev@var{nnn}.zip} archive (where @var{nnn} is the DJGPP version
3746 number), from the URL mentioned above.
3748 @strong{Warning!} Do @strong{not} use the popular WinZip program to
3749 unpack the Emacs distribution! WinZip is known to corrupt some of the
3750 files by converting them to the DOS CR-LF format, it doesn't always
3751 preserve the directory structure recorded in the compressed Emacs
3752 archive, and commits other atrocities. Some of these problems could
3753 actually prevent Emacs from building successfully!
3755 @item make, mv, sed, and rm
3756 All of these utilities are available at
3758 @uref{ftp://ftp.simtel.net/pub/simtelnet/gnu/djgpp/v2gnu}
3760 16-bit utilities can be found in GNUish, at
3762 @uref{ftp://ftp.simtel.net/pub/simtelnet/gnu/gnuish}
3765 (@code{mv} and @code{rm} are in the Fileutils package, @code{sed} and
3766 @code{make} are each one in a separate package named after them.)
3770 The files @file{INSTALL} (near its end) and @file{etc/PROBLEMS} in the
3771 directory of the Emacs sources contains some additional information
3772 regarding Emacs under MS-DOS.
3774 For a list of other MS-DOS implementations of Emacs (and Emacs
3775 look-alikes), consult the list of "Emacs implementations and literature,"
3778 @uref{ftp://rtfm.mit.edu/pub/usenet/comp.emacs/}
3780 Note that while many of these programs look similar to Emacs, they often
3781 lack certain features, such as the Emacs Lisp extension language.
3783 @node Emacs for Windows, Emacs for OS/2, Emacs for MS-DOS, Finding Emacs and related packages
3784 @section Where can I get Emacs for Microsoft Windows
3785 @cindex FAQ for NT Emacs
3786 @cindex Emacs for MS-Windows
3787 @cindex Microsoft Windows, Emacs for
3788 @cindex Windows 9X, ME, NT, 2K, and CE, Emacs for
3790 For information on Emacs for Windows 95 and NT, read the FAQ produced by
3791 @email{voelker@@cs.washington.edu, Geoff Voelker}, available at
3793 @uref{http://www.gnu.org/software/emacs/windows/ntemacs.html}
3795 @xref{Emacs for MS-DOS}, for Windows 3.1.
3797 A port of Emacs 20.7 for Windows CE, based on NTEmacs, is available at
3799 @uref{http://www.rainer-keuchel.de/software.html}
3802 This port was done by @email{coyxc@@rainer-keuchel.de, Rainer Keuchel},
3803 and supports all Emacs features except async subprocesses and menus.
3804 You will need MSVC 6.0 and a Windows CE SDK to build this port.
3806 @node Emacs for OS/2, Emacs for Atari ST, Emacs for Windows, Finding Emacs and related packages
3807 @section Where can I get Emacs for my PC running OS/2?
3808 @cindex OS/2, Emacs for
3810 Emacs 20.6 is ported for emx on OS/2 2.0 or 2.1, and is available at
3812 @uref{ftp://hobbes.nmsu.edu/pub/os2/apps/editors/emacs/e206*.zip}
3817 @uref{http://archiv.leo.org/pub/comp/os/os2/leo/gnu/emacs%2d20/}
3819 Instructions for installation, basic setup, and other useful information
3820 for OS/2 users of Emacs can be found at
3822 @uref{http://userpage.fu-berlin.de/~oheiabbd/emacs/emacs206-os2.html}
3824 @node Emacs for Atari ST, Emacs for the Amiga , Emacs for OS/2, Finding Emacs and related packages
3825 @section Where can I get Emacs for my Atari ST?
3826 @cindex Atari ST, Emacs for
3827 @cindex TOS, Emacs for
3829 Roland Schäuble reports that Emacs 18.58 running on plain TOS and MiNT
3831 @uref{ftp://atari.archive.umich.edu/Editors/Emacs-18-58/1858b-d3.zoo}.
3833 @node Emacs for the Amiga , Emacs for NeXTSTEP, Emacs for Atari ST, Finding Emacs and related packages
3834 @section Where can I get Emacs for my Amiga?
3835 @cindex Amiga, Emacs for
3837 The files you need are available at
3839 @uref{ftp://ftp.wustl.edu/pub/aminet/util/gnu/}
3841 @email{dgilbert@@gamiga.guelphnet.dweomer.org, David Gilbert} has released a
3842 beta version of Emacs 19.25 for the Amiga. You can get the binary at
3844 @uref{ftp://ftp.wustl.edu/pub/aminet/util/gnu/a2.0bEmacs-bin.lha}
3846 @node Emacs for NeXTSTEP, Emacs for Apple computers, Emacs for the Amiga , Finding Emacs and related packages
3847 @section Where can I get Emacs for NeXTSTEP?
3848 @cindex NeXTSTEP, Emacs for
3850 Emacs.app is a NeXTSTEP version of Emacs 19.34 which supports colors,
3851 menus, and multiple frames. You can get it from
3853 @uref{ftp://next-ftp.peak.org/pub/next/apps/emacs/Emacs_for_NeXTstep.4.20a1.NIHS.b.tar.gz}
3855 @node Emacs for Apple computers, Emacs for VMS and DECwindows, Emacs for NeXTSTEP, Finding Emacs and related packages
3856 @section Where can I get Emacs for my Apple computer?
3857 @cindex Apple computers, Emacs for
3858 @cindex Macintosh, Emacs for
3860 An unofficial port of GNU Emacs 18.59 to the Macintosh is available at a
3861 number of ftp sites, the home being
3862 @uref{ftp://ftp.cs.cornell.edu/pub/parmet/Emacs-1.17.sit.bin}.
3864 A port of Emacs 20.4 is available at
3865 @uref{http://www.cs.hku.hk/~choi/emacs/index.html}.
3867 Beginning with version 21.1, the Macintosh is supported in the official
3868 Emacs distribution; see the files @file{mac/README} and
3869 @file{mac/INSTALL} in the Emacs distribution for build instructions.
3871 Apple's forthcoming "OS X" is based largely on NeXTSTEP and OpenStep.
3872 @xref{Emacs for NeXTSTEP}, for more details about that version.
3874 @node Emacs for VMS and DECwindows, Modes for various languages, Emacs for Apple computers, Finding Emacs and related packages
3875 @section Where do I get Emacs that runs on VMS under DECwindows?
3876 @cindex DECwindows, Emacs for
3877 @cindex VMS, Emacs for
3879 Up-to-date information about GNU software (including Emacs) for VMS is
3880 available at @uref{http://vms.gnu.org/}.
3882 @node Modes for various languages, Translating names to IP addresses, Emacs for VMS and DECwindows, Finding Emacs and related packages
3883 @section Where can I get modes for Lex, Yacc/Bison, Bourne shell, csh, C@t{++}, Objective-C, Pascal, Java, and Awk?
3884 @cindex Awk, mode for
3885 @cindex @code{awk-mode}
3886 @cindex Bison, mode for
3887 @cindex Bourne Shell, mode for
3888 @cindex C@t{++}, mode for
3889 @cindex Java, mode for
3891 @cindex Objective-C, mode for
3892 @cindex @code{pascal-mode}
3895 @cindex @file{csh} mode
3896 @cindex @code{sh-mode}
3897 @cindex @code{cc-mode}
3899 Most of these modes are now available in standard Emacs distribution.
3900 To get additional modes, look in the Lisp Code Directory (@pxref{Finding
3901 a package with particular functionality}). For C@t{++}, if you use
3902 @code{lisp-dir-apropos}, you must specify the pattern with something
3903 like @kbd{M-x lisp-dir-apropos @key{RET} c\+\+ @key{RET}}.@footnote{
3904 The backslashes in @samp{\+\+} are required because @kbd{M-x
3905 lisp-dir-apropos} expects a regular expression as its argument
3906 (@pxref{Using regular expressions}), and @samp{+} has a special meaning
3907 in regular expressions.}
3909 Barry Warsaw's @code{cc-mode} now works for C, C@t{++}, Objective-C, and
3910 Java code. You can get the latest version from the Emacs Lisp Archive;
3911 @pxref{Packages that do not come with Emacs} for details. A FAQ for
3912 @code{cc-mode} is available at
3913 @uref{http://www.python.org/emacs/cc-mode/}.
3915 @node Translating names to IP addresses, , Modes for various languages, Finding Emacs and related packages
3916 @section What is the IP address of XXX.YYY.ZZZ?
3917 @cindex Translating names to IP addresses
3918 @cindex IP addresses from names
3919 @cindex Using BIND to translate addresses
3920 @cindex DNS and IP addresses
3922 If you are on a Unix machine, try using the @samp{nslookup} command,
3923 included in the Berkeley BIND package. For example, to find the IP
3924 address of @samp{ftp.gnu.org}, you would type @code{nslookup
3927 Your computer should then provide the IP address of that machine.
3929 If your site's nameserver is deficient, you can use IP addresses to FTP
3930 files. You can get this information by e-mail:
3933 To: dns@@[134.214.84.25] (to grasp.insa-lyon.fr)
3934 Body: ip XXX.YYY.ZZZ (or "help" for more information
3935 and options - no quotes)
3942 To: resolve@@[147.31.254.130] (to laverne.cs.widener.edu)
3943 Body: site XXX.YYY.ZZZ
3946 @c ------------------------------------------------------------
3947 @node Major packages and programs, Key bindings, Finding Emacs and related packages, Top
3948 @chapter Major packages and programs
3949 @cindex Major packages and programs
3966 @node VM, Supercite, Major packages and programs, Major packages and programs
3967 @section VM (View Mail) --- another mail reader within Emacs, with MIME support
3969 @cindex Alternative mail software
3971 @cindex E-mail reader, VM
3976 @email{kyle@@uunet.uu.net, Kyle Jones}
3978 @item Latest version
3982 @uref{ftp://ftp.wonderworks.com/pub/vm/vm.tar.gz}
3984 @item Informational newsgroup/mailing list
3985 @uref{news:gnu.emacs.vm.info}@*
3986 Subscription requests to @email{info-vm-request@@uunet.uu.net}@*
3987 Submissions to @email{info-vm@@uunet.uu.net}
3989 @item Bug reports newsgroup/mailing list
3990 @uref{news:gnu.emacs.vm.bug}@*
3991 Subscription requests to @email{bug-vm-request@@uunet.uu.net}@*
3992 Submissions to @email{bug-vm@@uunet.uu.net}
3995 VM 6 works with Emacs 20.4, and may cause problems with Emacs 20.3 and
3996 below. (But note that many people seem to use Emacs 20.3 with VM 6,
3997 without any problems.) Risk-averse users might wish to try VM 5.97,
3998 available from @uref{ftp://ftp.wonderworks.com/pub/vm/, the same FTP
4001 @node Supercite, Calc, VM, Major packages and programs
4002 @section Supercite --- mail and news citation package within Emacs
4005 @cindex Mail and news citations
4006 @cindex News and mail citations
4007 @cindex Citations in mail and news
4012 @email{bwarsaw@@cen.com, Barry Warsaw}
4014 @item Latest version
4015 3.54 (comes bundled with Emacs 20)
4018 @uref{http://www.python.org/emacs/supercite.tar.gz}
4021 Subscription requests to @email{supercite-request@@python.org}@*
4022 Submissions @email{supercite@@python.org}
4026 Superyank is an old version of Supercite.
4028 @node Calc, VIPER, Supercite, Major packages and programs
4029 @section Calc --- poor man's Mathematica within Emacs
4030 @cindex Programmable calculator
4032 @cindex Mathematical package
4037 @email{daveg@@csvax.cs.caltech.edu, Dave Gillespie}
4039 @item Latest version
4043 @uref{ftp://ftp.gnu.org/pub/gnu/calc/calc-2.02f.tar.gz}
4047 Note that Calc 2.02f needs patching to work with Emacs 21 and later.
4049 @cindex @code{calculator}, a package
4050 Emacs 21.1 and later comes with a package called @file{calculator.el}.
4051 It doesn't support all the mathematical wizardry offered by Calc, such
4052 as matrices, special functions, and statistics, but is more than
4053 adequate as a replacement for @code{xcalc} and similar programs.
4055 @node VIPER, AUC-TeX, Calc, Major packages and programs
4056 @section VIPER --- @code{vi} emulation for Emacs
4057 @cindex @code{vi} emulation
4059 @cindex Emulation of @code{vi}
4061 Since Emacs 19.29, the preferred @code{vi} emulation in Emacs is VIPER
4062 (@kbd{M-x viper-mode @key{RET}}), which comes with Emacs. It extends
4063 and supersedes VIP (including VIP 4.3) and provides @code{vi} emulation
4064 at several levels, from one that closely follows @code{vi} to one that
4065 departs from @code{vi} in several significant ways.
4067 For Emacs 19.28 and earlier, the following version of VIP is generally
4068 better than the one distributed with Emacs:
4072 @email{sane@@cs.uiuc.edu, Aamod Sane}
4074 @item Latest version
4078 @uref{ftp://archive.cis.ohio-state.edu/pub/emacs-lisp/modes/vip-mode.tar.Z}
4082 @node AUC-TeX, BBDB, VIPER, Major packages and programs
4083 @section AUC TeX --- enhanced LaTeX mode with debugging facilities
4084 @cindex Mode for @TeX{}
4086 @cindex AUC-TeX mode for editing @TeX{}
4087 @cindex Writing and debugging @TeX{}
4092 @email{krab@@iesd.auc.dk, Kresten Krab Thorup} and@*
4093 @email{abraham@@dina.kvl.dk, Per Abrahamsen}
4095 @item Latest version
4099 @uref{ftp://sunsite.auc.dk/packages/auctex/auctex.tar.gz}
4102 @uref{http://sunsite.auc.dk/auctex/}
4105 Subscription requests to @email{auc-tex-request@@iesd.auc.dk}@*
4106 Submissions to @email{auc-tex@@iesd.auc.dk}@*
4107 Development team is at @email{auc-tex_mgr@@iesd.auc.dk}
4111 @node BBDB, Ispell, AUC-TeX, Major packages and programs
4112 @section BBDB --- personal Info Rolodex integrated with mail/news readers
4114 @cindex Rolodex-like functionality
4115 @cindex Integrated contact database
4116 @cindex Contact database
4117 @cindex Big Brother Database
4118 @cindex Address book
4123 @email{simmonmt@@acm.org, Matt Simmons}
4125 @item Latest version
4129 @uref{http://www.netcom.com/~simmonmt/bbdb/index.html}
4132 Subscription requests to @email{info-bbdb-request@@xemacs.org}@*
4133 Submissions to @email{info-bbdb@@xemacs.org}@*
4134 Release announcements: @email{bbdb-announce-request@@xemacs.org}
4138 @node Ispell, w3-mode, BBDB, Major packages and programs
4139 @section Ispell --- spell checker in C with interface for Emacs
4140 @cindex Spell-checker
4141 @cindex Checking spelling
4147 @email{geoff@@itcorp.com, Geoff Kuenning}
4149 @item Latest version
4153 @uref{ftp://ftp.cs.ucla.edu/pub/ispell/ispell-3.1.20.tar.gz}@*
4156 @uref{http://fmg-www.cs.ucla.edu/geoff/ispell.html}
4163 Do not ask Geoff to send you the latest version of Ispell. He does not
4167 This Ispell program is distinct from GNU Ispell 4.0. GNU Ispell 4.0 is
4168 no longer a supported product.
4172 @node w3-mode, EDB, Ispell, Major packages and programs
4173 @section w3-mode --- A World Wide Web browser inside of Emacs
4176 @cindex HTML browser in Emacs
4177 @cindex @code{w3-mode}
4182 @email{wmperry@@spry.com, Bill Perry}
4184 @item Latest version
4188 @uref{ftp://ftp.cs.indiana.edu/pub/elisp/w3/w3.tar.gz}
4191 Receive announcements from @email{w3-announce-request@@indiana.edu}@*
4192 Become a beta tester at @email{w3-beta-request@@indiana.edu}@*
4193 Help to develop @code{w3-mode} at @email{w3-dev@@indiana.edu}
4197 @node EDB, Mailcrypt, w3-mode, Major packages and programs
4198 @section EDB --- Database program for Emacs; replaces forms editing modes
4205 @email{mernst@@theory.lcs.mit.edu, Michael Ernst}
4207 @item Latest version
4211 @uref{ftp://theory.lcs.mit.edu/pub/emacs/edb}
4215 @node Mailcrypt, JDE, EDB, Major packages and programs
4216 @section Mailcrypt --- PGP interface within Emacs mail and news
4219 @cindex Interface to PGP from Emacs mail and news
4220 @cindex News, interface to PGP from
4221 @cindex Mail, interface to PGP from
4222 @cindex Encryption software, interface to
4227 @email{patl@@lcs.mit.edu, Patrick J. LoPresti} and
4228 @email{jin@@atype.com, Jin S. Choi}
4231 @email{lbudney@@pobox.com, Len Budney}
4233 @item Latest version
4237 @uref{http://www.nb.net/~lbudney/linux/software/mailcrypt/mailcrypt-3.5.3.tar.gz}
4240 @uref{http://www.nb.net/~lbudney/linux/software/mailcrypt.html}
4244 @node JDE, Patch, Mailcrypt, Major packages and programs
4245 @section JDE --- Integrated development environment for Java
4246 @cindex Java development environment
4247 @cindex Integrated Java development environment
4253 @email{paulk@@mathworks.com, Paul Kinnucan}
4256 jde-subscribe@@sunsite.auc.dk
4258 @item Latest version
4262 @uref{http://sunsite.auc.dk/jde/}
4266 @node Patch, , JDE, Major packages and programs
4267 @section Patch --- program to apply "diffs" for updating files
4268 @cindex Updating files with diffs
4269 @cindex Patching source files with diffs
4270 @cindex Diffs and patching
4271 @cindex @file{patch}
4276 @email{lwall@@wall.org, Larry Wall} (with GNU modifications)
4278 @item Latest version
4282 @xref{Current GNU distributions}.
4286 @c ------------------------------------------------------------
4287 @node Key bindings, Alternate character sets, Major packages and programs, Top
4288 @chapter Key bindings
4289 @cindex Key bindings
4292 * Binding keys to commands::
4293 * Invalid prefix characters::
4294 * Terminal setup code works after Emacs has begun::
4295 * Using function keys under X::
4296 * Working with function and arrow keys::
4297 * X key translations for Emacs::
4298 * Handling C-s and C-q with flow control::
4299 * Binding C-s and C-q::
4300 * Backspace invokes help::
4301 * stty and Backspace key::
4303 * Producing C-XXX with the keyboard::
4306 * Compose Character::
4307 * Binding combinations of modifiers and function keys::
4308 * Meta key does not work in xterm::
4309 * ExtendChar key does not work as Meta::
4312 @node Binding keys to commands, Invalid prefix characters, Key bindings, Key bindings
4313 @section How do I bind keys (including function keys) to commands?
4314 @cindex Binding keys to commands
4315 @cindex Keys, binding to commands
4316 @cindex Commands, binding keys to
4318 Keys can be bound to commands either interactively or in your
4319 @file{.emacs} file. To interactively bind keys for all modes, type
4320 @kbd{M-x global-set-key @key{RET} @var{key} @var{cmd} @key{RET}}.
4322 To bind a key just in the current major mode, type @kbd{M-x
4323 local-set-key @key{RET} @var{key} @var{cmd} @key{RET}}.
4325 @inforef{Key Bindings, Key Bindings, emacs}, for further details.
4327 To make the process of binding keys interactively eaiser, use the
4328 following ``trick'': First bind the key interactively, then immediately
4329 type @kbd{C-x @key{ESC} @key{ESC} C-a C-k C-g}. Now, the command needed
4330 to bind the key is in the kill ring, and can be yanked into your
4331 @file{.emacs} file. If the key binding is global, no changes to the
4332 command are required. For example,
4335 (global-set-key (quote [f1]) (quote help-for-help))
4339 can be placed directly into the @file{.emacs} file. If the key binding is
4340 local, the command is used in conjunction with the "add-hook" command.
4341 For example, in tex-mode, a local binding might be
4344 (add-hook 'tex-mode-hook
4346 (local-set-key (quote [f1]) (quote help-for-help))))
4353 Control characters in key sequences, in the form yanked from the kill
4354 ring are given in their graphic form---i.e., @key{CTRL} is shown as
4355 @samp{^}, @key{TAB} as a set of spaces (usually 8), etc. You may want
4356 to convert these into their vector or string forms.
4359 If a prefix key of the character sequence to be bound is already
4360 bound as a complete key, then you must unbind it before the new
4361 binding. For example, if @kbd{ESC @{} is previously bound:
4364 (global-unset-key [?\e ?@{]) ;; or
4365 (local-unset-key [?\e ?@{])
4369 Aside from commands and ``lambda lists,'' a vector or string also
4370 can be bound to a key and thus treated as a macro. For example:
4373 (global-set-key [f10] [?\C-x?\e?\e?\C-a?\C-k?\C-g]) ;; or
4374 (global-set-key [f10] "\C-x\e\e\C-a\C-k\C-g")
4379 @node Invalid prefix characters, Terminal setup code works after Emacs has begun, Binding keys to commands, Key bindings
4380 @section Why does Emacs say "Key sequence XXX uses invalid prefix characters"?
4381 @cindex Prefix characters, invalid
4382 @cindex Invalid prefix characters
4383 @cindex Misspecified key sequences
4385 Usually, one of two things has happened. In one case, the control
4386 character in the key sequence has been misspecified (e.g. @samp{C-f}
4387 used instead of @samp{\C-f} within a Lisp expression). In the other
4388 case, a @dfn{prefix key} in the keystroke sequence you were trying to bind
4389 was already bound as a @dfn{complete key}. Historically, the @samp{ESC [}
4390 prefix was usually the problem, in which case you should evaluate either
4391 of these forms before attempting to bind the key sequence:
4394 (global-unset-key [?\e ?[]) ;; or
4395 (global-unset-key "\e[")
4398 @node Terminal setup code works after Emacs has begun, Using function keys under X, Invalid prefix characters, Key bindings
4399 @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?
4400 @cindex Terminal setup code in @file{.emacs}
4402 During startup, Emacs initializes itself according to a given code/file
4403 order. If some of the code executed in your @file{.emacs} file needs to
4404 be postponed until the initial terminal or window-system setup code has
4405 been executed but is not, then you will experience this problem (this
4406 code/file execution order is not enforced after startup).
4408 To postpone the execution of Emacs Lisp code until after terminal or
4409 window-system setup, treat the code as a @dfn{lambda list} and set the
4410 value of either the @code{term-setup-hook} or @code{window-setup-hook}
4411 variable to this lambda function. For example,
4414 (add-hook 'term-setup-hook
4416 (when (string-match "\\`vt220" (or (getenv "TERM") ""))
4417 ;; Make vt220's "Do" key behave like M-x:
4418 (global-set-key [do] 'execute-extended-command))))
4421 For information on what Emacs does every time it is started, see the
4422 @file{lisp/startup.el} file.
4424 @node Using function keys under X, Working with function and arrow keys, Terminal setup code works after Emacs has begun, Key bindings
4425 @section How do I use function keys under X?
4426 @cindex Function keys
4427 @cindex X Window System and function keys
4428 @cindex Binding function keys
4430 With Emacs 19, functions keys under X are bound like any other key. @xref{Binding keys to commands}, for details.
4432 @node Working with function and arrow keys, X key translations for Emacs, Using function keys under X, Key bindings
4433 @section How do I tell what characters or symbols my function or arrow keys emit?
4434 @cindex Working with arrow keys
4435 @cindex Arrow keys, symbols generated by
4436 @cindex Working with function keys
4437 @cindex Function keys, symbols generated by
4438 @cindex Symbols generated by function keys
4440 Type @kbd{C-h c} then the function or arrow keys. The command will
4441 return either a function key symbol or character sequence (see the
4442 Emacs on-line documentation for an explanation). This works for other
4445 @node X key translations for Emacs, Handling C-s and C-q with flow control, Working with function and arrow keys, Key bindings
4446 @section How do I set the X key ``translations'' for Emacs?
4447 @cindex X key translations
4448 @cindex Key translations under X
4449 @cindex Translations for keys under X
4451 Emacs is not written using the Xt library by default, so there are no
4452 ``translations'' to be set. (We aren't sure how to set such translations
4453 if you do build Emacs with Xt; please let us know if you've done this!)
4455 The only way to affect the behavior of keys within Emacs is through
4456 @code{xmodmap} (outside Emacs) or @code{define-key} (inside Emacs). The
4457 @code{define-key} command should be used in conjunction with the
4458 @code{function-key-map} map. For instance,
4461 (define-key function-key-map [M-@key{TAB}] [?\M-\t])
4465 defines the @kbd{M-@key{TAB}} key sequence.
4467 @node Handling C-s and C-q with flow control, Binding C-s and C-q, X key translations for Emacs, Key bindings
4468 @section How do I handle @kbd{C-s} and @kbd{C-q} being used for flow control?
4469 @cindex Flow control, @kbd{C-s} and @kbd{C-q} with
4470 @cindex @kbd{C-s} and @kbd{C-q} with flow control
4472 @kbd{C-s} and @kbd{C-q} are used in the XON/XOFF flow control protocol.
4473 This messes things up when you're using Emacs over a serial line,
4474 because Emacs binds these keys to commands by default. Because Emacs
4475 won't honor them as flow control characters, too many of these
4476 characters are not passed on and overwhelm output buffers. Sometimes,
4477 intermediate software using XON/XOFF flow control will prevent Emacs
4478 from ever seeing @kbd{C-s} and @kbd{C-q}.
4485 Disable the use of @kbd{C-s} and @kbd{C-q} for flow control.
4487 You need to determine the cause of the flow control.
4494 Your terminal may use XON/XOFF flow control to have time to display
4495 all the characters it receives. For example, VT series terminals do
4496 this. It may be possible to turn this off from a setup menu. For
4497 example, on a VT220 you may select ``No XOFF'' in the setup menu. This
4498 is also true for some terminal emulation programs on PCs.
4500 When you turn off flow control at the terminal, you will also need to
4501 turn it off at the other end, which might be at the computer you are
4502 logged in to or at some terminal server in between.
4504 If you turn off flow control, characters may be lost; using a printer
4505 connected to the terminal may fail. You may be able to get around
4506 this problem by modifying the @samp{termcap} entry for your terminal to
4507 include extra NUL padding characters.
4512 If you are using a dialup connection, the modems may be using
4513 XON/XOFF flow control. It's not clear how to get around this.
4516 a router or terminal server
4518 Some network box between the terminal and your computer may be using
4519 XON/XOFF flow control. It may be possible to make it use some other
4520 kind of flow control. You will probably have to ask your local
4521 network experts for help with this.
4524 @code{tty} and/or @code{pty} devices
4526 If your connection to Emacs goes through multiple @code{tty} and/or
4527 @code{pty} devices, they may be using XON/XOFF flow control even when it
4530 @email{eirik@@theory.tn.cornell.edu, Eirik Fuller} writes:
4533 Some versions of @code{rlogin} (and possibly @code{telnet}) do not pass
4534 flow control characters to the remote system to which they connect. On
4535 such systems, Emacs on the remote system cannot disable flow control on
4536 the local system. Sometimes @samp{rlogin -8} will avoid this problem.
4538 One way to cure this is to disable flow control on the local host (the
4539 one running @code{rlogin}, not the one running @code{rlogind}) using the
4540 @code{stty} command, before starting the @code{rlogin} process. On many
4541 systems, @samp{stty start u stop u} will do this.
4543 Some versions of @samp{tcsh} will prevent even this from working. One
4544 way around this is to start another shell before starting rlogin,
4545 and issue the @samp{stty} command to disable flow control from that shell.
4548 Use @samp{stty -ixon} instead of @samp{stty start u stop u} on some systems.
4553 Make Emacs speak the XON/XOFF flow control protocol.
4555 You can make Emacs treat @kbd{C-s} and @kbd{C-q} as flow control characters by
4559 (enable-flow-control)
4563 to unconditionally enable flow control or
4566 (enable-flow-control-on "vt100" "h19")
4570 (using your terminal names instead of @samp{vt100} or @samp{h19}) to
4571 enable selectively. These commands will automatically swap @kbd{C-s}
4572 and @kbd{C-q} to @kbd{C-\} and @kbd{C-^}. Variables can be used to
4573 change the default swap keys (@code{flow-control-c-s-replacement} and
4574 @code{flow-control-c-q-replacement}).
4576 If you are fixing this for yourself, simply put the form in your
4577 @file{.emacs} file. If you are fixing this for your entire site, the
4578 best place to put it is in the @file{site-lisp/site-start.el} file.
4579 (Here @file{site-lisp} is actually a subdirectory of your Emacs
4580 installation directory, typically @file{/usr/local/share/emacs}.)
4581 Putting this form in @file{site-lisp/default.el} has the problem that
4582 if the user's @file{.emacs} file has an error, this will prevent
4583 @file{default.el} from being loaded and Emacs may be unusable for the
4584 user, even for correcting their @file{.emacs} file (unless they're
4585 smart enough to move it to another name).
4587 @code{enable-flow-control} can be invoked interactively as well:
4588 @kbd{M-x enable-flow-control @key{RET}}.
4592 For further discussion of this issue, read the file @file{etc/PROBLEMS}
4593 (in the Emacs source directory when you unpack the Emacs distribution).
4595 @node Binding C-s and C-q, Backspace invokes help, Handling C-s and C-q with flow control, Key bindings
4596 @section How do I bind @kbd{C-s} and @kbd{C-q} (or any key) if these keys are filtered out?
4597 @cindex Binding @kbd{C-s} and @kbd{C-q}
4598 @cindex @kbd{C-s} and @kbd{C-q}, binding
4600 To bind @kbd{C-s} and @kbd{C-q}, use either @code{enable-flow-control}
4601 or @code{enable-flow-control-on}. @xref{Handling C-s and C-q with flow
4602 control}, for usage and implementation details.
4604 To bind other keys, use @code{keyboard-translate}. @xref{Swapping
4605 keys}, for usage details. To do this for an entire site, you should
4606 swap the keys in @file{site-lisp/site-start.el}. @xref{Handling C-s
4607 and C-q with flow control}, for an explanation of why
4608 @file{site-lisp/default.el} should not be used.
4613 If you do this for an entire site, the users will be confused by
4614 the disparity between what the documentation says and how Emacs
4619 @node Backspace invokes help, stty and Backspace key, Binding C-s and C-q, Key bindings
4620 @section Why does the @key{Backspace} key invoke help?
4621 @cindex Backspace key invokes help
4622 @cindex Help invoked by Backspace
4624 The @key{Backspace} key (on most keyboards) generates ASCII code 8.
4625 @kbd{C-h} sends the same code. In Emacs by default @kbd{C-h} invokes
4626 help-command. This is intended to be easy to remember since the first
4627 letter of @samp{help} is @samp{h}. The easiest solution to this problem
4628 is to use @kbd{C-h} (and @key{Backspace}) for help and @key{DEL} (the
4629 @key{Delete} key) for deleting the previous character.
4631 For many people this solution may be problematic:
4636 They normally use @key{Backspace} outside of Emacs for deleting the
4637 previous character. This can be solved by making @key{DEL} the command
4638 for deleting the previous character outside of Emacs. On many Unix
4639 systems, this command will remap @key{DEL}:
4646 The user may prefer the @key{Backspace} key for deleting the
4647 previous character because it is more conveniently located on their
4648 keyboard or because they don't even have a separate @key{Delete} key.
4649 In this case, the @key{Backspace} key should be made to behave like
4650 @key{Delete}. There are several methods.
4653 Some terminals (e.g., VT3## terminals) allow the character generated
4654 by the @key{Backspace} key to be changed from a setup menu.
4657 You may be able to get a keyboard that is completely programmable.
4660 Under X or on a dumb terminal, it is possible to swap the
4661 @key{Backspace} and @key{Delete} keys inside Emacs:
4664 (keyboard-translate ?\C-h ?\C-?)
4667 @xref{Swapping keys}, for further details of "keyboard-translate".
4670 Another approach is to switch key bindings and put help on @kbd{C-x h}
4674 (global-set-key "\C-h" 'delete-backward-char)
4676 ;;; overrides mark-whole-buffer
4677 (global-set-key "\C-xh" 'help-command)
4680 Other popular key bindings for help are @kbd{M-?} and @kbd{C-x ?}.
4682 Don't try to bind @key{DEL} to @code{help-command}, because there are
4683 many modes that have local bindings of @key{DEL} that will interfere.
4687 When Emacs 21 or later runs on a windowed display, it binds the
4688 @key{Delete} key to a command which deletes the character at point, to
4689 make Emacs more consistent with keyboard operation on these systems.
4691 @node stty and Backspace key, Swapping keys, Backspace invokes help, Key bindings
4692 @section Why doesn't Emacs look at the @file{stty} settings for @key{Backspace} vs. @key{Delete}?
4693 @cindex @file{stty} and Emacs
4694 @cindex Backspace and @file{stty}
4695 @cindex Delete and @file{stty}
4699 @c FIXME: RMS explained the reasons for this on emacs-hackers. It's
4700 @c probably worth putting that explanation here.
4702 @node Swapping keys, Producing C-XXX with the keyboard, stty and Backspace key, Key bindings
4703 @section How do I swap two keys?
4704 @cindex Swapping keys
4705 @cindex Keys, swapping
4706 @cindex @code{keyboard-translate}
4708 In Emacs 19, you can swap two keys (or key sequences) by using the
4709 @code{keyboard-translate} function. For example, to turn @kbd{C-h} into
4710 @key{DEL} and @key{DEL} to @kbd{C-h}, use
4713 (keyboard-translate ?\C-h ?\C-?) ; translate `C-h' to DEL
4714 (keyboard-translate ?\C-? ?\C-h) ; translate DEL to `C-h'.
4718 The first key sequence of the pair after the function identifies what is
4719 produced by the keyboard; the second, what is matched for in the
4722 Keyboard translations are not the same as key bindings in keymaps.
4723 Emacs contains numerous keymaps that apply in different situations, but
4724 there is only one set of keyboard translations, and it applies to every
4725 character that Emacs reads from the terminal. Keyboard translations
4726 take place at the lowest level of input processing; the keys that are
4727 looked up in keymaps contain the characters that result from keyboard
4730 @inforef{Keyboard Translations, Keyboard Translations, emacs}.
4732 @node Producing C-XXX with the keyboard, No Meta key, Swapping keys, Key bindings
4733 @section How do I produce C-XXX with my keyboard?
4734 @cindex Producing control characters
4735 @cindex Generating control characters
4736 @cindex Control characters, generating
4738 On terminals (but not under X), some common "aliases" are:
4742 @item @kbd{C-2} or @kbd{C-@key{SPC}}
4748 @item @kbd{C-7} or @kbd{C-S--}
4762 Often other aliases exist; use the @kbd{C-h c} command and try
4763 @key{CTRL} with all of the digits on your keyboard to see what gets
4764 generated. You can also try the @kbd{C-h w} command if you know the
4765 name of the command.
4767 @node No Meta key, No Escape key, Producing C-XXX with the keyboard, Key bindings
4768 @section What if I don't have a @key{Meta} key?
4769 @cindex No @key{Meta} key
4770 @cindex @key{Meta} key, what to do if you lack it
4772 On many keyboards, the @key{Alt} key acts as @key{Meta}, so try it.
4774 Instead of typing @kbd{M-a}, you can type @kbd{@key{ESC} a}. In fact,
4775 Emacs converts @kbd{M-a} internally into @kbd{@key{ESC} a} anyway
4776 (depending on the value of @code{meta-prefix-char}). Note that you
4777 press @key{Meta} and @key{a} together, but with @key{ESC}, you press
4778 @key{ESC}, release it, and then press @key{a}.
4780 @node No Escape key, Compose Character, No Meta key, Key bindings
4781 @section What if I don't have an @key{Escape} key?
4782 @cindex No Escape key
4783 @cindex Lacking an Escape key
4784 @cindex Escape key, lacking
4786 Type @kbd{C-[} instead. This should send ASCII code 27 just like an
4787 Escape key would. @kbd{C-3} may also work on some terminal (but not
4788 under X). For many terminals (notably DEC terminals) @key{F11}
4789 generates @key{ESC}. If not, the following form can be used to bind it:
4792 ;;; F11 is the documented ESC replacement on DEC terminals.
4793 (define-key function-key-map [f11] [?\e])
4796 @node Compose Character, Binding combinations of modifiers and function keys, No Escape key, Key bindings
4797 @section Can I make my @key{Compose Character} key behave like a @key{Meta} key?
4798 @cindex @key{Compose Character} key, using as @key{Meta}
4799 @cindex @key{Meta}, using @key{Compose Character} for
4801 On a dumb terminal such as a VT220, no. It is rumored that certain
4802 VT220 clones could have their @key{Compose} key configured this way. If
4803 you're using X, you might be able to do this with the @code{xmodmap}
4806 @node Binding combinations of modifiers and function keys, Meta key does not work in xterm, Compose Character, Key bindings
4807 @section How do I bind a combination of modifier key and function key?
4808 @cindex Modifiers and function keys
4809 @cindex Function keys and modifiers
4810 @cindex Binding modifiers and function keys
4812 With Emacs 19 and later, you can represent modified function keys in
4813 vector format by adding prefixes to the function key symbol. For
4814 example (from the on-line documentation):
4817 (global-set-key [?\C-x right] 'forward-page)
4821 where @samp{?\C-x} is the Lisp character constant for the character @kbd{C-x}.
4823 You can use the modifier keys @key{Control}, @key{Meta}, @key{Hyper},
4824 @key{Super}, @key{Alt}, and @key{Shift} with function keys. To
4825 represent these modifiers, prepend the strings @samp{C-}, @samp{M-},
4826 @samp{H-}, @samp{s-}, @samp{A-}, and @samp{S-} to the symbol name. Here
4827 is how to make @kbd{H-M-RIGHT} move forward a word:
4830 (global-set-key [H-M-right] 'forward-word)
4836 Not all modifiers are permitted in all situations. @key{Hyper},
4837 @key{Super}, and @key{Alt} are not available on Unix character
4838 terminals. Non-ASCII keys and mouse events (e.g. @kbd{C-=} and
4839 @kbd{Mouse-1}) also fall under this category.
4843 @xref{Binding keys to commands}, for general key binding instructions.
4845 @node Meta key does not work in xterm, ExtendChar key does not work as Meta, Binding combinations of modifiers and function keys, Key bindings
4846 @section Why doesn't my @key{Meta} key work in an @code{xterm} window?
4847 @cindex @key{Meta} key and @code{xterm}
4848 @cindex Xterm and @key{Meta} key
4850 @inforef{Single-Byte Character Support, Single-Byte Character Set
4853 If the advice in the Emacs manual fails, try all of these methods before
4854 asking for further help:
4859 You may have big problems using @code{mwm} as your window manager.
4860 (Does anyone know a good generic solution to allow the use of the
4861 @key{Meta} key in Emacs with @file{mwm}?)
4864 For X11: Make sure it really is a @key{Meta} key. Use @code{xev} to
4865 find out what keysym your @key{Meta} key generates. It should be either
4866 @code{Meta_L} or @code{Meta_R}. If it isn't, use @file{xmodmap} to fix
4870 Make sure the @code{pty} the @code{xterm} is using is passing 8 bit
4871 characters. @samp{stty -a} (or @samp{stty everything}) should show
4872 @samp{cs8} somewhere. If it shows @samp{cs7} instead, use @samp{stty
4873 cs8 -istrip} (or @samp{stty pass8}) to fix it.
4876 If there is an @code{rlogin} connection between @code{xterm} and Emacs, the
4877 @samp{-8} argument may need to be given to rlogin to make it pass all 8 bits
4881 If Emacs is running on Ultrix, it is reported that evaluating
4882 @code{(set-input-mode t nil)} helps.
4885 If all else fails, you can make @code{xterm} generate @kbd{@key{ESC} W} when
4886 you type @kbd{M-W}, which is the same conversion Emacs would make if it
4887 got the @kbd{M-W} anyway. In X11R4, the following resource
4888 specification will do this:
4891 XTerm.VT100.EightBitInput: false
4895 (This changes the behavior of the @code{insert-eight-bit} action.)
4897 With older @code{xterm}s, you can specify this behavior with a translation:
4900 XTerm.VT100.Translations: #override \
4901 Meta<KeyPress>: string(0x1b) insert()
4905 You might have to replace @samp{Meta} with @samp{Alt}.
4909 @node ExtendChar key does not work as Meta, , Meta key does not work in xterm, Key bindings
4910 @section Why doesn't my @key{ExtendChar} key work as a @key{Meta} key under HP-UX 8.0 and 9.x?
4911 @cindex @key{ExtendChar} key as @key{Meta}
4912 @cindex @key{Meta}, using @key{ExtendChar} for
4913 @cindex HP-UX, the @key{ExtendChar} key
4915 This is a result of an internationalization extension in X11R4 and the
4916 fact that HP is now using this extension. Emacs assumes that the
4917 @code{XLookupString} function returns the same result regardless of the
4918 @key{Meta} key state which is no longer necessarily true. Until Emacs
4919 is fixed, the temporary kludge is to run this command after each time
4920 the X server is started but preferably before any xterm clients are:
4923 xmodmap -e 'remove mod1 = Mode_switch'
4926 @c FIXME: Emacs 21 supports I18N in X11; does that mean that this bug is
4929 This will disable the use of the extra keysyms systemwide, which may be
4930 undesirable if you actually intend to use them.
4932 @c ------------------------------------------------------------
4933 @node Alternate character sets, Mail and news, Key bindings, Top
4934 @chapter Alternate character sets
4935 @cindex Alternate character sets
4938 * Emacs does not display 8-bit characters::
4939 * Inputting eight-bit characters::
4940 * Kanji and Chinese characters::
4941 * Right-to-left alphabets::
4944 @node Emacs does not display 8-bit characters, Inputting eight-bit characters, Alternate character sets, Alternate character sets
4945 @section How do I make Emacs display 8-bit characters?
4946 @cindex Displaying eight-bit characters
4947 @cindex Eight-bit characters, displaying
4949 @inforef{Single-Byte Character Support, Single-byte Character Set
4950 Support, emacs}. On a Unix, when Emacs runs on a text-only terminal
4951 display or is invoked with @samp{emacs -nw}, you typically need to use
4952 @code{set-terminal-coding-system} to tell Emacs what the terminal can
4953 display, even after setting the language environment; otherwise
4954 non-ASCII characters will display as @samp{?}. On other operating
4955 systems, such as MS-DOS and MS-Windows, Emacs queries the OS about the
4956 character set supported by the display, and sets up the required
4957 terminal coding system automatically.
4959 @node Inputting eight-bit characters, Kanji and Chinese characters, Emacs does not display 8-bit characters, Alternate character sets
4960 @section How do I input eight-bit characters?
4961 @cindex Entering eight-bit characters
4962 @cindex Eight-bit characters, entering
4963 @cindex Input, 8-bit characters
4965 Various methods are available for input of eight-bit characters. See
4966 @inforef{Single-Byte Character Support, Single-byte Character Set
4967 Support, emacs}. For more sophisticated methods, @inforef{Input
4968 Methods, Input Methods, emacs}.
4970 @node Kanji and Chinese characters, Right-to-left alphabets, Inputting eight-bit characters, Alternate character sets
4971 @section Where can I get an Emacs that handles kanji, Chinese, or other Far-Eastern character sets?
4972 @cindex Kanji, handling with Emacs
4973 @cindex Chinese, handling with Emacs
4974 @cindex Japanese, handling with Emacs
4975 @cindex Korean, handling with Emacs
4977 Emacs 20 and later includes many of the features of MULE, the MULtilingual
4978 Enhancement to Emacs. @xref{Installing Emacs}, for information on where
4979 to find and download the latest version of Emacs.
4981 @node Right-to-left alphabets, , Kanji and Chinese characters, Alternate character sets
4982 @section Where is an Emacs that can handle Semitic (right-to-left) alphabets?
4983 @cindex Right-to-left alphabets
4984 @cindex Hebrew, handling with Emacs
4985 @cindex Semitic alphabets
4986 @cindex Arabic alphabets
4988 Emacs 20 and later supports Hebrew characters (ISO 8859-8), but does not
4989 yet support right-to-left character entry and display.
4991 @email{joel@@exc.com, Joel M. Hoffman} has written a Lisp package called
4992 @file{hebrew.el} that allows right-to-left editing of Hebrew. It
4993 reportedly works out of the box with Emacs 19, but requires patches for
4994 Emacs 18. Write to Joel if you want the patches or package.
4996 @c FIXME: Should we mention Ehud Karni's package?
4998 @file{hebrew.el} requires a Hebrew screen font, but no other hardware support.
4999 Joel has a screen font for PCs running MS-DOS or GNU/Linux.
5001 You might also try to query archie for files named with @file{hebrew};
5002 several ftp sites in Israel may also have the necessary files.
5004 @c ------------------------------------------------------------
5005 @node Mail and news, Concept index, Alternate character sets, Top
5006 @chapter Mail and news
5007 @cindex Mail and news
5010 * Changing the included text prefix::
5011 * Saving a copy of outgoing mail::
5012 * Expanding aliases when sending mail::
5013 * Rmail thinks all messages are one big one::
5014 * Sorting the messages in an Rmail folder::
5015 * Rmail writes to /usr/spool/mail::
5016 * Recovering mail files when Rmail munges them::
5017 * Replying to the sender of a message::
5018 * MIME with Emacs mail packages::
5019 * Automatically starting a mail or news reader::
5020 * Reading news with Emacs::
5021 * Gnus does not work with NNTP::
5022 * Viewing articles with embedded underlining::
5023 * Saving a multi-part Gnus posting::
5024 * Starting Gnus faster::
5025 * Catching up in all newsgroups::
5026 * Killing based on nonstandard headers::
5027 * Removing flashing messages::
5028 * Catch-up is slow in Gnus::
5029 * Gnus hangs for a long time::
5030 * Learning more about Gnus::
5033 @node Changing the included text prefix, Saving a copy of outgoing mail, Mail and news, Mail and news
5034 @section How do I change the included text prefix in mail/news followups?
5035 @cindex Prefix in mail/news followups, changing
5036 @cindex Included text prefix, changing
5037 @cindex Setting the included text character
5038 @cindex Quoting in mail messages
5040 If you read mail with Rmail or news with Gnus, set the variable
5041 @code{mail-yank-prefix}. For VM, set @code{vm-included-text-prefix}.
5042 For mh-e, set @code{mh-ins-buf-prefix}.
5044 For fancier control of citations, use Supercite. @xref{Supercite}.
5046 To prevent Emacs from including various headers of the replied-to
5047 message, set the value of @code{mail-yank-ignored-headers} to an
5050 @node Saving a copy of outgoing mail, Expanding aliases when sending mail, Changing the included text prefix, Mail and news
5051 @section How do I save a copy of outgoing mail?
5052 @cindex Saving a copy of outgoing mail
5053 @cindex Copying outgoing mail to a file
5054 @cindex Filing outgoing mail
5055 @cindex Automatic filing of outgoing mail
5056 @cindex Mail, saving outgoing automatically
5058 You can either mail yourself a copy by including a @samp{BCC} header in the
5059 mail message, or store a copy of the message directly to a file by
5060 including an @samp{FCC} header.
5062 If you use standard mail, you can automatically create a @samp{BCC} to
5066 (setq mail-self-blind t)
5070 in your @file{.emacs} file. You can automatically include an @samp{FCC}
5071 field by putting something like the following in your @file{.emacs}
5075 (setq mail-archive-file-name (expand-file-name "~/outgoing"))
5078 The output file will be in Unix mail format, which can be read directly
5079 by VM, but not always by Rmail. @xref{Learning how to do something}.
5081 If you use @code{mh-e}, add an @samp{FCC} or @samp{BCC} field to your
5084 It does not work to put @samp{set record filename} in the @file{.mailrc}
5087 @node Expanding aliases when sending mail, Rmail thinks all messages are one big one, Saving a copy of outgoing mail, Mail and news
5088 @section Why doesn't Emacs expand my aliases when sending mail?
5089 @cindex Expanding aliases when sending mail
5090 @cindex Mail alias expansion
5091 @cindex Sending mail with aliases
5096 You must separate multiple addresses in the headers of the mail buffer
5097 with commas. This is because Emacs supports RFC822 standard addresses
5101 To: Willy Smith <wks@@xpnsv.lwyrs.com>
5104 However, you do not need to---and probably should not, unless your
5105 system's version of @file{/usr/ucb/mail} (a.k.a.@: @code{mailx})
5106 supports RFC822---separate addresses with commas in your
5107 @file{~/.mailrc} file.
5110 Emacs normally only reads the @file{.mailrc} file once per session,
5111 when you start to compose your first mail message. If you edit
5112 @file{.mailrc}, you can type @kbd{M-x rebuild-mail-abbrevs @key{RET}} to
5113 make Emacs reread @file{~/.mailrc}.
5116 If you like, you can expand mail aliases as abbrevs, as soon as you
5117 type them in. To enable this feature, execute the following:
5120 (add-hook 'mail-mode-hook 'mail-abbrevs-setup)
5123 Note that the aliases are expanded automatically only after you type
5124 @key{RET} or a punctuation character (e.g. @kbd{,}). You can force their
5125 expansion by moving point to the end of the alias and typing @kbd{C-x a e}
5126 (@kbd{M-x expand-abbrev}).
5129 @node Rmail thinks all messages are one big one, Sorting the messages in an Rmail folder, Expanding aliases when sending mail, Mail and news
5130 @section Why does Rmail think all my saved messages are one big message?
5131 @cindex Rmail thinks all messages are one large message
5133 A file created through the @samp{FCC} field in a message is in Unix mail
5134 format, not the format that Rmail uses (BABYL format). Rmail will try
5135 to convert a Unix mail file into BABYL format on input, but sometimes it
5136 makes errors. For guaranteed safety, you can make the
5137 @file{saved-messages} file be an inbox for your Rmail file by using the
5138 function @code{set-rmail-inbox-list}.
5140 @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
5141 @section How can I sort the messages in my Rmail folder?
5142 @cindex Rmail, sorting messages in
5143 @cindex Folder, sorting messages in an Rmail
5144 @cindex Sorting messages in an Rmail folder
5146 In Rmail, type @kbd{C-c C-s C-h} to get a list of sorting functions
5147 and their key bindings.
5149 @node Rmail writes to /usr/spool/mail, Recovering mail files when Rmail munges them, Sorting the messages in an Rmail folder, Mail and news
5150 @section Why does Rmail need to write to @file{/usr/spool/mail}?
5151 @cindex Rmail and @file{/usr/spool/mail}
5152 @cindex @file{/usr/spool/mail} and Rmail
5154 This is the behavior of the @code{movemail} program which Rmail uses.
5155 This indicates that @code{movemail} is configured to use lock files.
5160 Certain systems require lock files to interlock access to mail files.
5161 On these systems, @code{movemail} must write lock files, or you risk losing
5162 mail. You simply must arrange to let @code{movemail} write them.
5164 Other systems use the @code{flock} system call to interlock access. On
5165 these systems, you should configure @code{movemail} to use @code{flock}.
5168 @node Recovering mail files when Rmail munges them, Replying to the sender of a message, Rmail writes to /usr/spool/mail, Mail and news
5169 @section How do I recover my mail files after Rmail munges their format?
5170 @cindex Recovering munged mail files
5171 @cindex Rmail munged my files
5172 @cindex Mail files, recovering those munged by Rmail
5174 If you have just done @kbd{M-x rmail-input} on a file and you don't want
5175 to save it in Rmail's format (called BABYL), just kill the buffer (with
5178 @cindex Exporting messages as Unix mail files
5179 If you typed @kbd{M-x rmail} and it read some messages out of your inbox
5180 and you want to put them in a Unix mail file, use @kbd{C-o} on each
5183 @cindex Converting from BABYL to Unix mail format
5184 @cindex @code{unrmail} command
5185 If you want to convert an existing file from BABYL format to Unix mail
5186 format, use the command @kbd{M-x unrmail}: it will prompt you for the
5187 input and output file names.
5189 @node Replying to the sender of a message, MIME with Emacs mail packages, Recovering mail files when Rmail munges them, Mail and news
5190 @section How can I force Rmail to reply to the sender of a message, but not the other recipients?
5191 @cindex Replying only to the sender of a message
5192 @cindex Sender, replying only to
5193 @cindex Rmail, replying to the sender of a message in
5195 @email{isaacson@@seas.upenn.edu, Ron Isaacson} says: When you hit
5196 @key{r} to reply in Rmail, by default it CCs all of the original
5197 recipients (everyone on the original @samp{To} and @samp{CC}
5198 lists). With a prefix argument (i.e., typing @kbd{C-u} before @key{r}),
5199 it replies only to the sender. However, going through the whole
5200 @kbd{C-u} business every time you want to reply is a pain. This is the
5201 best fix I've been able to come up with:
5204 (defun rmail-reply-t ()
5205 "Reply only to the sender of the current message. (See rmail-reply.)"
5209 (add-hook 'rmail-mode-hook
5211 (define-key rmail-mode-map "r" 'rmail-reply-t)
5212 (define-key rmail-mode-map "R" 'rmail-reply)))
5215 @node MIME with Emacs mail packages, Automatically starting a mail or news reader, Replying to the sender of a message, Mail and news
5216 @section How can I get my favorite Emacs mail package to support MIME?
5217 @cindex MIME and Emacs mail packages
5218 @cindex Mail packages and MIME
5219 @cindex FAQ for MIME and Emacs
5221 Read the Emacs MIME FAQ, maintained by @email{trey@@cs.berkeley.edu,
5222 MacDonald Hall Jackson} at
5224 @uref{http://bmrc.berkeley.edu/~trey/emacs/mime.html}
5226 Version 6.x of VM supports MIME. @xref{VM}. Gnus supports MIME in mail
5227 and news messages as of version 5.8.1 (Pterodactyl). Rmail has limited
5228 support for single-part MIME messages beginning with Emacs 20.3.
5230 @node Automatically starting a mail or news reader, Reading news with Emacs, MIME with Emacs mail packages, Mail and news
5231 @section How do I make Emacs automatically start my mail/news reader?
5232 @cindex Mail reader, starting automatically
5233 @cindex News reader, starting automatically
5234 @cindex Starting mail/news reader automatically
5236 To start Emacs in Gnus:
5249 A more convenient way to start with Gnus:
5252 alias gnus 'emacs -f gnus'
5256 It is probably unwise to automatically start your mail or news reader
5257 from your @file{.emacs} file. This would cause problems if you needed to run
5258 two copies of Emacs at the same time. Also, this would make it difficult for
5259 you to start Emacs quickly when you needed to.
5261 @node Reading news with Emacs, Gnus does not work with NNTP, Automatically starting a mail or news reader, Mail and news
5262 @section How do I read news under Emacs?
5263 @cindex Reading news under Emacs
5264 @cindex Usenet reader in Emacs
5265 @cindex Gnus newsreader
5267 Use @kbd{M-x gnus}. It is documented in Info (@pxref{Learning how to do
5270 @node Gnus does not work with NNTP, Viewing articles with embedded underlining, Reading news with Emacs, Mail and news
5271 @section Why doesn't Gnus work via NNTP?
5272 @cindex Gnus and NNTP
5273 @cindex NNTP, Gnus fails to work with
5275 There is a bug in NNTP version 1.5.10, such that when multiple requests
5276 are sent to the NNTP server, the server only handles the first one
5277 before blocking waiting for more input which never comes. NNTP version
5278 1.5.11 claims to fix this.
5280 You can work around the bug inside Emacs like this:
5283 (setq nntp-maximum-request 1)
5286 You can find out what version of NNTP your news server is running by
5287 telnetting to the NNTP port (usually 119) on the news server machine
5288 (i.e., @kbd{telnet server-machine 119}). The server should give its
5289 version number in the welcome message. Type @kbd{quit} to get out.
5291 @xref{Spontaneous entry into isearch-mode}, for some additional ideas.
5293 @node Viewing articles with embedded underlining, Saving a multi-part Gnus posting, Gnus does not work with NNTP, Mail and news
5294 @section How do I view news articles with embedded underlining (e.g., ClariNews)?
5295 @cindex Underlining, embedded in news articles
5296 @cindex News articles with embedded underlining
5297 @cindex Embedded underlining in news articles
5299 Underlining appears like this:
5302 _^Hu_^Hn_^Hd_^He_^Hr_^Hl_^Hi_^Hn_^Hi_^Hn_^Hg
5305 @email{abraham@@dina.kvl.dk, Per Abrahamsen} suggests using the following
5306 code, which uses the underline face to turn such text into true
5307 underlining, inconjunction with Gnus:
5310 (defun gnus-article-prepare-overstrike ()
5311 ;; Prepare article for overstrike commands.
5313 (set-buffer gnus-article-buffer)
5314 (let ((buffer-read-only nil))
5315 (goto-char (point-min))
5316 (while (search-forward "\b" nil t)
5317 (let ((next (following-char))
5318 (previous (char-after (- (point) 2))))
5319 (cond ((eq next previous)
5320 (delete-region (- (point) 2) (point))
5321 (put-text-property (point) (1+ (point))
5324 (delete-region (1- (point)) (1+ (point)))
5325 (put-text-property (1- (point)) (point)
5328 (delete-region (- (point) 2) (point))
5329 (put-text-property (point) (1+ (point))
5330 'face 'underline))))))))
5332 (add-hook 'gnus-article-prepare-hook 'gnus-article-prepare-overstrike)
5335 Latest versions of Gnus do such a conversion automatically.
5337 If you prefer to do away with underlining altogether, you can
5338 destructively remove it with @kbd{M-x ununderline-region}; do this
5342 (add-hook 'gnus-article-prepare-hook
5343 (lambda () (ununderline-region (point-min) (point-max))))
5346 @node Saving a multi-part Gnus posting, Starting Gnus faster, Viewing articles with embedded underlining, Mail and news
5347 @section How do I save all the items of a multi-part posting in Gnus?
5348 @cindex Multi-part postings in Gnus, saving
5349 @cindex Saving multi-part postings in Gnus
5350 @cindex Gnus, saving multi-part postings in
5352 Use @code{gnus-uu}. Type @kbd{C-c C-v C-h} in the Gnus summary buffer
5353 to see a list of available commands.
5355 @node Starting Gnus faster, Catching up in all newsgroups, Saving a multi-part Gnus posting, Mail and news
5356 @section How do I make Gnus start up faster?
5357 @cindex Faster, starting Gnus
5358 @cindex Starting Gnus faster
5359 @cindex Gnus, starting faster
5361 From the Gnus FAQ (@pxref{Learning more about Gnus}):
5364 @email{pktiwari@@eos.ncsu.edu, Pranav Kumar Tiwari} writes: I posted
5365 the same query recently and I got an answer to it. I am going to
5366 repeat the answer. What you need is a newer version of gnus, version
5367 5.0.4+. I am using 5.0.12 and it works fine with me with the
5371 (setq gnus-check-new-newsgroups nil
5372 gnus-read-active-file 'some
5373 gnus-nov-is-evil nil
5374 gnus-select-method '(nntp gnus-nntp-server))
5378 @node Catching up in all newsgroups, Killing based on nonstandard headers, Starting Gnus faster, Mail and news
5379 @section How do I catch up all newsgroups in Gnus?
5380 @cindex Catching up all newsgroups in Gnus
5381 @cindex Gnus, Catching up all newsgroups in
5383 In the @file{*Newsgroup*} buffer, type @kbd{M-< C-x ( c y C-x ) M-0 C-x e}
5385 Leave off the initial @kbd{M-<} if you only want to catch up from point
5386 to the end of the @file{*Newsgroup*} buffer.
5388 @node Killing based on nonstandard headers, Removing flashing messages, Catching up in all newsgroups, Mail and news
5389 @section Why can't I kill in Gnus based on the Newsgroups/Keywords/Control headers?
5390 @cindex Killing articles based on nonstandard headers
5391 @cindex Newsgroups header, killing articles based on
5392 @cindex Keywords header, killing articles based on
5393 @cindex Control header, killing articles based on
5395 Gnus will complain that the @samp{Newsgroups}, @samp{Keywords}, and
5396 @samp{Control} headers are ``Unknown header'' fields.
5398 For the @samp{Newsgroups} header, there is an easy workaround: kill on the
5399 @samp{Xref} header instead, which will be present on any cross-posted article
5400 (as long as your site carries the cross-post group).
5402 If you really want to kill on one of these headers, you can do it like
5406 (gnus-kill nil "^Newsgroups: .*\\(bad\\.group\\|worse\\.group\\)")
5409 @node Removing flashing messages, Catch-up is slow in Gnus, Killing based on nonstandard headers, Mail and news
5410 @section How do I get rid of flashing messages in Gnus for slow connections?
5411 @cindex Flashing Gnus messages, removing
5412 @cindex Removing flashing Gnus messages
5413 @cindex Slow connections causing flashing messages in Gnus
5414 @cindex Gnus, flashing messages in
5416 Set @code{nntp-debug-read} to @code{nil}.
5418 @node Catch-up is slow in Gnus, Gnus hangs for a long time, Removing flashing messages, Mail and news
5419 @section Why is catch up slow in Gnus?
5420 @cindex Slow catch up in Gnus
5421 @cindex Gnus is slow when catching up
5422 @cindex Crosspostings make Gnus catching up slow
5424 Because Gnus is marking crosspostings read. You can control this with
5425 the variable @code{gnus-use-cross-reference}.
5427 @node Gnus hangs for a long time, Learning more about Gnus, Catch-up is slow in Gnus, Mail and news
5428 @section Why does Gnus hang for a long time when posting?
5429 @cindex Hangs in Gnus
5430 @cindex Gnus hangs while posting
5431 @cindex Posting, Gnus hangs wile
5433 @email{tale@@uunet.uu.net, David Lawrence} explains:
5436 The problem is almost always interaction between NNTP and C News. NNTP
5437 POST asks C News's @code{inews} to not background itself but rather hang
5438 around and give its exit status so it knows whether the post was successful.
5439 (That wait will on some systems not return the exit status of the
5440 waited for job is a different sort of problem.) It ends up taking a
5441 long time because @code{inews} is calling @code{relaynews}, which often
5442 waits for another @code{relaynews} to free the lock on the news system
5443 so it can file the article.
5445 My preferred solution is to change @code{inews} to not call
5446 @code{relaynews}, but rather use @code{newsspool}. This loses some
5447 error-catching functionality, but is for the most part safe as
5448 @code{inews} will detect a lot of the errors on its own. The C News
5449 folks have sped up @code{inews}, too, so speed should look better to
5450 most folks as that update propagates around.
5453 @node Learning more about Gnus, , Gnus hangs for a long time, Mail and news
5454 @section Where can I find out more about Gnus?
5455 @cindex FAQ for Gnus
5457 @cindex Learning more about GNU
5459 Look for the Gnus FAQ, available at
5461 @uref{http://www.ccs.neu.edu/software/contrib/gnus/}
5463 @node Concept index, , Mail and news, Top
5464 @unnumbered Concept Index