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