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