1 \input texinfo @c -*- mode: texinfo; -*-
3 @setfilename ../info/efaq
4 @settitle GNU Emacs FAQ
9 @c This is used in many places
12 @c This file is maintained by Romain Francoise <rfrancoise@gnu.org>.
13 @c Feel free to install changes without prior permission (but I'd
14 @c appreciate a notice if you do).
17 Copyright (C) 2001, 2002, 2003, 2004, 2005, 2006 Free Software Foundation, Inc.
18 Copyright 1994,1995,1996,1997,1998,1999,2000 Reuven M. Lerner@*
19 Copyright 1992,1993 Steven Byrnes@*
20 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 heavily edited since it was included in the Emacs
44 * Emacs FAQ: (efaq). Frequently Asked Questions about Emacs.
47 @c The @titlepage stuff only appears in the printed version
50 @center @titlefont{GNU Emacs FAQ}
52 @c The following two commands start the copyright page.
54 @vskip 0pt plus 1filll
58 @node Top, FAQ notation, (dir), (dir)
60 This is the GNU Emacs FAQ, last updated on @today{}.
62 This FAQ is maintained as a part of GNU Emacs. If you find any errors,
63 or have any suggestions, please use @kbd{M-x report-emacs-bug} to report
73 * Compiling and installing Emacs::
74 * Finding Emacs and related packages::
75 * Major packages and programs::
77 * Alternate character sets::
82 @c ------------------------------------------------------------
83 @node FAQ notation, General questions, Top, Top
87 This chapter describes notation used in the GNU Emacs FAQ, as well as in
88 the Emacs documentation. Consult this section if this is the first time
89 you are reading the FAQ, or if you are confused by notation or terms
96 * File-name conventions::
100 @node Basic keys, Extended commands, FAQ notation, FAQ notation
101 @section What do these mean: @kbd{C-h}, @kbd{C-M-a}, @key{RET}, @kbd{@key{ESC} a}, etc.?
103 @cindex Control key, notation for
104 @cindex @key{Meta} key, notation for
105 @cindex Control-Meta characters, notation for
106 @cindex @kbd{C-h}, definition of
107 @cindex @kbd{C-M-h}, definition of
108 @cindex @key{DEL}, definition of
109 @cindex @key{ESC}, definition of
110 @cindex @key{LFD}, definition of
111 @cindex @key{RET}, definition of
112 @cindex @key{SPC}, definition of
113 @cindex @key{TAB}, definition of
114 @cindex Notation for keys
119 @kbd{C-x}: press the @key{x} key while holding down the @key{Control} key
122 @kbd{M-x}: press the @key{x} key while holding down the @key{Meta} key
123 (if your computer doesn't have a @key{Meta} key, @pxref{No Meta key})
126 @kbd{M-C-x}: press the @key{x} key while holding down both @key{Control}
130 @kbd{C-M-x}: a synonym for the above
133 @key{LFD}: Linefeed or Newline; same as @kbd{C-j}
136 @key{RET}: @key{Return}, sometimes marked @key{Enter}; same as @kbd{C-m}
139 @key{DEL}: @key{Delete}, usually @strong{not} the same as
140 @key{Backspace}; same as @kbd{C-?} (see @ref{Backspace invokes help}, if
141 deleting invokes Emacs help)
144 @key{ESC}: Escape; same as @kbd{C-[}
147 @key{TAB}: Tab; same as @kbd{C-i}
154 Key sequences longer than one key (and some single-key sequences) are
155 written inside quotes or on lines by themselves, like this:
158 @kbd{M-x frobnicate-while-foo RET}
162 Any real spaces in such a key sequence should be ignored; only @key{SPC}
163 really means press the space key.
165 The @acronym{ASCII} code sent by @kbd{C-x} (except for @kbd{C-?}) is the value
166 that would be sent by pressing just @key{x} minus 96 (or 64 for
167 upper-case @key{X}) and will be from 0 to 31. On Unix and GNU/Linux
168 terminals, the @acronym{ASCII} code sent by @kbd{M-x} is the sum of 128 and the
169 @acronym{ASCII} code that would be sent by pressing just @key{x}. Essentially,
170 @key{Control} turns off bits 5 and 6 and @key{Meta} turns on bit
172 DOS and Windows terminals don't set bit 7 when the @key{Meta} key is
175 @kbd{C-?} (aka @key{DEL}) is @acronym{ASCII} code 127. It is a misnomer to call
176 @kbd{C-?} a ``control'' key, since 127 has both bits 5 and 6 turned ON.
177 Also, on very few keyboards does @kbd{C-?} generate @acronym{ASCII} code 127.
179 @inforef{Text Characters, Text Characters, emacs}, and @inforef{Keys,
180 Keys, emacs}, for more information. (@xref{On-line manual}, for more
181 information about Info.)
183 @node Extended commands, On-line manual, Basic keys, FAQ notation
184 @section What does @file{M-x @var{command}} mean?
185 @cindex Extended commands
186 @cindex Commands, extended
187 @cindex M-x, meaning of
189 @kbd{M-x @var{command}} means type @kbd{M-x}, then type the name of the
190 command, then type @key{RET}. (@xref{Basic keys}, if you're not sure
191 what @kbd{M-x} and @key{RET} mean.)
193 @kbd{M-x} (by default) invokes the command
194 @code{execute-extended-command}. This command allows you to run any
195 Emacs command if you can remember the command's name. If you can't
196 remember the command's name, you can type @key{TAB} and @key{SPC} for
197 completion, @key{?} for a list of possibilities, and @kbd{M-p} and
198 @kbd{M-n} (or up-arrow and down-arrow on terminals that have these
199 editing keys) to see previous commands entered. An Emacs @dfn{command}
200 is an @dfn{interactive} Emacs function.
203 Your system administrator may have bound other key sequences to invoke
204 @code{execute-extended-command}. A function key labeled @kbd{Do} is a
205 good candidate for this, on keyboards that have such a key.
207 If you need to run non-interactive Emacs functions, see @ref{Evaluating
210 @node On-line manual, File-name conventions, Extended commands, FAQ notation
211 @section How do I read topic XXX in the on-line manual?
212 @cindex On-line manual, reading topics in
213 @cindex Reading topics in the on-line manual
214 @cindex Finding topics in the on-line manual
215 @cindex Info, finding topics in
217 When we refer you to some @var{topic} in the on-line manual, you can
218 read this manual node inside Emacs (assuming nothing is broken) by
219 typing @kbd{C-h i m emacs @key{RET} m @var{topic} @key{RET}}.
221 This invokes Info, the GNU hypertext documentation browser. If you don't
222 already know how to use Info, type @key{?} from within Info.
224 If we refer to @var{topic}:@var{subtopic}, type @kbd{C-h i m emacs
225 @key{RET} m @var{topic} @key{RET} m @var{subtopic} @key{RET}}.
227 If these commands don't work as expected, your system administrator may
228 not have installed the Info files, or may have installed them
229 improperly. In this case you should complain.
231 @xref{Getting a printed manual}, if you would like a paper copy of the
234 @node File-name conventions, Common acronyms, On-line manual, FAQ notation
235 @section What are @file{etc/SERVICE}, @file{src/config.h}, and @file{lisp/default.el}?
236 @cindex File-name conventions
237 @cindex Conventions for file names
238 @cindex Directories and files that come with Emacs
240 These are files that come with Emacs. The Emacs distribution is divided
241 into subdirectories; the important ones are @file{etc}, @file{lisp}, and
244 If you use Emacs, but don't know where it is kept on your system, start
245 Emacs, then type @kbd{C-h v data-directory @key{RET}}. The directory
246 name displayed by this will be the full pathname of the installed
247 @file{etc} directory. (This full path is recorded in the Emacs variable
248 @code{data-directory}, and @kbd{C-h v} displays the value and the
249 documentation of a variable.)
251 The location of your Info directory (i.e., where on-line documentation
252 is stored) is kept in the variable @code{Info-default-directory-list}. Use
253 @kbd{C-h v Info-default-directory-list @key{RET}} to see the value of
254 this variable, which will be a list of directory names. The last
255 directory in that list is probably where most Info files are stored. By
256 default, Info documentation is placed in @file{/usr/local/info}.
258 Some of these files are available individually via FTP or e-mail; see
259 @ref{Informational files for Emacs}. They all are available in the
260 source distribution. Many of the files in the @file{etc} directory are
261 also available via the Emacs @samp{Help} menu, or by typing @kbd{C-h ?}
262 (@kbd{M-x help-for-help}).
264 Your system administrator may have removed the @file{src} directory and
265 many files from the @file{etc} directory.
267 @node Common acronyms, , File-name conventions, FAQ notation
268 @section What are FSF, LPF, OSF, GNU, RMS, FTP, and GPL?
269 @cindex FSF, definition of
270 @cindex LPF, definition of
271 @cindex OSF, definition of
272 @cindex GNU, definition of
273 @cindex RMS, definition of
274 @cindex Stallman, Richard, acronym for
275 @cindex Richard Stallman, acronym for
276 @cindex FTP, definition of
277 @cindex GPL, definition of
278 @cindex Acronyms, definitions for
279 @cindex Common acronyms, definitions for
284 Free Software Foundation
287 League for Programming Freedom
290 Open Software Foundation
296 Richard Matthew Stallman
299 File Transfer Protocol
302 GNU General Public License
306 Avoid confusing the FSF, the LPF, and the OSF. The LPF opposes
307 look-and-feel copyrights and software patents. The FSF aims to make
308 high quality free software available for everyone. The OSF is a
309 consortium of computer vendors which develops commercial software for
312 The word ``free'' in the title of the Free Software Foundation refers to
313 ``freedom,'' not ``zero dollars.'' Anyone can charge any price for
314 GPL-covered software that they want to. However, in practice, the
315 freedom enforced by the GPL leads to low prices, because you can always
316 get the software for less money from someone else, since everyone has
317 the right to resell or give away GPL-covered software.
319 @c ------------------------------------------------------------
320 @node General questions, Getting help, FAQ notation, Top
321 @chapter General questions
322 @cindex General questions
324 This chapter contains general questions having to do with Emacs, the
325 Free Software Foundation, and related organizations.
329 * Real meaning of copyleft::
330 * Guidelines for newsgroup postings::
331 * Newsgroup archives::
333 * Unsubscribing from Emacs lists::
334 * Contacting the FSF::
337 @node The LPF, Real meaning of copyleft, General questions, General questions
338 @section What is the LPF?
339 @cindex LPF, description of
340 @cindex League for Programming Freedom
341 @cindex Software patents, opposition to
342 @cindex Patents for software, opposition to
344 The LPF opposes the expanding danger of software patents and
345 look-and-feel copyrights. To get more information, feel free to contact
346 the LPF via e-mail or otherwise. You may also contact
347 @email{jbw@@cs.bu.edu, Joe Wells}; he will be happy to talk to you
350 You can find more information about the LPF in the file @file{etc/LPF}.
351 More papers describing the LPF's views are available on the Internet and
352 also from @uref{http://lpf.ai.mit.edu/, the LPF home page}.
354 @node Real meaning of copyleft, Guidelines for newsgroup postings, The LPF, General questions
355 @section What is the real legal meaning of the GNU copyleft?
356 @cindex Copyleft, real meaning of
357 @cindex GPL, real meaning of
358 @cindex General Public License, real meaning of
359 @cindex Discussion of the GPL
361 The real legal meaning of the GNU General Public License (copyleft) will
362 only be known if and when a judge rules on its validity and scope.
363 There has never been a copyright infringement case involving the GPL to
364 set any precedents. Please take any discussion regarding this issue to
365 the newsgroup @uref{news:gnu.misc.discuss}, which was created to hold the
366 extensive flame wars on the subject.
371 The legal meaning of the GNU copyleft is less important than the spirit,
372 which is that Emacs is a free software project and that work pertaining
373 to Emacs should also be free software. ``Free'' means that all users
374 have the freedom to study, share, change and improve Emacs. To make
375 sure everyone has this freedom, pass along source code when you
376 distribute any version of Emacs or a related program, and give the
377 recipients the same freedom that you enjoyed.
380 @node Guidelines for newsgroup postings, Newsgroup archives, Real meaning of copyleft, General questions
381 @section What are appropriate messages for @uref{news:gnu.emacs.help}, @uref{news:gnu.emacs.bug}, @uref{news:comp.emacs}, etc.?
382 @cindex Newsgroups, appropriate messages for
383 @cindex GNU newsgroups, appropriate messages for
384 @cindex Usenet groups, appropriate messages for
385 @cindex Mailing lists, appropriate messages for
386 @cindex Posting messages to newsgroups
388 @cindex GNU mailing lists
389 The file @file{etc/MAILINGLISTS} describes the purpose of each GNU
390 mailing list. (@xref{Informational files for Emacs}, if you want a copy
391 of the file.) For those lists which are gatewayed with newsgroups, it
392 lists both the newsgroup name and the mailing list address.
394 The newsgroup @uref{news:comp.emacs} is for discussion of Emacs programs
395 in general. This includes Emacs along with various other
396 implementations, such as XEmacs, JOVE, MicroEmacs, Freemacs, MG,
397 Unipress, CCA, and Epsilon.
399 Many people post Emacs questions to @uref{news:comp.emacs} because they
400 don't receive any of the @code{gnu.*} newsgroups. Arguments have been
401 made both for and against posting GNU-Emacs-specific material to
402 @uref{news:comp.emacs}. You have to decide for yourself.
404 Messages advocating ``non-free'' software are considered unacceptable on
405 any of the @code{gnu.*} newsgroups except for @uref{news:gnu.misc.discuss},
406 which was created to hold the extensive flame-wars on the subject.
407 ``Non-free'' software includes any software for which the end user can't
408 freely modify the source code and exchange enhancements. Be careful to
409 remove the @code{gnu.*} groups from the @samp{Newsgroups:} line when
410 posting a followup that recommends such software.
412 @uref{news:gnu.emacs.bug} is a place where bug reports appear, but avoid
413 posting bug reports to this newsgroup directly (@pxref{Reporting bugs}).
415 @node Newsgroup archives, Reporting bugs, Guidelines for newsgroup postings, General questions
416 @section Where can I get old postings to @uref{news:gnu.emacs.help} and other GNU groups?
417 @cindex Archived postings from @code{gnu.emacs.help}
418 @cindex Usenet archives for GNU groups
419 @cindex Old Usenet postings for GNU groups
421 The FSF has maintained archives of all of the GNU mailing lists for many
422 years, although there may be some unintentional gaps in coverage. The
423 archive is not particularly well organized or easy to retrieve
424 individual postings from, but pretty much everything is there.
426 The archive is at @uref{ftp://ftp-mailing-list-archives.gnu.org}.
428 The archive can be browsed over the web at
429 @uref{http://mail.gnu.org/archive/html/, the GNU mail archive}.
431 Web-based Usenet search services, such as
432 @uref{http://groups.google.com, Google}, also archive the
435 @node Reporting bugs, Unsubscribing from Emacs lists, Newsgroup archives, General questions
436 @section Where should I report bugs and other problems with Emacs?
437 @cindex Bug reporting
438 @cindex Good bug reports
439 @cindex How to submit a bug report
440 @cindex Reporting bugs
442 The correct way to report Emacs bugs is by e-mail to
443 @email{bug-gnu-emacs@@gnu.org}. Anything sent here also appears in the
444 newsgroup @uref{news:gnu.emacs.bug}, but please use e-mail instead of
445 news to submit the bug report. This ensures a reliable return address
446 so you can be contacted for further details.
448 Be sure to read the ``Bugs'' section of the Emacs manual before reporting
449 a bug to bug-gnu-emacs! The manual describes in detail how to submit a
450 useful bug report. (@xref{On-line manual}, if you don't know how to read the
456 Sending bug reports to @email{help-gnu-emacs@@gnu.org} (which has the
457 effect of posting on @uref{news:gnu.emacs.help}) is undesirable because
458 it takes the time of an unnecessarily large group of people, most of
459 whom are just users and have no idea how to fix these problem.
460 @email{bug-gnu-emacs@@gnu.org} reaches a much smaller group of people
461 who are more likely to know what to do and have expressed a wish to
462 receive more messages about Emacs than the others.
465 RMS says it is sometimes fine to post to @uref{news:gnu.emacs.help}:
468 If you have reported a bug and you don't hear about a possible fix,
469 then after a suitable delay (such as a week) it is okay to post on
470 @code{gnu.emacs.help} asking if anyone can help you.
473 If you are unsure whether you have found a bug, consider the following
474 non-exhaustive list, courtesy of RMS:
477 If Emacs crashes, that is a bug. If Emacs gets compilation errors
478 while building, that is a bug. If Emacs crashes while building, that
479 is a bug. If Lisp code does not do what the documentation says it
483 @node Unsubscribing from Emacs lists, Contacting the FSF, Reporting bugs, General questions
484 @section How do I unsubscribe from this mailing list?
485 @cindex Unsubscribing from GNU mailing lists
486 @cindex Removing yourself from GNU mailing lists
488 If you are receiving a GNU mailing list named @var{list}, you might be
489 able to unsubscribe from it by sending a request to the address
490 @email{@var{list}-request@@gnu.org}. However, this will not work if you are
491 not listed on the main mailing list, but instead receive the mail from a
492 distribution point. In that case, you will have to track down at which
493 distribution point you are listed. Inspecting the @samp{Received} headers
494 on the mail messages may help, along with liberal use of the @samp{EXPN} or
495 @samp{VRFY} sendmail commands through @samp{telnet @var{site-address}
496 smtp}. Ask your postmaster for help, if you cannot figure out these
499 @node Contacting the FSF, , Unsubscribing from Emacs lists, General questions
500 @section What is the current address of the FSF?
501 @cindex Snail mail address of the FSF
502 @cindex Postal address of the FSF
503 @cindex Contracting the FSF
504 @cindex Free Software Foundation, contacting
518 @uref{http://www.gnu.org/}
521 Free Software Foundation@*
522 51 Franklin Street, Fifth Floor@*
523 Boston, MA 02110-1301@*
528 @cindex Ordering GNU software
529 For details on how to order items directly from the FSF, see the
530 @uref{http://www.gnu.org/order/order.html, GNU Web site}.
532 @c ------------------------------------------------------------
533 @node Getting help, Status of Emacs, General questions, Top
534 @chapter Getting help
537 This chapter tells you how to get help with Emacs
541 * Learning how to do something::
542 * Getting a printed manual::
543 * Emacs Lisp documentation::
544 * Installing Texinfo documentation::
545 * Printing a Texinfo file::
546 * Viewing Info files outside of Emacs::
547 * Informational files for Emacs::
548 * Help installing Emacs::
549 * Obtaining the FAQ::
552 @node Basic editing, Learning how to do something, Getting help, Getting help
553 @section I'm just starting Emacs; how do I do basic editing?
554 @cindex Basic editing with Emacs
555 @cindex Beginning editing
556 @cindex Tutorial, invoking the
557 @cindex Self-paced tutorial, invoking the
558 @cindex Help system, entering the
560 Type @kbd{C-h t} to invoke the self-paced tutorial. Just typing
561 @kbd{C-h} enters the help system. Starting with Emacs 22, the tutorial
562 is available in many foreign languages such as French, German, Japanese,
563 Russian, etc. Use @kbd{M-x help-with-tutorial-spec-language @key{RET}}
564 to choose your language and start the tutorial.
566 Your system administrator may have changed @kbd{C-h} to act like
567 @key{DEL} to deal with local keyboards. You can use @kbd{M-x
568 help-for-help} instead to invoke help. To discover what key (if any)
569 invokes help on your system, type @kbd{M-x where-is @key{RET}
570 help-for-help @key{RET}}. This will print a comma-separated list of key
571 sequences in the echo area. Ignore the last character in each key
572 sequence listed. Each of the resulting key sequences invokes help.
574 Emacs help works best if it is invoked by a single key whose value
575 should be stored in the variable @code{help-char}.
577 @node Learning how to do something, Getting a printed manual, Basic editing, Getting help
578 @section How do I find out how to do something in Emacs?
579 @cindex Help for Emacs
580 @cindex Learning to do something in Emacs
581 @cindex Reference card for Emacs
582 @cindex Overview of help systems
584 There are several methods for finding out how to do things in Emacs.
588 @cindex Reading the Emacs manual
590 The complete text of the Emacs manual is available on-line via the Info
591 hypertext reader. Type @kbd{C-h r} to display the manual in Info mode.
592 Typing @key{h} immediately after entering Info will provide a short
593 tutorial on how to use it.
595 @cindex Lookup a subject in a manual
596 @cindex Index search in a manual
598 To quickly locate the section of the manual which discusses a certain
599 issue, or describes a command or a variable, type @kbd{C-h i m emacs
600 @key{RET} i @var{topic} @key{RET}}, where @var{topic} is the name of the
601 topic, the command, or the variable which you are looking for. If this
602 does not land you on the right place in the manual, press @kbd{,}
603 (comma) repeatedly until you find what you need. (The @kbd{i} and
604 @kbd{,} keys invoke the index-searching functions, which look for the
605 @var{topic} you type in all the indices of the Emacs manual.)
609 You can list all of the commands whose names contain a certain word
610 (actually which match a regular expression) using @kbd{C-h a} (@kbd{M-x
613 @cindex Command description in the manual
615 The command @kbd{C-h F} (@code{Info-goto-emacs-command-node}) prompts
616 for the name of a command, and then attempts to find the section in the
617 Emacs manual where that command is described.
619 @cindex Finding commands and variables
621 You can list all of the functions and variables whose names contain a
622 certain word using @kbd{M-x apropos}.
625 You can list all of the functions and variables whose documentation
626 matches a regular expression or a string, using @kbd{M-x
627 apropos-documentation}.
630 You can order a hardcopy of the manual from the FSF. @xref{Getting a
633 @cindex Reference cards, in other languages
635 You can get a printed reference card listing commands and keys to
636 invoke them. You can order one from the FSF for $1 (or 10 for $5),
637 or you can print your own from the @file{etc/refcard.tex} or
638 @file{etc/refcard.ps} files in the Emacs distribution. Beginning with
639 version 21.1, the Emacs distribution comes with translations of the
640 reference card into several languages; look for files named
641 @file{etc/@var{lang}-refcard.*}, where @var{lang} is a two-letter code
642 of the language. For example, the German version of the reference card
643 is in the files @file{etc/de-refcard.tex} and @file{etc/de-refcard.ps}.
646 There are many other commands in Emacs for getting help and
647 information. To get a list of these commands, type @samp{?} after
652 @node Getting a printed manual, Emacs Lisp documentation, Learning how to do something, Getting help
653 @section How do I get a printed copy of the Emacs manual?
654 @cindex Printed Emacs manual, obtaining
655 @cindex Manual, obtaining a printed or HTML copy of
656 @cindex Emacs manual, obtaining a printed or HTML copy of
658 You can order a printed copy of the Emacs manual from the FSF. For
659 details see the @uref{http://www.gnu.org/order/order.html, GNU Web site}.
661 @c The number 620 below is version-dependent!
662 The full Texinfo source for the manual also comes in the @file{man}
663 directory of the Emacs distribution, if you're daring enough to try to
664 print out this 620-page manual yourself (@pxref{Printing a Texinfo
667 If you absolutely have to print your own copy, and you don't have @TeX{},
668 you can get a PostScript version from
670 @uref{http://www.gnu.org/software/emacs/manual/emacs.ps.gz}
672 @cindex HTML version of Emacs manual, obtaining
673 An HTML version of the manual is at
675 @uref{http://www.gnu.org/software/emacs/manual/emacs.html}
677 @xref{Learning how to do something}, for how to view the manual on-line.
679 @node Emacs Lisp documentation, Installing Texinfo documentation, Getting a printed manual, Getting help
680 @section Where can I get documentation on Emacs Lisp?
681 @cindex Documentation on Emacs Lisp
682 @cindex Function documentation
683 @cindex Variable documentation
684 @cindex Emacs Lisp Reference Manual
685 @cindex Reference manual for Emacs Lisp
687 Within Emacs, you can type @kbd{C-h f} to get the documentation for a
688 function, @kbd{C-h v} for a variable.
690 For more information, the Emacs Lisp Reference Manual is available
691 on-line, in Info format. @xref{Top, Emacs Lisp,, elisp, The
692 Emacs Lisp Reference Manual}.
694 You can also order a hardcopy of the manual, details on ordering it from
695 FSF are on the @uref{http://www.gnu.org/order/order.html, GNU Web site}.
697 An HTML version of the Emacs Lisp Reference Manual is available at
699 @uref{http://www.gnu.org/software/emacs/elisp-manual/elisp.html}
701 @node Installing Texinfo documentation, Printing a Texinfo file, Emacs Lisp documentation, Getting help
702 @section How do I install a piece of Texinfo documentation?
703 @cindex Texinfo documentation, installing
704 @cindex Installing Texinfo documentation
705 @cindex New Texinfo files, installing
706 @cindex Documentation, installing new Texinfo files
707 @cindex Info files, how to install
709 First, you must turn the Texinfo files into Info files. You may do this
710 using the stand-alone @file{makeinfo} program, available as part of the latest
713 @uref{ftp://ftp.gnu.org/pub/gnu/texinfo/texinfo-4.8.tar.gz}
715 and all mirrors of @samp{ftp.gnu.org} (for a list, @pxref{Current GNU
718 For information about the Texinfo format, read the Texinfo manual which
719 comes with the Texinfo package. This manual also comes installed in
720 Info format, so you can read it on-line; type @kbd{C-h i m texinfo
723 Alternatively, you could use the Emacs command @kbd{M-x
724 texinfo-format-buffer}, after visiting the Texinfo source file of the
725 manual you want to convert.
727 Neither @code{texinfo-format-buffer} nor @file{makeinfo} installs the
728 resulting Info files in Emacs's Info tree. To install Info files,
733 Move the files to the @file{info} directory in the installed Emacs
734 distribution. @xref{File-name conventions}, if you don't know where that
738 Run the @code{install-info} command, which is part of the Texinfo
739 distribution, to update the main Info directory menu, like this:
742 install-info --info-dir=@var{dir-path} @var{dir-path}/@var{file}
746 where @var{dir-path} is the full path to the directory where you copied
747 the produced Info file(s), and @var{file} is the name of the Info file
748 you produced and want to install.
750 If you don't have the @code{install-info} command installed, you can
751 edit the file @file{info/dir} in the installed Emacs distribution, and
752 add a line for the top level node in the Info package that you are
753 installing. Follow the examples already in this file. The format is:
756 * Topic: (relative-pathname). Short description of topic.
761 If you want to install Info files and you don't have the necessary
762 privileges, you have several options:
766 Info files don't actually need to be installed before being used. You
767 can feed a file name to the @code{Info-goto-node} command (invoked by
768 pressing @key{g} in Info mode) by typing the name of the file in
769 parentheses. This goes to the node named ``Top'' in that file. For
770 example, to view a Info file named @file{@var{info-file}} in your home
771 directory, you can type this:
774 @kbd{C-h i g (~/@var{info-file}) @key{RET}}
778 You can create your own Info directory. You can tell Emacs where that
779 Info directory is by adding its pathname to the value of the variable
780 @code{Info-default-directory-list}. For example, to use a private Info
781 directory which is a subdirectory of your home directory named @file{Info},
782 you could put this in your @file{.emacs} file:
785 (setq Info-default-directory-list
786 (cons "~/Info" Info-default-directory-list))
789 You will need a top-level Info file named @file{dir} in this directory
790 which has everything the system @file{dir} file has in it, except it should
791 list only entries for Info files in that directory. You might not need
792 it if all files in this directory were referenced by other @file{dir}
793 files. The node lists from all @file{dir} files in
794 @code{Info-default-directory-list} are merged by the Info system.
798 @node Printing a Texinfo file, Viewing Info files outside of Emacs, Installing Texinfo documentation, Getting help
799 @section How do I print a Texinfo file?
800 @cindex Printing a Texinfo file
801 @cindex Texinfo file, printing
802 @cindex Printing documentation
804 You can't get nicely printed output from Info files; you must still have
805 the original Texinfo source file for the manual you want to print.
807 Assuming you have @TeX{} installed on your system, follow these steps:
812 Make sure the first line of the Texinfo file looks like this:
818 You may need to change @samp{texinfo} to the full pathname of the
819 @file{texinfo.tex} file, which comes with Emacs as
820 @file{man/texinfo.tex} (or copy or link it into the current directory).
823 Type @kbd{texi2dvi @var{texinfo-source}}, where @var{texinfo-source} is
824 the name of the Texinfo source file for which you want to produce a
827 The @samp{texi2dvi} script is part of the GNU Texinfo distribution
828 (@pxref{Installing Texinfo documentation}).
831 Print the DVI file @file{@var{texinfo-source}.dvi} in the normal way for
832 printing DVI files at your site. For example, if you have a PostScript
833 printer, run the @code{dvips} program to print the DVI file on that
838 To get more general instructions, retrieve the latest Texinfo package
839 (@pxref{Installing Texinfo documentation}).
841 @node Viewing Info files outside of Emacs, Informational files for Emacs, Printing a Texinfo file, Getting help
842 @section Can I view Info files without using Emacs?
843 @cindex Viewing Info files
844 @cindex Info file viewers
845 @cindex Alternative Info file viewers
847 Yes. Here are some alternative programs:
852 @code{info}, a stand-alone version of the Info program, comes as part of
853 the Texinfo package. @xref{Installing Texinfo documentation}, for
857 Xinfo, a stand-alone version of the Info program that runs under X
858 Window system. You can get it at
859 @uref{ftp://ftp.gnu.org/pub/gnu/xinfo/xinfo-1.01.01.tar.gz} and all
860 mirrors of @samp{ftp.gnu.org} (see @ref{Current GNU distributions}, for a
864 Tkinfo, an Info viewer that runs under X Window system and uses Tcl/Tk.
865 You can get Tkinfo at
866 @uref{http://math-www.uni-paderborn.de/~axel/tkinfo/}.
870 @node Informational files for Emacs, Help installing Emacs, Viewing Info files outside of Emacs, Getting help
871 @section What informational files are available for Emacs?
872 @cindex Informational files included with Emacs
873 @cindex Files included with Emacs
874 @cindex @file{COPYING}, description of file
875 @cindex @file{DISTRIB}, description of file
876 @cindex @file{FTP}, description of file
877 @cindex @file{GNU}, description of file
878 @cindex @file{INTERVIEW}, description of file
879 @cindex @file{LPF}, description of file
880 @cindex @file{MACHINES}, description of file
881 @cindex @file{MAILINGLISTS}, description of file
882 @cindex @file{NEWS}, description of file
883 @cindex @file{SERVICE}, description of file
884 @cindex @file{SUN-SUPPORT}, description of file
886 This isn't a frequently asked question, but it should be! A variety of
887 informational files about Emacs and relevant aspects of the GNU project
888 are available for you to read.
890 The following files are available in the @file{etc} directory of the
891 Emacs distribution (see @ref{File-name conventions}, if you're not sure
897 GNU General Public License
900 Emacs Availability Information, including the popular Free Software
901 Foundation Order Form
904 How to get GNU Software by Internet FTP or by UUCP
910 Richard Stallman discusses his public-domain UNIX-compatible software
911 system with BYTE editors
914 Why you should join the League for Programming Freedom
917 Status of Emacs on Various Machines and Systems
920 GNU Project Electronic Mailing Lists
923 Emacs news, a history of recent user-visible changes
926 GNU Service Directory
929 including ``Using Emacstool with GNU Emacs''
933 More GNU information, including back issues of the @cite{GNU's
936 @uref{http://www.gnu.org/bulletins/bulletins.html} and
938 @uref{http://www.cs.pdx.edu/~trent/gnu/gnu.html}
940 @node Help installing Emacs, Obtaining the FAQ, Informational files for Emacs, Getting help
941 @section Where can I get help in installing Emacs?
942 @cindex Installation help
943 @cindex Help installing Emacs
945 @xref{Installing Emacs}, for some basic installation hints, and see
946 @ref{Problems building Emacs}, or @ref{Linking with -lX11 fails}, if you
947 have problems with the installation.
949 The file @file{etc/SERVICE} (see @ref{File-name conventions}, if you're
950 not sure where that is) lists companies and individuals willing to sell
951 you help in installing or using Emacs. An up-to-date version this file
952 is available on @samp{ftp.gnu.org} (@pxref{Informational files for
955 @node Obtaining the FAQ, , Help installing Emacs, Getting help
956 @section Where can I get the latest version of this FAQ?
957 @cindex FAQ, obtaining the
958 @cindex Latest FAQ version, obtaining the
959 @cindex Retrieving the latest FAQ version
960 @cindex E-mail, retrieving the FAQ via
961 @cindex Web, reading the FAQ on the
963 The Emacs FAQ is available in several ways:
968 Inside of Emacs itself. You can get it from selecting the @samp{Emacs
969 FAQ} option from the @samp{Help} menu of the Emacs menu bar at the top
970 of any Emacs frame, or by typing @kbd{C-h C-f} (@kbd{M-x view-emacs-FAQ}).
973 Via USENET. If you can read news, the FAQ should be available in your
974 news spool, in both the @uref{news:gnu.emacs.help} and
975 @uref{news:comp.emacs} newsgroups. Every news reader should allow you
976 to read any news article that is still in the news spool, even if you
977 have read the article before. You may need to read the instructions for
978 your news reader to discover how to do this. In @file{rn}, this command
979 will do this for you at the article selection level:
982 ?GNU Emacs Frequently Asked Questions?rc:m
985 In Gnus, you should type @kbd{C-u C-x C-s} from the @file{*Summary*}
986 buffer or @kbd{C-u @key{SPC}} from the @file{*Newsgroup*} buffer to view
987 all articles in a newsgroup.
989 If the FAQ articles have expired and have been deleted from your news
990 spool, it might (or might not) do some good to complain to your news
991 administrator, because the most recent FAQ should not expire for a
995 In the Emacs distribution. Since Emacs 18.56, the FAQ at the time
996 of release has been part of the Emacs distribution as either
997 @file{etc/FAQ} or @file{man/faq.texi} (@pxref{File-name conventions}).
1000 Via anonymous ftp and e-mail from @file{rtfm.mit.edu} (and its mirror in
1001 Europe), the main repository for FAQs and other items posted to
1002 news.answers. The Emacs FAQs are available at
1004 @uref{ftp://rtfm.mit.edu/pub/usenet/comp.emacs/} and
1006 @uref{ftp://ftp.uni-paderborn.de/pub/doc/FAQ/comp/emacs/}
1008 If you do not have access to anonymous FTP, you can access the archives
1009 using the @file{rtfm.mit.edu} mail server. The Emacs FAQ can be
1010 retrieved by sending mail to @email{mail-server@@rtfm.mit.edu} with a
1011 blank subject and containing
1014 send usenet/news.answers/GNU-Emacs-FAQ/diffs
1015 send usenet/news.answers/GNU-Emacs-FAQ/part1
1016 send usenet/news.answers/GNU-Emacs-FAQ/part2
1017 send usenet/news.answers/GNU-Emacs-FAQ/part3
1018 send usenet/news.answers/GNU-Emacs-FAQ/part4
1019 send usenet/news.answers/GNU-Emacs-FAQ/part5
1022 For more information, send email to @email{mail-server@@rtfm.mit.edu}
1023 with @samp{help} and @samp{index} in the body on separate lines.
1026 @c ------------------------------------------------------------
1027 @node Status of Emacs, Common requests, Getting help, Top
1028 @chapter Status of Emacs
1029 @cindex Status of Emacs
1031 This chapter gives you basic information about Emacs, including its
1032 latest version status.
1035 * Origin of the term Emacs::
1036 * Latest version of Emacs::
1042 @node Origin of the term Emacs, Latest version of Emacs, Status of Emacs, Status of Emacs
1043 @section Where does the name ``Emacs'' come from?
1044 @cindex Origin of the term ``Emacs''
1045 @cindex Emacs name origin
1047 @cindex Original version of Emacs
1049 Emacs originally was an acronym for Editor MACroS. RMS says he ``picked
1050 the name Emacs because @key{E} was not in use as an abbreviation on ITS at
1051 the time.'' The first Emacs was a set of macros written in 1976 at MIT
1052 by RMS for the editor TECO (Text Editor and COrrector, originally Tape
1053 Editor and COrrector) under ITS on a PDP-10. RMS had already extended
1054 TECO with a ``real-time'' full-screen mode with reprogrammable keys.
1055 Emacs was started by @email{gls@@east.sun.com, Guy Steele} as a project
1056 to unify the many divergent TECO command sets and key bindings at MIT,
1057 and completed by RMS.
1059 Many people have said that TECO code looks a lot like line noise; you
1060 can read more at @uref{news:alt.lang.teco}. Someone has written a TECO
1061 implementation in Emacs Lisp (to find it, see @ref{Packages that do not
1062 come with Emacs}); it would be an interesting project to run the
1063 original TECO Emacs inside of Emacs.
1066 For some not-so-serious alternative reasons for Emacs to have that
1067 name, check out the file @file{etc/JOKES} (@pxref{File-name
1070 @node Latest version of Emacs, New in Emacs 20, Origin of the term Emacs, Status of Emacs
1071 @section What is the latest version of Emacs?
1072 @cindex Version, latest
1073 @cindex Latest version of Emacs
1075 Emacs @value{VER} is the current version as of this writing.
1077 @node New in Emacs 20, New in Emacs 21, Latest version of Emacs, Status of Emacs
1078 @section What is different about Emacs 20?
1079 @cindex Differences between Emacs 19 and Emacs 20
1080 @cindex Emacs 20, new features in
1082 To find out what has changed in recent versions, type @kbd{C-h C-n}
1083 (@kbd{M-x view-emacs-news}). The oldest changes are at the bottom of
1084 the file, so you might want to read it starting there, rather than at
1087 The differences between Emacs versions 18 and 19 was rather dramatic;
1088 the introduction of frames, faces, and colors on windowing systems was
1089 obvious to even the most casual user.
1091 There are differences between Emacs versions 19 and 20 as well, but many
1092 are more subtle or harder to find. Among the changes are the inclusion
1093 of MULE code for languages that use non-Latin characters and for mixing
1094 several languages in the same document; the ``Customize'' facility for
1095 modifying variables without having to use Lisp; and automatic conversion
1096 of files from Macintosh, Microsoft, and Unix platforms.
1098 A number of older Lisp packages, such as Gnus, Supercite and the
1099 calendar/diary, have been updated and enhanced to work with Emacs 20,
1100 and are now included with the standard distribution.
1103 @node New in Emacs 21, New in Emacs 22, New in Emacs 20, Status of Emacs
1104 @section What is different about Emacs 21?
1105 @cindex Differences between Emacs 20 and Emacs 21
1106 @cindex Emacs 21, new features in
1107 @cindex Recently introduced features
1109 @cindex Variable-size fonts
1110 @cindex Toolbar support
1111 Emacs 21 features a thorough rewrite of the display engine. The new
1112 display engine supports variable-size fonts, images, and can play sounds
1113 on platforms which support that. As a result, the visual appearance of
1114 Emacs, when it runs on a windowed display, is much more reminiscent of
1115 modern GUI programs, and includes 3D widgets (used for the mode line and
1116 the scroll bars), a configurable and extensible toolbar, tooltips
1117 (a.k.a.@: balloon help), and other niceties.
1119 @cindex Colors on text-only terminals
1121 In addition, Emacs 21 supports faces on text-only terminals. This means
1122 that you can now have colors when you run Emacs on a GNU/Linux console
1123 and on @code{xterm} with @kbd{emacs -nw}.
1125 @node New in Emacs 22, , New in Emacs 21, Status of Emacs
1126 @section What is different about Emacs 22?
1127 @cindex Differences between Emacs 21 and Emacs 22
1128 @cindex Emacs 22, new features in
1129 @cindex Recently introduced features
1131 @c FIXME: Improve this node before the 22.1 release.
1132 @cindex Default features
1133 Font-lock mode, auto-compression mode, and file name shadow mode are now
1134 enabled by default. It is now possible to follow links with
1137 @cindex Supported systems
1138 Emacs 22 features support for GNU/Linux systems on S390 and X86-64
1139 machines, as well as support for the Mac OS X and Cygwin operating
1142 @cindex GTK+ Toolkit
1143 @cindex Drag-and-drop
1145 Emacs can now be built with GTK+ widgets, and supports drag-and-drop
1146 operation on X. Mouse wheel support is now enabled by default.
1149 Many new modes and packages have been included in Emacs, such as Leim,
1150 Calc, Tramp and URL, as well as IDO, CUA, rcirc, ERC, conf-mode,
1151 python-mode, table, tumme, SES, ruler, Flymake, Org, etc.
1153 @cindex Documentation
1154 @cindex Emacs Lisp Manual
1155 In addition, Emacs 22 now includes the Emacs Lisp Reference Manual
1156 (@pxref{Emacs Lisp documentation}) and the Emacs Lisp Intro.
1158 @c ------------------------------------------------------------
1159 @node Common requests, Bugs and problems, Status of Emacs, Top
1160 @chapter Common requests
1161 @cindex Common requests
1164 * Setting up a customization file::
1166 * Debugging a customization file::
1168 * Displaying the current line or column::
1169 * Displaying the current file name in the titlebar::
1170 * Turning on abbrevs by default::
1171 * Turning on auto-fill by default::
1172 * Associating modes with files::
1173 * Working with unprintable characters::
1174 * Highlighting a region::
1175 * Controlling case sensitivity::
1176 * Wrapping words automatically::
1177 * Searching for/replacing newlines::
1178 * Yanking text in isearch::
1180 * Checking TeX and *roff documents::
1181 * Changing load-path::
1182 * Using an already running Emacs process::
1183 * Compiler error messages::
1184 * Indenting switch statements::
1185 * Customizing C and C++ indentation::
1186 * Horizontal scrolling::
1188 * Turning off beeping::
1189 * Turning the volume down::
1190 * Automatic indentation::
1191 * Matching parentheses::
1192 * Hiding #ifdef lines::
1193 * Repeating commands::
1194 * Valid X resources::
1195 * Evaluating Emacs Lisp code::
1196 * Changing the length of a Tab::
1197 * Inserting text at the beginning of each line::
1198 * Underlining paragraphs::
1199 * Repeating a command as many times as possible::
1200 * Forcing the cursor to remain in the same column::
1201 * Forcing Emacs to iconify itself::
1202 * Using regular expressions::
1203 * Replacing text across multiple files::
1204 * Documentation for etags::
1205 * Disabling backups::
1206 * Disabling auto-save-mode::
1207 * Going to a line by number::
1208 * Modifying pull-down menus::
1209 * Deleting menus and menu options::
1210 * Turning on syntax highlighting::
1211 * Scrolling only one line::
1212 * Replacing highlighted text::
1213 * Editing MS-DOS files::
1214 * Filling paragraphs with a single space::
1215 * Escape sequences in shell output::
1218 @node Setting up a customization file, Using Customize, Common requests, Common requests
1219 @section How do I set up a @file{.emacs} file properly?
1220 @cindex @file{.emacs} file, setting up
1221 @cindex @file{.emacs} file, locating
1222 @cindex Init file, setting up
1223 @cindex Customization file, setting up
1225 @inforef{Init File, Init File, emacs}.
1227 In general, new Emacs users should not have @file{.emacs} files, because
1228 it causes confusing non-standard behavior. Then they send questions to
1229 @email{help-gnu-emacs@@gnu.org} asking why Emacs isn't behaving as
1232 Beginning with version 20.1, Emacs includes the new Customize facility
1233 (@pxref{Using Customize}). This allows users who are unfamiliar with
1234 Emacs Lisp to modify their @file{.emacs} files in a relatively
1235 straightforward way, using menus rather than Lisp code. Most packages
1236 support Customize as of this writing.
1238 While Customize might indeed make it easier to configure Emacs,
1239 consider taking a bit of time to learn Emacs Lisp and modifying your
1240 @file{.emacs} directly. Simple configuration options are described
1241 rather completely in @inforef{Init File, Init File, emacs}, for users
1242 interested in performing frequently requested, basic tasks.
1244 Sometimes users are unsure as to where their @file{.emacs} file should
1245 be found. Visiting the file as @file{~/.emacs} from Emacs will find
1248 @node Using Customize, Colors on a TTY, Setting up a customization file, Common requests
1249 @section How do I start using Customize?
1250 @cindex Customize groups
1251 @cindex Customizing variables
1252 @cindex Customizing faces
1254 The main Customize entry point is @kbd{M-x customize @key{RET}}. This
1255 command takes you to a buffer listing all the available Customize
1256 groups. From there, you can access all customizable options and faces,
1257 change their values, and save your changes to your init file.
1258 @inforef{Easy Customization, Easy Customization, emacs}.
1260 If you know the name of the group in advance (e.g. ``shell''), use
1261 @kbd{M-x customize-group @key{RET}}.
1263 If you wish to customize a single option, use @kbd{M-x customize-option
1264 @key{RET}}. This command prompts you for the name of the option to
1265 customize, with completion.
1267 @node Colors on a TTY, Debugging a customization file, Using Customize, Common requests
1268 @section How do I get colors and syntax highlighting on a TTY?
1269 @cindex Colors on a TTY
1270 @cindex Syntax highlighting on a TTY
1271 @cindex Console, colors
1273 In Emacs 21.1 and later, colors and faces are supported in non-windowed mode,
1274 i.e.@: on Unix and GNU/Linux text-only terminals and consoles, and when
1275 invoked as @samp{emacs -nw} on X, MS-Windows, and Mac. (Colors and faces were
1276 supported in the MS-DOS port since Emacs 19.29.) Emacs automatically
1277 detects color support at startup and uses it if available. If you think
1278 that your terminal supports colors, but Emacs won't use them, check the
1279 @code{termcap} entry for your display type for color-related
1282 The command @kbd{M-x list-colors-display} pops up a window which
1283 exhibits all the colors Emacs knows about on the current display.
1285 Syntax highlighting is on by default since version 22.1.
1287 @node Debugging a customization file, Displaying the current line or column, Colors on a TTY, Common requests
1288 @section How do I debug a @file{.emacs} file?
1289 @cindex Debugging @file{.emacs} file
1290 @cindex @file{.emacs} debugging
1291 @cindex Init file debugging
1292 @cindex @samp{-debug-init} option
1294 Start Emacs with the @samp{-debug-init} command-line option. This
1295 enables the Emacs Lisp debugger before evaluating your @file{.emacs}
1296 file, and places you in the debugger if something goes wrong. The top
1297 line in the @file{trace-back} buffer will be the error message, and the
1298 second or third line of that buffer will display the Lisp code from your
1299 @file{.emacs} file that caused the problem.
1301 You can also evaluate an individual function or argument to a function
1302 in your @file{.emacs} file by moving the cursor to the end of the
1303 function or argument and typing @kbd{C-x C-e} (@kbd{M-x
1306 Use @kbd{C-h v} (@kbd{M-x describe-variable}) to check the value of
1307 variables which you are trying to set or use.
1309 @node Displaying the current line or column, Displaying the current file name in the titlebar, Debugging a customization file, Common requests
1310 @section How do I make Emacs display the current line (or column) number?
1311 @cindex @code{line-number-mode}
1312 @cindex Displaying the current line or column
1313 @cindex Line number, displaying the current
1314 @cindex Column, displaying the current
1315 @cindex @code{mode-line-format}
1317 To have Emacs automatically display the current line number of the point
1318 in the mode line, do @kbd{M-x line-number-mode}. You can also put the
1322 (setq line-number-mode t)
1326 in your @file{.emacs} file to achieve this whenever you start Emacs.
1327 (Line number display is on by default, unless your site-specific
1328 initialization disables it.) Note that Emacs will not display the line
1329 number if the buffer's size in bytes is larger than the value of the
1330 variable @code{line-number-display-limit}.
1332 As of Emacs 20, you can similarly display the current column with
1333 @kbd{M-x column-number-mode}, or by putting the form
1336 (setq column-number-mode t)
1340 in your @file{.emacs} file.
1342 The @code{"%c"} format specifier in the variable @code{mode-line-format}
1343 will insert the current column's value into the mode line. See the
1344 documentation for @code{mode-line-format} (using @kbd{C-h v
1345 mode-line-format @key{RET}}) for more information on how to set and use
1348 Users of all Emacs versions can display the current column using the
1349 @samp{column} package written by @email{abraham@@dina.kvl.dk, Per
1350 Abrahamsen}. @xref{Packages that do not come with Emacs}, for
1351 instructions on how to get it.
1353 @cindex Set number capability in @code{vi} emulators
1354 None of the @code{vi} emulation modes provide the ``set number''
1355 capability of @code{vi} (as far as we know). The @samp{setnu} package
1356 written by @email{kyle@@wonderworks.com, Kyle Jones} provides this
1357 feature. So too does @samp{wb-line-number}, written by
1358 @email{naoki.y.nakamura@@nifty.com, Naoki Nakamura}.
1360 @node Displaying the current file name in the titlebar, Turning on abbrevs by default, Displaying the current line or column, Common requests
1361 @section How can I modify the titlebar to contain the current file name?
1362 @cindex Titlebar, displaying the current file name in
1363 @cindex File name, displaying in the titlebar
1364 @cindex @code{frame-title-format}
1366 The contents of an Emacs frame's titlebar is controlled by the variable
1367 @code{frame-title-format}, which has the same structure as the variable
1368 @code{mode-line-format}. (Use @kbd{C-h v} or @kbd{M-x
1369 describe-variable} to get information about one or both of these
1372 By default, the titlebar for a frame does contain the name of the buffer
1373 currently being visited, except if there is a single frame. In such a
1374 case, the titlebar contains Emacs invocation name and the name of the
1375 machine at which Emacs was invoked. This is done by setting
1376 @code{frame-title-format} to the default value of
1379 (multiple-frames "%b" ("" invocation-name "@@" system-name))
1382 To modify the behavior such that frame titlebars contain the buffer's
1383 name regardless of the number of existing frames, include the following
1384 in your @file{.emacs}:
1387 (setq frame-title-format "%b")
1390 @node Turning on abbrevs by default, Turning on auto-fill by default, Displaying the current file name in the titlebar, Common requests
1391 @section How do I turn on abbrevs by default just in mode @var{mymode}?
1392 @cindex Abbrevs, turning on by default
1394 Put this in your @file{.emacs} file:
1398 (quietly-read-abbrev-file)
1401 (add-hook '@var{mymode}-mode-hook
1403 (setq abbrev-mode t)))
1406 Starting with Emacs 22, the standard abbrevs file is read automatically
1407 at startup, so the first of these two forms becomes unnecessary.
1409 @node Turning on auto-fill by default, Associating modes with files, Turning on abbrevs by default, Common requests
1410 @section How do I turn on @code{auto-fill-mode} by default?
1411 @cindex @code{auto-fill-mode}, activating automatically
1412 @cindex Filling automatically
1413 @cindex Automatic entry to @code{auto-fill-mode}
1415 To turn on @code{auto-fill-mode} just once for one buffer, use @kbd{M-x
1418 To turn it on for every buffer in a certain mode, you must use the hook
1419 for that mode. For example, to turn on @code{auto-fill} mode for all
1420 text buffers, including the following in your @file{.emacs} file:
1423 (add-hook 'text-mode-hook 'turn-on-auto-fill)
1426 If you want @code{auto-fill} mode on in all major modes, do this:
1429 (setq-default auto-fill-function 'do-auto-fill)
1432 @node Associating modes with files, Working with unprintable characters, Turning on auto-fill by default, Common requests
1433 @section How do I make Emacs use a certain major mode for certain files?
1434 @cindex Associating modes with files
1435 @cindex File extensions and modes
1436 @cindex @code{auto-mode-alist}, modifying
1437 @cindex Modes, associating with file extensions
1439 If you want to use a certain mode @var{foo} for all files whose names end
1440 with the extension @file{.@var{bar}}, this will do it for you:
1443 (setq auto-mode-alist (cons '("\\.@var{bar}\\'" . @var{foo}-mode) auto-mode-alist))
1446 Otherwise put this somewhere in the first line of any file you want to
1447 edit in the mode @var{foo} (in the second line, if the first line begins
1454 @cindex Major mode for shell scripts
1455 Beginning with Emacs 19, the variable @code{interpreter-mode-alist}
1456 specifies which mode to use when loading a shell script. (Emacs
1457 determines which interpreter you're using by examining the first line of
1458 the script.) This feature only applies when the file name doesn't
1459 indicate which mode to use. Use @kbd{C-h v} (or @kbd{M-x
1460 describe-variable}) on @code{interpreter-mode-alist} to learn more.
1462 @node Working with unprintable characters, Highlighting a region, Associating modes with files, Common requests
1463 @section How do I search for, delete, or replace unprintable (eight-bit or control) characters?
1464 @cindex Unprintable characters, working with
1465 @cindex Working with unprintable characters
1466 @cindex Control characters, working with
1467 @cindex Eight-bit characters, working with
1468 @cindex Searching for unprintable characters
1469 @cindex Regexps and unprintable characters
1471 To search for a single character that appears in the buffer as, for
1472 example, @samp{\237}, you can type @kbd{C-s C-q 2 3 7}. (This assumes
1473 the value of @code{search-quote-char} is 17 (i.e., @kbd{C-q}).)
1474 Searching for @strong{all} unprintable characters is best done with a
1475 regular expression (@dfn{regexp}) search. The easiest regexp to use for
1476 the unprintable chars is the complement of the regexp for the printable
1482 Regexp for the printable chars: @samp{[\t\n\r\f -~]}
1485 Regexp for the unprintable chars: @samp{[^\t\n\r\f -~]}
1489 To type these special characters in an interactive argument to
1490 @code{isearch-forward-regexp} or @code{re-search-forward}, you need to
1491 use @kbd{C-q}. (@samp{\t}, @samp{\n}, @samp{\r}, and @samp{\f} stand
1492 respectively for @key{TAB}, @key{LFD}, @key{RET}, and @kbd{C-l}.) So,
1493 to search for unprintable characters using @code{re-search-forward}:
1495 @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}}
1497 Using @code{isearch-forward-regexp}:
1499 @kbd{C-M-s [^ @key{TAB} @key{LFD} C-q @key{RET} C-q C-l @key{SPC} -~]}
1501 To delete all unprintable characters, simply use replace-regexp:
1503 @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}}
1505 Replacing is similar to the above. To replace all unprintable
1506 characters with a colon, use:
1508 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}
1513 You don't need to quote @key{TAB} with either isearch or typing
1514 something in the minibuffer.
1518 @node Highlighting a region, Controlling case sensitivity, Working with unprintable characters, Common requests
1519 @section How can I highlight a region of text in Emacs?
1520 @cindex Highlighting text
1521 @cindex Text, highlighting
1522 @cindex @code{transient-mark-mode}
1523 @cindex Region, highlighting a
1525 You can cause the region to be highlighted when the mark is active by
1529 (transient-mark-mode t)
1533 in your @file{.emacs} file. (Also see @ref{Turning on syntax
1536 @node Controlling case sensitivity, Searching for/replacing newlines, Highlighting a region, Common requests
1537 @section How do I control Emacs's case-sensitivity when searching/replacing?
1538 @cindex @code{case-fold-search}
1539 @cindex Case sensitivity of searches
1540 @cindex Searching without case sensitivity
1541 @cindex Ignoring case in searches
1543 For searching, the value of the variable @code{case-fold-search}
1544 determines whether they are case sensitive:
1547 (setq case-fold-search nil) ; make searches case sensitive
1548 (setq case-fold-search t) ; make searches case insensitive
1551 @cindex Case sensitivity in replacements
1552 @cindex Replacing, and case sensitivity
1553 @cindex @code{case-replace}
1554 Similarly, for replacing, the variable @code{case-replace} determines
1555 whether replacements preserve case.
1557 You can also toggle case sensitivity at will in isearch with @kbd{M-c}.
1559 To change the case sensitivity just for one major mode, use the major
1560 mode's hook. For example:
1563 (add-hook '@var{foo}-mode-hook
1565 (setq case-fold-search nil)))
1568 @node Searching for/replacing newlines, Yanking text in isearch, Controlling case sensitivity, Common requests
1569 @section How do I input a newline character in isearch or query-replace?
1570 @cindex Searching for newlines
1571 @cindex Replacing newlines
1573 Use @kbd{C-q C-j}. For more information, see @inforef{Special Isearch,
1574 Special Input for Incremental Search, emacs}.
1577 @node Yanking text in isearch, Wrapping words automatically, Searching for/replacing newlines, Common requests
1578 @section How do I copy text from the kill ring into the search string?
1579 @cindex Yanking text into the search string
1580 @cindex isearch yanking
1582 Use @kbd{M-y}. @inforef{Isearch Yank, Isearch Yanking, emacs}.
1584 @node Wrapping words automatically, Spell-checkers, Yanking text in isearch, Common requests
1585 @section How do I make Emacs wrap words for me?
1586 @cindex Wrapping word automatically
1587 @cindex Wrapping lines
1589 @cindex @code{auto-fill-mode}, introduction to
1590 @cindex Maximum line width, default value
1591 @cindex @code{fill-column}, default value
1593 Use @code{auto-fill-mode}, activated by typing @kbd{M-x auto-fill-mode}.
1594 The default maximum line width is 70, determined by the variable
1595 @code{fill-column}. To learn how to turn this on automatically, see
1596 @ref{Turning on auto-fill by default}.
1598 @node Spell-checkers, Checking TeX and *roff documents, Wrapping words automatically, Common requests
1599 @section Where can I get a better spelling checker for Emacs?
1600 @cindex Checking spelling
1601 @cindex Spelling, checking text documents
1603 Use Ispell. @xref{Ispell}.
1605 @node Checking TeX and *roff documents, Changing load-path, Spell-checkers, Common requests
1606 @section How can I spell-check @TeX{} or *roff documents?
1607 @cindex Spelling, checking @TeX{} documents
1608 @cindex @TeX{} documents, checking spelling in
1610 Use Ispell. Ispell can handle @TeX{} and *roff documents.
1613 @node Changing load-path, Using an already running Emacs process, Checking TeX and *roff documents, Common requests
1614 @section How do I change @code{load-path}?
1615 @cindex @code{load-path}, modifying
1616 @cindex Modifying @code{load-path}
1617 @cindex Adding to @code{load-path}
1619 In general, you should only add to the @code{load-path}. You can add
1620 directory @var{/dir/subdir} to the load path like this:
1623 (setq load-path (cons "/dir/subdir/" load-path))
1626 To do this relative to your home directory:
1629 (setq load-path (cons "~/mysubdir/" load-path))
1632 @node Using an already running Emacs process, Compiler error messages, Changing load-path, Common requests
1633 @section How do I use an already running Emacs from another window?
1634 @cindex @code{emacsclient}
1635 @cindex Emacs server functions
1636 @cindex Using an existing Emacs process
1638 @code{emacsclient}, which comes with Emacs, is for editing a file using
1639 an already running Emacs rather than starting up a new Emacs. It does
1640 this by sending a request to the already running Emacs, which must be
1641 expecting the request.
1648 Emacs must have executed the @code{server-start} function for
1649 @samp{emacsclient} to work. This can be done either by a command line
1653 emacs -f server-start
1656 or by invoking @code{server-start} from @file{.emacs}:
1659 (if (@var{some conditions are met}) (server-start))
1662 When this is done, Emacs creates a Unix domain socket named
1663 @file{server} in @file{/tmp/emacs@var{userid}}. See
1664 @code{server-socket-dir}.
1666 To get your news reader, mail reader, etc., to invoke
1667 @samp{emacsclient}, try setting the environment variable @code{EDITOR}
1668 (or sometimes @code{VISUAL}) to the value @samp{emacsclient}. You may
1669 have to specify the full pathname of the @samp{emacsclient} program
1674 setenv EDITOR emacsclient
1676 # using full pathname
1677 setenv EDITOR /usr/local/emacs/etc/emacsclient
1680 EDITOR=emacsclient ; export EDITOR
1686 When @samp{emacsclient} is run, it connects to the socket and passes its
1687 command line options to Emacs, which at the next opportunity will visit
1688 the files specified. (Line numbers can be specified just like with
1689 Emacs.) The user will have to switch to the Emacs window by hand. When
1690 the user is done editing a file, the user can type @kbd{C-x #} (or
1691 @kbd{M-x server-edit}) to indicate this. If there is another buffer
1692 requested by @code{emacsclient}, Emacs will switch to it; otherwise
1693 @code{emacsclient} will exit, signaling the calling program to continue.
1695 @cindex @code{gnuserv}
1696 There is an enhanced version of @samp{emacsclient} called
1697 @samp{gnuserv}, written by @email{ange@@hplb.hpl.hp.com, Andy Norman}
1698 (@pxref{Packages that do not come with Emacs}). @samp{gnuserv} uses
1699 Internet domain sockets, so it can work across most network connections.
1701 The most recent @samp{gnuserv} package is available at
1703 @uref{http://meltin.net/hacks/emacs/}
1707 @node Compiler error messages, Indenting switch statements, Using an already running Emacs process, Common requests
1708 @section How do I make Emacs recognize my compiler's funny error messages?
1709 @cindex Compiler error messages, recognizing
1710 @cindex Recognizing non-standard compiler errors
1711 @cindex Regexps for recognizing compiler errors
1712 @cindex Errors, recognizing compiler
1714 Customize the @code{compilation-error-regexp-alist} variable.
1716 @node Indenting switch statements, Customizing C and C++ indentation, Compiler error messages, Common requests
1717 @section How do I change the indentation for @code{switch}?
1718 @cindex @code{switch}, indenting
1719 @cindex Indenting of @code{switch}
1721 Many people want to indent their @code{switch} statements like this:
1739 The solution at first appears to be: set @code{c-indent-level} to 4 and
1740 @code{c-label-offset} to -2. However, this will give you an indentation
1741 spacing of four instead of two.
1743 The @emph{real} solution is to use @code{cc-mode} (the default mode for
1744 C programming in Emacs 20 and later) and add the following line to your
1748 (c-set-offset 'case-label '+)
1751 There appears to be no way to do this with the old @code{c-mode}.
1753 @node Customizing C and C++ indentation, Horizontal scrolling, Indenting switch statements, Common requests
1754 @section How to customize indentation in C, C@t{++}, and Java buffers?
1755 @cindex Indentation, how to customize
1756 @cindex Customize indentation
1758 The Emacs @code{cc-mode} features an interactive procedure for
1759 customizing the indentation style, which is fully explained in the
1760 @cite{CC Mode} manual that is part of the Emacs distribution, see
1761 @ref{Customizing Indentation, , Customization Indentation, ccmode,
1762 The CC Mode Manual}. Here's a short summary of the procedure:
1766 Go to the beginning of the first line where you don't like the
1767 indentation and type @kbd{C-c C-o}. Emacs will prompt you for the
1768 syntactic symbol; type @key{RET} to accept the default it suggests.
1771 Emacs now prompts for the offset of this syntactic symbol, showing the
1772 default (the current definition) inside parentheses. You can choose
1777 No extra indentation.
1779 Indent one basic offset.
1781 Outdent one basic offset.
1783 Indent two basic offsets
1785 Outdent two basic offsets.
1787 Indent half basic offset.
1789 Outdent half basic offset.
1793 After choosing one of these symbols, type @kbd{C-c C-q} to reindent
1794 the line or the block according to what you just specified.
1797 If you don't like the result, go back to step 1. Otherwise, add the
1798 following line to your @file{.emacs}:
1801 (c-set-offset '@var{syntactic-symbol} @var{offset})
1805 where @var{syntactic-symbol} is the name Emacs shows in the minibuffer
1806 when you type @kbd{C-c C-o} at the beginning of the line, and
1807 @var{offset} is one of the indentation symbols listed above (@code{+},
1808 @code{/}, @code{0}, etc.) that you've chosen during the interactive
1812 Go to the next line whose indentation is not to your liking and repeat
1816 It is recommended to put all the resulting @code{(c-set-offset ...)}
1817 customizations inside a C mode hook, like this:
1820 (defun my-c-mode-hook ()
1823 (add-hook 'c-mode-hook 'my-c-mode-hook)
1827 Using @code{c-mode-hook} avoids the need to put a @w{@code{(require
1828 'cc-mode)}} into your @file{.emacs} file, because @code{c-set-offset}
1829 might be unavailable when @code{cc-mode} is not loaded.
1831 Note that @code{c-mode-hook} runs for C source files only; use
1832 @code{c++-mode-hook} for C@t{++} sources, @code{java-mode-hook} for
1833 Java sources, etc. If you want the same customizations to be in
1834 effect in @emph{all} languages supported by @code{cc-mode}, use
1835 @code{c-mode-common-hook}.
1837 @node Horizontal scrolling, Overwrite mode, Customizing C and C++ indentation, Common requests
1838 @section How can I make Emacs automatically scroll horizontally?
1839 @cindex @code{hscroll-mode}
1840 @cindex Horizontal scrolling
1841 @cindex Scrolling horizontally
1843 In Emacs 21 and later, this is on by default: if the variable
1844 @code{truncate-lines} is non-@code{nil} in the current buffer, Emacs
1845 automatically scrolls the display horizontally when point moves off the
1846 left or right edge of the window.
1848 In Emacs 20, use the @code{hscroll-mode}. Here is some information from
1849 the documentation, available by typing @kbd{C-h f hscroll-mode @key{RET}}:
1851 Automatically scroll horizontally when the point moves off the
1852 left or right edge of the window.
1856 Type @kbd{M-x hscroll-mode} to enable it in the current buffer.
1859 Type @kbd{M-x hscroll-global-mode} to enable it in every buffer.
1862 @code{turn-on-hscroll} is useful in mode hooks as in:
1865 (add-hook 'text-mode-hook 'turn-on-hscroll)
1869 @code{hscroll-margin} controls how close the cursor can get to the
1873 @code{hscroll-step-percent} controls how far to jump once we decide to do so.
1876 @node Overwrite mode, Turning off beeping, Horizontal scrolling, Common requests
1877 @section How do I make Emacs ``typeover'' or ``overwrite'' instead of inserting?
1878 @cindex @key{Insert}
1879 @cindex @code{overwrite-mode}
1880 @cindex Overwriting existing text
1881 @cindex Toggling @code{overwrite-mode}
1883 @kbd{M-x overwrite-mode} (a minor mode). This toggles
1884 @code{overwrite-mode} on and off, so exiting from @code{overwrite-mode}
1885 is as easy as another @kbd{M-x overwrite-mode}.
1887 On some systems, @key{Insert} toggles @code{overwrite-mode} on and off.
1889 @node Turning off beeping, Turning the volume down, Overwrite mode, Common requests
1890 @section How do I stop Emacs from beeping on a terminal?
1891 @cindex Beeping, turning off
1892 @cindex Visible bell
1893 @cindex Bell, visible
1895 @email{martin@@cc.gatech.edu, Martin R. Frank} writes:
1897 Tell Emacs to use the @dfn{visible bell} instead of the audible bell,
1898 and set the visible bell to nothing.
1900 That is, put the following in your @code{TERMCAP} environment variable
1901 (assuming you have one):
1907 And evaluate the following Lisp form:
1910 (setq visible-bell t)
1913 @node Turning the volume down, Automatic indentation, Turning off beeping, Common requests
1914 @section How do I turn down the bell volume in Emacs running under X?
1915 @cindex Bell, volume of
1916 @cindex Volume of bell
1918 On X Window system, you can adjust the bell volume and duration for all
1919 programs with the shell command @code{xset}.
1921 Invoking @code{xset} without any arguments produces some basic
1922 information, including the following:
1925 usage: xset [-display host:dpy] option ...
1928 To set bell volume, pitch and duration:
1929 b [vol [pitch [dur]]] b on
1932 @node Automatic indentation, Matching parentheses, Turning the volume down, Common requests
1933 @section How do I tell Emacs to automatically indent a new line to the indentation of the previous line?
1934 @cindex Indenting new lines
1935 @cindex New lines, indenting of
1936 @cindex Previous line, indenting according to
1937 @cindex Text indentation
1939 Such behavior is automatic in Emacs 20 and later. From the
1940 @file{etc/NEWS} file for Emacs 20.2:
1943 ** In Text mode, now only blank lines separate paragraphs. This makes
1944 it possible to get the full benefit of Adaptive Fill mode in Text mode,
1945 and other modes derived from it (such as Mail mode). @key{TAB} in Text
1946 mode now runs the command @code{indent-relative}; this makes a practical
1947 difference only when you use indented paragraphs.
1949 As a result, the old Indented Text mode is now identical to Text mode,
1950 and is an alias for it.
1952 If you want spaces at the beginning of a line to start a paragraph, use
1953 the new mode, Paragraph Indent Text mode.
1956 @cindex Prefixing lines
1958 If you have @code{auto-fill-mode} turned on (@pxref{Turning on auto-fill
1959 by default}), you can tell Emacs to prefix every line with a certain
1960 character sequence, the @dfn{fill prefix}. Type the prefix at the
1961 beginning of a line, position point after it, and then type @kbd{C-x .}
1962 (@code{set-fill-prefix}) to set the fill prefix. Thereafter,
1963 auto-filling will automatically put the fill prefix at the beginning of
1964 new lines, and @kbd{M-q} (@code{fill-paragraph}) will maintain any fill
1965 prefix when refilling the paragraph.
1967 If you have paragraphs with different levels of indentation, you will
1968 have to set the fill prefix to the correct value each time you move to a
1969 new paragraph. There are many packages available to deal with this
1970 (@pxref{Packages that do not come with Emacs}). Look for ``fill'' and
1971 ``indent'' keywords 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 Call @code{show-paren-mode} in your @file{.emacs} file:
1987 You can also enable this mode by selecting the @samp{Paren Match
1988 Highlighting} option from the @samp{Options} menu of the Emacs menu bar
1989 at the top of any Emacs frame.
1991 Alternatives to this mode include:
1996 If you're looking at a right parenthesis (or brace or bracket) you can
1997 delete it and reinsert it. Emacs will momentarily move the cursor to
1998 the matching parenthesis.
2001 @kbd{C-M-f} (@code{forward-sexp}) and @kbd{C-M-b} (@code{backward-sexp})
2002 will skip over one set of balanced parentheses, so you can see which
2003 parentheses match. (You can train it to skip over balanced brackets
2004 and braces at the same time by modifying the syntax table.)
2006 @cindex Show matching paren as in @code{vi}
2008 Here is some Emacs Lisp that will make the @key{%} key show the matching
2009 parenthesis, like in @code{vi}. In addition, if the cursor isn't over a
2010 parenthesis, it simply inserts a % like normal.
2013 ;; By an unknown contributor
2015 (global-set-key "%" 'match-paren)
2017 (defun match-paren (arg)
2018 "Go to the matching paren if on a paren; otherwise insert %."
2020 (cond ((looking-at "\\s\(") (forward-list 1) (backward-char 1))
2021 ((looking-at "\\s\)") (forward-char 1) (backward-list 1))
2022 (t (self-insert-command (or arg 1)))))
2027 @node Hiding #ifdef lines, Repeating commands, Matching parentheses, Common requests
2028 @section In C mode, can I show just the lines that will be left after @code{#ifdef} commands are handled by the compiler?
2029 @cindex @code{#ifdef}, selective display of
2030 @cindex @code{hide-ifdef-mode}
2031 @cindex Hiding @code{#ifdef} text
2032 @cindex Selectively displaying @code{#ifdef} code
2034 @kbd{M-x hide-ifdef-mode}. (This is a minor mode.) You might also want
2035 to investigate @file{cpp.el}, which is distributed with Emacs.
2037 @node Repeating commands, Valid X resources, Hiding #ifdef lines, Common requests
2038 @section Is there an equivalent to the @code{.} (dot) command of vi?
2039 @cindex Repeating commands as with @code{vi}
2040 @cindex Command, repeat last
2041 @cindex @code{.}, equivalent to @code{vi} command
2043 (@code{.} is the redo command in @code{vi}. It redoes the last
2044 insertion/deletion.)
2046 As of Emacs 20.3, there is indeed a @code{repeat} command (@kbd{C-x z})
2047 that repeats the last command. If you preface it with a prefix
2048 argument, the prefix arg is applied to the command.
2050 You can also type @kbd{C-x @key{ESC} @key{ESC}}
2051 (@code{repeat-complex-command}) to reinvoke commands that used the
2052 minibuffer to get arguments. In @code{repeat-complex-command} you can
2053 type @kbd{M-p} and @kbd{M-n} (and also up-arrow and down-arrow, if your
2054 keyboard has these keys) to scan through all the different complex
2055 commands you've typed.
2057 To repeat a set of commands, use keyboard macros. (@inforef{Keyboard
2058 Macros, Keyboard Macros, emacs}.)
2060 If you're really desperate for the @code{.} command, use VIPER, a
2061 @code{vi} emulation mode which comes with Emacs, and which appears to
2062 support it. (@xref{VIPER}.)
2064 @node Valid X resources, Evaluating Emacs Lisp code, Repeating commands, Common requests
2065 @section What are the valid X resource settings (i.e., stuff in .Xdefaults)?
2066 @cindex Resources, X
2068 @cindex Setting X resources
2070 @inforef{X Resources, X Resources, emacs}.
2072 You can also use a resource editor, such as editres (for X11R5 and
2073 onwards), to look at the resource names for the menu bar, assuming Emacs
2074 was compiled with the X toolkit.
2076 @node Evaluating Emacs Lisp code, Changing the length of a Tab, Valid X resources, Common requests
2077 @section How do I execute (``evaluate'') a piece of Emacs Lisp code?
2078 @cindex Evaluating Lisp code
2079 @cindex Lisp forms, evaluating
2081 There are a number of ways to execute (@dfn{evaluate}, in Lisp lingo) an
2082 Emacs Lisp @dfn{form}:
2087 If you want it evaluated every time you run Emacs, put it in a file
2088 named @file{.emacs} in your home directory. This is known as ``your
2089 @file{.emacs} file,'' and contains all of your personal customizations.
2092 You can type the form in the @file{*scratch*} buffer, and then type
2093 @key{LFD} (or @kbd{C-j}) after it. The result of evaluating the form
2094 will be inserted in the buffer.
2097 In @code{emacs-lisp-mode}, typing @kbd{C-M-x} evaluates a top-level form
2098 before or around point.
2101 Typing @kbd{C-x C-e} in any buffer evaluates the Lisp form immediately
2102 before point and prints its value in the echo area.
2105 Typing @kbd{M-:} or @kbd{M-x eval-expression} allows you to type a Lisp
2106 form in the minibuffer which will be evaluated once you press @key{RET}.
2109 You can use @kbd{M-x load-file} to have Emacs evaluate all the Lisp
2110 forms in a file. (To do this from Lisp use the function @code{load}
2113 The functions @code{load-library}, @code{eval-region},
2114 @code{eval-current-buffer}, @code{require}, and @code{autoload} are also
2115 useful; see @ref{Emacs Lisp documentation}, if you want to learn more
2120 @node Changing the length of a Tab, Inserting text at the beginning of each line, Evaluating Emacs Lisp code, Common requests
2121 @section How do I change Emacs's idea of the @key{TAB} character's length?
2123 @cindex Length of tab character
2124 @cindex @code{default-tab-width}
2126 Set the variable @code{default-tab-width}. For example, to set
2127 @key{TAB} stops every 10 characters, insert the following in your
2131 (setq default-tab-width 10)
2134 Do not confuse variable @code{tab-width} with variable
2135 @code{tab-stop-list}. The former is used for the display of literal
2136 @key{TAB} characters. The latter controls what characters are inserted
2137 when you press the @key{TAB} character in certain modes.
2139 @node Inserting text at the beginning of each line, Underlining paragraphs, Changing the length of a Tab, Common requests
2140 @section How do I insert <some text> at the beginning of every line?
2141 @cindex Prefixing a region with some text
2142 @cindex Prefix character, inserting in mail/news replies
2143 @cindex Replies to mail/news, inserting a prefix character
2144 @cindex @code{mail-yank-prefix}
2145 @cindex Mail replies, inserting a prefix character
2146 @cindex News replies, inserting a prefix character
2148 To do this to an entire buffer, type @kbd{M-< M-x replace-regexp
2149 @key{RET} ^ @key{RET} your text @key{RET}}.
2151 To do this to a region, use @code{string-insert-rectangle}.
2152 Set the mark (@kbd{C-@key{SPC}}) at the beginning of the first line you
2153 want to prefix, move the cursor to last line to be prefixed, and type
2154 @kbd{M-x string-insert-rectangle @key{RET}}. To do this for the whole
2155 buffer, type @kbd{C-x h M-x string-insert-rectangle @key{RET}}.
2157 If you are trying to prefix a yanked mail message with @samp{>}, you
2158 might want to set the variable @code{mail-yank-prefix}. In Message
2159 buffers, you can even use @kbd{M-;} to cite yanked messages (@kbd{M-;}
2160 runs the function @code{comment-region}, it is a general-purpose
2161 mechanism to comment regions).
2163 @node Underlining paragraphs, Repeating a command as many times as possible, Inserting text at the beginning of each line, Common requests
2164 @section How do I insert @samp{_^H} before each character in a region to get an underlined paragraph?
2165 @cindex Underlining a region of text
2166 @cindex @code{underline-region}
2168 Mark the region and then type @kbd{M-x underline-region @key{RET}}.
2170 @node Repeating a command as many times as possible, Forcing the cursor to remain in the same column, Underlining paragraphs, Common requests
2171 @section How do I repeat a command as many times as possible?
2172 @cindex Repeating commands many times
2173 @cindex Commands, repeating many times
2175 Use @kbd{C-x (} and @kbd{C-x )} to make a keyboard macro that invokes
2176 the command and then type @kbd{M-0 C-x e}.
2178 Any messages your command prints in the echo area will be suppressed.
2180 If you need to repeat a command a small number of times, you can use
2181 @kbd{C-x z} (@pxref{Repeating commands}) or @kbd{C-x e}.
2183 @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
2184 @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?
2185 @cindex @code{picture-mode}
2186 @cindex Remaining in the same column, regardless of contents
2187 @cindex Vertical movement in empty documents
2189 @kbd{M-x picture-mode}.
2191 @node Forcing Emacs to iconify itself, Using regular expressions, Forcing the cursor to remain in the same column, Common requests
2192 @section How do I tell Emacs to iconify itself?
2193 @cindex Iconification under the X Window System
2194 @cindex X Window System and iconification
2195 @cindex Suspending Emacs
2197 @kbd{C-z} iconifies Emacs when running under X and suspends Emacs
2198 otherwise. @inforef{Frame Commands, Frame Commands, emacs}.
2200 @node Using regular expressions, Replacing text across multiple files, Forcing Emacs to iconify itself, Common requests
2201 @section How do I use regexps (regular expressions) in Emacs?
2203 @cindex Regular expressions
2204 @cindex Differences between Unix and Emacs regexps
2205 @cindex Unix regeps, differences from Emacs
2206 @cindex Text strings, putting regexps in
2208 @inforef{Regexp Backslash, Regexp Backslash, emacs}.
2210 The @code{or} operator is @samp{\|}, not @samp{|}, and the grouping operators
2211 are @samp{\(} and @samp{\)}. Also, the string syntax for a backslash is
2212 @samp{\\}. To specify a regular expression like @samp{xxx\(foo\|bar\)}
2213 in a Lisp string, use @samp{xxx\\(foo\\|bar\\)}.
2215 Note the doubled backslashes!
2220 Unlike in Unix @file{grep}, @file{sed}, etc., a complement character set
2221 (@samp{[^...]}) can match a newline character (@key{LFD} a.k.a.@:
2222 @kbd{C-j} a.k.a.@: @samp{\n}), unless newline is mentioned as one of the
2223 characters not to match.
2226 The character syntax regexps (e.g., @samp{\sw}) are not
2227 meaningful inside character set regexps (e.g., @samp{[aeiou]}). (This
2228 is actually typical for regexp syntax.)
2232 @node Replacing text across multiple files, Documentation for etags, Using regular expressions, Common requests
2233 @section How do I perform a replace operation across more than one file?
2234 @cindex Replacing strings across files
2235 @cindex Multiple files, replacing across
2236 @cindex Files, replacing strings across multiple
2238 The ``tags'' feature of Emacs includes the command
2239 @code{tags-query-replace} which performs a query-replace across all the
2240 files mentioned in the @file{TAGS} file. @inforef{Tags Search, Tags Search,
2243 As of Emacs 19.29, Dired mode (@kbd{M-x dired @key{RET}}, or @kbd{C-x
2244 d}) supports the command @code{dired-do-query-replace}, which allows
2245 users to replace regular expressions in multiple files.
2247 @node Documentation for etags, Disabling backups, Replacing text across multiple files, Common requests
2248 @section Where is the documentation for @code{etags}?
2249 @cindex Documentation for @code{etags}
2250 @cindex @code{etags}, documentation for
2252 The @code{etags} man page should be in the same place as the
2253 @code{emacs} man page.
2255 Quick command-line switch descriptions are also available. For example,
2258 @node Disabling backups, Disabling auto-save-mode, Documentation for etags, Common requests
2259 @section How do I disable backup files?
2260 @cindex Backups, disabling
2261 @cindex Disabling backups
2263 You probably don't want to do this, since backups are useful, especially
2264 when something goes wrong.
2266 To avoid seeing backup files (and other ``uninteresting'' files) in Dired,
2267 load @code{dired-x} by adding the following to your @file{.emacs} file:
2270 (add-hook 'dired-load-hook
2275 With @code{dired-x} loaded, @kbd{M-o} toggles omitting in each dired buffer.
2276 You can make omitting the default for new dired buffers by putting the
2277 following in your @file{.emacs}:
2280 (add-hook 'dired-mode-hook 'dired-omit-toggle)
2283 If you're tired of seeing backup files whenever you do an @samp{ls} at
2284 the Unix shell, try GNU @code{ls} with the @samp{-B} option. GNU
2285 @code{ls} is part of the GNU Fileutils package, available from
2286 @samp{ftp.gnu.org} and its mirrors (@pxref{Current GNU distributions}).
2288 To disable or change the way backups are made, @inforef{Backup Names, ,
2291 @cindex Backup files in a single directory
2292 Beginning with Emacs 21.1, you can control where Emacs puts backup files
2293 by customizing the variable @code{backup-directory-alist}. This
2294 variable's value specifies that files whose names match specific patters
2295 should have their backups put in certain directories. A typical use is
2296 to add the element @code{("." . @var{dir})} to force Emacs to put
2297 @strong{all} backup files in the directory @file{dir}.
2299 @node Disabling auto-save-mode, Going to a line by number, Disabling backups, Common requests
2300 @section How do I disable @code{auto-save-mode}?
2301 @cindex Disabling @code{auto-save-mode}
2303 @cindex Saving at frequent intervals
2305 You probably don't want to do this, since auto-saving is useful,
2306 especially when Emacs or your computer crashes while you are editing a
2309 Instead, you might want to change the variable
2310 @code{auto-save-interval}, which specifies how many keystrokes Emacs
2311 waits before auto-saving. Increasing this value forces Emacs to wait
2312 longer between auto-saves, which might annoy you less.
2314 You might also want to look into Sebastian Kremer's @code{auto-save}
2315 package (@pxref{Packages that do not come with Emacs}). This
2316 package also allows you to place all auto-save files in one directory,
2317 such as @file{/tmp}.
2319 To disable or change how @code{auto-save-mode} works, @inforef{Auto
2322 @node Going to a line by number, Modifying pull-down menus, Disabling auto-save-mode, Common requests
2323 @section How can I go to a certain line given its number?
2324 @cindex Going to a line by number
2325 @cindex Compilation error messages
2326 @cindex Recompilation
2328 Are you sure you indeed need to go to a line by its number? Perhaps all
2329 you want is to display a line in your source file for which a compiler
2330 printed an error message? If so, compiling from within Emacs using the
2331 @kbd{M-x compile} and @kbd{M-x recompile} commands is a much more
2332 effective way of doing that. Emacs automatically intercepts the compile
2333 error messages, inserts them into a special buffer called
2334 @code{*compilation*}, and lets you visit the locus of each message in
2335 the source. Type @kbd{C-x `} to step through the offending lines one by
2336 one (starting with Emacs 22, you can also use @kbd{M-g M-p} and
2337 @kbd{M-g M-n} to go to the previous and next matches directly). Click
2338 @kbd{Mouse-2} or press @key{RET} on a message text in the
2339 @code{*compilation*} buffer to go to the line whose number is mentioned
2342 But if you indeed need to go to a certain text line, type @kbd{M-g M-g}
2343 (which is the default binding of the @code{goto-line} function starting
2344 with Emacs 22). Emacs will prompt you for the number of the line and go
2347 You can do this faster by invoking @code{goto-line} with a numeric
2348 argument that is the line's number. For example, @kbd{C-u 286 M-g M-g}
2349 will jump to line number 286 in the current buffer.
2351 @node Modifying pull-down menus, Deleting menus and menu options, Going to a line by number, Common requests
2352 @section How can I create or modify new pull-down menu options?
2353 @cindex Pull-down menus, creating or modifying
2354 @cindex Menus, creating or modifying
2355 @cindex Creating new menu options
2356 @cindex Modifying pull-down menus
2357 @cindex Menus and keymaps
2358 @cindex Keymaps and menus
2360 Each menu title (e.g., @samp{File}, @samp{Edit}, @samp{Buffers})
2361 represents a local or global keymap. Selecting a menu title with the
2362 mouse displays that keymap's non-@code{nil} contents in the form of a menu.
2364 So to add a menu option to an existing menu, all you have to do is add a
2365 new definition to the appropriate keymap. Adding a @samp{Forward Word}
2366 item to the @samp{Edit} menu thus requires the following Lisp code:
2369 (define-key global-map
2370 [menu-bar edit forward]
2371 '("Forward word" . forward-word))
2375 The first line adds the entry to the global keymap, which includes
2376 global menu bar entries. Replacing the reference to @code{global-map}
2377 with a local keymap would add this menu option only within a particular
2380 The second line describes the path from the menu-bar to the new entry.
2381 Placing this menu entry underneath the @samp{File} menu would mean
2382 changing the word @code{edit} in the second line to @code{file}.
2384 The third line is a cons cell whose first element is the title that will
2385 be displayed, and whose second element is the function that will be
2386 called when that menu option is invoked.
2388 To add a new menu, rather than a new option to an existing menu, we must
2389 define an entirely new keymap:
2392 (define-key global-map [menu-bar words]
2393 (cons "Words" (make-sparse-keymap "Words")))
2396 The above code creates a new sparse keymap, gives it the name
2397 @samp{Words}, and attaches it to the global menu bar. Adding the
2398 @samp{Forward Word} item to this new menu would thus require the
2402 (define-key global-map
2403 [menu-bar words forward]
2404 '("Forward word" . forward-word))
2408 Note that because of the way keymaps work, menu options are displayed
2409 with the more recently defined items at the top. Thus if you were to
2410 define menu options @samp{foo}, @samp{bar}, and @samp{baz} (in that
2411 order), the menu option @samp{baz} would appear at the top, and
2412 @samp{foo} would be at the bottom.
2414 One way to avoid this problem is to use the function @code{define-key-after},
2415 which works the same as @code{define-key}, but lets you modify where items
2416 appear. The following Lisp code would insert the @samp{Forward Word}
2417 item in the @samp{Edit} menu immediately following the @samp{Undo} item:
2421 (lookup-key global-map [menu-bar edit])
2423 '("Forward word" . forward-word)
2427 Note how the second and third arguments to @code{define-key-after} are
2428 different from those of @code{define-key}, and that we have added a new
2429 (final) argument, the function after which our new key should be
2432 To move a menu option from one position to another, simply evaluate
2433 @code{define-key-after} with the appropriate final argument.
2435 More detailed information---and more examples of how to create and
2436 modify menu options---are in the @cite{Emacs Lisp Reference Manual}, under
2437 ``Menu Keymaps''. (@xref{Emacs Lisp documentation}, for information on
2440 @node Deleting menus and menu options, Turning on syntax highlighting, Modifying pull-down menus, Common requests
2441 @section How do I delete menus and menu options?
2442 @cindex Deleting menus and menu options
2443 @cindex Menus, deleting
2445 The simplest way to remove a menu is to set its keymap to @samp{nil}.
2446 For example, to delete the @samp{Words} menu (@pxref{Modifying pull-down
2450 (define-key global-map [menu-bar words] nil)
2453 Similarly, removing a menu option requires redefining a keymap entry to
2454 @code{nil}. For example, to delete the @samp{Forward word} menu option
2455 from the @samp{Edit} menu (we added it in @ref{Modifying pull-down
2459 (define-key global-map [menu-bar edit forward] nil)
2462 @node Turning on syntax highlighting, Scrolling only one line, Deleting menus and menu options, Common requests
2463 @section How do I turn on syntax highlighting?
2464 @cindex Syntax highlighting
2465 @cindex @code{font-lock-mode}
2466 @cindex Highlighting based on syntax
2467 @cindex Colorizing text
2468 @cindex FAQ, @code{font-lock-mode}
2470 @code{font-lock-mode} is the standard way to have Emacs perform syntax
2471 highlighting in the current buffer. It is enabled by default in Emacs
2474 With @code{font-lock-mode} turned on, different types of text will
2475 appear in different colors. For instance, in a programming mode,
2476 variables will appear in one face, keywords in a second, and comments in
2479 @cindex hilit19 is deprecated
2480 Earlier versions of Emacs supported hilit19, a similar package. Use of
2481 hilit19 is now considered non-standard, although @file{hilit19.el} comes
2482 with the stock Emacs distribution. It is no longer maintained.
2484 To turn @code{font-lock-mode} off within an existing buffer, use
2485 @kbd{M-x font-lock-mode @key{RET}}.
2487 In Emacs 21 and earlier versions, you could use the following code in
2488 your @file{.emacs} file to turn on @code{font-lock-mode} globally:
2491 (global-font-lock-mode 1)
2494 Highlighting a buffer with @code{font-lock-mode} can take quite a while,
2495 and cause an annoying delay in display, so several features exist to
2498 @cindex Just-In-Time syntax highlighting
2499 In Emacs 21 and later, turning on @code{font-lock-mode} automatically
2500 activates the new @dfn{Just-In-Time fontification} provided by
2501 @code{jit-lock-mode}. @code{jit-lock-mode} defers the fontification of
2502 portions of buffer until you actually need to see them, and can also
2503 fontify while Emacs is idle. This makes display of the visible portion
2504 of a buffer almost instantaneous. For details about customizing
2505 @code{jit-lock-mode}, type @kbd{C-h f jit-lock-mode @key{RET}}.
2507 @cindex Levels of syntax highlighting
2508 @cindex Decoration level, in @code{font-lock-mode}
2509 In versions of Emacs before 21, different levels of decoration are
2510 available, from slight to gaudy. More decoration means you need to wait
2511 more time for a buffer to be fontified (or a faster machine). To
2512 control how decorated your buffers should become, set the value of
2513 @code{font-lock-maximum-decoration} in your @file{.emacs} file, with a
2514 @code{nil} value indicating default (usually minimum) decoration, and a
2515 @code{t} value indicating the maximum decoration. For the gaudiest
2516 possible look, then, include the line
2519 (setq font-lock-maximum-decoration t)
2523 in your @file{.emacs} file. You can also set this variable such that
2524 different modes are highlighted in a different ways; for more
2525 information, see the documentation for
2526 @code{font-lock-maximum-decoration} with @kbd{C-h v} (or @kbd{M-x
2527 describe-variable @key{RET}}).
2529 Also see the documentation for the function @code{font-lock-mode},
2530 available by typing @kbd{C-h f font-lock-mode} (@kbd{M-x
2531 describe-function @key{RET} font-lock-mode @key{RET}}).
2533 To print buffers with the faces (i.e., colors and fonts) intact, use
2534 @kbd{M-x ps-print-buffer-with-faces} or @kbd{M-x
2535 ps-print-region-with-faces}. You will need a way to send text to a
2536 PostScript printer, or a PostScript interpreter such as Ghostscript;
2537 consult the documentation of the variables @code{ps-printer-name},
2538 @code{ps-lpr-command}, and @code{ps-lpr-switches} for more details.
2540 @node Scrolling only one line, Replacing highlighted text, Turning on syntax highlighting, Common requests
2541 @section How can I force Emacs to scroll only one line when I move past the bottom of the screen?
2542 @cindex Scrolling only one line
2543 @cindex Reducing the increment when scrolling
2545 Customize the @code{scroll-conservatively} variable with @kbd{M-x
2546 customize-variable @key{RET} scroll-conservatively @key{RET}} and set it
2547 to a large value like, say, 10000. For an explanation of what this
2548 means, @inforef{Scrolling, Scrolling, emacs}.
2550 Alternatively, use the following Lisp form in your @file{.emacs}:
2553 (setq scroll-conservatively most-positive-fixnum)
2556 @node Replacing highlighted text, Editing MS-DOS files, Scrolling only one line, Common requests
2557 @section How can I replace highlighted text with what I type?
2558 @cindex @code{delete-selection-mode}
2559 @cindex Replacing highlighted text
2560 @cindex Highlighting and replacing text
2562 Use @code{delete-selection-mode}, which you can start automatically by
2563 placing the following Lisp form in your @file{.emacs} file:
2566 (delete-selection-mode 1)
2569 According to the documentation string for @code{delete-selection-mode}
2570 (which you can read using @kbd{M-x describe-function @key{RET}
2571 delete-selection-mode @key{RET}}):
2574 When ON, typed text replaces the selection if the selection is active.
2575 When OFF, typed text is just inserted at point.
2578 This mode also allows you to delete (not kill) the highlighted region by
2581 @node Editing MS-DOS files, Filling paragraphs with a single space, Replacing highlighted text, Common requests
2582 @section How can I edit MS-DOS files using Emacs?
2583 @cindex Editing MS-DOS files
2584 @cindex MS-DOS files, editing
2585 @cindex Microsoft files, editing
2586 @cindex Windows files, editing
2588 As of Emacs 20, detection and handling of MS-DOS (and Windows) files is
2589 performed transparently. You can open MS-DOS files on a Unix system,
2590 edit it, and save it without having to worry about the file format.
2592 When editing an MS-DOS style file, the mode line will indicate that it
2593 is a DOS file. On Unix and GNU/Linux systems, and also on a Macintosh,
2594 the string @samp{(DOS)} will appear near the left edge of the mode line;
2595 on DOS and Windows, where the DOS end-of-line (EOL) format is the
2596 default, a backslash (@samp{\}) will appear in the mode line.
2598 If you are running a version of Emacs before 20.1, get @code{crypt++}
2599 (@pxref{Packages that do not come with Emacs}). Among other things,
2600 @code{crypt++} transparently modifies MS-DOS files as they are loaded
2601 and saved, allowing you to ignore the different conventions that Unix
2602 and MS-DOS have for delineating the end of a line.
2604 @node Filling paragraphs with a single space, Escape sequences in shell output, Editing MS-DOS files, Common requests
2605 @section How can I tell Emacs to fill paragraphs with a single space after each period?
2606 @cindex One space following periods
2607 @cindex Single space following periods
2608 @cindex Periods, one space following
2610 Add the following line to your @file{.emacs} file:
2613 (setq sentence-end-double-space nil)
2616 @node Escape sequences in shell output, , Filling paragraphs with a single space, Common requests
2617 @section Why these strange escape sequences from @code{ls} from the Shell mode?
2618 @cindex Escape sequences in @code{ls} output
2619 @cindex @code{ls} in Shell mode
2621 This happens because @code{ls} is aliased to @samp{ls --color} in your
2622 shell init file. You have two alternatives to solve this:
2626 Make the alias conditioned on the @code{EMACS} variable in the
2627 environment. When Emacs runs a subsidiary shell, it exports the
2628 @code{EMACS} variable with the value @code{t} to that shell. You can
2629 unalias @code{ls} when that happens, thus limiting the alias to your
2630 interactive sessions.
2633 Install the @code{ansi-color} package (bundled with Emacs 21.1 and
2634 later), which converts these ANSI escape sequences into colors.
2637 @c ------------------------------------------------------------
2638 @node Bugs and problems, Compiling and installing Emacs, Common requests, Top
2639 @chapter Bugs and problems
2640 @cindex Bugs and problems
2642 The Emacs manual lists some common kinds of trouble users could get
2643 into, see @ref{Lossage, , Dealing with Emacs Trouble, emacs, The GNU
2644 Emacs Manual}, so you might look there if the problem you encounter
2645 isn't described in this chapter. If you decide you've discovered a bug,
2646 see @ref{Bugs, , Reporting Bugs, emacs, The GNU Emacs Manual}, for
2647 instructions how to do that.
2649 The file @file{etc/PROBLEMS} in the Emacs distribution lists various
2650 known problems with building and using Emacs on specific platforms;
2651 type @kbd{C-h C-e} to read it.
2654 * Problems with very large files::
2655 * ^M in the shell buffer::
2656 * Shell process exits abnormally::
2657 * Problems with Shell Mode on MS-Windows::
2658 * Termcap/Terminfo entries for Emacs::
2659 * Spontaneous entry into isearch-mode::
2660 * Problems talking to certain hosts::
2661 * Errors with init files::
2662 * Emacs ignores X resources::
2663 * Emacs ignores frame parameters::
2664 * Emacs takes a long time to visit files::
2665 * Editing files with $ in the name::
2666 * Shell mode loses the current directory::
2667 * Security risks with Emacs::
2668 * Dired claims that no file is on this line::
2671 @node Problems with very large files, ^M in the shell buffer, Bugs and problems, Bugs and problems
2672 @section Does Emacs have problems with files larger than 8 megabytes?
2673 @cindex Very large files, opening
2674 @cindex Large files, opening
2675 @cindex Opening very large files
2676 @cindex Maximum file size
2677 @cindex Files, maximum size
2679 Old versions (i.e., anything before 19.29) of Emacs had problems editing
2680 files larger than 8 megabytes. In versions 19.29 and later, the maximum
2681 buffer size is at least 2^27-1, or 134,217,727 bytes, or 132 MBytes.
2682 And in Emacs 22, the maximum buffer size has been increased to
2683 268,435,455 bytes (or 256 MBytes) on 32-bit machines.
2685 @node ^M in the shell buffer, Shell process exits abnormally, Problems with very large files, Bugs and problems
2686 @section How do I get rid of @samp{^M} or echoed commands in my shell buffer?
2687 @cindex Shell buffer, echoed commands and @samp{^M} in
2688 @cindex Echoed commands in @code{shell-mode}
2690 Try typing @kbd{M-x shell-strip-ctrl-m @key{RET}} while in @code{shell-mode} to
2691 make them go away. If that doesn't work, you have several options:
2693 For @code{tcsh}, put this in your @file{.cshrc} (or @file{.tcshrc})
2698 if ("$EMACS" == t) then
2699 if ($?tcsh) unset edit
2705 Or put this in your @file{.emacs_tcsh} file:
2712 Alternatively, use @code{csh} in your shell buffers instead of
2713 @code{tcsh}. One way is:
2716 (setq explicit-shell-file-name "/bin/csh")
2720 and another is to do this in your @file{.cshrc} (or @file{.tcshrc})
2724 setenv ESHELL /bin/csh
2728 (You must start Emacs over again with the environment variable properly
2729 set for this to take effect.)
2731 You can also set the @code{ESHELL} environment variable in Emacs Lisp
2732 with the following Lisp form,
2735 (setenv "ESHELL" "/bin/csh")
2738 The above solutions try to prevent the shell from producing the
2739 @samp{^M} characters in the first place. If this is not possible
2740 (e.g., if you use a Windows shell), you can get Emacs to remove these
2741 characters from the buffer by adding this to your @file{.emacs} init
2745 (add-hook 'comint-output-filter-functions 'shell-strip-ctrl-m)
2748 On a related note: if your shell is echoing your input line in the shell
2749 buffer, you might want to customize the @code{comint-process-echoes}
2750 variable in your shell buffers, or try the following command in your
2751 shell start-up file:
2754 stty -icrnl -onlcr -echo susp ^Z
2757 @node Shell process exits abnormally, Problems with Shell Mode on MS-Windows, ^M in the shell buffer, Bugs and problems
2758 @section Why do I get ``Process shell exited abnormally with code 1''?
2759 @cindex Abnormal exits from @code{shell-mode}
2760 @cindex @code{shell-mode} exits
2761 @cindex Process shell exited
2763 The most likely reason for this message is that the @samp{env} program
2764 is not properly installed. Compile this program for your architecture,
2765 and install it with @samp{a+x} permission in the architecture-dependent
2766 Emacs program directory. (You can find what this directory is at your
2767 site by inspecting the value of the variable @code{exec-directory} by
2768 typing @kbd{C-h v exec-directory @key{RET}}.)
2770 You should also check for other programs named @samp{env} in your path
2771 (e.g., SunOS has a program named @file{/usr/bin/env}). We don't
2772 understand why this can cause a failure and don't know a general
2773 solution for working around the problem in this case.
2775 The @samp{make clean} command will remove @samp{env} and other vital
2776 programs, so be careful when using it.
2778 It has been reported that this sometimes happened when Emacs was started
2779 as an X client from an xterm window (i.e., had a controlling tty) but the
2780 xterm was later terminated.
2782 See also @samp{PROBLEMS} (in the @file{etc} subdirectory of the
2783 top-level directory when you unpack the Emacs source) for other
2784 possible causes of this message.
2786 @node Problems with Shell Mode on MS-Windows, Termcap/Terminfo entries for Emacs, Shell process exits abnormally, Bugs and problems
2787 @section Why do I get an error message when I try to run @kbd{M-x shell}?
2789 @cindex Shell Mode, and MS-Windows
2790 @cindex @code{explicit-shell-file-name}
2791 On MS-Windows, this might happen because Emacs tries to look for the
2792 shell in a wrong place. The default file name @file{/bin/sh} is
2793 usually incorrect for non-Unix systems. If you know where your shell
2794 executable is, set the variable @code{explicit-shell-file-name} in
2795 your @file{.emacs} file to point to its full file name, like this:
2798 (setq explicit-shell-file-name "d:/shells/bash.exe")
2801 If you don't know what shell does Emacs use, try the @kbd{M-!}
2802 command; if that works, put the following line into your
2806 (setq explicit-shell-file-name shell-file-name)
2809 @cindex Antivirus programs, and Shell Mode
2810 Some people have trouble with Shell Mode because of intrusive
2811 antivirus software; disabling the resident antivirus program solves
2812 the problems in those cases.
2814 @node Termcap/Terminfo entries for Emacs, Spontaneous entry into isearch-mode, Problems with Shell Mode on MS-Windows, Bugs and problems
2815 @section Where is the termcap/terminfo entry for terminal type @samp{emacs}?
2818 @cindex Emacs entries for termcap/terminfo
2820 The termcap entry for terminal type @samp{emacs} is ordinarily put in
2821 the @samp{TERMCAP} environment variable of subshells. It may help in
2822 certain situations (e.g., using rlogin from shell buffer) to add an
2823 entry for @samp{emacs} to the system-wide termcap file. Here is a
2824 correct termcap entry for @samp{emacs}:
2830 To make a terminfo entry for @samp{emacs}, use @code{tic} or
2831 @code{captoinfo}. You need to generate
2832 @file{/usr/lib/terminfo/e/emacs}. It may work to simply copy
2833 @file{/usr/lib/terminfo/d/dumb} to @file{/usr/lib/terminfo/e/emacs}.
2835 Having a termcap/terminfo entry will not enable the use of full screen
2836 programs in shell buffers. Use @kbd{M-x terminal-emulator} for that
2839 A workaround to the problem of missing termcap/terminfo entries is to
2840 change terminal type @samp{emacs} to type @samp{dumb} or @samp{unknown}
2841 in your shell start up file. @code{csh} users could put this in their
2842 @file{.cshrc} files:
2845 if ("$term" == emacs) set term=dumb
2848 @node Spontaneous entry into isearch-mode, Problems talking to certain hosts, Termcap/Terminfo entries for Emacs, Bugs and problems
2849 @section Why does Emacs spontaneously start displaying @samp{I-search:} and beeping?
2850 @cindex Spontaneous entry into isearch-mode
2851 @cindex isearch-mode, spontaneous entry into
2852 @cindex Beeping without obvious reason
2854 Your terminal (or something between your terminal and the computer) is
2855 sending @kbd{C-s} and @kbd{C-q} for flow control, and Emacs is receiving
2856 these characters and interpreting them as commands. (The @kbd{C-s}
2857 character normally invokes the @code{isearch-forward} command.) For
2858 possible solutions, see @ref{Handling C-s and C-q with flow control}.
2860 @node Problems talking to certain hosts, Errors with init files, Spontaneous entry into isearch-mode, Bugs and problems
2861 @section Why can't Emacs talk to certain hosts (or certain hostnames)?
2862 @cindex Hosts, Emacs cannot talk to
2863 @cindex @code{gethostbyname}, problematic version
2865 The problem may be that Emacs is linked with a wimpier version of
2866 @code{gethostbyname} than the rest of the programs on the machine. This
2867 is often manifested as a message on startup of ``X server not responding.
2868 Check your @samp{DISPLAY} environment variable.'' or a message of
2869 ``Unknown host'' from @code{open-network-stream}.
2871 On a Sun, this may be because Emacs had to be linked with the static C
2872 library. The version of @code{gethostbyname} in the static C library
2873 may only look in @file{/etc/hosts} and the NIS (YP) maps, while the
2874 version in the dynamic C library may be smart enough to check DNS in
2875 addition to or instead of NIS. On a Motorola Delta running System V
2876 R3.6, the version of @code{gethostbyname} in the standard library works,
2877 but the one that works with NIS doesn't (the one you get with -linet).
2878 Other operating systems have similar problems.
2885 Explicitly add the host you want to communicate with to @file{/etc/hosts}.
2888 Relink Emacs with this line in @file{src/config.h}:
2891 #define LIBS_SYSTEM -lresolv
2895 Replace @code{gethostbyname} and friends in @file{libc.a} with more
2896 useful versions such as the ones in @file{libresolv.a}. Then relink
2900 If you are actually running NIS, make sure that @code{ypbind} is
2901 properly told to do DNS lookups with the correct command line switch.
2905 @node Errors with init files, Emacs ignores X resources, Problems talking to certain hosts, Bugs and problems
2906 @section Why does Emacs say @samp{Error in init file}?
2907 @cindex Error in @file{.emacs}
2908 @cindex Error in init file
2909 @cindex Init file, errors in
2910 @cindex @file{.emacs} file, errors in
2911 @cindex Debugging @file{.emacs} file
2913 An error occurred while loading either your @file{.emacs} file or the
2914 system-wide file @file{lisp/default.el}. Emacs 21.1 and later pops the
2915 @file{*Messages*} buffer, and puts there some additional information
2916 about the error, to provide some hints for debugging.
2918 For information on how to debug your @file{.emacs} file, see
2919 @ref{Debugging a customization file}.
2921 It may be the case that you need to load some package first, or use a
2922 hook that will be evaluated after the package is loaded. A common case
2923 of this is explained in @ref{Terminal setup code works after Emacs has
2926 @node Emacs ignores X resources, Emacs ignores frame parameters, Errors with init files, Bugs and problems
2927 @section Why does Emacs ignore my X resources (my .Xdefaults file)?
2928 @cindex X resources being ignored
2929 @cindex Ignored X resources
2930 @cindex @file{.Xdefaults}
2932 As of version 19, Emacs searches for X resources in the files specified
2933 by the following environment variables:
2937 @item @code{XFILESEARCHPATH}
2938 @item @code{XUSERFILESEARCHPATH}
2939 @item @code{XAPPLRESDIR}
2943 This emulates the functionality provided by programs written using the
2946 @code{XFILESEARCHPATH} and @code{XUSERFILESEARCHPATH} should be a list
2947 of file names separated by colons. @code{XAPPLRESDIR} should be a list
2948 of directory names separated by colons.
2950 Emacs searches for X resources:
2955 specified on the command line, with the @samp{-xrm RESOURCESTRING} option,
2958 then in the value of the @samp{XENVIRONMENT} environment variable,
2963 or if that is unset, in the file named
2964 @file{~/.Xdefaults-@var{hostname}} if it exists (where @var{hostname} is
2965 the name of the machine Emacs is running on),
2970 then in the screen-specific and server-wide resource properties provided
2976 or if those properties are unset, in the file named @file{~/.Xdefaults}
2982 then in the files listed in @samp{XUSERFILESEARCHPATH},
2987 or in files named @file{@var{lang}/Emacs} in directories listed in
2988 @samp{XAPPLRESDIR} (where @var{lang} is the value of the @code{LANG}
2989 environment variable), if the @samp{LANG} environment variable is set,
2991 or in files named Emacs in the directories listed in @samp{XAPPLRESDIR}
2993 or in @file{~/@var{lang}/Emacs} (if the @code{LANG} environment variable
2996 or in @file{~/Emacs},
3001 then in the files listed in @code{XFILESEARCHPATH}.
3005 @node Emacs ignores frame parameters, Emacs takes a long time to visit files, Emacs ignores X resources, Bugs and problems
3006 @section Why don't my customizations of the frame parameters work?
3007 @cindex Frame parameters
3009 This probably happens because you have set the frame parameters in the
3010 variable @code{initial-frame-alist}. That variable holds parameters
3011 used only for the first frame created when Emacs starts. To customize
3012 the parameters of all frames, change the variable
3013 @code{default-frame-alist} instead.
3015 These two variables exist because many users customize the initial frame
3016 in a special way. For example, you could determine the position and
3017 size of the initial frame, but would like to control the geometry of the
3018 other frames by individually positioning each one of them.
3021 @node Emacs takes a long time to visit files, Editing files with $ in the name, Emacs ignores frame parameters, Bugs and problems
3022 @section Why does Emacs take 20 seconds to visit a file?
3023 @cindex Visiting files takes a long time
3024 @cindex Delay when visiting files
3025 @cindex Files, take a long time to visit
3027 Old versions of Emacs (i.e., versions before Emacs 20.x) often
3028 encountered this when the master lock file, @file{!!!SuperLock!!!}, has
3029 been left in the lock directory somehow. Delete it.
3031 @email{meuer@@geom.umn.edu, Mark Meuer} says that NeXT NFS has a bug
3032 where an exclusive create succeeds but returns an error status. This
3033 can cause the same problem. Since Emacs's file locking doesn't work
3034 over NFS anyway, the best solution is to recompile Emacs with
3035 @code{CLASH_DETECTION} undefined.
3037 @node Editing files with $ in the name, Shell mode loses the current directory, Emacs takes a long time to visit files, Bugs and problems
3038 @section How do I edit a file with a @samp{$} in its name?
3039 @cindex Editing files with @samp{$} in the name
3040 @cindex @samp{$} in file names
3041 @cindex File names containing @samp{$}, editing
3043 When entering a file name in the minibuffer, Emacs will attempt to expand
3044 a @samp{$} followed by a word as an environment variable. To suppress
3045 this behavior, type @kbd{$$} instead.
3047 @node Shell mode loses the current directory, Security risks with Emacs, Editing files with $ in the name, Bugs and problems
3048 @section Why does shell mode lose track of the shell's current directory?
3049 @cindex Current directory and @code{shell-mode}
3050 @cindex @code{shell-mode} and current directory
3051 @cindex Directory, current in @code{shell-mode}
3053 Emacs has no way of knowing when the shell actually changes its
3054 directory. This is an intrinsic limitation of Unix. So it tries to
3055 guess by recognizing @samp{cd} commands. If you type @kbd{cd} followed
3056 by a directory name with a variable reference (@kbd{cd $HOME/bin}) or
3057 with a shell metacharacter (@kbd{cd ../lib*}), Emacs will fail to
3058 correctly guess the shell's new current directory. A huge variety of
3059 fixes and enhancements to shell mode for this problem have been written
3060 to handle this problem (@pxref{Finding a package with particular
3063 You can tell Emacs the shell's current directory with the command
3066 @node Security risks with Emacs, Dired claims that no file is on this line, Shell mode loses the current directory, Bugs and problems
3067 @section Are there any security risks in Emacs?
3068 @cindex Security with Emacs
3069 @cindex @samp{movemail} and security
3070 @cindex @code{file-local-variable} and security
3071 @cindex Synthetic X events and security
3072 @cindex X events and security
3077 The @file{movemail} incident. (No, this is not a risk.)
3079 In his book @cite{The Cuckoo's Egg}, Cliff Stoll describes this in
3080 chapter 4. The site at LBL had installed the @file{/etc/movemail}
3081 program setuid root. (As of version 19, @file{movemail} is in your
3082 architecture-specific directory; type @kbd{C-h v exec-directory
3083 @key{RET}} to see what it is.) Since @code{movemail} had not been
3084 designed for this situation, a security hole was created and users could
3085 get root privileges.
3087 @code{movemail} has since been changed so that this security hole will
3088 not exist, even if it is installed setuid root. However,
3089 @code{movemail} no longer needs to be installed setuid root, which
3090 should eliminate this particular risk.
3092 We have heard unverified reports that the 1988 Internet worm took
3093 advantage of this configuration problem.
3096 The @code{file-local-variable} feature. (Yes, a risk, but easy to
3099 There is an Emacs feature that allows the setting of local values for
3100 variables when editing a file by including specially formatted text near
3101 the end of the file. This feature also includes the ability to have
3102 arbitrary Emacs Lisp code evaluated when the file is visited.
3103 Obviously, there is a potential for Trojan horses to exploit this
3106 Emacs 18 allowed this feature by default; users could disable it by
3107 setting the variable @code{inhibit-local-variables} to a non-@code{nil} value.
3109 As of Emacs 19, Emacs has a list of local variables that create a
3110 security risk. If a file tries to set one of them, it asks the user to
3111 confirm whether the variables should be set. You can also tell Emacs
3112 whether to allow the evaluation of Emacs Lisp code found at the bottom
3113 of files by setting the variable @code{enable-local-eval}.
3115 For more information, @inforef{File Variables, File Variables, emacs}.
3118 Synthetic X events. (Yes, a risk; use @samp{MIT-MAGIC-COOKIE-1} or
3121 Emacs accepts synthetic X events generated by the @code{SendEvent}
3122 request as though they were regular events. As a result, if you are
3123 using the trivial host-based authentication, other users who can open X
3124 connections to your X workstation can make your Emacs process do
3125 anything, including run other processes with your privileges.
3127 The only fix for this is to prevent other users from being able to open
3128 X connections. The standard way to prevent this is to use a real
3129 authentication mechanism, such as @samp{MIT-MAGIC-COOKIE-1}. If using
3130 the @code{xauth} program has any effect, then you are probably using
3131 @samp{MIT-MAGIC-COOKIE-1}. Your site may be using a superior
3132 authentication method; ask your system administrator.
3134 If real authentication is not a possibility, you may be satisfied by
3135 just allowing hosts access for brief intervals while you start your X
3136 programs, then removing the access. This reduces the risk somewhat by
3137 narrowing the time window when hostile users would have access, but
3138 @emph{does not eliminate the risk}.
3140 On most computers running Unix and X, you enable and disable
3141 access using the @code{xhost} command. To allow all hosts access to
3149 at the shell prompt, which (on an HP machine, at least) produces the
3153 access control disabled, clients can connect from any host
3156 To deny all hosts access to your X server (except those explicitly
3157 allowed by name), use
3163 On the test HP computer, this command generated the following message:
3166 access control enabled, only authorized clients can connect
3171 @node Dired claims that no file is on this line, , Security risks with Emacs, Bugs and problems
3172 @section Dired says, @samp{no file on this line} when I try to do something.
3173 @cindex Dired does not see a file
3175 @c FIXME: I think this is fixed in Emacs 21, but I didn't have time to
3177 Chances are you're using a localized version of Unix that doesn't use US
3178 date format in dired listings. You can check this by looking at dired
3179 listings or by typing @kbd{ls -l} to a shell and looking at the dates that
3182 Dired uses a regular expression to find the beginning of a file name.
3183 In a long Unix-style directory listing (@samp{ls -l}), the file name
3184 starts after the date. The regexp has thus been written to look for the
3185 date, the format of which can vary on non-US systems.
3187 There are two approaches to solving this. The first one involves
3188 setting things up so that @samp{ls -l} outputs US date format. This can
3189 be done by setting the locale. See your OS manual for more information.
3191 The second approach involves changing the regular expression used by
3192 dired, @code{directory-listing-before-filename-regexp}.
3194 @c ------------------------------------------------------------
3195 @node Compiling and installing Emacs, Finding Emacs and related packages, Bugs and problems, Top
3196 @chapter Compiling and installing Emacs
3197 @cindex Compiling and installing Emacs
3200 * Installing Emacs::
3202 * Problems building Emacs::
3203 * Linking with -lX11 fails::
3206 @node Installing Emacs, Updating Emacs, Compiling and installing Emacs, Compiling and installing Emacs
3207 @section How do I install Emacs?
3208 @cindex Installing Emacs
3209 @cindex Unix systems, installing Emacs on
3210 @cindex Downloading and installing Emacs
3211 @cindex Retrieving and installing Emacs
3212 @cindex Building Emacs from source
3213 @cindex Source code, building Emacs from
3214 @cindex Unpacking and installing Emacs
3216 This answer is meant for users of Unix and Unix-like systems. Users of
3217 other operating systems should see the series of questions beginning
3218 with @ref{Emacs for MS-DOS}, which describe where to get non-Unix source
3219 and binaries, and how to install Emacs on those systems.
3221 For Unix and Unix-like systems, the easiest way is often to compile it
3222 from scratch. You will need:
3227 Emacs sources. @xref{Current GNU distributions}, for a list of ftp sites
3228 that make them available. On @file{ftp.gnu.org}, the main GNU
3229 distribution site, sources are available as
3231 @uref{ftp://ftp.gnu.org/pub/gnu/emacs/emacs-@value{VER}.tar.gz}
3233 The above will obviously change as new versions of Emacs come out. For
3234 instance, when Emacs 22.42 is released, it will most probably be
3237 @uref{ftp://ftp.gnu.org/pub/gnu/emacs/emacs-22.42.tar.gz}
3239 Again, you should use one of the GNU mirror sites (see @ref{Current GNU
3240 distributions}, and adjust the URL accordingly) so as to reduce load on
3244 @code{gzip}, the GNU compression utility. You can get @code{gzip} via
3245 anonymous ftp at mirrors of @file{ftp.gnu.org} sites; it should compile
3246 and install without much trouble on most systems. Once you have
3247 retrieved the Emacs sources, you will probably be able to uncompress
3248 them with the command
3251 gunzip --verbose emacs-@value{VER}.tar.gz
3255 changing the Emacs version (@value{VER}), as necessary. Once
3256 @code{gunzip} has finished doing its job, a file by the name of
3257 @file{emacs-@value{VER}.tar} should be in your build directory.
3260 @code{tar}, the @dfn{tape archiving} program, which moves multiple files
3261 into and out of archive files, or @dfn{tarfiles}. All of the files
3262 comprising the Emacs source come in a single tarfile, and must be
3263 extracted using @code{tar} before you can build Emacs. Typically, the
3264 extraction command would look like
3267 tar -xvvf emacs-@value{VER}.tar
3271 The @samp{x} indicates that we want to extract files from this tarfile,
3272 the two @samp{v}s force verbose output, and the @samp{f} tells
3273 @code{tar} to use a disk file, rather than one on the tape drive.
3275 If you're using GNU @code{tar} (available at mirrors of
3276 @file{ftp.gnu.org}), you can combine this step and the previous one by
3280 tar -zxvvf emacs-@value{VER}.tar.gz
3284 The additional @samp{z} at the beginning of the options list tells GNU
3285 @code{tar} to uncompress the file with @code{gunzip} before extracting
3286 the tarfile's components.
3290 At this point, the Emacs sources (all 70+ megabytes of them) should be
3291 sitting in a directory called @file{emacs-@value{VER}}. On most common
3292 Unix and Unix-like systems, you should be able to compile Emacs (with X
3293 Window system support) with the following commands:
3296 cd emacs-@value{VER} # change directory to emacs-@value{VER}
3297 ./configure # configure Emacs for your particular system
3298 make # use Makefile to build components, then Emacs
3301 If the @code{make} completes successfully, the odds are fairly good that
3302 the build has gone well. (@xref{Problems building Emacs}, if you weren't
3305 By default, Emacs is installed in the following directories:
3308 @item /usr/local/bin
3311 @item /usr/local/share/emacs/@value{VER}
3312 Lisp code and support files.
3314 @item /usr/local/info
3318 To install files in those default directories, become the superuser and
3325 Note that @samp{make install} will overwrite @file{/usr/local/bin/emacs}
3326 and any Emacs Info files that might be in @file{/usr/local/info}.
3328 Much more verbose instructions (with many more hints and suggestions)
3329 come with the Emacs sources, in the file @file{INSTALL}.
3331 @node Updating Emacs, Problems building Emacs, Installing Emacs, Compiling and installing Emacs
3332 @section How do I update Emacs to the latest version?
3333 @cindex Updating Emacs
3335 @xref{Installing Emacs}, and follow the instructions there for
3338 Most files are placed in version-specific directories. Emacs
3339 @value{VER}, for instance, places files in
3340 @file{/usr/local/share/emacs/@value{VER}}.
3342 Upgrading should overwrite only, @file{/usr/local/bin/emacs} (the Emacs
3343 binary) and documentation in @file{/usr/local/info}. Back up these
3344 files before you upgrade, and you shouldn't have too much trouble.
3346 @node Problems building Emacs, Linking with -lX11 fails, Updating Emacs, Compiling and installing Emacs
3347 @section What should I do if I have trouble building Emacs?
3348 @cindex Problems building Emacs
3349 @cindex Errors when building Emacs
3351 First look in the file @file{etc/PROBLEMS} (where you unpack the Emacs
3352 source) to see if there is already a solution for your problem. Next,
3353 look for other questions in this FAQ that have to do with Emacs
3354 installation and compilation problems.
3356 If you'd like to have someone look at your problem and help solve it,
3357 see @ref{Help installing Emacs}.
3359 If you cannot find a solution in the documentation, send a message to
3360 @email{bug-gnu-emacs@@gnu.org}.
3362 Please don't post it to @uref{news:gnu.emacs.help} or send e-mail to
3363 @email{help-gnu-emacs@@gnu.org}. For further guidelines, see
3364 @ref{Guidelines for newsgroup postings} and @ref{Reporting bugs}.
3366 @node Linking with -lX11 fails, , Problems building Emacs, Compiling and installing Emacs
3367 @section Why does linking Emacs with -lX11 fail?
3368 @cindex Linking with -lX11 fails
3369 @cindex lX11, linking fails with
3371 Emacs needs to be linked with the static version of the X11 library,
3372 @file{libX11.a}. This may be missing.
3374 On OpenWindows, you may need to use @code{add_services} to add the
3375 ``OpenWindows Programmers'' optional software category from the CD-ROM.
3377 On HP-UX 8.0, you may need to run @code{update} again to load the
3378 X11-PRG ``fileset''. This may be missing even if you specified ``all
3379 filesets'' the first time. If @file{libcurses.a} is missing, you may
3380 need to load the ``Berkeley Development Option.''
3382 @email{zoo@@armadillo.com, David Zuhn} says that MIT X builds shared
3383 libraries by default, and only shared libraries, on those platforms that
3384 support them. These shared libraries can't be used when undumping
3385 @code{temacs} (the last stage of the Emacs build process). To get
3386 regular libraries in addition to shared libraries, add this to
3390 #define ForceNormalLib YES
3393 Other systems may have similar problems. You can always define
3394 @code{CANNOT_DUMP} and link with the shared libraries instead.
3396 @cindex X Menus don't work
3397 To get the Xmenu stuff to work, you need to find a copy of MIT's
3400 @c ------------------------------------------------------------
3401 @node Finding Emacs and related packages, Major packages and programs, Compiling and installing Emacs, Top
3402 @chapter Finding Emacs and related packages
3403 @cindex Finding Emacs and related packages
3406 * Finding Emacs on the Internet::
3407 * Finding a package with particular functionality::
3408 * Packages that do not come with Emacs::
3409 * Current GNU distributions::
3410 * Difference between Emacs and XEmacs::
3411 * Emacs for MS-DOS::
3412 * Emacs for Windows::
3414 * Emacs for Atari ST::
3415 * Emacs for the Amiga ::
3416 * Emacs for NeXTSTEP::
3417 * Emacs for Apple computers::
3418 * Emacs for VMS and DECwindows::
3419 * Modes for various languages::
3422 @node Finding Emacs on the Internet, Finding a package with particular functionality, Finding Emacs and related packages, Finding Emacs and related packages
3423 @section Where can I get Emacs on the net (or by snail mail)?
3424 @cindex Finding Emacs on the Internet
3425 @cindex Snail mail, ordering Emacs via
3426 @cindex Postal service, ordering Emacs via
3427 @cindex Distribution, retrieving Emacs
3428 @cindex Internet, retrieving from
3430 Look in the files @file{etc/DISTRIB} and @file{etc/FTP} for
3431 information on nearby archive sites. If you don't already have Emacs,
3432 see @ref{Informational files for Emacs}, for how to get these files.
3434 @xref{Installing Emacs}, for information on how to obtain and build the latest
3435 version of Emacs, and see @ref{Current GNU distributions}, for a list of
3436 archive sites that make GNU software available.
3438 @node Finding a package with particular functionality, Packages that do not come with Emacs, Finding Emacs on the Internet, Finding Emacs and related packages
3439 @section How do I find a Emacs Lisp package that does XXX?
3440 @cindex Package, finding
3441 @cindex Finding an Emacs Lisp package
3442 @cindex Functionality, finding a particular package
3444 First of all, you should check to make sure that the package isn't
3445 already available. For example, typing @kbd{M-x apropos @key{RET}
3446 wordstar @key{RET}} lists all functions and variables containing the
3447 string @samp{wordstar}.
3449 It is also possible that the package is on your system, but has not been
3450 loaded. To see which packages are available for loading, look through
3451 your computer's lisp directory (@pxref{File-name conventions}). The Lisp
3452 source to most packages contains a short description of how they
3453 should be loaded, invoked, and configured---so before you use or
3454 modify a Lisp package, see if the author has provided any hints in the
3457 The command @kbd{C-h p} (@code{finder-by-keyword}) allows you to browse
3458 the constituent Emacs packages.
3460 For advice on how to find extra packages that are not part of Emacs,
3461 see @ref{Packages that do not come with Emacs}.
3463 @node Packages that do not come with Emacs, Current GNU distributions, Finding a package with particular functionality, Finding Emacs and related packages
3464 @section Where can I get Emacs Lisp packages that don't come with Emacs?
3465 @cindex Unbundled packages
3466 @cindex Finding other packages
3467 @cindex Lisp packages that do not come with Emacs
3468 @cindex Packages, those that do not come with Emacs
3469 @cindex Emacs Lisp List
3470 @cindex Emacs Lisp Archive
3472 @uref{http://www.anc.ed.ac.uk/~stephen/emacs/ell.html, The Emacs Lisp
3473 List (ELL)}, maintained by @email{stephen@@anc.ed.ac.uk, Stephen Eglen},
3474 aims to provide one compact list with links to all of the current Emacs
3475 Lisp files on the internet. The ELL can be browsed over the web, or
3476 from Emacs with @uref{http://www.anc.ed.ac.uk/~stephen/emacs/ell.el,
3477 the @file{ell} package}.
3479 Many authors post their packages to the @uref{news:gnu.emacs.sources,
3480 Emacs sources newsgroup}. You can search the archives of this
3481 group with @uref{http://groups.google.com, Google}, for example.
3483 Several packages are stored in
3484 @uref{http://emacswiki.org/elisp/, the Lisp area of the Emacs Wiki}.
3486 For a long time, the Emacs Lisp Archive provided a central repository
3487 for Emacs packages. Sadly, it has not been active for some time,
3488 although you can still access the old files at
3490 @uref{ftp://ftp.cis.ohio-state.edu/pub/emacs-lisp/WWW/index.html}
3492 @node Current GNU distributions, Difference between Emacs and XEmacs, Packages that do not come with Emacs, Finding Emacs and related packages
3493 @section Where can I get other up-to-date GNU stuff?
3494 @cindex Current GNU distributions
3495 @cindex Sources for current GNU distributions
3496 @cindex Stuff, current GNU
3497 @cindex Up-to-date GNU stuff
3498 @cindex Finding current GNU software
3499 @cindex Official GNU software sites
3501 The most up-to-date official GNU software is normally kept at
3503 @uref{ftp://ftp.gnu.org/pub/gnu}
3505 Read the files @file{etc/DISTRIB} and @file{etc/FTP} for more
3508 A list of sites mirroring @samp{ftp.gnu.org} can be found at
3510 @uref{http://www.gnu.org/order/ftp.html}
3512 @node Difference between Emacs and XEmacs, Emacs for MS-DOS, Current GNU distributions, Finding Emacs and related packages
3513 @section What is the difference between Emacs and XEmacs (formerly Lucid Emacs)?
3515 @cindex Difference Emacs and XEmacs
3519 XEmacs is a branch version of Emacs. It was first called Lucid Emacs,
3520 and was initially derived from a prerelease version of Emacs 19. In
3521 this FAQ, we use the name ``Emacs'' only for the official version.
3523 Emacs and XEmacs each come with Lisp packages that are lacking in the
3524 other. The two versions have some significant differences at the Lisp
3525 programming level. Their current features are roughly comparable,
3526 though the support for some operating systems, character sets and
3527 specific packages might be quite different.
3529 Some XEmacs code has been contributed to Emacs, and we would like to
3530 use other parts, but the earlier XEmacs maintainers did not always
3531 keep track of the authors of contributed code, which makes it
3532 impossible for the FSF to get copyright papers signed for that code.
3533 (The FSF requires these papers for all the code included in the Emacs
3534 release, aside from generic C support packages that retain their
3535 separate identity and are not integrated into the code of Emacs
3538 If you want to talk about these two versions and distinguish them,
3539 please call them ``Emacs'' and ``XEmacs.'' To contrast ``XEmacs''
3540 with ``GNU Emacs'' would be misleading, since XEmacs too has its
3541 origin in the work of the GNU Project. Terms such as ``Emacsen'' and
3542 ``(X)Emacs'' are not wrong, but they are not very clear, so it
3543 is better to write ``Emacs and XEmacs.''
3545 @node Emacs for MS-DOS, Emacs for Windows, Difference between Emacs and XEmacs, Finding Emacs and related packages
3546 @section Where can I get Emacs for my PC running MS-DOS?
3547 @cindex MS-DOS, Emacs for
3548 @cindex DOS, Emacs for
3549 @cindex Compiling Emacs for DOS
3550 @cindex Emacs for MS-DOS
3551 @cindex Tools needed to compile Emacs under DOS
3553 A pre-built binary distribution of Emacs is available from the
3554 SimTel.NET archives. This version apparently works under MS-DOS and
3555 Windows (3.X, 9X, ME, NT, and 2000) and supports long file names under
3556 Windows 9X, Windows ME, and Windows 2000. More information is available
3559 @uref{ftp://ftp.delorie.com/pub/djgpp/current/v2gnu/emacs.README}
3561 The binary itself is available in the files @file{em*.zip} in the
3564 @uref{ftp://ftp.delorie.com/pub/djgpp/current/v2gnu/}
3566 If you prefer to compile Emacs for yourself, you can do so with the
3567 current distribution directly. You will need a 386 (or
3568 better) processor, and to be running MS-DOS 3.0 or later. According to
3569 @email{eliz@@gnu.org, Eli Zaretskii} and
3570 @email{hankedr@@dms.auburn.edu, Darrel Hankerson}, you will need the
3576 DJGPP version 1.12 maint 1 or later. Djgpp 2.0 or later is
3577 recommended, since 1.x is very old an unmaintained. Djgpp 2 supports
3578 long file names on Windows 9X/ME/2K.
3580 You can get the latest release of DJGPP by retrieving all of
3583 @uref{ftp://ftp.delorie.com/pub/djgpp/current/v2*}
3585 @item Unpacking program
3586 The easiest way is to use @code{djtar} which comes with DJGPP v2.x,
3587 because it can open gzip'ed tarfiles (i.e., those ending with
3588 @file{.tar.gz}) in one step. @code{Djtar} comes in
3589 @file{djdev@var{nnn}.zip} archive (where @var{nnn} is the DJGPP version
3590 number), from the URL mentioned above.
3592 @strong{Warning!} Do @strong{not} use the popular WinZip program to
3593 unpack the Emacs distribution! WinZip is known to corrupt some of the
3594 files by converting them to the DOS CR-LF format, it doesn't always
3595 preserve the directory structure recorded in the compressed Emacs
3596 archive, and commits other atrocities. Some of these problems could
3597 actually prevent Emacs from building successfully!
3599 @item make, mv, sed, and rm
3600 All of these utilities are available at
3602 @uref{ftp://ftp.delorie.com/pub/djgpp/current/v2gnu}
3604 16-bit utilities can be found in GNUish, at
3606 @uref{http://www.simtel.net/pub/gnuish/}
3609 (@code{mv} and @code{rm} are in the Fileutils package, @code{sed} and
3610 @code{make} are each one in a separate package named after them.)
3614 The files @file{INSTALL} (near its end) and @file{etc/PROBLEMS} in the
3615 directory of the Emacs sources contains some additional information
3616 regarding Emacs under MS-DOS.
3618 For a list of other MS-DOS implementations of Emacs (and Emacs
3619 look-alikes), consult the list of ``Emacs implementations and literature,''
3622 @uref{ftp://rtfm.mit.edu/pub/usenet/comp.emacs/}
3624 Note that while many of these programs look similar to Emacs, they often
3625 lack certain features, such as the Emacs Lisp extension language.
3627 @node Emacs for Windows, Emacs for OS/2, Emacs for MS-DOS, Finding Emacs and related packages
3628 @section Where can I get Emacs for Microsoft Windows?
3629 @cindex FAQ for NT Emacs
3630 @cindex Emacs for MS-Windows
3631 @cindex Microsoft Windows, Emacs for
3632 @cindex Windows 9X, ME, NT, 2K, and CE, Emacs for
3634 For information on Emacs for Windows 95 and NT, read the FAQ produced by
3635 @email{voelker@@cs.washington.edu, Geoff Voelker}, available at
3637 @uref{http://www.gnu.org/software/emacs/windows/ntemacs.html}
3639 @xref{Emacs for MS-DOS}, for Windows 3.1.
3641 A port of Emacs 20.7 for Windows CE, based on NTEmacs, is available at
3643 @uref{http://www.rainer-keuchel.de/software.html}
3646 This port was done by @email{coyxc@@rainer-keuchel.de, Rainer Keuchel},
3647 and supports all Emacs features except async subprocesses and menus.
3648 You will need MSVC 6.0 and a Windows CE SDK to build this port.
3650 @node Emacs for OS/2, Emacs for Atari ST, Emacs for Windows, Finding Emacs and related packages
3651 @section Where can I get Emacs for my PC running OS/2?
3652 @cindex OS/2, Emacs for
3654 Emacs 20.6 is ported for emx on OS/2 2.0 or 2.1, and is available at
3656 @uref{ftp://hobbes.nmsu.edu/pub/os2/apps/editors/emacs/e206*.zip}
3661 @uref{http://archiv.leo.org/pub/comp/os/os2/leo/gnu/emacs%2d20/}
3663 Instructions for installation, basic setup, and other useful information
3664 for OS/2 users of Emacs can be found at
3666 @uref{http://userpage.fu-berlin.de/~oheiabbd/emacs/emacs206-os2.html}
3668 @node Emacs for Atari ST, Emacs for the Amiga , Emacs for OS/2, Finding Emacs and related packages
3669 @section Where can I get Emacs for my Atari ST?
3670 @cindex Atari ST, Emacs for
3671 @cindex TOS, Emacs for
3673 Roland Sch@"auble reports that Emacs 18.58 running on plain TOS and MiNT
3675 @uref{ftp://atari.archive.umich.edu/Editors/Emacs-18-58/1858b-d3.zoo}.
3677 @node Emacs for the Amiga , Emacs for NeXTSTEP, Emacs for Atari ST, Finding Emacs and related packages
3678 @section Where can I get Emacs for my Amiga?
3679 @cindex Amiga, Emacs for
3681 The files you need are available at
3683 @uref{ftp://ftp.wustl.edu/pub/aminet/util/gnu/}
3685 @email{dgilbert@@gamiga.guelphnet.dweomer.org, David Gilbert} has released a
3686 beta version of Emacs 19.25 for the Amiga. You can get the binary at
3688 @uref{ftp://ftp.wustl.edu/pub/aminet/util/gnu/a2.0bEmacs-bin.lha}
3690 @node Emacs for NeXTSTEP, Emacs for Apple computers, Emacs for the Amiga , Finding Emacs and related packages
3691 @section Where can I get Emacs for NeXTSTEP?
3692 @cindex NeXTSTEP, Emacs for
3694 Emacs.app is a NeXTSTEP version of Emacs 19.34 which supports colors,
3695 menus, and multiple frames. You can get it from
3697 @uref{ftp://next-ftp.peak.org/pub/next/apps/emacs/Emacs_for_NeXTstep.4.20a1.NIHS.b.tar.gz}
3699 @node Emacs for Apple computers, Emacs for VMS and DECwindows, Emacs for NeXTSTEP, Finding Emacs and related packages
3700 @section Where can I get Emacs for my Apple computer?
3701 @cindex Apple computers, Emacs for
3702 @cindex Macintosh, Emacs for
3704 Beginning with version 21.1, the Macintosh is supported in the official
3705 Emacs distribution; see the files @file{mac/README} and
3706 @file{mac/INSTALL} in the Emacs distribution for build instructions.
3708 Beginning with version 22.1, Emacs supports Mac OS X natively.
3710 @node Emacs for VMS and DECwindows, Modes for various languages, Emacs for Apple computers, Finding Emacs and related packages
3711 @section Where do I get Emacs that runs on VMS under DECwindows?
3712 @cindex DECwindows, Emacs for
3713 @cindex VMS, Emacs for
3715 Up-to-date information about GNU software (including Emacs) for VMS is
3716 available at @uref{http://vms.gnu.org/}.
3718 @node Modes for various languages, , Emacs for VMS and DECwindows, Finding Emacs and related packages
3719 @section Where can I get modes for Lex, Yacc/Bison, Bourne shell, csh, C@t{++}, Objective-C, Pascal, Java, and Awk?
3720 @cindex Awk, mode for
3721 @cindex @code{awk-mode}
3722 @cindex Bison, mode for
3723 @cindex Bourne Shell, mode for
3724 @cindex C@t{++}, mode for
3725 @cindex Java, mode for
3727 @cindex Objective-C, mode for
3728 @cindex @code{pascal-mode}
3731 @cindex @file{csh} mode
3732 @cindex @code{sh-mode}
3733 @cindex @code{cc-mode}
3735 Most of these modes are now available in standard Emacs distribution.
3736 To get additional modes, see @ref{Finding a package with particular
3739 Barry Warsaw's @code{cc-mode} now works for C, C@t{++}, Objective-C, and
3740 Java code. It is distributed with Emacs, but has
3741 @uref{http://cc-mode.sourceforge.net/, its own homepage}.
3743 @c ------------------------------------------------------------
3744 @node Major packages and programs, Key bindings, Finding Emacs and related packages, Top
3745 @chapter Major packages and programs
3746 @cindex Major packages and programs
3763 @node VM, Supercite, Major packages and programs, Major packages and programs
3764 @section VM (View Mail) --- another mail reader within Emacs, with MIME support
3766 @cindex Alternative mail software
3768 @cindex E-mail reader, VM
3773 @email{kyle_jones@@wonderworks.com, Kyle Jones}
3775 @item Latest version
3779 @uref{ftp://ftp.wonderworks.com/pub/vm/vm.tar.gz}
3781 @item Informational newsgroup
3782 @uref{news:gnu.emacs.vm.info}@*
3784 @item Bug reports newsgroup
3785 @uref{news:gnu.emacs.vm.bug}@*
3786 Or send reports to @email{bug-vm@@wonderworks.com}
3789 VM 7 works well with Emacs 21. Older versions of VM suitable for use
3790 with older versions of Emacs are available from
3791 @uref{ftp://ftp.wonderworks.com/pub/vm/, the same FTP site}.
3794 @node Supercite, Calc, VM, Major packages and programs
3795 @section Supercite --- mail and news citation package within Emacs
3798 @cindex Mail and news citations
3799 @cindex News and mail citations
3800 @cindex Citations in mail and news
3805 @email{barry@@python.org, Barry Warsaw}
3807 @item Latest version
3808 3.54 (comes bundled with Emacs since version 20)
3811 @uref{http://www.python.org/emacs/supercite.tar.gz}
3814 Subscription requests to @email{supercite-request@@python.org}@*
3815 Submissions @email{supercite@@python.org}
3819 Superyank is an old version of Supercite.
3821 @node Calc, VIPER, Supercite, Major packages and programs
3822 @section Calc --- poor man's Mathematica within Emacs
3823 @cindex Programmable calculator
3825 @cindex Mathematical package
3830 @email{daveg@@csvax.cs.caltech.edu, Dave Gillespie}
3832 @item Latest version
3833 2.1 (part of Emacs since version 22.1)
3836 No separate distribution outside of Emacs. Older versions
3837 are available at @uref{ftp://ftp.gnu.org/pub/gnu/calc/}.
3841 Note that Calc 2.02f needs patching to work with Emacs 21 and later.
3843 @cindex @code{calculator}, a package
3844 Emacs 21.1 and later comes with a package called @file{calculator.el}.
3845 It doesn't support all the mathematical wizardry offered by Calc, such
3846 as matrices, special functions, and statistics, but is more than
3847 adequate as a replacement for @code{xcalc} and similar programs.
3849 @node VIPER, AUCTeX, Calc, Major packages and programs
3850 @section VIPER --- @code{vi} emulation for Emacs
3851 @cindex @code{vi} emulation
3853 @cindex Emulation of @code{vi}
3855 Since Emacs 19.29, the preferred @code{vi} emulation in Emacs is VIPER
3856 (@kbd{M-x viper-mode @key{RET}}), which comes with Emacs. It extends
3857 and supersedes VIP (including VIP 4.3) and provides @code{vi} emulation
3858 at several levels, from one that closely follows @code{vi} to one that
3859 departs from @code{vi} in several significant ways.
3861 For Emacs 19.28 and earlier, the following version of VIP is generally
3862 better than the one distributed with Emacs:
3866 @email{sane@@cs.uiuc.edu, Aamod Sane}
3868 @item Latest version
3872 @uref{ftp://archive.cis.ohio-state.edu/pub/emacs-lisp/old-archive/modes/vip-mode.tar.Z}
3876 @node AUCTeX, BBDB, VIPER, Major packages and programs
3877 @section AUC@TeX{} --- enhanced @TeX{} modes with debugging facilities
3878 @cindex Mode for @TeX{}
3880 @cindex AUC@TeX{} mode for editing @TeX{}
3881 @cindex Writing and debugging @TeX{}
3883 AUC@TeX{} is a set of sophisticated major modes for @TeX{}, LaTeX,
3884 ConTeXt, and Texinfo offering context-sensitive syntax highlighting,
3885 indentation, formatting and folding, macro completion, @TeX{} shell
3886 functionality, and debugging. Be also sure to check out
3887 @ref{Introduction, RefTeX, Introduction, reftex, Ref@TeX{} User Manual}.
3888 Current versions of AUC@TeX{} include the
3889 @uref{http://www.gnu.org/software/auctex/preview-latex,preview-latex}
3890 package for WYSIWYG previews of various LaTeX constructs in the Emacs
3896 @email{krab@@iesd.auc.dk, Kresten Krab Thorup}, @*
3897 @email{abraham@@dina.kvl.dk, Per Abrahamsen}, @* and others.
3900 @email{dak@@gnu.org, David Kastrup}
3902 @item Latest version
3906 @uref{ftp://ftp.gnu.org/pub/gnu/auctex/}
3909 @uref{http://www.gnu.org/software/auctex/}
3912 Subscription requests to @email{auctex-request@@gnu.org}@*
3913 Submissions to @email{auctex@@gnu.org}
3917 @node BBDB, Ispell, AUCTeX, Major packages and programs
3918 @section BBDB --- personal Info Rolodex integrated with mail/news readers
3920 @cindex Rolodex-like functionality
3921 @cindex Integrated contact database
3922 @cindex Contact database
3923 @cindex Big Brother Database
3924 @cindex Address book
3929 @email{waider@@waider.ie, Ronan Waide}
3931 @item Latest version
3935 @uref{http://bbdb.sourceforge.net/}
3938 Subscription requests to @email{bbdb-info-request@@lists.sourceforge.net}@*
3939 Submissions to @email{bbdb-info@@lists.sourceforge.net}@*
3940 Release announcements: @email{bbdb-announce-request@@lists.sourceforge.net}
3944 @node Ispell, w3-mode, BBDB, Major packages and programs
3945 @section Ispell --- spell checker in C with interface for Emacs
3946 @cindex Spell-checker
3947 @cindex Checking spelling
3953 @email{geoff@@itcorp.com, Geoff Kuenning}
3955 @item Latest version
3959 @uref{ftp://ftp.cs.ucla.edu/pub/ispell/ispell-3.1.20.tar.gz}@*
3962 @uref{http://fmg-www.cs.ucla.edu/geoff/ispell.html}
3969 Do not ask Geoff to send you the latest version of Ispell. He does not
3973 This Ispell program is distinct from GNU Ispell 4.0. GNU Ispell 4.0 is
3974 no longer a supported product.
3978 @node w3-mode, EDB, Ispell, Major packages and programs
3979 @section w3-mode --- A World Wide Web browser inside of Emacs
3982 @cindex HTML browser in Emacs
3983 @cindex @code{w3-mode}
3988 @email{wmperry@@spry.com, Bill Perry}
3990 @item Latest version
3994 @uref{ftp://ftp.cs.indiana.edu/pub/elisp/w3/w3.tar.gz}
3997 Receive announcements from @email{w3-announce-request@@indiana.edu}@*
3998 Become a beta tester at @email{w3-beta-request@@indiana.edu}@*
3999 Help to develop @code{w3-mode} at @email{w3-dev@@indiana.edu}
4003 @node EDB, Mailcrypt, w3-mode, Major packages and programs
4004 @section EDB --- Database program for Emacs; replaces forms editing modes
4011 @email{mernst@@theory.lcs.mit.edu, Michael Ernst}
4013 @item Latest version
4017 @uref{ftp://theory.lcs.mit.edu/pub/emacs/edb}
4021 @node Mailcrypt, JDE, EDB, Major packages and programs
4022 @section Mailcrypt --- PGP interface within Emacs mail and news
4025 @cindex Interface to PGP from Emacs mail and news
4026 @cindex News, interface to PGP from
4027 @cindex Mail, interface to PGP from
4028 @cindex Encryption software, interface to
4033 @email{patl@@lcs.mit.edu, Patrick J. LoPresti} and
4034 @email{jin@@atype.com, Jin S. Choi}
4037 @email{warner-mailcrypt@@lothar.com, Brian Warner}
4039 @item Latest version
4043 @uref{http://dl.sourceforge.net/sourceforge/mailcrypt/mailcrypt-3.5.8.tar.gz}
4046 @uref{http://mailcrypt.sourceforge.net/}
4050 @node JDE, Patch, Mailcrypt, Major packages and programs
4051 @section JDE --- Integrated development environment for Java
4052 @cindex Java development environment
4053 @cindex Integrated Java development environment
4059 @email{paulk@@mathworks.com, Paul Kinnucan}
4062 jde-subscribe@@sunsite.auc.dk
4064 @item Latest version
4068 @uref{http://sunsite.auc.dk/jde/}
4072 @node Patch, , JDE, Major packages and programs
4073 @section Patch --- program to apply ``diffs'' for updating files
4074 @cindex Updating files with diffs
4075 @cindex Patching source files with diffs
4076 @cindex Diffs and patching
4077 @cindex @file{patch}
4082 @email{lwall@@wall.org, Larry Wall} (with GNU modifications)
4084 @item Latest version
4088 @xref{Current GNU distributions}.
4092 @c ------------------------------------------------------------
4093 @node Key bindings, Alternate character sets, Major packages and programs, Top
4094 @chapter Key bindings
4095 @cindex Key bindings
4098 * Binding keys to commands::
4099 * Invalid prefix characters::
4100 * Terminal setup code works after Emacs has begun::
4101 * Using function keys under X::
4102 * Working with function and arrow keys::
4103 * X key translations for Emacs::
4104 * Handling C-s and C-q with flow control::
4105 * Binding C-s and C-q::
4106 * Backspace invokes help::
4107 * stty and Backspace key::
4109 * Producing C-XXX with the keyboard::
4112 * Compose Character::
4113 * Binding combinations of modifiers and function keys::
4114 * Meta key does not work in xterm::
4115 * ExtendChar key does not work as Meta::
4116 * SPC no longer completes file names::
4119 @node Binding keys to commands, Invalid prefix characters, Key bindings, Key bindings
4120 @section How do I bind keys (including function keys) to commands?
4121 @cindex Binding keys to commands
4122 @cindex Keys, binding to commands
4123 @cindex Commands, binding keys to
4125 Keys can be bound to commands either interactively or in your
4126 @file{.emacs} file. To interactively bind keys for all modes, type
4127 @kbd{M-x global-set-key @key{RET} @var{key} @var{cmd} @key{RET}}.
4129 To bind a key just in the current major mode, type @kbd{M-x
4130 local-set-key @key{RET} @var{key} @var{cmd} @key{RET}}.
4132 @inforef{Key Bindings, Key Bindings, emacs}, for further details.
4134 To make the process of binding keys interactively easier, use the
4135 following ``trick'': First bind the key interactively, then immediately
4136 type @kbd{C-x @key{ESC} @key{ESC} C-a C-k C-g}. Now, the command needed
4137 to bind the key is in the kill ring, and can be yanked into your
4138 @file{.emacs} file. If the key binding is global, no changes to the
4139 command are required. For example,
4142 (global-set-key (quote [f1]) (quote help-for-help))
4146 can be placed directly into the @file{.emacs} file. If the key binding is
4147 local, the command is used in conjunction with the @samp{add-hook} function.
4148 For example, in TeX mode, a local binding might be
4151 (add-hook 'tex-mode-hook
4153 (local-set-key (quote [f1]) (quote help-for-help))))
4160 Control characters in key sequences, in the form yanked from the kill
4161 ring are given in their graphic form---i.e., @key{CTRL} is shown as
4162 @samp{^}, @key{TAB} as a set of spaces (usually 8), etc. You may want
4163 to convert these into their vector or string forms.
4166 If a prefix key of the character sequence to be bound is already
4167 bound as a complete key, then you must unbind it before the new
4168 binding. For example, if @kbd{ESC @{} is previously bound:
4171 (global-unset-key [?\e ?@{]) ;; or
4172 (local-unset-key [?\e ?@{])
4176 Aside from commands and ``lambda lists,'' a vector or string also
4177 can be bound to a key and thus treated as a macro. For example:
4180 (global-set-key [f10] [?\C-x?\e?\e?\C-a?\C-k?\C-g]) ;; or
4181 (global-set-key [f10] "\C-x\e\e\C-a\C-k\C-g")
4186 @node Invalid prefix characters, Terminal setup code works after Emacs has begun, Binding keys to commands, Key bindings
4187 @section Why does Emacs say @samp{Key sequence XXX uses invalid prefix characters}?
4188 @cindex Prefix characters, invalid
4189 @cindex Invalid prefix characters
4190 @cindex Misspecified key sequences
4192 Usually, one of two things has happened. In one case, the control
4193 character in the key sequence has been misspecified (e.g. @samp{C-f}
4194 used instead of @samp{\C-f} within a Lisp expression). In the other
4195 case, a @dfn{prefix key} in the keystroke sequence you were trying to bind
4196 was already bound as a @dfn{complete key}. Historically, the @samp{ESC [}
4197 prefix was usually the problem, in which case you should evaluate either
4198 of these forms before attempting to bind the key sequence:
4201 (global-unset-key [?\e ?[]) ;; or
4202 (global-unset-key "\e[")
4205 @node Terminal setup code works after Emacs has begun, Using function keys under X, Invalid prefix characters, Key bindings
4206 @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?
4207 @cindex Terminal setup code in @file{.emacs}
4209 During startup, Emacs initializes itself according to a given code/file
4210 order. If some of the code executed in your @file{.emacs} file needs to
4211 be postponed until the initial terminal or window-system setup code has
4212 been executed but is not, then you will experience this problem (this
4213 code/file execution order is not enforced after startup).
4215 To postpone the execution of Emacs Lisp code until after terminal or
4216 window-system setup, treat the code as a @dfn{lambda list} and set the
4217 value of either the @code{term-setup-hook} or @code{window-setup-hook}
4218 variable to this lambda function. For example,
4221 (add-hook 'term-setup-hook
4223 (when (string-match "\\`vt220" (or (getenv "TERM") ""))
4224 ;; Make vt220's "Do" key behave like M-x:
4225 (global-set-key [do] 'execute-extended-command))))
4228 For information on what Emacs does every time it is started, see the
4229 @file{lisp/startup.el} file.
4231 @node Using function keys under X, Working with function and arrow keys, Terminal setup code works after Emacs has begun, Key bindings
4232 @section How do I use function keys under X?
4233 @cindex Function keys
4234 @cindex X Window System and function keys
4235 @cindex Binding function keys
4237 With Emacs 19, functions keys under X are bound like any other key. @xref{Binding keys to commands}, for details.
4239 @node Working with function and arrow keys, X key translations for Emacs, Using function keys under X, Key bindings
4240 @section How do I tell what characters or symbols my function or arrow keys emit?
4241 @cindex Working with arrow keys
4242 @cindex Arrow keys, symbols generated by
4243 @cindex Working with function keys
4244 @cindex Function keys, symbols generated by
4245 @cindex Symbols generated by function keys
4247 Type @kbd{C-h c} then the function or arrow keys. The command will
4248 return either a function key symbol or character sequence (see the
4249 Emacs on-line documentation for an explanation). This works for other
4252 @node X key translations for Emacs, Handling C-s and C-q with flow control, Working with function and arrow keys, Key bindings
4253 @section How do I set the X key ``translations'' for Emacs?
4254 @cindex X key translations
4255 @cindex Key translations under X
4256 @cindex Translations for keys under X
4258 Emacs is not written using the Xt library by default, so there are no
4259 ``translations'' to be set. (We aren't sure how to set such translations
4260 if you do build Emacs with Xt; please let us know if you've done this!)
4262 The only way to affect the behavior of keys within Emacs is through
4263 @code{xmodmap} (outside Emacs) or @code{define-key} (inside Emacs). The
4264 @code{define-key} command should be used in conjunction with the
4265 @code{function-key-map} map. For instance,
4268 (define-key function-key-map [M-@key{TAB}] [?\M-\t])
4272 defines the @kbd{M-@key{TAB}} key sequence.
4274 @node Handling C-s and C-q with flow control, Binding C-s and C-q, X key translations for Emacs, Key bindings
4275 @section How do I handle @kbd{C-s} and @kbd{C-q} being used for flow control?
4276 @cindex Flow control, @kbd{C-s} and @kbd{C-q} with
4277 @cindex @kbd{C-s} and @kbd{C-q} with flow control
4279 @kbd{C-s} and @kbd{C-q} are used in the XON/XOFF flow control protocol.
4280 This messes things up when you're using Emacs over a serial line,
4281 because Emacs binds these keys to commands by default. Because Emacs
4282 won't honor them as flow control characters, too many of these
4283 characters are not passed on and overwhelm output buffers. Sometimes,
4284 intermediate software using XON/XOFF flow control will prevent Emacs
4285 from ever seeing @kbd{C-s} and @kbd{C-q}.
4292 Disable the use of @kbd{C-s} and @kbd{C-q} for flow control.
4294 You need to determine the cause of the flow control.
4301 Your terminal may use XON/XOFF flow control to have time to display
4302 all the characters it receives. For example, VT series terminals do
4303 this. It may be possible to turn this off from a setup menu. For
4304 example, on a VT220 you may select ``No XOFF'' in the setup menu. This
4305 is also true for some terminal emulation programs on PCs.
4307 When you turn off flow control at the terminal, you will also need to
4308 turn it off at the other end, which might be at the computer you are
4309 logged in to or at some terminal server in between.
4311 If you turn off flow control, characters may be lost; using a printer
4312 connected to the terminal may fail. You may be able to get around
4313 this problem by modifying the @samp{termcap} entry for your terminal to
4314 include extra NUL padding characters.
4319 If you are using a dialup connection, the modems may be using
4320 XON/XOFF flow control. It's not clear how to get around this.
4323 a router or terminal server
4325 Some network box between the terminal and your computer may be using
4326 XON/XOFF flow control. It may be possible to make it use some other
4327 kind of flow control. You will probably have to ask your local
4328 network experts for help with this.
4331 @code{tty} and/or @code{pty} devices
4333 If your connection to Emacs goes through multiple @code{tty} and/or
4334 @code{pty} devices, they may be using XON/XOFF flow control even when it
4337 @email{eirik@@theory.tn.cornell.edu, Eirik Fuller} writes:
4340 Some versions of @code{rlogin} (and possibly @code{telnet}) do not pass
4341 flow control characters to the remote system to which they connect. On
4342 such systems, Emacs on the remote system cannot disable flow control on
4343 the local system. Sometimes @samp{rlogin -8} will avoid this problem.
4345 One way to cure this is to disable flow control on the local host (the
4346 one running @code{rlogin}, not the one running @code{rlogind}) using the
4347 @code{stty} command, before starting the @code{rlogin} process. On many
4348 systems, @samp{stty start u stop u} will do this.
4350 Some versions of @samp{tcsh} will prevent even this from working. One
4351 way around this is to start another shell before starting rlogin,
4352 and issue the @samp{stty} command to disable flow control from that shell.
4355 Use @samp{stty -ixon} instead of @samp{stty start u stop u} on some systems.
4360 Make Emacs speak the XON/XOFF flow control protocol.
4362 You can make Emacs treat @kbd{C-s} and @kbd{C-q} as flow control characters by
4366 (enable-flow-control)
4370 to unconditionally enable flow control or
4373 (enable-flow-control-on "vt100" "h19")
4377 (using your terminal names instead of @samp{vt100} or @samp{h19}) to
4378 enable selectively. These commands will automatically swap @kbd{C-s}
4379 and @kbd{C-q} to @kbd{C-\} and @kbd{C-^}. Variables can be used to
4380 change the default swap keys (@code{flow-control-c-s-replacement} and
4381 @code{flow-control-c-q-replacement}).
4383 If you are fixing this for yourself, simply put the form in your
4384 @file{.emacs} file. If you are fixing this for your entire site, the
4385 best place to put it is in the @file{site-lisp/site-start.el} file.
4386 (Here @file{site-lisp} is actually a subdirectory of your Emacs
4387 installation directory, typically @file{/usr/local/share/emacs}.)
4388 Putting this form in @file{site-lisp/default.el} has the problem that
4389 if the user's @file{.emacs} file has an error, this will prevent
4390 @file{default.el} from being loaded and Emacs may be unusable for the
4391 user, even for correcting their @file{.emacs} file (unless they're
4392 smart enough to move it to another name).
4394 @code{enable-flow-control} can be invoked interactively as well:
4395 @kbd{M-x enable-flow-control @key{RET}}.
4399 For further discussion of this issue, read the file @file{etc/PROBLEMS}
4400 (in the Emacs source directory when you unpack the Emacs distribution).
4402 @node Binding C-s and C-q, Backspace invokes help, Handling C-s and C-q with flow control, Key bindings
4403 @section How do I bind @kbd{C-s} and @kbd{C-q} (or any key) if these keys are filtered out?
4404 @cindex Binding @kbd{C-s} and @kbd{C-q}
4405 @cindex @kbd{C-s} and @kbd{C-q}, binding
4407 To bind @kbd{C-s} and @kbd{C-q}, use either @code{enable-flow-control}
4408 or @code{enable-flow-control-on}. @xref{Handling C-s and C-q with flow
4409 control}, for usage and implementation details.
4411 To bind other keys, use @code{keyboard-translate}. @xref{Swapping
4412 keys}, for usage details. To do this for an entire site, you should
4413 swap the keys in @file{site-lisp/site-start.el}. @xref{Handling C-s
4414 and C-q with flow control}, for an explanation of why
4415 @file{site-lisp/default.el} should not be used.
4420 If you do this for an entire site, the users will be confused by
4421 the disparity between what the documentation says and how Emacs
4426 @node Backspace invokes help, stty and Backspace key, Binding C-s and C-q, Key bindings
4427 @section Why does the @key{Backspace} key invoke help?
4428 @cindex Backspace key invokes help
4429 @cindex Help invoked by Backspace
4430 @cindex DEL key does not delete
4432 The @key{Backspace} key (on most keyboards) generates @acronym{ASCII} code 8.
4433 @kbd{C-h} sends the same code. In Emacs by default @kbd{C-h} invokes
4434 help-command. This is intended to be easy to remember since the first
4435 letter of @samp{help} is @samp{h}. The easiest solution to this problem
4436 is to use @kbd{C-h} (and @key{Backspace}) for help and @key{DEL} (the
4437 @key{Delete} key) for deleting the previous character.
4439 For many people this solution may be problematic:
4444 They normally use @key{Backspace} outside of Emacs for deleting the
4445 previous character. This can be solved by making @key{DEL} the command
4446 for deleting the previous character outside of Emacs. On many Unix
4447 systems, this command will remap @key{DEL}:
4454 The user may prefer the @key{Backspace} key for deleting the
4455 previous character because it is more conveniently located on their
4456 keyboard or because they don't even have a separate @key{Delete} key.
4457 In this case, the @key{Backspace} key should be made to behave like
4458 @key{Delete}. There are several methods.
4462 Some terminals (e.g., VT3## terminals) and terminal emulators (e.g.,
4463 TeraTerm) allow the character generated by the @key{Backspace} key to be
4464 changed from a setup menu.
4467 You may be able to get a keyboard that is completely programmable, or a
4468 terminal emulator that supports remapping of any key to any other key.
4471 With Emacs 21.1 and later, you can control the effect of the
4472 @key{Backspace} and @key{Delete} keys, on both dumb terminals and a
4473 windowed displays, by customizing the option
4474 @code{normal-erase-is-backspace-mode}, or by invoking @kbd{M-x
4475 normal-erase-is-backspace}. See the documentation of these symbols
4476 (@pxref{Emacs Lisp documentation}) for more info.
4479 It is possible to swap the @key{Backspace} and @key{DEL} keys inside
4483 (keyboard-translate ?\C-h ?\C-?)
4487 This is the recommended method of forcing @key{Backspace} to act as
4488 @key{DEL}, because it works even in modes which bind @key{DEL} to
4489 something other than @code{delete-backward-char}.
4491 Similarly, you could remap @key{DEL} to act as @kbd{C-d}, which by
4492 default deletes forward:
4495 (keyboard-translate ?\C-? ?\C-d)
4498 @xref{Swapping keys}, for further details about @code{keyboard-translate}.
4501 Another approach is to switch key bindings and put help on @kbd{C-x h}
4505 (global-set-key "\C-h" 'delete-backward-char)
4507 ;;; overrides mark-whole-buffer
4508 (global-set-key "\C-xh" 'help-command)
4512 This method is not recommended, though: it only solves the problem for
4513 those modes which bind @key{DEL} to @code{delete-backward-char}. Modes
4514 which bind @key{DEL} to something else, such as @code{view-mode}, will
4515 not work as you expect when you press the @key{Backspace} key. For this
4516 reason, we recommend the @code{keyboard-translate} method, shown
4519 Other popular key bindings for help are @kbd{M-?} and @kbd{C-x ?}.
4522 Don't try to bind @key{DEL} to @code{help-command}, because there are
4523 many modes that have local bindings of @key{DEL} that will interfere.
4527 When Emacs 21 or later runs on a windowed display, it binds the
4528 @key{Delete} key to a command which deletes the character at point, to
4529 make Emacs more consistent with keyboard operation on these systems.
4531 For more information about troubleshooting this problem, see @ref{DEL
4532 Does Not Delete, , If @key{DEL} Fails to Delete, emacs, The GNU Emacs
4535 @node stty and Backspace key, Swapping keys, Backspace invokes help, Key bindings
4536 @section Why doesn't Emacs look at the @file{stty} settings for @key{Backspace} vs. @key{Delete}?
4537 @cindex @file{stty} and Emacs
4538 @cindex Backspace and @file{stty}
4539 @cindex Delete and @file{stty}
4543 @c FIXME: RMS explained the reasons for this on emacs-hackers. It's
4544 @c probably worth putting that explanation here.
4546 @node Swapping keys, Producing C-XXX with the keyboard, stty and Backspace key, Key bindings
4547 @section How do I swap two keys?
4548 @cindex Swapping keys
4549 @cindex Keys, swapping
4550 @cindex @code{keyboard-translate}
4552 You can swap two keys (or key sequences) by using the
4553 @code{keyboard-translate} function. For example, to turn @kbd{C-h}
4554 into @key{DEL} and @key{DEL} to @kbd{C-h}, use
4557 (keyboard-translate ?\C-h ?\C-?) ; translate `C-h' to DEL
4558 (keyboard-translate ?\C-? ?\C-h) ; translate DEL to `C-h'.
4562 The first key sequence of the pair after the function identifies what is
4563 produced by the keyboard; the second, what is matched for in the
4566 However, in the specific case of @kbd{C-h} and @key{DEL}, you should
4567 toggle @code{normal-erase-is-backspace-mode} instead of calling
4568 @code{keyboard-translate}. @inforef{DEL Does Not Delete, DEL Does Not Delete,
4571 Keyboard translations are not the same as key bindings in keymaps.
4572 Emacs contains numerous keymaps that apply in different situations, but
4573 there is only one set of keyboard translations, and it applies to every
4574 character that Emacs reads from the terminal. Keyboard translations
4575 take place at the lowest level of input processing; the keys that are
4576 looked up in keymaps contain the characters that result from keyboard
4579 @node Producing C-XXX with the keyboard, No Meta key, Swapping keys, Key bindings
4580 @section How do I produce C-XXX with my keyboard?
4581 @cindex Producing control characters
4582 @cindex Generating control characters
4583 @cindex Control characters, generating
4585 On terminals (but not under X), some common ``aliases'' are:
4589 @item @kbd{C-2} or @kbd{C-@key{SPC}}
4595 @item @kbd{C-7} or @kbd{C-S--}
4609 Often other aliases exist; use the @kbd{C-h c} command and try
4610 @key{CTRL} with all of the digits on your keyboard to see what gets
4611 generated. You can also try the @kbd{C-h w} command if you know the
4612 name of the command.
4614 @node No Meta key, No Escape key, Producing C-XXX with the keyboard, Key bindings
4615 @section What if I don't have a @key{Meta} key?
4616 @cindex No @key{Meta} key
4617 @cindex @key{Meta} key, what to do if you lack it
4619 On many keyboards, the @key{Alt} key acts as @key{Meta}, so try it.
4621 Instead of typing @kbd{M-a}, you can type @kbd{@key{ESC} a}. In fact,
4622 Emacs converts @kbd{M-a} internally into @kbd{@key{ESC} a} anyway
4623 (depending on the value of @code{meta-prefix-char}). Note that you
4624 press @key{Meta} and @key{a} together, but with @key{ESC}, you press
4625 @key{ESC}, release it, and then press @key{a}.
4627 @node No Escape key, Compose Character, No Meta key, Key bindings
4628 @section What if I don't have an @key{Escape} key?
4629 @cindex No Escape key
4630 @cindex Lacking an Escape key
4631 @cindex Escape key, lacking
4633 Type @kbd{C-[} instead. This should send @acronym{ASCII} code 27 just like an
4634 Escape key would. @kbd{C-3} may also work on some terminal (but not
4635 under X). For many terminals (notably DEC terminals) @key{F11}
4636 generates @key{ESC}. If not, the following form can be used to bind it:
4639 ;;; F11 is the documented ESC replacement on DEC terminals.
4640 (define-key function-key-map [f11] [?\e])
4643 @node Compose Character, Binding combinations of modifiers and function keys, No Escape key, Key bindings
4644 @section Can I make my @key{Compose Character} key behave like a @key{Meta} key?
4645 @cindex @key{Compose Character} key, using as @key{Meta}
4646 @cindex @key{Meta}, using @key{Compose Character} for
4648 On a dumb terminal such as a VT220, no. It is rumored that certain
4649 VT220 clones could have their @key{Compose} key configured this way. If
4650 you're using X, you might be able to do this with the @code{xmodmap}
4653 @node Binding combinations of modifiers and function keys, Meta key does not work in xterm, Compose Character, Key bindings
4654 @section How do I bind a combination of modifier key and function key?
4655 @cindex Modifiers and function keys
4656 @cindex Function keys and modifiers
4657 @cindex Binding modifiers and function keys
4659 With Emacs 19 and later, you can represent modified function keys in
4660 vector format by adding prefixes to the function key symbol. For
4661 example (from the on-line documentation):
4664 (global-set-key [?\C-x right] 'forward-page)
4668 where @samp{?\C-x} is the Lisp character constant for the character @kbd{C-x}.
4670 You can use the modifier keys @key{Control}, @key{Meta}, @key{Hyper},
4671 @key{Super}, @key{Alt}, and @key{Shift} with function keys. To
4672 represent these modifiers, prepend the strings @samp{C-}, @samp{M-},
4673 @samp{H-}, @samp{s-}, @samp{A-}, and @samp{S-} to the symbol name. Here
4674 is how to make @kbd{H-M-RIGHT} move forward a word:
4677 (global-set-key [H-M-right] 'forward-word)
4683 Not all modifiers are permitted in all situations. @key{Hyper},
4684 @key{Super}, and @key{Alt} are not available on Unix character
4685 terminals. Non-@acronym{ASCII} keys and mouse events (e.g. @kbd{C-=} and
4686 @kbd{Mouse-1}) also fall under this category.
4690 @xref{Binding keys to commands}, for general key binding instructions.
4692 @node Meta key does not work in xterm, ExtendChar key does not work as Meta, Binding combinations of modifiers and function keys, Key bindings
4693 @section Why doesn't my @key{Meta} key work in an @code{xterm} window?
4694 @cindex @key{Meta} key and @code{xterm}
4695 @cindex Xterm and @key{Meta} key
4697 @inforef{Unibyte Mode, Single-Byte Character Set Support, emacs}.
4699 If the advice in the Emacs manual fails, try all of these methods before
4700 asking for further help:
4705 You may have big problems using @code{mwm} as your window manager.
4706 (Does anyone know a good generic solution to allow the use of the
4707 @key{Meta} key in Emacs with @file{mwm}?)
4710 For X11: Make sure it really is a @key{Meta} key. Use @code{xev} to
4711 find out what keysym your @key{Meta} key generates. It should be either
4712 @code{Meta_L} or @code{Meta_R}. If it isn't, use @file{xmodmap} to fix
4713 the situation. If @key{Meta} does generate @code{Meta_L} or
4714 @code{Meta_R}, but @kbd{M-x} produces a non-@acronym{ASCII} character, put this in
4715 your @file{~/.Xdefaults} file:
4718 XTerm*eightBitInput: false
4719 XTerm*eightBitOutput: true
4723 Make sure the @code{pty} the @code{xterm} is using is passing 8 bit
4724 characters. @samp{stty -a} (or @samp{stty everything}) should show
4725 @samp{cs8} somewhere. If it shows @samp{cs7} instead, use @samp{stty
4726 cs8 -istrip} (or @samp{stty pass8}) to fix it.
4729 If there is an @code{rlogin} connection between @code{xterm} and Emacs, the
4730 @samp{-8} argument may need to be given to rlogin to make it pass all 8 bits
4734 If Emacs is running on Ultrix, it is reported that evaluating
4735 @code{(set-input-mode t nil)} helps.
4738 If all else fails, you can make @code{xterm} generate @kbd{@key{ESC} W} when
4739 you type @kbd{M-W}, which is the same conversion Emacs would make if it
4740 got the @kbd{M-W} anyway. In X11R4, the following resource
4741 specification will do this:
4744 XTerm.VT100.EightBitInput: false
4748 (This changes the behavior of the @code{insert-eight-bit} action.)
4750 With older @code{xterm}s, you can specify this behavior with a translation:
4753 XTerm.VT100.Translations: #override \
4754 Meta<KeyPress>: string(0x1b) insert()
4758 You might have to replace @samp{Meta} with @samp{Alt}.
4762 @node ExtendChar key does not work as Meta, SPC no longer completes file names, Meta key does not work in xterm, Key bindings
4763 @section Why doesn't my @key{ExtendChar} key work as a @key{Meta} key under HP-UX 8.0 and 9.x?
4764 @cindex @key{ExtendChar} key as @key{Meta}
4765 @cindex @key{Meta}, using @key{ExtendChar} for
4766 @cindex HP-UX, the @key{ExtendChar} key
4768 This is a result of an internationalization extension in X11R4 and the
4769 fact that HP is now using this extension. Emacs assumes that the
4770 @code{XLookupString} function returns the same result regardless of the
4771 @key{Meta} key state which is no longer necessarily true. Until Emacs
4772 is fixed, the temporary kludge is to run this command after each time
4773 the X server is started but preferably before any xterm clients are:
4776 xmodmap -e 'remove mod1 = Mode_switch'
4779 @c FIXME: Emacs 21 supports I18N in X11; does that mean that this bug is
4782 This will disable the use of the extra keysyms systemwide, which may be
4783 undesirable if you actually intend to use them.
4785 @node SPC no longer completes file names, , ExtendChar key does not work as Meta, Key bindings
4786 @section Why doesn't SPC complete file names anymore?
4787 @cindex @kbd{SPC} file name completion
4789 Starting with Emacs 22.1, @kbd{SPC} no longer completes file names in
4790 the minibuffer, so that file names with embedded spaces could be typed
4791 without the need to quote the spaces.
4793 You can get the old behavior by binding @kbd{SPC} to
4794 @code{minibuffer-complete-word} in the minibuffer, as follows:
4797 (define-key minibuffer-local-filename-completion-map (kbd "SPC")
4798 'minibuffer-complete-word)
4800 (define-key minibuffer-local-must-match-filename-map (kbd "SPC")
4801 'minibuffer-complete-word)
4804 @c ------------------------------------------------------------
4805 @node Alternate character sets, Mail and news, Key bindings, Top
4806 @chapter Alternate character sets
4807 @cindex Alternate character sets
4810 * Emacs does not display 8-bit characters::
4811 * Inputting eight-bit characters::
4812 * Kanji and Chinese characters::
4813 * Right-to-left alphabets::
4816 @node Emacs does not display 8-bit characters, Inputting eight-bit characters, Alternate character sets, Alternate character sets
4817 @section How do I make Emacs display 8-bit characters?
4818 @cindex Displaying eight-bit characters
4819 @cindex Eight-bit characters, displaying
4821 @inforef{Unibyte Mode, Single-byte Character Set
4822 Support, emacs}. On a Unix, when Emacs runs on a text-only terminal
4823 display or is invoked with @samp{emacs -nw}, you typically need to use
4824 @code{set-terminal-coding-system} to tell Emacs what the terminal can
4825 display, even after setting the language environment; otherwise
4826 non-@acronym{ASCII} characters will display as @samp{?}. On other operating
4827 systems, such as MS-DOS and MS-Windows, Emacs queries the OS about the
4828 character set supported by the display, and sets up the required
4829 terminal coding system automatically.
4831 @node Inputting eight-bit characters, Kanji and Chinese characters, Emacs does not display 8-bit characters, Alternate character sets
4832 @section How do I input eight-bit characters?
4833 @cindex Entering eight-bit characters
4834 @cindex Eight-bit characters, entering
4835 @cindex Input, 8-bit characters
4837 Various methods are available for input of eight-bit characters. See
4838 @inforef{Unibyte Mode, Single-byte Character Set
4839 Support, emacs}. For more sophisticated methods, @inforef{Input
4840 Methods, Input Methods, emacs}.
4842 @node Kanji and Chinese characters, Right-to-left alphabets, Inputting eight-bit characters, Alternate character sets
4843 @section Where can I get an Emacs that handles kanji, Chinese, or other Far-Eastern character sets?
4844 @cindex Kanji, handling with Emacs
4845 @cindex Chinese, handling with Emacs
4846 @cindex Japanese, handling with Emacs
4847 @cindex Korean, handling with Emacs
4849 Emacs 20 and later includes many of the features of MULE, the MULtilingual
4850 Enhancement to Emacs. @xref{Installing Emacs}, for information on where
4851 to find and download the latest version of Emacs.
4853 @node Right-to-left alphabets, , Kanji and Chinese characters, Alternate character sets
4854 @section Where is an Emacs that can handle Semitic (right-to-left) alphabets?
4855 @cindex Right-to-left alphabets
4856 @cindex Hebrew, handling with Emacs
4857 @cindex Semitic alphabets
4858 @cindex Arabic alphabets
4860 Emacs 20 and later supports Hebrew characters (ISO 8859-8), but does not
4861 yet support right-to-left character entry and display.
4863 @email{joel@@exc.com, Joel M. Hoffman} has written a Lisp package called
4864 @file{hebrew.el} that allows right-to-left editing of Hebrew. It
4865 reportedly works out of the box with Emacs 19, but requires patches for
4866 Emacs 18. Write to Joel if you want the patches or package.
4868 @c FIXME: Should we mention Ehud Karni's package?
4870 @file{hebrew.el} requires a Hebrew screen font, but no other hardware support.
4871 Joel has a screen font for PCs running MS-DOS or GNU/Linux.
4873 You might also try to query archie for files named with @file{hebrew};
4874 several ftp sites in Israel may also have the necessary files.
4876 @c ------------------------------------------------------------
4877 @node Mail and news, Concept index, Alternate character sets, Top
4878 @chapter Mail and news
4879 @cindex Mail and news
4882 * Changing the included text prefix::
4883 * Saving a copy of outgoing mail::
4884 * Expanding aliases when sending mail::
4885 * Rmail thinks all messages are one big one::
4886 * Sorting the messages in an Rmail folder::
4887 * Rmail writes to /usr/spool/mail::
4888 * Recovering mail files when Rmail munges them::
4889 * Replying to the sender of a message::
4890 * MIME with Emacs mail packages::
4891 * Automatically starting a mail or news reader::
4892 * Reading news with Emacs::
4893 * Gnus does not work with NNTP::
4894 * Viewing articles with embedded underlining::
4895 * Saving a multi-part Gnus posting::
4896 * Starting Gnus faster::
4897 * Catching up in all newsgroups::
4898 * Killing based on nonstandard headers::
4899 * Removing flashing messages::
4900 * Catch-up is slow in Gnus::
4901 * Gnus hangs for a long time::
4902 * Learning more about Gnus::
4905 @node Changing the included text prefix, Saving a copy of outgoing mail, Mail and news, Mail and news
4906 @section How do I change the included text prefix in mail/news followups?
4907 @cindex Prefix in mail/news followups, changing
4908 @cindex Included text prefix, changing
4909 @cindex Setting the included text character
4910 @cindex Quoting in mail messages
4912 If you read mail with Rmail or news with Gnus, set the variable
4913 @code{mail-yank-prefix}. For VM, set @code{vm-included-text-prefix}.
4914 For mh-e, set @code{mh-ins-buf-prefix}.
4916 For fancier control of citations, use Supercite. @xref{Supercite}.
4918 To prevent Emacs from including various headers of the replied-to
4919 message, set the value of @code{mail-yank-ignored-headers} to an
4922 @node Saving a copy of outgoing mail, Expanding aliases when sending mail, Changing the included text prefix, Mail and news
4923 @section How do I save a copy of outgoing mail?
4924 @cindex Saving a copy of outgoing mail
4925 @cindex Copying outgoing mail to a file
4926 @cindex Filing outgoing mail
4927 @cindex Automatic filing of outgoing mail
4928 @cindex Mail, saving outgoing automatically
4930 You can either mail yourself a copy by including a @samp{BCC} header in the
4931 mail message, or store a copy of the message directly to a file by
4932 including an @samp{FCC} header.
4934 If you use standard mail, you can automatically create a @samp{BCC} to
4938 (setq mail-self-blind t)
4942 in your @file{.emacs} file. You can automatically include an @samp{FCC}
4943 field by putting something like the following in your @file{.emacs}
4947 (setq mail-archive-file-name (expand-file-name "~/outgoing"))
4950 The output file will be in Unix mail format, which can be read directly
4951 by VM, but not always by Rmail. @xref{Learning how to do something}.
4953 If you use @code{mh-e}, add an @samp{FCC} or @samp{BCC} field to your
4956 It does not work to put @samp{set record filename} in the @file{.mailrc}
4959 @node Expanding aliases when sending mail, Rmail thinks all messages are one big one, Saving a copy of outgoing mail, Mail and news
4960 @section Why doesn't Emacs expand my aliases when sending mail?
4961 @cindex Expanding aliases when sending mail
4962 @cindex Mail alias expansion
4963 @cindex Sending mail with aliases
4968 You must separate multiple addresses in the headers of the mail buffer
4969 with commas. This is because Emacs supports RFC822 standard addresses
4973 To: Willy Smith <wks@@xpnsv.lwyrs.com>
4976 However, you do not need to---and probably should not, unless your
4977 system's version of @file{/usr/ucb/mail} (a.k.a.@: @code{mailx})
4978 supports RFC822---separate addresses with commas in your
4979 @file{~/.mailrc} file.
4982 Emacs normally only reads the @file{.mailrc} file once per session,
4983 when you start to compose your first mail message. If you edit
4984 @file{.mailrc}, you can type @kbd{M-x rebuild-mail-abbrevs @key{RET}} to
4985 make Emacs reread @file{~/.mailrc}.
4988 If you like, you can expand mail aliases as abbrevs, as soon as you
4989 type them in. To enable this feature, execute the following:
4992 (add-hook 'mail-mode-hook 'mail-abbrevs-setup)
4995 Note that the aliases are expanded automatically only after you type
4996 @key{RET} or a punctuation character (e.g. @kbd{,}). You can force their
4997 expansion by moving point to the end of the alias and typing @kbd{C-x a e}
4998 (@kbd{M-x expand-abbrev}).
5001 @node Rmail thinks all messages are one big one, Sorting the messages in an Rmail folder, Expanding aliases when sending mail, Mail and news
5002 @section Why does Rmail think all my saved messages are one big message?
5003 @cindex Rmail thinks all messages are one large message
5005 A file created through the @samp{FCC} field in a message is in Unix mail
5006 format, not the format that Rmail uses (BABYL format). Rmail will try
5007 to convert a Unix mail file into BABYL format on input, but sometimes it
5008 makes errors. For guaranteed safety, you can make the
5009 @file{saved-messages} file be an inbox for your Rmail file by using the
5010 function @code{set-rmail-inbox-list}.
5012 @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
5013 @section How can I sort the messages in my Rmail folder?
5014 @cindex Rmail, sorting messages in
5015 @cindex Folder, sorting messages in an Rmail
5016 @cindex Sorting messages in an Rmail folder
5018 In Rmail, type @kbd{C-c C-s C-h} to get a list of sorting functions
5019 and their key bindings.
5021 @node Rmail writes to /usr/spool/mail, Recovering mail files when Rmail munges them, Sorting the messages in an Rmail folder, Mail and news
5022 @section Why does Rmail need to write to @file{/usr/spool/mail}?
5023 @cindex Rmail and @file{/usr/spool/mail}
5024 @cindex @file{/usr/spool/mail} and Rmail
5026 This is the behavior of the @code{movemail} program which Rmail uses.
5027 This indicates that @code{movemail} is configured to use lock files.
5032 Certain systems require lock files to interlock access to mail files.
5033 On these systems, @code{movemail} must write lock files, or you risk losing
5034 mail. You simply must arrange to let @code{movemail} write them.
5036 Other systems use the @code{flock} system call to interlock access. On
5037 these systems, you should configure @code{movemail} to use @code{flock}.
5040 @node Recovering mail files when Rmail munges them, Replying to the sender of a message, Rmail writes to /usr/spool/mail, Mail and news
5041 @section How do I recover my mail files after Rmail munges their format?
5042 @cindex Recovering munged mail files
5043 @cindex Rmail munged my files
5044 @cindex Mail files, recovering those munged by Rmail
5046 If you have just done @kbd{M-x rmail-input} on a file and you don't want
5047 to save it in Rmail's format (called BABYL), just kill the buffer (with
5050 @cindex Exporting messages as Unix mail files
5051 If you typed @kbd{M-x rmail} and it read some messages out of your inbox
5052 and you want to put them in a Unix mail file, use @kbd{C-o} on each
5055 @cindex Converting from BABYL to Unix mail format
5056 @cindex @code{unrmail} command
5057 If you want to convert an existing file from BABYL format to Unix mail
5058 format, use the command @kbd{M-x unrmail}: it will prompt you for the
5059 input and output file names.
5062 Alternatively, you could use the @code{b2m} program supplied with
5063 Emacs. @code{b2m} is a filter, and is used like this:
5066 b2m < @var{babyl-file} > @var{mbox-file}
5070 where @var{babyl-file} is the name of the BABYL file, and
5071 @var{mbox-file} is the name of the file where the converted mail will
5074 @node Replying to the sender of a message, MIME with Emacs mail packages, Recovering mail files when Rmail munges them, Mail and news
5075 @section How can I force Rmail to reply to the sender of a message, but not the other recipients?
5076 @cindex Replying only to the sender of a message
5077 @cindex Sender, replying only to
5078 @cindex Rmail, replying to the sender of a message in
5080 @email{isaacson@@seas.upenn.edu, Ron Isaacson} says: When you hit
5081 @key{r} to reply in Rmail, by default it CCs all of the original
5082 recipients (everyone on the original @samp{To} and @samp{CC}
5083 lists). With a prefix argument (i.e., typing @kbd{C-u} before @key{r}),
5084 it replies only to the sender. However, going through the whole
5085 @kbd{C-u} business every time you want to reply is a pain. This is the
5086 best fix I've been able to come up with:
5089 (defun rmail-reply-t ()
5090 "Reply only to the sender of the current message. (See rmail-reply.)"
5094 (add-hook 'rmail-mode-hook
5096 (define-key rmail-mode-map "r" 'rmail-reply-t)
5097 (define-key rmail-mode-map "R" 'rmail-reply)))
5100 @node MIME with Emacs mail packages, Automatically starting a mail or news reader, Replying to the sender of a message, Mail and news
5101 @section How can I get my favorite Emacs mail package to support MIME?
5102 @cindex MIME and Emacs mail packages
5103 @cindex Mail packages and MIME
5104 @cindex FAQ for MIME and Emacs
5106 Version 6.x of VM supports MIME. @xref{VM}. Gnus supports MIME in mail
5107 and news messages as of version 5.8.1 (Pterodactyl). Rmail has limited
5108 support for single-part MIME messages beginning with Emacs 20.3.
5110 @node Automatically starting a mail or news reader, Reading news with Emacs, MIME with Emacs mail packages, Mail and news
5111 @section How do I make Emacs automatically start my mail/news reader?
5112 @cindex Mail reader, starting automatically
5113 @cindex News reader, starting automatically
5114 @cindex Starting mail/news reader automatically
5116 To start Emacs in Gnus:
5129 A more convenient way to start with Gnus:
5132 alias gnus 'emacs -f gnus'
5136 It is probably unwise to automatically start your mail or news reader
5137 from your @file{.emacs} file. This would cause problems if you needed to run
5138 two copies of Emacs at the same time. Also, this would make it difficult for
5139 you to start Emacs quickly when you needed to.
5141 @node Reading news with Emacs, Gnus does not work with NNTP, Automatically starting a mail or news reader, Mail and news
5142 @section How do I read news under Emacs?
5143 @cindex Reading news under Emacs
5144 @cindex Usenet reader in Emacs
5145 @cindex Gnus newsreader
5147 Use @kbd{M-x gnus}. It is documented in Info (@pxref{Learning how to do
5150 @node Gnus does not work with NNTP, Viewing articles with embedded underlining, Reading news with Emacs, Mail and news
5151 @section Why doesn't Gnus work via NNTP?
5152 @cindex Gnus and NNTP
5153 @cindex NNTP, Gnus fails to work with
5155 There is a bug in NNTP version 1.5.10, such that when multiple requests
5156 are sent to the NNTP server, the server only handles the first one
5157 before blocking waiting for more input which never comes. NNTP version
5158 1.5.11 claims to fix this.
5160 You can work around the bug inside Emacs like this:
5163 (setq nntp-maximum-request 1)
5166 You can find out what version of NNTP your news server is running by
5167 telnetting to the NNTP port (usually 119) on the news server machine
5168 (i.e., @kbd{telnet server-machine 119}). The server should give its
5169 version number in the welcome message. Type @kbd{quit} to get out.
5171 @xref{Spontaneous entry into isearch-mode}, for some additional ideas.
5173 @node Viewing articles with embedded underlining, Saving a multi-part Gnus posting, Gnus does not work with NNTP, Mail and news
5174 @section How do I view news articles with embedded underlining (e.g., ClariNews)?
5175 @cindex Underlining, embedded in news articles
5176 @cindex News articles with embedded underlining
5177 @cindex Embedded underlining in news articles
5179 Underlining appears like this:
5182 _^Hu_^Hn_^Hd_^He_^Hr_^Hl_^Hi_^Hn_^Hi_^Hn_^Hg
5185 @email{abraham@@dina.kvl.dk, Per Abrahamsen} suggests using the following
5186 code, which uses the underline face to turn such text into true
5187 underlining, inconjunction with Gnus:
5190 (defun gnus-article-prepare-overstrike ()
5191 ;; Prepare article for overstrike commands.
5193 (set-buffer gnus-article-buffer)
5194 (let ((buffer-read-only nil))
5195 (goto-char (point-min))
5196 (while (search-forward "\b" nil t)
5197 (let ((next (following-char))
5198 (previous (char-after (- (point) 2))))
5199 (cond ((eq next previous)
5200 (delete-region (- (point) 2) (point))
5201 (put-text-property (point) (1+ (point))
5204 (delete-region (1- (point)) (1+ (point)))
5205 (put-text-property (1- (point)) (point)
5208 (delete-region (- (point) 2) (point))
5209 (put-text-property (point) (1+ (point))
5210 'face 'underline))))))))
5212 (add-hook 'gnus-article-prepare-hook 'gnus-article-prepare-overstrike)
5215 Latest versions of Gnus do such a conversion automatically.
5217 If you prefer to do away with underlining altogether, you can
5218 destructively remove it with @kbd{M-x ununderline-region}; do this
5222 (add-hook 'gnus-article-prepare-hook
5223 (lambda () (ununderline-region (point-min) (point-max))))
5226 @node Saving a multi-part Gnus posting, Starting Gnus faster, Viewing articles with embedded underlining, Mail and news
5227 @section How do I save all the items of a multi-part posting in Gnus?
5228 @cindex Multi-part postings in Gnus, saving
5229 @cindex Saving multi-part postings in Gnus
5230 @cindex Gnus, saving multi-part postings in
5232 Use @code{gnus-uu}. Type @kbd{C-c C-v C-h} in the Gnus summary buffer
5233 to see a list of available commands.
5235 @node Starting Gnus faster, Catching up in all newsgroups, Saving a multi-part Gnus posting, Mail and news
5236 @section How do I make Gnus start up faster?
5237 @cindex Faster, starting Gnus
5238 @cindex Starting Gnus faster
5239 @cindex Gnus, starting faster
5241 From the Gnus FAQ (@pxref{Learning more about Gnus}):
5244 @email{pktiwari@@eos.ncsu.edu, Pranav Kumar Tiwari} writes: I posted
5245 the same query recently and I got an answer to it. I am going to
5246 repeat the answer. What you need is a newer version of gnus, version
5247 5.0.4+. I am using 5.0.12 and it works fine with me with the
5251 (setq gnus-check-new-newsgroups nil
5252 gnus-read-active-file 'some
5253 gnus-nov-is-evil nil
5254 gnus-select-method '(nntp gnus-nntp-server))
5258 @node Catching up in all newsgroups, Killing based on nonstandard headers, Starting Gnus faster, Mail and news
5259 @section How do I catch up all newsgroups in Gnus?
5260 @cindex Catching up all newsgroups in Gnus
5261 @cindex Gnus, Catching up all newsgroups in
5263 In the @file{*Newsgroup*} buffer, type @kbd{M-< C-x ( c y C-x ) M-0 C-x e}
5265 Leave off the initial @kbd{M-<} if you only want to catch up from point
5266 to the end of the @file{*Newsgroup*} buffer.
5268 @node Killing based on nonstandard headers, Removing flashing messages, Catching up in all newsgroups, Mail and news
5269 @section Why can't I kill in Gnus based on the Newsgroups/Keywords/Control headers?
5270 @cindex Killing articles based on nonstandard headers
5271 @cindex Newsgroups header, killing articles based on
5272 @cindex Keywords header, killing articles based on
5273 @cindex Control header, killing articles based on
5275 Gnus will complain that the @samp{Newsgroups}, @samp{Keywords}, and
5276 @samp{Control} headers are ``Unknown header'' fields.
5278 For the @samp{Newsgroups} header, there is an easy workaround: kill on the
5279 @samp{Xref} header instead, which will be present on any cross-posted article
5280 (as long as your site carries the cross-post group).
5282 If you really want to kill on one of these headers, you can do it like
5286 (gnus-kill nil "^Newsgroups: .*\\(bad\\.group\\|worse\\.group\\)")
5289 @node Removing flashing messages, Catch-up is slow in Gnus, Killing based on nonstandard headers, Mail and news
5290 @section How do I get rid of flashing messages in Gnus for slow connections?
5291 @cindex Flashing Gnus messages, removing
5292 @cindex Removing flashing Gnus messages
5293 @cindex Slow connections causing flashing messages in Gnus
5294 @cindex Gnus, flashing messages in
5296 Set @code{nntp-debug-read} to @code{nil}.
5298 @node Catch-up is slow in Gnus, Gnus hangs for a long time, Removing flashing messages, Mail and news
5299 @section Why is catch up slow in Gnus?
5300 @cindex Slow catch up in Gnus
5301 @cindex Gnus is slow when catching up
5302 @cindex Crosspostings make Gnus catching up slow
5304 Because Gnus is marking crosspostings read. You can control this with
5305 the variable @code{gnus-use-cross-reference}.
5307 @node Gnus hangs for a long time, Learning more about Gnus, Catch-up is slow in Gnus, Mail and news
5308 @section Why does Gnus hang for a long time when posting?
5309 @cindex Hangs in Gnus
5310 @cindex Gnus hangs while posting
5311 @cindex Posting, Gnus hangs wile
5313 @email{tale@@uunet.uu.net, David Lawrence} explains:
5316 The problem is almost always interaction between NNTP and C News. NNTP
5317 POST asks C News's @code{inews} to not background itself but rather hang
5318 around and give its exit status so it knows whether the post was successful.
5319 (That wait will on some systems not return the exit status of the
5320 waited for job is a different sort of problem.) It ends up taking a
5321 long time because @code{inews} is calling @code{relaynews}, which often
5322 waits for another @code{relaynews} to free the lock on the news system
5323 so it can file the article.
5325 My preferred solution is to change @code{inews} to not call
5326 @code{relaynews}, but rather use @code{newsspool}. This loses some
5327 error-catching functionality, but is for the most part safe as
5328 @code{inews} will detect a lot of the errors on its own. The C News
5329 folks have sped up @code{inews}, too, so speed should look better to
5330 most folks as that update propagates around.
5333 @node Learning more about Gnus, , Gnus hangs for a long time, Mail and news
5334 @section Where can I find out more about Gnus?
5335 @cindex FAQ for Gnus
5337 @cindex Learning more about Gnus
5339 For more information on Gnus, consult the Gnus manual and FAQ, which are
5340 part of the Gnus distribution.
5342 @node Concept index, , Mail and news, Top
5343 @unnumbered Concept Index
5350 arch-tag: fee0d62d-06cf-43d8-ac21-123408eaf10f