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