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