# HG changeset patch # User ben # Date 1107202132 0 # Node ID b7b90f750a78fe09f80fc2d7977613c323adfdbb # Parent 7edc33019aa40583fbdf8196de39d790006b5a96 [xemacs-hg @ 2005-01-31 20:08:32 by ben] Documentation updates GETTING.GNU.SOFTWARE, Makefile.in.in: Delete GETTING.GNU.SOFTWARE from SOURCES. PROBLEMS: Delete reference to check_cygwin_setup.sh. Delete stuff that is irrelevant, mislocated or woefully out-of-date. GNU, SERVICE: Delete. * ORDERS, ORDERS.EUROPE, ORDERS.JAPAN: Delete. * CHARSETS, CODINGS: Delete. * DEBUG, LPF, MORE.STUFF, MOTIVATION: Delete. aliases.ksh: Delete. (moved to xemacs-builds/steve) * README.HYPERBOLE, README.OO-BROWSER: Delete. * chr.png, chrm.png: Move to photos/. check_cygwin_setup.sh: Delete. * gnu.xpm, gnu.xbm, sink.xbm: Delete. * ms-kermit, ms-kermit-7bit: Delete. TERMS: Delete. * DISTRIB, FTP, MACHINES, MAILINGLISTS, PACKAGES: Delete and move to FAQ. BETA: Delete and move to man/beta.texi. README: Update. help.el: Removed. xemacs/help.texi: Delete references to DISTRIB. Point to FAQ. xemacs/new.texi: Update sample code for version checking. xemacs/xemacs.texi: Delete references to DISTRIB. Point directly to web site. Update stuff referring to GNU Emacs. Delete references to Win-Emacs. Makefile: Add beta.texi and built files. xemacs-faq.texi: Major overhaul of section 1. Add mailing list info, update downloading info, add info on CVS, etc. xemacs.mak: Also copy BUGS, README, COPYING and Installation. diff -r 7edc33019aa4 -r b7b90f750a78 etc/CHARSETS --- a/etc/CHARSETS Mon Jan 31 20:01:50 2005 +0000 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000 @@ -1,57 +0,0 @@ -######################### -## LIST OF CHARSETS -## Each line corresponds to one charset. -## The following attributes are listed in this order -## separated by a colon `:' in one line. -## CHARSET-SYMBOL-NAME, -## CHARSET-ID, -## DIMENSION (1 or 2) -## CHARS (94 or 96) -## BYTES (of multibyte form: 1, 2, 3, or 4), -## WIDTH (occupied column numbers: 1 or 2), -## DIRECTION (0:left-to-right, 1:right-to-left), -## ISO-FINAL-CHAR (character code of ISO-2022's final character) -## ISO-GRAPHIC-PLANE (ISO-2022's graphic plane, 0:GL, 1:GR) -## DESCRIPTION (describing string of the charset) -tibetan-1-column:241:2:94:4:1:0:56:0:Tibetan 1 column glyph -tibetan:252:2:94:4:2:0:55:0:Tibetan characters -lao:167:1:94:3:1:0:49:0:Lao characters (ISO10646 0E80..0EDF) -indian-1-column:240:2:94:4:1:0:54:0:Indian charset for 2-column width glyphs -indian-2-column:251:2:94:4:2:0:53:0:Indian charset for 2-column width glyphs -indian-is13194:225:1:94:3:2:0:53:1:Generic Indian charset for data exchange with IS 13194 -ascii-right-to-left:166:1:94:3:1:1:66:0:ASCII (left half of ISO8859-1) with right-to-left direction -chinese-cns11643-7:250:2:94:4:2:0:77:0:CNS11643 Plane 7 Chinese Traditional -chinese-cns11643-6:249:2:94:4:2:0:76:0:CNS11643 Plane 6 Chinese Traditional -chinese-cns11643-5:248:2:94:4:2:0:75:0:CNS11643 Plane 5 Chinese Traditional -chinese-cns11643-4:247:2:94:4:2:0:74:0:CNS11643 Plane 4 Chinese Traditional -chinese-cns11643-3:246:2:94:4:2:0:73:0:CNS11643 Plane 3 Chinese Traditional -ethiopic:245:2:94:4:2:0:51:0:Ethiopic characters -arabic-2-column:224:1:94:3:2:1:52:0:Arabic 2-column -arabic-1-column:165:1:94:3:1:1:51:0:Arabic 1-column -arabic-digit:164:1:94:3:1:0:50:0:Arabic digit -vietnamese-viscii-upper:163:1:96:3:1:0:50:1:VISCII1.1 upper-case -vietnamese-viscii-lower:162:1:96:3:1:0:49:1:VISCII1.1 lower-case -ipa:161:1:96:3:1:0:48:1:IPA (International Phonetic Association) -chinese-sisheng:160:1:94:3:1:0:48:0:SiSheng characters for PinYin/ZhuYin -chinese-big5-2:153:2:94:3:2:0:49:0:Big5 Level-2 Chinese traditional -chinese-big5-1:152:2:94:3:2:0:48:0:Big5 Level-1 Chinese traditional -chinese-cns11643-2:150:2:94:3:2:0:72:0:CNS11643 Plane 2 Chinese traditional -chinese-cns11643-1:149:2:94:3:2:0:71:0:CNS11643 Plane 1 Chinese traditional -japanese-jisx0212:148:2:94:3:2:0:68:0:JISX0212 Japanese supplement -korean-ksc5601:147:2:94:3:2:0:67:0:KSC5601 Korean Hangul and Hanja -japanese-jisx0208:146:2:94:3:2:0:66:0:JISX0208.1983/1990 Japanese Kanji -chinese-gb2312:145:2:94:3:2:0:65:0:GB2312 Chinese simplified -japanese-jisx0208-1978:144:2:94:3:2:0:64:0:JISX0208.1978 Japanese Kanji (so called "old JIS") -latin-iso8859-9:141:1:96:2:1:0:77:1:ISO8859-9 (Latin-5) -cyrillic-iso8859-5:140:1:96:2:1:0:76:1:ISO8859-5 (Cyrillic) -latin-jisx0201:138:1:94:2:1:0:74:0:JISX0201.1976 Japanese Roman -katakana-jisx0201:137:1:94:2:1:0:73:1:JISX0201.1976 Japanese Kana -hebrew-iso8859-8:136:1:96:2:1:1:72:1:ISO8859-8 (Hebrew) -arabic-iso8859-6:135:1:96:2:1:1:71:1:ISO8859-6 (Arabic) -greek-iso8859-7:134:1:96:2:1:0:70:1:ISO8859-7 (Greek) -thai-tis620:133:1:96:2:1:0:84:1:TIS620.2529 (Thai) -latin-iso8859-4:132:1:96:2:1:0:68:1:ISO8859-4 (Latin-4) -latin-iso8859-3:131:1:96:2:1:0:67:1:ISO8859-3 (Latin-3) -latin-iso8859-2:130:1:96:2:1:0:66:1:ISO8859-2 (Latin-2) -latin-iso8859-1:129:1:96:2:1:0:65:1:ISO8859-1 (Latin-1) -ascii:000:1:94:1:1:0:66:0:ASCII (ISO646 IRV) diff -r 7edc33019aa4 -r b7b90f750a78 etc/CODINGS --- a/etc/CODINGS Mon Jan 31 20:01:50 2005 +0000 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000 @@ -1,74 +0,0 @@ -######################### -## LIST OF CODING SYSTEMS -## Each line corresponds to one coding system -## Format of a line is: -## NAME:TYPE:MNEMONIC:EOL:FLAGS:DOCSTRING, -## where -## TYPE = nil (no conversion), t (auto conversion), -## 0 (Mule internal), 1 (SJIS), 2 (ISO2022), 3 (BIG5), or 4 (CCL) -## EOL = 0 (LF), 1 (CRLF), 2 (CR), or 3 (Automatic detection) -## FLAGS = -## if TYPE = 2 then -## comma (`,') separated data of the followings: -## G0, G1, G2, G3, SHORT-FORM, ASCII-EOL, ASCII-CNTL, SEVEN, -## LOCKING-SHIFT, SINGLE-SHIFT, USE-ROMAN, USE-OLDJIS, NO-ISO6429 -## else if TYPE = 4 then -## comma (`,') separated CCL programs for read and write -## else -## 0 -## -no-conversion:nil:=:0:0:Do no conversion -undecided:t:+:3:0:Detect coding-system automatically -hz:0:z:3:0:Codins-system of Hz/ZW used for Chinese (GB). -emacs-mule:0:=:3:0:Internal coding system used in a buffer. -shift_jis:1:S:3:0:Coding-system of Shift-JIS used in Japan. -sjis:1:S:3:0:Coding-system of Shift-JIS used in Japan. -euc-japan-1990:2:E:3:ascii,japanese-jisx0208,katakana-jisx0201,japanese-jisx0212,1,1,1,0,0,1,0,0,0:Coding-system of Japanese EUC (Extended Unix Code). -iso-2022-lock:2:i:3:(ascii,t),-2,-1,-1,0,1,1,1,0,0,0,0,0:ISO-2022 coding system using Locking-Shift for 96-charset. -iso-2022-ss2-7:2:I:3:(ascii,t),-1,-2,-1,1,1,1,1,0,1,0,0,0:ISO-2022 coding system using SS2 for 96-charset in 7-bit code. -iso-2022-ss2-8:2:I:3:(ascii,t),-1,-2,-1,0,1,1,0,0,1,0,0,0:ISO-2022 coding system using SS2 for 96-charset in 8-bit code. -iso-2022-cjk:2:I:3:(ascii,t),(nil,korean-ksc5601,chinese-gb2312,chinese-cns11643-1,t),(nil,chinese-cns11643-2),(nil,chinese-cns11643-3,chinese-cns11643-4,chinese-cns11643-5,chinese-cns11643-6,chinese-cns11643-7),1,1,1,1,1,1,0,0,0:Mixture of ISO-2022-JP, ISO-2022-KR, and ISO-2022-CN -cn-gb-2312:2:C:3:(ascii,t),chinese-gb2312,chinese-sisheng,-1,0,1,1,0,0,1,0,0,0:Coding-system of Chinese EUC (so called GB Encoding). -lao:2:T:3:(ascii,t),(lao,t),-1,-1,0,1,0,0,0,0,0,0,0:Coding-system used for ASCII(MSB=0) & LAO(MSB=1). -iso-2022-jp-1978-irv:2:J:3:(ascii,t),-1,-1,-1,1,1,1,1,0,0,1,1,0:Coding-system used for old jis terminal. -junet:2:J:3:(ascii,t),-1,-1,-1,1,1,1,1,0,0,0,0,0:Coding system based on ISO2022 7-bit encoding. -tis620:2:T:3:(ascii,t),(thai-tis620,t),-1,-1,0,1,0,0,0,0,0,0,0:Coding-system used for ASCII(MSB=0) & TIS620(MSB=1). -euc-japan:2:E:3:ascii,japanese-jisx0208,katakana-jisx0201,japanese-jisx0212,1,1,1,0,0,1,0,0,0:Coding-system of Japanese EUC (Extended Unix Code). -iso-2022-int-1:2:I:3:(ascii,t),(korean-ksc5601,t),-1,-1,1,1,1,1,1,0,0,0,0:ISO-2022-INT-1 -euc-china:2:C:3:(ascii,t),chinese-gb2312,chinese-sisheng,-1,0,1,1,0,0,1,0,0,0:Coding-system of Chinese EUC (so called GB Encoding). -old-jis:2:J:3:(ascii,t),-1,-1,-1,1,1,1,1,0,0,1,1,0:Coding-system used for old jis terminal. -iso-2022-7:2:J:3:(ascii,t),-1,-1,-1,1,1,1,1,0,0,0,0,0:Coding system based on ISO2022 7-bit encoding. -iso-2022-cn:2:C:3:ascii,(nil,chinese-gb2312,chinese-cns11643-1),(nil,chinese-cns11643-2),(nil,chinese-cns11643-3,chinese-cns11643-4,chinese-cns11643-5,chinese-cns11643-6,chinese-cns11643-7),0,1,1,1,1,1,0,0,0:Coding system ISO-2022-CN for Chinese (GB and CNS character sets). -ctext:2:X:3:(ascii,t),(latin-iso8859-1,t),-1,-1,0,1,1,0,0,0,0,0,0:MIME ISO-8859-1 Compound Text Encoding. -iso-2022-jp:2:J:3:(ascii,t),-1,-1,-1,1,1,1,1,0,0,0,0,0:Coding system based on ISO2022 7-bit encoding. -iso-2022-kr:2:k:3:ascii,(nil,korean-ksc5601),-1,-1,0,1,1,1,1,0,0,0,0:MIME ISO-2022-KR -iso-2022-cn-ext:2:C:3:ascii,(nil,chinese-gb2312,chinese-cns11643-1),(nil,chinese-cns11643-2),(nil,chinese-cns11643-3,chinese-cns11643-4,chinese-cns11643-5,chinese-cns11643-6,chinese-cns11643-7),0,1,1,1,1,1,0,0,0:Coding system ISO-2022-CN for Chinese (GB and CNS character sets). -iso-8859-1:2:X:3:(ascii,t),(latin-iso8859-1,t),-1,-1,0,1,1,0,0,0,0,0,0:MIME ISO-8859-1 Compound Text Encoding. -iso-8859-2:2:2:3:(ascii,t),(latin-iso8859-2,t),-1,-1,0,1,1,0,0,0,0,0,0:MIME ISO-8859-2 -iso-8859-3:2:3:3:(ascii,t),(latin-iso8859-3,t),-1,-1,0,1,1,0,0,0,0,0,0:MIME ISO-8859-3 -iso-8859-4:2:4:3:(ascii,t),(latin-iso8859-4,t),-1,-1,0,1,1,0,0,0,0,0,0:MIME ISO-8859-4 -iso-8859-5:2:5:3:(ascii,t),(cyrillic-iso8859-5,t),-1,-1,0,1,1,0,0,0,0,0,0:MIME ISO-8859-5 -iso-8859-7:2:7:3:(ascii,t),(greek-iso8859-7,t),-1,-1,0,1,1,0,0,0,0,0,0:MIME ISO-8859-7 -iso-8859-8:2:8:3:(ascii,t),(hebrew-iso8859-8,t),-1,-1,0,1,1,0,0,0,0,0,1:MIME ISO-8859-8 -iso-8859-9:2:9:3:(ascii,t),(latin-iso8859-9,t),-1,-1,0,1,1,0,0,0,0,0,0:MIME ISO-8859-9 -euc-kr:2:K:3:(ascii,t),korean-ksc5601,-1,-1,0,1,1,0,0,0,0,0,0:Coding-system of Korean EUC (Extended Unix Code). -euc-korea:2:K:3:(ascii,t),korean-ksc5601,-1,-1,0,1,1,0,0,0,0,0,0:Coding-system of Korean EUC (Extended Unix Code). -cn-big5:3:B:3:0:Coding-system of BIG5. -big5:3:B:3:0:Coding-system of BIG5. -viscii:4:V:3: 3 106 e ffffff0b 100 0 1 19c6 3 4 19c7 19e7 7 8 9 a b c d e f 10 11 12 13 19d6 15 16 17 18 19db 1a 1b 1c 1d 19dc 1f 20 21 22 23 24 25 26 27 28 29 2a 2b 2c 2d 2e 2f 30 31 32 33 34 35 36 37 38 39 3a 3b 3c 3d 3e 3f 40 41 42 43 44 45 46 47 48 49 4a 4b 4c 4d 4e 4f 50 51 52 53 54 55 56 57 58 59 5a 5b 5c 5d 5e 5f 60 61 62 63 64 65 66 67 68 69 6a 6b 6c 6d 6e 6f 70 71 72 73 74 75 76 77 78 79 7a 7b 7c 7d 7e 7f 19d5 19a1 19a2 19a3 19a4 19a5 19a6 19a7 19a8 19a9 19aa 19ab 19ac 19ad 19ae 19af 19b0 19b1 19b2 19b5 19fe 19be 19b6 19b7 19b8 19f6 19f7 19ef 19fc 19fb 19f8 19cf 19f5 1921 1922 1923 1924 1925 1926 1927 1928 1929 192a 192b 192c 192d 192e 192f 1930 1931 1932 19de 19bd 1935 1936 1937 1938 19f1 19d1 19d7 19d8 193d 193e 19df 19e0 19e1 19e2 19e3 19e4 19e5 1946 1947 19e8 19e9 19ea 19eb 19ec 19ed 19ee 194f 19f0 1951 19f2 19f3 19f4 1955 1956 1957 1958 19f9 19fa 195b 195c 19fd 195e 195f 1960 1961 1962 1963 1964 1965 1966 1967 1968 1969 196a 196b 196c 196d 196e 196f 1970 1971 1972 1973 1974 1975 1976 1977 1978 1979 197a 197b 197c 197d 197e 19e6 fffefd0c 16, 1 121 e 41b 10 80 fffffc07 fffffb0c 41b 15 9a fffff707 fffff60c 881d 12 a2 e 4017 80 ffffef0b 80 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 a1 a2 a3 a4 a5 a6 a7 a8 a9 aa ab ac ad ae af b0 b1 b2 0 0 b5 b6 b7 b8 0 0 0 0 bd be 0 0 0 0 0 0 0 c6 c7 0 0 0 0 0 0 0 cf 0 d1 0 0 0 d5 d6 d7 d8 0 0 db dc 0 de df e0 e1 e2 e3 e4 e5 e6 e7 e8 e9 ea eb ec ed ee ef f0 f1 f2 f3 f4 f5 f6 f7 f8 f9 fa fb fc fd fe 0 ffff6d0c 881b 12 a3 e 4017 80 ffff660b 80 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 81 82 83 84 85 86 87 88 89 8a 8b 8c 8d 8e 8f 90 91 92 0 0 93 96 97 98 0 0 0 0 b4 95 0 0 0 0 0 0 0 2 5 0 0 0 0 0 0 0 9f 0 ba 0 0 0 80 14 bb bc 0 0 19 1e 0 b3 bf c0 c1 c2 c3 c4 c5 ff 6 c8 c9 ca cb cc cd ce 9b d0 b9 d2 d3 d4 a0 99 9a 9e d9 da 9d 9c dd 94 0 fffee40c fffee307 fffee20c 16:Coding-system used for VISCII 1.1. -koi8:4:K:3: 3 106 e ffffff0b 100 0 1 2 3 4 5 6 7 8 9 a b c d e f 10 11 12 13 14 15 16 17 18 19 1a 1b 1c 1d 1e 1f 20 21 22 23 24 25 26 27 28 29 2a 2b 2c 2d 2e 2f 30 31 32 33 34 35 36 37 38 39 3a 3b 3c 3d 3e 3f 40 41 42 43 44 45 46 47 48 49 4a 4b 4c 4d 4e 4f 50 51 52 53 54 55 56 57 58 59 5a 5b 5c 5d 5e 5f 60 61 62 63 64 65 66 67 68 69 6a 6b 6c 6d 6e 6f 70 71 72 73 74 75 76 77 78 79 7a 7b 7c 7d 7e 7f 80 81 82 83 84 85 86 87 88 89 8a 8b 8c 8d 8e 8f 90 91 92 93 94 95 96 97 98 99 9a 9b 9c 9d 9e 9f 20 20 20 e71 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 e21 20 20 20 20 20 20 20 20 20 20 20 20 e6e e50 e51 e66 e54 e55 e64 e53 e65 e58 e59 e5a e5b e5c e5d e5e e5f e6f e60 e61 e62 e63 e56 e52 e6c e6b e57 e68 e6d e69 e67 e6a e4e e30 e31 e46 e34 e35 e44 e33 e45 e38 e39 e3a e3b e3c e3d e3e e3f e4f e40 e41 e42 e43 e36 e32 e4c e4b e37 e48 e4d e49 e47 e4a fffefd0c 16, 1 6e e 41b 15 8c fffffc07 fffffb0c e 4017 a0 fffff70b 60 20 b3 20 20 20 20 20 20 20 20 20 20 20 20 20 20 e1 e2 f7 e7 e4 e5 f6 fa e9 ea eb ec ed ee ef f0 f2 f3 f4 f5 e6 e8 e3 fe fb fd ff f9 f8 fc e0 f1 c1 c2 d7 c7 c4 c5 d6 da c9 ca cb cc cd ce cf d0 d2 d3 d4 d5 c6 c8 c3 de db dd df d9 d8 dc c0 d1 20 a3 20 20 20 20 20 20 20 20 20 20 20 20 20 20 ffff950c 16:Coding-system used for KOI8. -koi8-r:4:K:3: 3 106 e ffffff0b 100 0 1 2 3 4 5 6 7 8 9 a b c d e f 10 11 12 13 14 15 16 17 18 19 1a 1b 1c 1d 1e 1f 20 21 22 23 24 25 26 27 28 29 2a 2b 2c 2d 2e 2f 30 31 32 33 34 35 36 37 38 39 3a 3b 3c 3d 3e 3f 40 41 42 43 44 45 46 47 48 49 4a 4b 4c 4d 4e 4f 50 51 52 53 54 55 56 57 58 59 5a 5b 5c 5d 5e 5f 60 61 62 63 64 65 66 67 68 69 6a 6b 6c 6d 6e 6f 70 71 72 73 74 75 76 77 78 79 7a 7b 7c 7d 7e 7f 80 81 82 83 84 85 86 87 88 89 8a 8b 8c 8d 8e 8f 90 91 92 93 94 95 96 97 98 99 9a 9b 9c 9d 9e 9f 20 20 20 e71 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 e21 20 20 20 20 20 20 20 20 20 20 20 20 e6e e50 e51 e66 e54 e55 e64 e53 e65 e58 e59 e5a e5b e5c e5d e5e e5f e6f e60 e61 e62 e63 e56 e52 e6c e6b e57 e68 e6d e69 e67 e6a e4e e30 e31 e46 e34 e35 e44 e33 e45 e38 e39 e3a e3b e3c e3d e3e e3f e4f e40 e41 e42 e43 e36 e32 e4c e4b e37 e48 e4d e49 e47 e4a fffefd0c 16, 1 6e e 41b 15 8c fffffc07 fffffb0c e 4017 a0 fffff70b 60 20 b3 20 20 20 20 20 20 20 20 20 20 20 20 20 20 e1 e2 f7 e7 e4 e5 f6 fa e9 ea eb ec ed ee ef f0 f2 f3 f4 f5 e6 e8 e3 fe fb fd ff f9 f8 fc e0 f1 c1 c2 d7 c7 c4 c5 d6 da c9 ca cb cc cd ce cf d0 d2 d3 d4 d5 c6 c8 c3 de db dd df d9 d8 dc c0 d1 20 a3 20 20 20 20 20 20 20 20 20 20 20 20 20 20 ffff950c 16:Coding-system used for KOI8. -alternativnyj:4:A:3: 3 106 e ffffff0b 100 0 1 2 3 4 5 6 7 8 9 a b c d e f 10 11 12 13 14 15 16 17 18 19 1a 1b 1c 1d 1e 1f 20 21 22 23 24 25 26 27 28 29 2a 2b 2c 2d 2e 2f 30 31 32 33 34 35 36 37 38 39 3a 3b 3c 3d 3e 3f 40 41 42 43 44 45 46 47 48 49 4a 4b 4c 4d 4e 4f 50 51 52 53 54 55 56 57 58 59 5a 5b 5c 5d 5e 5f 60 61 62 63 64 65 66 67 68 69 6a 6b 6c 6d 6e 6f 70 71 72 73 74 75 76 77 78 79 7a 7b 7c 7d 7e 7f e30 e31 e32 e33 e34 e35 e36 e37 e38 e39 e3a e3b e3c e3d e3e e3f e40 e41 e42 e43 e44 e45 e46 e47 e48 e49 e4a e4b e4c e4d e4e e4f e50 e51 e52 e53 e54 e55 e56 e57 e58 e59 e5a e5b e5c e5d e5e e5f 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 e60 e61 e62 e63 e64 e65 e66 e67 e68 e69 e6a e6b e6c e6d e6e e6f e21 e71 20 20 20 20 20 20 20 20 20 20 20 20 20 e70 fffefd0c 16, 1 6e e 41b 15 8c fffffc07 fffffb0c e 4017 a0 fffff70b 60 20 f0 20 20 20 20 20 20 20 20 20 20 20 20 20 20 80 81 82 83 84 85 86 87 88 89 8a 8b 8c 8d 8e 8f 90 91 92 93 94 95 96 97 98 99 9a 9b 9c 9d 9e 9f a0 a1 a2 a3 a4 a5 a6 a7 a8 a9 aa ab ac ad ae af e0 e1 e2 e3 e4 e5 e6 e7 e8 e9 ea eb ec ed ee ef ff f1 20 20 20 20 20 20 20 20 20 20 20 20 20 20 ffff950c 16:Coding-system used for Alternativnyj -vscii:4:V:3: 3 106 e ffffff0b 100 0 19fa 19f8 3 19d7 19d8 19e6 7 8 9 a b c d e f 10 19d1 19df 19cf 19d6 19db 19fd 19dc 18 19 1a 1b 1c 1d 1e 1f 20 21 22 23 24 25 26 27 28 29 2a 2b 2c 2d 2e 2f 30 31 32 33 34 35 36 37 38 39 3a 3b 3c 3d 3e 3f 40 41 42 43 44 45 46 47 48 49 4a 4b 4c 4d 4e 4f 50 51 52 53 54 55 56 57 58 59 5a 5b 5c 5d 5e 5f 60 61 62 63 64 65 66 67 68 69 6a 6b 6c 6d 6e 6f 70 71 72 73 74 75 76 77 78 79 7a 7b 7c 7d 7e 7f 19e0 19e4 19e3 19e1 19d5 19a3 19a7 19e8 19eb 19a8 19e9 19a9 19ae 19ec 19ef 19ee 19ed 19b8 19f2 19f6 19f5 19f3 19f7 19b5 19b6 19b7 19de 19be 19fe 19f9 19fc 19fb a0 19e5 19e2 19ea 19f4 19bd 19df 19f0 1965 1962 196a 1974 193e 1979 1970 19a2 c0 c1 c2 c3 c4 1960 1964 1963 1961 1955 19c6 1922 1946 1947 1921 19c7 19a1 19a5 19a6 19e7 19a5 19ab 1923 1925 1926 1967 1924 1927 1968 19ac 196b 1928 1969 1929 192b 192c 192d 192a 192e 196c 196f 19ad 19aa 19b0 196e 196d 1938 1972 19b1 1976 1975 1973 1977 1930 1931 1932 192f 1935 1936 1937 195e 193e 197e 1979 19b2 197c 197b 197a 1978 1957 1958 1966 1951 1971 194f 1956 195b 197d 195c 19af fffefd0c 16, 1 121 e 41b 10 80 fffffc07 fffffb0c 41b 15 9a fffff707 fffff60c 881d 12 a2 e 4017 80 ffffef0b 80 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 be bb c6 ca c7 c8 cb cf d1 d5 d2 d3 d4 d6 e8 e5 e6 e7 0 0 e9 ea eb de 0 0 0 0 0 ed 0 0 0 0 0 0 0 bc bd 0 0 0 0 0 0 0 fa 0 f8 0 0 0 b9 fb f5 f6 0 0 fc fe 0 ec 0 b5 b8 a9 b7 b6 a8 f7 c9 cc d0 aa ce d7 dd dc d8 ae f9 df e3 ab e2 e1 e4 f4 ef f3 f2 f1 fd ee 0 ffff6d0c 881b 12 a3 e 4017 80 ffff660b 80 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 81 82 83 84 85 86 87 88 89 8a 8b 8c 8d 8e 8f 90 91 92 0 0 93 96 97 98 0 0 0 0 b4 95 0 0 0 0 0 0 0 2 5 0 0 0 0 0 0 0 9f 0 ba 0 0 0 80 14 bb bc 0 0 19 1e 0 b3 bf c0 c1 c2 c3 c4 c5 ff 6 c8 c9 ca cb cc cd ce 9b d0 b9 d2 d3 d4 a0 99 9a 9e d9 da 9d 9c dd 94 0 fffee40c fffee307 fffee20c 16:Coding-system used for VSCII-1. -############################ -## LIST OF CODING CATEGORIES (ordered by priority) -## CATEGORY:CODING-SYSTEM -## -coding-category-iso-7:iso-2022-7 -coding-category-iso-8-1:iso-8859-1 -coding-category-iso-8-2:iso-8859-1 -coding-category-iso-else:iso-2022-lock -coding-category-emacs-mule:emacs-mule -coding-category-sjis:sjis -coding-category-big5:big5 -coding-category-binary:no-conversion diff -r 7edc33019aa4 -r b7b90f750a78 etc/COPYING.LIB --- a/etc/COPYING.LIB Mon Jan 31 20:01:50 2005 +0000 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000 @@ -1,483 +0,0 @@ - GNU LIBRARY GENERAL PUBLIC LICENSE - Version 2, June 1991 - - Copyright (C) 1991 Free Software Foundation, Inc. - 59 Temple Place - Suite 330 - Boston, MA 02111-1307, USA. - Everyone is permitted to copy and distribute verbatim copies - of this license document, but changing it is not allowed. - -[This is the first released version of the library GPL. It is - numbered 2 because it goes with version 2 of the ordinary GPL.] - - Preamble - - The licenses for most software are designed to take away your -freedom to share and change it. By contrast, the GNU General Public -Licenses are intended to guarantee your freedom to share and change -free software--to make sure the software is free for all its users. - - This license, the Library General Public License, applies to some -specially designated Free Software Foundation software, and to any -other libraries whose authors decide to use it. You can use it for -your libraries, too. - - When we speak of free software, we are referring to freedom, not -price. Our General Public Licenses are designed to make sure that you -have the freedom to distribute copies of free software (and charge for -this service if you wish), that you receive source code or can get it -if you want it, that you can change the software or use pieces of it -in new free programs; and that you know you can do these things. - - To protect your rights, we need to make restrictions that forbid -anyone to deny you these rights or to ask you to surrender the rights. -These restrictions translate to certain responsibilities for you if -you distribute copies of the library, or if you modify it. - - For example, if you distribute copies of the library, whether gratis -or for a fee, you must give the recipients all the rights that we gave -you. You must make sure that they, too, receive or can get the source -code. If you link a program with the library, you must provide -complete object files to the recipients so that they can relink them -with the library, after making changes to the library and recompiling -it. And you must show them these terms so they know their rights. - - Our method of protecting your rights has two steps: (1) copyright -the library, and (2) offer you this license which gives you legal -permission to copy, distribute and/or modify the library. - - Also, for each distributor's protection, we want to make certain -that everyone understands that there is no warranty for this free -library. If the library is modified by someone else and passed on, we -want its recipients to know that what they have is not the original -version, so that any problems introduced by others will not reflect on -the original authors' reputations. - - Finally, any free program is threatened constantly by software -patents. We wish to avoid the danger that companies distributing free -software will individually obtain patent licenses, thus in effect -transforming the program into proprietary software. To prevent this, -we have made it clear that any patent must be licensed for everyone's -free use or not licensed at all. - - Most GNU software, including some libraries, is covered by the ordinary -GNU General Public License, which was designed for utility programs. This -license, the GNU Library General Public License, applies to certain -designated libraries. This license is quite different from the ordinary -one; be sure to read it in full, and don't assume that anything in it is -the same as in the ordinary license. - - The reason we have a separate public license for some libraries is that -they blur the distinction we usually make between modifying or adding to a -program and simply using it. Linking a program with a library, without -changing the library, is in some sense simply using the library, and is -analogous to running a utility program or application program. However, in -a textual and legal sense, the linked executable is a combined work, a -derivative of the original library, and the ordinary General Public License -treats it as such. - - Because of this blurred distinction, using the ordinary General -Public License for libraries did not effectively promote software -sharing, because most developers did not use the libraries. We -concluded that weaker conditions might promote sharing better. - - However, unrestricted linking of non-free programs would deprive the -users of those programs of all benefit from the free status of the -libraries themselves. This Library General Public License is intended to -permit developers of non-free programs to use free libraries, while -preserving your freedom as a user of such programs to change the free -libraries that are incorporated in them. (We have not seen how to achieve -this as regards changes in header files, but we have achieved it as regards -changes in the actual functions of the Library.) The hope is that this -will lead to faster development of free libraries. - - The precise terms and conditions for copying, distribution and -modification follow. Pay close attention to the difference between a -"work based on the library" and a "work that uses the library". The -former contains code derived from the library, while the latter only -works together with the library. - - Note that it is possible for a library to be covered by the ordinary -General Public License rather than by this special one. - - GNU LIBRARY GENERAL PUBLIC LICENSE - TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION - - 0. This License Agreement applies to any software library which -contains a notice placed by the copyright holder or other authorized -party saying it may be distributed under the terms of this Library -General Public License (also called "this License"). Each licensee is -addressed as "you". - - A "library" means a collection of software functions and/or data -prepared so as to be conveniently linked with application programs -(which use some of those functions and data) to form executables. - - The "Library", below, refers to any such software library or work -which has been distributed under these terms. A "work based on the -Library" means either the Library or any derivative work under -copyright law: that is to say, a work containing the Library or a -portion of it, either verbatim or with modifications and/or translated -straightforwardly into another language. (Hereinafter, translation is -included without limitation in the term "modification".) - - "Source code" for a work means the preferred form of the work for -making modifications to it. For a library, complete source code means -all the source code for all modules it contains, plus any associated -interface definition files, plus the scripts used to control compilation -and installation of the library. - - Activities other than copying, distribution and modification are not -covered by this License; they are outside its scope. The act of -running a program using the Library is not restricted, and output from -such a program is covered only if its contents constitute a work based -on the Library (independent of the use of the Library in a tool for -writing it). Whether that is true depends on what the Library does -and what the program that uses the Library does. - - 1. You may copy and distribute verbatim copies of the Library's -complete source code as you receive it, in any medium, provided that -you conspicuously and appropriately publish on each copy an -appropriate copyright notice and disclaimer of warranty; keep intact -all the notices that refer to this License and to the absence of any -warranty; and distribute a copy of this License along with the -Library. - - You may charge a fee for the physical act of transferring a copy, -and you may at your option offer warranty protection in exchange for a -fee. - - 2. You may modify your copy or copies of the Library or any portion -of it, thus forming a work based on the Library, and copy and -distribute such modifications or work under the terms of Section 1 -above, provided that you also meet all of these conditions: - - a) The modified work must itself be a software library. - - b) You must cause the files modified to carry prominent notices - stating that you changed the files and the date of any change. - - c) You must cause the whole of the work to be licensed at no - charge to all third parties under the terms of this License. - - d) If a facility in the modified Library refers to a function or a - table of data to be supplied by an application program that uses - the facility, other than as an argument passed when the facility - is invoked, then you must make a good faith effort to ensure that, - in the event an application does not supply such function or - table, the facility still operates, and performs whatever part of - its purpose remains meaningful. - - (For example, a function in a library to compute square roots has - a purpose that is entirely well-defined independent of the - application. Therefore, Subsection 2d requires that any - application-supplied function or table used by this function must - be optional: if the application does not supply it, the square - root function must still compute square roots.) - -These requirements apply to the modified work as a whole. If -identifiable sections of that work are not derived from the Library, -and can be reasonably considered independent and separate works in -themselves, then this License, and its terms, do not apply to those -sections when you distribute them as separate works. But when you -distribute the same sections as part of a whole which is a work based -on the Library, the distribution of the whole must be on the terms of -this License, whose permissions for other licensees extend to the -entire whole, and thus to each and every part regardless of who wrote -it. - -Thus, it is not the intent of this section to claim rights or contest -your rights to work written entirely by you; rather, the intent is to -exercise the right to control the distribution of derivative or -collective works based on the Library. - -In addition, mere aggregation of another work not based on the Library -with the Library (or with a work based on the Library) on a volume of -a storage or distribution medium does not bring the other work under -the scope of this License. - - 3. You may opt to apply the terms of the ordinary GNU General Public -License instead of this License to a given copy of the Library. To do -this, you must alter all the notices that refer to this License, so -that they refer to the ordinary GNU General Public License, version 2, -instead of to this License. (If a newer version than version 2 of the -ordinary GNU General Public License has appeared, then you can specify -that version instead if you wish.) Do not make any other change in -these notices. - - Once this change is made in a given copy, it is irreversible for -that copy, so the ordinary GNU General Public License applies to all -subsequent copies and derivative works made from that copy. - - This option is useful when you wish to copy part of the code of -the Library into a program that is not a library. - - 4. You may copy and distribute the Library (or a portion or -derivative of it, under Section 2) in object code or executable form -under the terms of Sections 1 and 2 above provided that you accompany -it with the complete corresponding machine-readable source code, which -must be distributed under the terms of Sections 1 and 2 above on a -medium customarily used for software interchange. - - If distribution of object code is made by offering access to copy -from a designated place, then offering equivalent access to copy the -source code from the same place satisfies the requirement to -distribute the source code, even though third parties are not -compelled to copy the source along with the object code. - - 5. A program that contains no derivative of any portion of the -Library, but is designed to work with the Library by being compiled or -linked with it, is called a "work that uses the Library". Such a -work, in isolation, is not a derivative work of the Library, and -therefore falls outside the scope of this License. - - However, linking a "work that uses the Library" with the Library -creates an executable that is a derivative of the Library (because it -contains portions of the Library), rather than a "work that uses the -library". The executable is therefore covered by this License. -Section 6 states terms for distribution of such executables. - - When a "work that uses the Library" uses material from a header file -that is part of the Library, the object code for the work may be a -derivative work of the Library even though the source code is not. -Whether this is true is especially significant if the work can be -linked without the Library, or if the work is itself a library. The -threshold for this to be true is not precisely defined by law. - - If such an object file uses only numerical parameters, data -structure layouts and accessors, and small macros and small inline -functions (ten lines or less in length), then the use of the object -file is unrestricted, regardless of whether it is legally a derivative -work. (Executables containing this object code plus portions of the -Library will still fall under Section 6.) - - Otherwise, if the work is a derivative of the Library, you may -distribute the object code for the work under the terms of Section 6. -Any executables containing that work also fall under Section 6, -whether or not they are linked directly with the Library itself. - - 6. As an exception to the Sections above, you may also compile or -link a "work that uses the Library" with the Library to produce a -work containing portions of the Library, and distribute that work -under terms of your choice, provided that the terms permit -modification of the work for the customer's own use and reverse -engineering for debugging such modifications. - - You must give prominent notice with each copy of the work that the -Library is used in it and that the Library and its use are covered by -this License. You must supply a copy of this License. If the work -during execution displays copyright notices, you must include the -copyright notice for the Library among them, as well as a reference -directing the user to the copy of this License. Also, you must do one -of these things: - - a) Accompany the work with the complete corresponding - machine-readable source code for the Library including whatever - changes were used in the work (which must be distributed under - Sections 1 and 2 above); and, if the work is an executable linked - with the Library, with the complete machine-readable "work that - uses the Library", as object code and/or source code, so that the - user can modify the Library and then relink to produce a modified - executable containing the modified Library. (It is understood - that the user who changes the contents of definitions files in the - Library will not necessarily be able to recompile the application - to use the modified definitions.) - - b) Accompany the work with a written offer, valid for at - least three years, to give the same user the materials - specified in Subsection 6a, above, for a charge no more - than the cost of performing this distribution. - - c) If distribution of the work is made by offering access to copy - from a designated place, offer equivalent access to copy the above - specified materials from the same place. - - d) Verify that the user has already received a copy of these - materials or that you have already sent this user a copy. - - For an executable, the required form of the "work that uses the -Library" must include any data and utility programs needed for -reproducing the executable from it. However, as a special exception, -the source code distributed need not include anything that is normally -distributed (in either source or binary form) with the major -components (compiler, kernel, and so on) of the operating system on -which the executable runs, unless that component itself accompanies -the executable. - - It may happen that this requirement contradicts the license -restrictions of other proprietary libraries that do not normally -accompany the operating system. Such a contradiction means you cannot -use both them and the Library together in an executable that you -distribute. - - 7. You may place library facilities that are a work based on the -Library side-by-side in a single library together with other library -facilities not covered by this License, and distribute such a combined -library, provided that the separate distribution of the work based on -the Library and of the other library facilities is otherwise -permitted, and provided that you do these two things: - - a) Accompany the combined library with a copy of the same work - based on the Library, uncombined with any other library - facilities. This must be distributed under the terms of the - Sections above. - - b) Give prominent notice with the combined library of the fact - that part of it is a work based on the Library, and explaining - where to find the accompanying uncombined form of the same work. - - 8. You may not copy, modify, sublicense, link with, or distribute -the Library except as expressly provided under this License. Any -attempt otherwise to copy, modify, sublicense, link with, or -distribute the Library is void, and will automatically terminate your -rights under this License. However, parties who have received copies, -or rights, from you under this License will not have their licenses -terminated so long as such parties remain in full compliance. - - 9. You are not required to accept this License, since you have not -signed it. However, nothing else grants you permission to modify or -distribute the Library or its derivative works. These actions are -prohibited by law if you do not accept this License. Therefore, by -modifying or distributing the Library (or any work based on the -Library), you indicate your acceptance of this License to do so, and -all its terms and conditions for copying, distributing or modifying -the Library or works based on it. - - 10. Each time you redistribute the Library (or any work based on the -Library), the recipient automatically receives a license from the -original licensor to copy, distribute, link with or modify the Library -subject to these terms and conditions. You may not impose any further -restrictions on the recipients' exercise of the rights granted herein. -You are not responsible for enforcing compliance by third parties to -this License. - - 11. If, as a consequence of a court judgment or allegation of patent -infringement or for any other reason (not limited to patent issues), -conditions are imposed on you (whether by court order, agreement or -otherwise) that contradict the conditions of this License, they do not -excuse you from the conditions of this License. If you cannot -distribute so as to satisfy simultaneously your obligations under this -License and any other pertinent obligations, then as a consequence you -may not distribute the Library at all. For example, if a patent -license would not permit royalty-free redistribution of the Library by -all those who receive copies directly or indirectly through you, then -the only way you could satisfy both it and this License would be to -refrain entirely from distribution of the Library. - -If any portion of this section is held invalid or unenforceable under any -particular circumstance, the balance of the section is intended to apply, -and the section as a whole is intended to apply in other circumstances. - -It is not the purpose of this section to induce you to infringe any -patents or other property right claims or to contest validity of any -such claims; this section has the sole purpose of protecting the -integrity of the free software distribution system which is -implemented by public license practices. Many people have made -generous contributions to the wide range of software distributed -through that system in reliance on consistent application of that -system; it is up to the author/donor to decide if he or she is willing -to distribute software through any other system and a licensee cannot -impose that choice. - -This section is intended to make thoroughly clear what is believed to -be a consequence of the rest of this License. - - 12. If the distribution and/or use of the Library is restricted in -certain countries either by patents or by copyrighted interfaces, the -original copyright holder who places the Library under this License may add -an explicit geographical distribution limitation excluding those countries, -so that distribution is permitted only in or among countries not thus -excluded. In such case, this License incorporates the limitation as if -written in the body of this License. - - 13. The Free Software Foundation may publish revised and/or new -versions of the Library General Public License from time to time. -Such new versions will be similar in spirit to the present version, -but may differ in detail to address new problems or concerns. - -Each version is given a distinguishing version number. If the Library -specifies a version number of this License which applies to it and -"any later version", you have the option of following the terms and -conditions either of that version or of any later version published by -the Free Software Foundation. If the Library does not specify a -license version number, you may choose any version ever published by -the Free Software Foundation. - - 14. If you wish to incorporate parts of the Library into other free -programs whose distribution conditions are incompatible with these, -write to the author to ask for permission. For software which is -copyrighted by the Free Software Foundation, write to the Free -Software Foundation; we sometimes make exceptions for this. Our -decision will be guided by the two goals of preserving the free status -of all derivatives of our free software and of promoting the sharing -and reuse of software generally. - - NO WARRANTY - - 15. BECAUSE THE LIBRARY IS LICENSED FREE OF CHARGE, THERE IS NO -WARRANTY FOR THE LIBRARY, TO THE EXTENT PERMITTED BY APPLICABLE LAW. -EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR -OTHER PARTIES PROVIDE THE LIBRARY "AS IS" WITHOUT WARRANTY OF ANY -KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE -IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR -PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE -LIBRARY IS WITH YOU. SHOULD THE LIBRARY PROVE DEFECTIVE, YOU ASSUME -THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION. - - 16. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN -WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY -AND/OR REDISTRIBUTE THE LIBRARY AS PERMITTED ABOVE, BE LIABLE TO YOU -FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR -CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE -LIBRARY (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING -RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A -FAILURE OF THE LIBRARY TO OPERATE WITH ANY OTHER SOFTWARE), EVEN IF -SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH -DAMAGES. - - END OF TERMS AND CONDITIONS - - Appendix: How to Apply These Terms to Your New Libraries - - If you develop a new library, and you want it to be of the greatest -possible use to the public, we recommend making it free software that -everyone can redistribute and change. You can do so by permitting -redistribution under these terms (or, alternatively, under the terms of the -ordinary General Public License). - - To apply these terms, attach the following notices to the library. It is -safest to attach them to the start of each source file to most effectively -convey the exclusion of warranty; and each file should have at least the -"copyright" line and a pointer to where the full notice is found. - - - Copyright (C) - - This library is free software; you can redistribute it and/or - modify it under the terms of the GNU Library General Public - License as published by the Free Software Foundation; either - version 2 of the License, or (at your option) any later version. - - This library is distributed in the hope that it will be useful, - but WITHOUT ANY WARRANTY; without even the implied warranty of - MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU - Library General Public License for more details. - - You should have received a copy of the GNU General Public License - along with this library; see the file COPYING. If not, write to - the Free Software Foundation, Inc., 59 Temple Place - Suite 330, - Boston, MA 02111-1307, USA. - -Also add information on how to contact you by electronic and paper mail. - -You should also get your employer (if you work as a programmer) or your -school, if any, to sign a "copyright disclaimer" for the library, if -necessary. Here is a sample; alter the names: - - Yoyodyne, Inc., hereby disclaims all copyright interest in the - library `Frob' (a library for tweaking knobs) written by James Random Hacker. - - , 1 April 1990 - Ty Coon, President of Vice - -That's all there is to it! diff -r 7edc33019aa4 -r b7b90f750a78 etc/ChangeLog --- a/etc/ChangeLog Mon Jan 31 20:01:50 2005 +0000 +++ b/etc/ChangeLog Mon Jan 31 20:08:52 2005 +0000 @@ -1,3 +1,28 @@ +2005-01-31 Ben Wing + + Delete stuff that is irrelevant, mislocated or woefully out-of-date. + + * GNU: Delete. + * SERVICE: Delete. + * ORDERS, ORDERS.EUROPE, ORDERS.JAPAN: Delete. + * CHARSETS, CODINGS: Delete. + * DEBUG, LPF, MORE.STUFF, MOTIVATION: Delete. + * aliases.ksh: Delete. (moved to xemacs-builds/steve) + * README.HYPERBOLE, README.OO-BROWSER: Delete. + * chr.png, chrm.png: Move to photos/. + * check_cygwin_setup.sh: Delete. + * gnu.xpm, gnu.xbm, sink.xbm: Delete. + * ms-kermit, ms-kermit-7bit: Delete. + * TERMS: Delete. + + * DISTRIB, FTP, MACHINES, MAILINGLISTS, PACKAGES: + Delete and move to FAQ. + + * BETA: + Delete and move to man/beta.texi. + + * README: Update. + 2004-11-13 Ben Wing * CODING-STANDARDS: Delete and incorporate into Internals manual. diff -r 7edc33019aa4 -r b7b90f750a78 etc/DEBUG --- a/etc/DEBUG Mon Jan 31 20:01:50 2005 +0000 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000 @@ -1,143 +0,0 @@ -Debugging GNU Emacs -Copyright (c) 1985 Richard M. Stallman. - - Permission is granted to anyone to make or distribute verbatim copies - of this document as received, in any medium, provided that the - copyright notice and permission notice are preserved, - and that the distributor grants the recipient permission - for further redistribution as permitted by this notice. - - Permission is granted to distribute modified versions - of this document, or of portions of it, - under the above conditions, provided also that they - carry prominent notices stating who last changed them. - -On 4.2 you will probably find that dbx does not work for -debugging GNU Emacs. For one thing, dbx does not keep the -inferior process's terminal modes separate from its own. -For another, dbx does not put the inferior in a separate -process group, which makes trouble when an inferior uses -interrupt input, which GNU Emacs must do on 4.2. - -dbx has also been observed to have other problems, -such as getting incorrect values for register variables -in stack frames other than the innermost one. - -The Emacs distribution now contains GDB, the new source-level -debugger for the GNU system. GDB works for debugging Emacs. -GDB currently runs on vaxes under 4.2 and on Sun 2 and Sun 3 -systems. - - -** Some useful techniques - -`Fsignal' is a very useful place to stop in. -All Lisp errors go through there. - -It is useful, when debugging, to have a guaranteed way -to return to the debugger at any time. If you are using -interrupt-driven input, which is the default, then Emacs is using -RAW mode and the only way you can do it is to store -the code for some character into the variable stop_character: - - set stop_character = 29 - -makes Control-] (decimal code 29) the stop character. -Typing Control-] will cause immediate stop. You cannot -use the set command until the inferior process has been started. -Put a breakpoint early in `main', or suspend the Emacs, -to get an opportunity to do the set command. - -If you are using cbreak input (see the Lisp function set-input-mode), -then typing Control-g will cause a SIGINT, which will return control -to the debugger immediately unless you have done - - ignore 3 (in dbx) -or handle 3 nostop noprint (in gdb) - -You will note that most of GNU Emacs is written to avoid -declaring a local variable in an inner block, even in -cases where using one would be the cleanest thing to do. -This is because dbx cannot access any of the variables -in a function which has even one variable defined in an -inner block. A few functions in GNU Emacs do have variables -in inner blocks, only because I wrote them before realizing -that dbx had this problem and never rewrote them to avoid it. - -I believe that GDB does not have such a problem. - - -** Examining Lisp object values. - -When you have a live process to debug, and it has not encountered a -fatal error, you can use the GDB command `pr'. First print the value -in the ordinary way, with the `p' command. Then type `pr' with no -arguments. This calls a subroutine which uses the Lisp printer. - -If you can't use this command, either because the process can't run -a subroutine or because the data is invalid, you can fall back on -lower-level commands. - -Use the `xtype' command to print out the data type of the last data -value. Once you know the data type, use the command that corresponds -to that type. Here are these commands: - - xint xptr xwindow xmarker xoverlay xmiscfree xintfwd xboolfwd xobjfwd - xbufobjfwd xkbobjfwd xbuflocal xbuffer xsymbol xstring xvector xframe - xwinconfig xcompiled xcons xcar xcdr xsubr xprocess xfloat xscrollbar - -Each one of them applies to a certain type or class of types. -(Some of these types are not visible in Lisp, because they exist only -internally.) - -Each x... command prints some information about the value, and -produces a GDB value (subsequently available in $) through which you -can get at the rest of the contents. - -In general, most of the rest of the contents will be addition Lisp -objects which you can examine in turn with the x... commands. - -** If GDB does not run and your debuggers can't load Emacs. - -On some systems, no debugger can load Emacs with a symbol table, -perhaps because they all have fixed limits on the number of symbols -and Emacs exceeds the limits. Here is a method that can be used -in such an extremity. Do - - nm -n temacs > nmout - strip temacs - adb temacs - 0xd:i - 0xe:i - 14:i - 17:i - :r -l loadup (or whatever) - -It is necessary to refer to the file `nmout' to convert -numeric addresses into symbols and vice versa. - -It is useful to be running under a window system. -Then, if Emacs becomes hopelessly wedged, you can create -another window to do kill -9 in. kill -ILL is often -useful too, since that may make Emacs dump core or return -to adb. - - -** Debugging incorrect screen updating. - -To debug Emacs problems that update the screen wrong, it is useful -to have a record of what input you typed and what Emacs sent to the -screen. To make these records, do - -(open-dribble-file "~/.dribble") -(open-termscript "~/.termscript") - -The dribble file contains all characters read by Emacs from the -terminal, and the termscript file contains all characters it sent to -the terminal. The use of the directory `~/' prevents interference -with any other user. - -If you have irreproducible display problems, put those two expressions -in your ~/.emacs file. When the problem happens, exit the Emacs that -you were running, kill it, and rename the two files. Then you can start -another Emacs without clobbering those files, and use it to examine them. diff -r 7edc33019aa4 -r b7b90f750a78 etc/DISTRIB --- a/etc/DISTRIB Mon Jan 31 20:01:50 2005 +0000 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000 @@ -1,18 +0,0 @@ - -*- text -*- - - XEmacs availability information. Last Modified: 18-Jul-99. - -XEmacs is available via anonymous FTP from ftp.xemacs.org (207.96.122.8) -in the directory /pub/xemacs/. - -ftp.xemacs.org is the primary distribution point, but you may find -copies of it at other sites as well. Please see the file FTP for mirrors. - -The most up-to-date list of distribution sites can always be found on -the XEmacs WWW page, http://www.xemacs.org/. Try to pick a site -that is networkologically close to you. If you know of other mirrors -of the XEmacs archives, please send us mail and we will list them here -as well. - -There are mailing lists and newsgroups specifically for discussing and -reporting bugs in XEmacs; see the file MAILINGLISTS in this directory. diff -r 7edc33019aa4 -r b7b90f750a78 etc/FTP --- a/etc/FTP Mon Jan 31 20:01:50 2005 +0000 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000 @@ -1,206 +0,0 @@ - - XEmacs availability information. Last Modified: 2001-02-01 - -XEmacs is available via anonymous FTP at ftp://ftp.xemacs.org/pub/xemacs/ -and also via HTTP at http://ftp.xemacs.org/. - -ftp.xemacs.org is the primary distribution point, but you may find -copies of it at other sites as well. Some sites to try include: - -* Africa - - Goto Mirror Index - o South Africa - - + ftp.za.xemacs.org (FTP) - + ftp.za.xemacs.org (HTTP) - -* America - - Goto Mirror Index - - o North America - - + Canada - + ftp.ca.xemacs.org (FTP) - + ftp.ca.xemacs.org (HTTP) - - Secondary Mirrors - + ftp://ftp.crc.ca/pub/packages/editors/xemacs/ - - + United States - - + ftp.us.xemacs.org (FTP) - + ftp.us.xemacs.org (HTTP) - - Secondary Mirrors - + ftp://ftp.twoguys.org/pub/xemacs/ - + ftp://ftp.stealth.net/pub/mirrors/ftp.xemacs.org/pub/xemacs/ - + ftp://metalab.unc.edu/pub/packages/editors/xemacs/ - + http://metalab.unc.edu/pub/packages/editors/xemacs/ - - o South America - - + Brazil - - + ftp.br.xemacs.org (FTP) - -* Asia - - Goto Mirror Index - - o Japan - - + ftp.jp.xemacs.org (FTP) - - Secondary Mirrors - + ftp://ftp.jaist.ac.jp/pub/GNU/xemacs/ - + ftp://ring.aist.go.jp/pub/text/xemacs/ - + ftp://ring.asahi-net.or.jp/pub/text/xemacs/ - + ftp://sunsite.sut.ac.jp/pub/archives/packages/xemacs/ - + ftp://ftp.dti.ad.jp/pub/unix/editor/xemacs/ - + ftp://mirror.nucba.ac.jp/mirror/xemacs/ - - o Korea - - + ftp.kr.xemacs.org (FTP) - - o Taiwan - - + ftp.tw.xemacs.org (FTP) - + ftp.tw.xemacs.org (HTTP) - -* Australia - - Goto Mirror Index - - o Queensland - - + ftp.au.xemacs.org (FTP) - + ftp.au.xemacs.org (HTTP) - - Secondary Mirrors - + ftp://mirror.aarnet.edu.au/pub/xemacs/ - + http://mirror.aarnet.edu.au/pub/xemacs/ - -* Europe - - Goto Mirror Index - - o Austria - - + ftp.at.xemacs.org (FTP) - + ftp.at.xemacs.org (HTTP) - - o Belgium - - + ftp.be.xemacs.org (FTP) - + ftp.be.xemacs.org (HTTP) - - o Denmark - - + ftp.dk.xemacs.org (FTP) - + ftp.dk.xemacs.org (HTTP) - - o Finland - - + ftp.fi.xemacs.org (FTP) - + ftp.fi.xemacs.org (HTTP) - - o France - - + ftp.fr.xemacs.org (FTP) - + ftp.fr.xemacs.org (HTTP) - - Secondary Mirrors - + ftp://ftp.pasteur.fr/pub/computing/xemacs/ - - o Germany - - + ftp.de.xemacs.org (FTP) - + ftp.de.xemacs.org (HTTP) - - Secondary Mirrors - + ftp://ftp.tu-darmstadt.de/pub/editors/xemacs/ - - o Hungary - - + ftp.hu.xemacs.org (FTP) - + ftp.hu.xemacs.org (HTTP) - - o Ireland - - + ftp.ie.xemacs.org (FTP) - + ftp.ie.xemacs.org (HTTP) - - o Italy - - + ftp.it.xemacs.org (FTP) - + ftp.it.xemacs.org (HTTP) - - o Norway - - + ftp.no.xemacs.org (FTP) - + ftp.no.xemacs.org (HTTP) - - o Poland - - + ftp.pl.xemacs.org (FTP) - + ftp.pl.xemacs.org (HTTP) - - o Russia - - + ftp.ru.xemacs.org (FTP) - + ftp.ru.xemacs.org (HTTP) - - o Slovakia - - + ftp.sk.xemacs.org (FTP) - + ftp.sk.xemacs.org (HTTP) - - o Sweden - - + ftp.se.xemacs.org (FTP) - + ftp.se.xemacs.org (HTTP) - - o Switzerland - - + ftp.ch.xemacs.org (FTP) - + ftp.ch.xemacs.org (HTTP) - - o United Kingdom - - + ftp.uk.xemacs.org (FTP) - + ftp.uk.xemacs.org (HTTP) - - Secondary Mirrors - + ftp://sunsite.doc.ic.ac.uk/packages/xemacs/ - + http://sunsite.doc.ic.ac.uk/packages/xemacs/ - -* Middle East - - Goto Mirror Index - - o Saudi Arabia - - + ftp.sa.xemacs.org (FTP) - + ftp.sa.xemacs.org (HTTP) - - -The most up-to-date list of distribution sites can always be found on -the XEmacs WWW page at http://www.xemacs.org/Download/. Try to pick a -site that is networkologically close to you. If you know of other -mirrors of the XEmacs archives, please send e-mail to - and we will list them here as well. - -There are mailing lists and newsgroups specifically for discussing and -reporting bugs in XEmacs; see the file MAILINGLISTS in this directory. - ------------------------------------------------------------------------ - - How to get GNU Software by Internet FTP or by UUCP: - -The XEmacs project is separate from and not managed by the GNU -project. The latest GNU project FTP and UUCP availability information -can be found at ftp://ftp.gnu.org/gnu/GNUinfo/FTP - diff -r 7edc33019aa4 -r b7b90f750a78 etc/GNU --- a/etc/GNU Mon Jan 31 20:01:50 2005 +0000 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000 @@ -1,532 +0,0 @@ -Copyright (C) 1985, 1993 Free Software Foundation, Inc. - - Permission is granted to anyone to make or distribute verbatim copies -of this document, in any medium, provided that the copyright notice and -permission notice are preserved, and that the distributor grants the -recipient permission for further redistribution as permitted by this -notice. - - Modified versions may not be made. - -The GNU Manifesto -***************** - - The GNU Manifesto which appears below was written by Richard - Stallman at the beginning of the GNU project, to ask for - participation and support. For the first few years, it was - updated in minor ways to account for developments, but now it - seems best to leave it unchanged as most people have seen it. - - Since that time, we have learned about certain common - misunderstandings that different wording could help avoid. - Footnotes added in 1993 help clarify these points. - - For up-to-date information about the available GNU software, - please see the latest issue of the GNU's Bulletin. The list is - much too long to include here. - -What's GNU? Gnu's Not Unix! -============================ - - GNU, which stands for Gnu's Not Unix, is the name for the complete -Unix-compatible software system which I am writing so that I can give it -away free to everyone who can use it.(1) Several other volunteers are -helping me. Contributions of time, money, programs and equipment are -greatly needed. - - So far we have an Emacs text editor with Lisp for writing editor -commands, a source level debugger, a yacc-compatible parser generator, -a linker, and around 35 utilities. A shell (command interpreter) is -nearly completed. A new portable optimizing C compiler has compiled -itself and may be released this year. An initial kernel exists but -many more features are needed to emulate Unix. When the kernel and -compiler are finished, it will be possible to distribute a GNU system -suitable for program development. We will use TeX as our text -formatter, but an nroff is being worked on. We will use the free, -portable X window system as well. After this we will add a portable -Common Lisp, an Empire game, a spreadsheet, and hundreds of other -things, plus on-line documentation. We hope to supply, eventually, -everything useful that normally comes with a Unix system, and more. - - GNU will be able to run Unix programs, but will not be identical to -Unix. We will make all improvements that are convenient, based on our -experience with other operating systems. In particular, we plan to -have longer file names, file version numbers, a crashproof file system, -file name completion perhaps, terminal-independent display support, and -perhaps eventually a Lisp-based window system through which several -Lisp programs and ordinary Unix programs can share a screen. Both C -and Lisp will be available as system programming languages. We will -try to support UUCP, MIT Chaosnet, and Internet protocols for -communication. - - GNU is aimed initially at machines in the 68000/16000 class with -virtual memory, because they are the easiest machines to make it run -on. The extra effort to make it run on smaller machines will be left -to someone who wants to use it on them. - - To avoid horrible confusion, please pronounce the `G' in the word -`GNU' when it is the name of this project. - -Why I Must Write GNU -==================== - - I consider that the golden rule requires that if I like a program I -must share it with other people who like it. Software sellers want to -divide the users and conquer them, making each user agree not to share -with others. I refuse to break solidarity with other users in this -way. I cannot in good conscience sign a nondisclosure agreement or a -software license agreement. For years I worked within the Artificial -Intelligence Lab to resist such tendencies and other inhospitalities, -but eventually they had gone too far: I could not remain in an -institution where such things are done for me against my will. - - So that I can continue to use computers without dishonor, I have -decided to put together a sufficient body of free software so that I -will be able to get along without any software that is not free. I -have resigned from the AI lab to deny MIT any legal excuse to prevent -me from giving GNU away. - -Why GNU Will Be Compatible with Unix -==================================== - - Unix is not my ideal system, but it is not too bad. The essential -features of Unix seem to be good ones, and I think I can fill in what -Unix lacks without spoiling them. And a system compatible with Unix -would be convenient for many other people to adopt. - -How GNU Will Be Available -========================= - - GNU is not in the public domain. Everyone will be permitted to -modify and redistribute GNU, but no distributor will be allowed to -restrict its further redistribution. That is to say, proprietary -modifications will not be allowed. I want to make sure that all -versions of GNU remain free. - -Why Many Other Programmers Want to Help -======================================= - - I have found many other programmers who are excited about GNU and -want to help. - - Many programmers are unhappy about the commercialization of system -software. It may enable them to make more money, but it requires them -to feel in conflict with other programmers in general rather than feel -as comrades. The fundamental act of friendship among programmers is the -sharing of programs; marketing arrangements now typically used -essentially forbid programmers to treat others as friends. The -purchaser of software must choose between friendship and obeying the -law. Naturally, many decide that friendship is more important. But -those who believe in law often do not feel at ease with either choice. -They become cynical and think that programming is just a way of making -money. - - By working on and using GNU rather than proprietary programs, we can -be hospitable to everyone and obey the law. In addition, GNU serves as -an example to inspire and a banner to rally others to join us in -sharing. This can give us a feeling of harmony which is impossible if -we use software that is not free. For about half the programmers I -talk to, this is an important happiness that money cannot replace. - -How You Can Contribute -====================== - - I am asking computer manufacturers for donations of machines and -money. I'm asking individuals for donations of programs and work. - - One consequence you can expect if you donate machines is that GNU -will run on them at an early date. The machines should be complete, -ready to use systems, approved for use in a residential area, and not -in need of sophisticated cooling or power. - - I have found very many programmers eager to contribute part-time -work for GNU. For most projects, such part-time distributed work would -be very hard to coordinate; the independently-written parts would not -work together. But for the particular task of replacing Unix, this -problem is absent. A complete Unix system contains hundreds of utility -programs, each of which is documented separately. Most interface -specifications are fixed by Unix compatibility. If each contributor -can write a compatible replacement for a single Unix utility, and make -it work properly in place of the original on a Unix system, then these -utilities will work right when put together. Even allowing for Murphy -to create a few unexpected problems, assembling these components will -be a feasible task. (The kernel will require closer communication and -will be worked on by a small, tight group.) - - If I get donations of money, I may be able to hire a few people full -or part time. The salary won't be high by programmers' standards, but -I'm looking for people for whom building community spirit is as -important as making money. I view this as a way of enabling dedicated -people to devote their full energies to working on GNU by sparing them -the need to make a living in another way. - -Why All Computer Users Will Benefit -=================================== - - Once GNU is written, everyone will be able to obtain good system -software free, just like air.(2) - - This means much more than just saving everyone the price of a Unix -license. It means that much wasteful duplication of system programming -effort will be avoided. This effort can go instead into advancing the -state of the art. - - Complete system sources will be available to everyone. As a result, -a user who needs changes in the system will always be free to make them -himself, or hire any available programmer or company to make them for -him. Users will no longer be at the mercy of one programmer or company -which owns the sources and is in sole position to make changes. - - Schools will be able to provide a much more educational environment -by encouraging all students to study and improve the system code. -Harvard's computer lab used to have the policy that no program could be -installed on the system if its sources were not on public display, and -upheld it by actually refusing to install certain programs. I was very -much inspired by this. - - Finally, the overhead of considering who owns the system software -and what one is or is not entitled to do with it will be lifted. - - Arrangements to make people pay for using a program, including -licensing of copies, always incur a tremendous cost to society through -the cumbersome mechanisms necessary to figure out how much (that is, -which programs) a person must pay for. And only a police state can -force everyone to obey them. Consider a space station where air must -be manufactured at great cost: charging each breather per liter of air -may be fair, but wearing the metered gas mask all day and all night is -intolerable even if everyone can afford to pay the air bill. And the -TV cameras everywhere to see if you ever take the mask off are -outrageous. It's better to support the air plant with a head tax and -chuck the masks. - - Copying all or parts of a program is as natural to a programmer as -breathing, and as productive. It ought to be as free. - -Some Easily Rebutted Objections to GNU's Goals -============================================== - - "Nobody will use it if it is free, because that means they can't - rely on any support." - - "You have to charge for the program to pay for providing the - support." - - If people would rather pay for GNU plus service than get GNU free -without service, a company to provide just service to people who have -obtained GNU free ought to be profitable.(3) - - We must distinguish between support in the form of real programming -work and mere handholding. The former is something one cannot rely on -from a software vendor. If your problem is not shared by enough -people, the vendor will tell you to get lost. - - If your business needs to be able to rely on support, the only way -is to have all the necessary sources and tools. Then you can hire any -available person to fix your problem; you are not at the mercy of any -individual. With Unix, the price of sources puts this out of -consideration for most businesses. With GNU this will be easy. It is -still possible for there to be no available competent person, but this -problem cannot be blamed on distribution arrangements. GNU does not -eliminate all the world's problems, only some of them. - - Meanwhile, the users who know nothing about computers need -handholding: doing things for them which they could easily do -themselves but don't know how. - - Such services could be provided by companies that sell just -hand-holding and repair service. If it is true that users would rather -spend money and get a product with service, they will also be willing -to buy the service having got the product free. The service companies -will compete in quality and price; users will not be tied to any -particular one. Meanwhile, those of us who don't need the service -should be able to use the program without paying for the service. - - "You cannot reach many people without advertising, and you must - charge for the program to support that." - - "It's no use advertising a program people can get free." - - There are various forms of free or very cheap publicity that can be -used to inform numbers of computer users about something like GNU. But -it may be true that one can reach more microcomputer users with -advertising. If this is really so, a business which advertises the -service of copying and mailing GNU for a fee ought to be successful -enough to pay for its advertising and more. This way, only the users -who benefit from the advertising pay for it. - - On the other hand, if many people get GNU from their friends, and -such companies don't succeed, this will show that advertising was not -really necessary to spread GNU. Why is it that free market advocates -don't want to let the free market decide this?(4) - - "My company needs a proprietary operating system to get a - competitive edge." - - GNU will remove operating system software from the realm of -competition. You will not be able to get an edge in this area, but -neither will your competitors be able to get an edge over you. You and -they will compete in other areas, while benefiting mutually in this -one. If your business is selling an operating system, you will not -like GNU, but that's tough on you. If your business is something else, -GNU can save you from being pushed into the expensive business of -selling operating systems. - - I would like to see GNU development supported by gifts from many -manufacturers and users, reducing the cost to each.(5) - - "Don't programmers deserve a reward for their creativity?" - - If anything deserves a reward, it is social contribution. -Creativity can be a social contribution, but only in so far as society -is free to use the results. If programmers deserve to be rewarded for -creating innovative programs, by the same token they deserve to be -punished if they restrict the use of these programs. - - "Shouldn't a programmer be able to ask for a reward for his - creativity?" - - There is nothing wrong with wanting pay for work, or seeking to -maximize one's income, as long as one does not use means that are -destructive. But the means customary in the field of software today -are based on destruction. - - Extracting money from users of a program by restricting their use of -it is destructive because the restrictions reduce the amount and the -ways that the program can be used. This reduces the amount of wealth -that humanity derives from the program. When there is a deliberate -choice to restrict, the harmful consequences are deliberate destruction. - - The reason a good citizen does not use such destructive means to -become wealthier is that, if everyone did so, we would all become -poorer from the mutual destructiveness. This is Kantian ethics; or, -the Golden Rule. Since I do not like the consequences that result if -everyone hoards information, I am required to consider it wrong for one -to do so. Specifically, the desire to be rewarded for one's creativity -does not justify depriving the world in general of all or part of that -creativity. - - "Won't programmers starve?" - - I could answer that nobody is forced to be a programmer. Most of us -cannot manage to get any money for standing on the street and making -faces. But we are not, as a result, condemned to spend our lives -standing on the street making faces, and starving. We do something -else. - - But that is the wrong answer because it accepts the questioner's -implicit assumption: that without ownership of software, programmers -cannot possibly be paid a cent. Supposedly it is all or nothing. - - The real reason programmers will not starve is that it will still be -possible for them to get paid for programming; just not paid as much as -now. - - Restricting copying is not the only basis for business in software. -It is the most common basis because it brings in the most money. If it -were prohibited, or rejected by the customer, software business would -move to other bases of organization which are now used less often. -There are always numerous ways to organize any kind of business. - - Probably programming will not be as lucrative on the new basis as it -is now. But that is not an argument against the change. It is not -considered an injustice that sales clerks make the salaries that they -now do. If programmers made the same, that would not be an injustice -either. (In practice they would still make considerably more than -that.) - - "Don't people have a right to control how their creativity is - used?" - - "Control over the use of one's ideas" really constitutes control over -other people's lives; and it is usually used to make their lives more -difficult. - - People who have studied the issue of intellectual property rights -carefully (such as lawyers) say that there is no intrinsic right to -intellectual property. The kinds of supposed intellectual property -rights that the government recognizes were created by specific acts of -legislation for specific purposes. - - For example, the patent system was established to encourage -inventors to disclose the details of their inventions. Its purpose was -to help society rather than to help inventors. At the time, the life -span of 17 years for a patent was short compared with the rate of -advance of the state of the art. Since patents are an issue only among -manufacturers, for whom the cost and effort of a license agreement are -small compared with setting up production, the patents often do not do -much harm. They do not obstruct most individuals who use patented -products. - - The idea of copyright did not exist in ancient times, when authors -frequently copied other authors at length in works of non-fiction. This -practice was useful, and is the only way many authors' works have -survived even in part. The copyright system was created expressly for -the purpose of encouraging authorship. In the domain for which it was -invented--books, which could be copied economically only on a printing -press--it did little harm, and did not obstruct most of the individuals -who read the books. - - All intellectual property rights are just licenses granted by society -because it was thought, rightly or wrongly, that society as a whole -would benefit by granting them. But in any particular situation, we -have to ask: are we really better off granting such license? What kind -of act are we licensing a person to do? - - The case of programs today is very different from that of books a -hundred years ago. The fact that the easiest way to copy a program is -from one neighbor to another, the fact that a program has both source -code and object code which are distinct, and the fact that a program is -used rather than read and enjoyed, combine to create a situation in -which a person who enforces a copyright is harming society as a whole -both materially and spiritually; in which a person should not do so -regardless of whether the law enables him to. - - "Competition makes things get done better." - - The paradigm of competition is a race: by rewarding the winner, we -encourage everyone to run faster. When capitalism really works this -way, it does a good job; but its defenders are wrong in assuming it -always works this way. If the runners forget why the reward is offered -and become intent on winning, no matter how, they may find other -strategies--such as, attacking other runners. If the runners get into -a fist fight, they will all finish late. - - Proprietary and secret software is the moral equivalent of runners -in a fist fight. Sad to say, the only referee we've got does not seem -to object to fights; he just regulates them ("For every ten yards you -run, you can fire one shot"). He really ought to break them up, and -penalize runners for even trying to fight. - - "Won't everyone stop programming without a monetary incentive?" - - Actually, many people will program with absolutely no monetary -incentive. Programming has an irresistible fascination for some -people, usually the people who are best at it. There is no shortage of -professional musicians who keep at it even though they have no hope of -making a living that way. - - But really this question, though commonly asked, is not appropriate -to the situation. Pay for programmers will not disappear, only become -less. So the right question is, will anyone program with a reduced -monetary incentive? My experience shows that they will. - - For more than ten years, many of the world's best programmers worked -at the Artificial Intelligence Lab for far less money than they could -have had anywhere else. They got many kinds of non-monetary rewards: -fame and appreciation, for example. And creativity is also fun, a -reward in itself. - - Then most of them left when offered a chance to do the same -interesting work for a lot of money. - - What the facts show is that people will program for reasons other -than riches; but if given a chance to make a lot of money as well, they -will come to expect and demand it. Low-paying organizations do poorly -in competition with high-paying ones, but they do not have to do badly -if the high-paying ones are banned. - - "We need the programmers desperately. If they demand that we stop - helping our neighbors, we have to obey." - - You're never so desperate that you have to obey this sort of demand. -Remember: millions for defense, but not a cent for tribute! - - "Programmers need to make a living somehow." - - In the short run, this is true. However, there are plenty of ways -that programmers could make a living without selling the right to use a -program. This way is customary now because it brings programmers and -businessmen the most money, not because it is the only way to make a -living. It is easy to find other ways if you want to find them. Here -are a number of examples. - - A manufacturer introducing a new computer will pay for the porting of -operating systems onto the new hardware. - - The sale of teaching, hand-holding and maintenance services could -also employ programmers. - - People with new ideas could distribute programs as freeware, asking -for donations from satisfied users, or selling hand-holding services. -I have met people who are already working this way successfully. - - Users with related needs can form users' groups, and pay dues. A -group would contract with programming companies to write programs that -the group's members would like to use. - - All sorts of development can be funded with a Software Tax: - - Suppose everyone who buys a computer has to pay x percent of the - price as a software tax. The government gives this to an agency - like the NSF to spend on software development. - - But if the computer buyer makes a donation to software development - himself, he can take a credit against the tax. He can donate to - the project of his own choosing--often, chosen because he hopes to - use the results when it is done. He can take a credit for any - amount of donation up to the total tax he had to pay. - - The total tax rate could be decided by a vote of the payers of the - tax, weighted according to the amount they will be taxed on. - - The consequences: - - * The computer-using community supports software development. - - * This community decides what level of support is needed. - - * Users who care which projects their share is spent on can - choose this for themselves. - - In the long run, making programs free is a step toward the -post-scarcity world, where nobody will have to work very hard just to -make a living. People will be free to devote themselves to activities -that are fun, such as programming, after spending the necessary ten -hours a week on required tasks such as legislation, family counseling, -robot repair and asteroid prospecting. There will be no need to be -able to make a living from programming. - - We have already greatly reduced the amount of work that the whole -society must do for its actual productivity, but only a little of this -has translated itself into leisure for workers because much -nonproductive activity is required to accompany productive activity. -The main causes of this are bureaucracy and isometric struggles against -competition. Free software will greatly reduce these drains in the -area of software production. We must do this, in order for technical -gains in productivity to translate into less work for us. - - ---------- Footnotes ---------- - - (1) The wording here was careless. The intention was that nobody -would have to pay for *permission* to use the GNU system. But the -words don't make this clear, and people often interpret them as saying -that copies of GNU should always be distributed at little or no charge. -That was never the intent; later on, the manifesto mentions the -possibility of companies providing the service of distribution for a -profit. Subsequently I have learned to distinguish carefully between -"free" in the sense of freedom and "free" in the sense of price. Free -software is software that users have the freedom to distribute and -change. Some users may obtain copies at no charge, while others pay to -obtain copies--and if the funds help support improving the software, so -much the better. The important thing is that everyone who has a copy -has the freedom to cooperate with others in using it. - - (2) This is another place I failed to distinguish carefully between -the two different meanings of "free". The statement as it stands is -not false--you can get copies of GNU software at no charge, from your -friends or over the net. But it does suggest the wrong idea. - - (3) Several such companies now exist. - - (4) The Free Software Foundation raises most of its funds from a -distribution service, although it is a charity rather than a company. -If *no one* chooses to obtain copies by ordering the from the FSF, it -will be unable to do its work. But this does not mean that proprietary -restrictions are justified to force every user to pay. If a small -fraction of all the users order copies from the FSF, that is sufficient -to keep the FSF afloat. So we ask users to choose to support us in -this way. Have you done your part? - - (5) A group of computer companies recently pooled funds to support -maintenance of the GNU C Compiler. - diff -r 7edc33019aa4 -r b7b90f750a78 etc/LPF --- a/etc/LPF Mon Jan 31 20:01:50 2005 +0000 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000 @@ -1,122 +0,0 @@ - Protect Your Freedom to Write Programs - Join the League for Programming Freedom - (Version of February 3, 1994) - -Ten years ago, programmers were allowed to write programs using all -the techniques they knew, and providing whatever features they felt -were useful. This is no longer the case. New monopolies, known as -software patents and interface copyrights, have taken away our freedom -of expression and our ability to do a good job. - -"Look and feel" lawsuits attempt to monopolize well-known command -languages; some have succeeded. Copyrights on command languages -enforce gratuitous incompatibility, close opportunities for -competition, and stifle incremental improvements. - -Software patents are even more dangerous; they make every design -decision in the development of a program carry a risk of a lawsuit, -with draconian pretrial seizure. It is difficult and expensive to -find out whether the techniques you consider using are patented; it is -impossible to find out whether they will be patented in the future. - -The League for Programming Freedom is a grass-roots organization of -professors, students, businessmen, programmers and users dedicated to -bringing back the freedom to write programs. The League is not -opposed to the legal system that Congress expressly established for -software--copyright on individual programs. Our aim is to reverse the -recent changes that prevent programmers from doing their work. - -The League works to abolish the new monopolies by publishing articles, -talking with public officials, denouncing egregious offenders, and -filing amicus curiae briefs, most notably against Lotus in its suit -against Borland. We testified twice at the recent Patent Office -hearings on software patents. We welcome suggestions for other -activities, as well as help in carrying them out. - -Membership dues in the League are $42 per year for programmers, -managers and professionals; $10.50 for students; $21 for others. -Please give more if you can. The League's funds will be used for -filing briefs; for printing handouts, buttons and signs; whatever will -persuade the courts, the legislators, and the people. You may not get -anything personally for your dues--except for the freedom to write -programs. The League is a non-profit corporation, but not considered -a tax-exempt charity. However, for those self-employed in software, -the dues can be a business expense. - -The League needs both activist members and members who only pay their -dues. We also greatly need additional corporate members; contact us -for information. - -If you have any questions, please write to the League, phone -+1 617 621 7084, or send Internet mail to lpf@uunet.uu.net. - - Chris Hofstader, President - Dean Anderson, Secretary - Aubrey Jaffer, Treasurer - -Chris Hofstader can be reached at (617) 492-0023; FAX (617) 497-1632. - To join, please send a check and the following information to: - - League for Programming Freedom - 1 Kendall Square #143 - P.O.Box 9171 - Cambridge, Massachusetts 02139 - -(Outside the US, please send a check in US dollars on a bank -having a US correspondent bank, to save us check cashing fees.) - -Your name: - - -The address for League mailings, a few each year; please indicate -whether it is your home address or your work address: - - - -The company you work for, and your position: - - -Your phone numbers (home, work or both): - - -Your email address, so we can contact you for demonstrations or for -writing letters. (If you don't want us to contact you for these -things, please say so, but please give us your email address anyway -so we can save paper and postage by sending you the newsletter by email.) - - -Is there anything about you which would enable your endorsement of the -LPF to impress the public? For example, if you are or have been a -professor or an executive, or have written software that has a good -reputation, please tell us. - - - -Would you like to help with LPF activities? - - - - -The corporate charter of the League for Programming Freedom states: - - The purpose of the corporation is to engage in the following - activities: - - 1. To determine the existence of, and warn the public about - restrictions and monopolies on classes of computer programs where such - monopolies prevent or restrict the right to develop certain types of - computer programs. - - 2. To develop countermeasures and initiatives, in the public interest, - effective to block or otherwise prevent or restrain such monopolistic - activities including education, research, publications, public - assembly, legislative testimony, and intervention in court proceedings - involving public interest issues (as a friend of the court). - - 3. To engage in any business or other activity in service of and - related to the foregoing paragraphs that lawfully may be carried on - by a corporation organized under Chapter 180 of the Massachusetts - General Laws. - -The officers and directors of the League will be elected annually by -the members. diff -r 7edc33019aa4 -r b7b90f750a78 etc/MACHINES --- a/etc/MACHINES Mon Jan 31 20:01:50 2005 +0000 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000 @@ -1,45 +0,0 @@ -This is a list of the status of XEmacs on various machines and systems. -See PROBLEMS for particular problems and possible workarounds. - -Much effort has gone into making XEmacs work on as many different -machines, configurations, and compilers as possible. - -Much effort has gone into making XEmacs 64-bit clean. - -Much effort has gone into removing system-specific code, and replacing -such code with autodetection at configure time. - -The XEmacs core should build "out of the box" on most Unix-like systems. - -XEmacs 21.2 was tested and `make check' succeeded on these Unix -configurations as of 2001-02-10: - -alphaev56-dec-osf4.0e (both Compaq C and gcc) -i386-unknown-freebsd4.2 -i386-unknown-netbsdelf1.5 -i586-sco-sysv5uw7.0.1 (both SCO's cc and gcc) -i686-pc-linux-gnu -hppa2.0-hp-hpux10.20 (both HP's ANSI cc and gcc) -mips-sgi-irix6.5 (both MIPSpro cc and gcc) -rs6000-ibm-aix4.3.0.0 (both IBM's xlc and gcc) -sparc-sun-solaris2.6 (both Sun's Forte C and gcc) -sparc-sun-solaris2.7 (both Sun's Forte C and gcc) -sparc-sun-sunos4.1.4 (gcc) - -Some systems have a dual mode 32-bit/64-bit compiler. On most of -these, XEmacs requires the --pdump configure option to build -correctly with the 64-bit version of the compiler. - -mips-sgi-irix6.5, CC="gcc -mabi=64" -mips-sgi-irix6.5, CC="cc -64" -rs6000-ibm-aix4.3.0.0, CC="cc -q64" - -On most of these systems, XEmacs also builds with a C++ compiler, -but not "out of the box". This feature is only for use by the -maintainers. - -XEmacs 21.2 is known _not_ to work on any machines with m680x0 -processors. Sorry, all you sun3 and Unix PC nostalgia buffs out there. - -VMS has never been supported by XEmacs. In fact, all the old VMS code -inherited from Emacs has been removed. Sorry, all you VMS fans out there. diff -r 7edc33019aa4 -r b7b90f750a78 etc/MAILINGLISTS --- a/etc/MAILINGLISTS Mon Jan 31 20:01:50 2005 +0000 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000 @@ -1,112 +0,0 @@ - - XEmacs Electronic Mailing Lists. Last Modified: 1999-11-08 - -XEmacs has its own mailing lists and newsgroup which are distinct from -the FSF GNU Emacs mailing lists and newsgroups. The mailing lists are: - -xemacs@xemacs.org comp.emacs.xemacs bi-directional gateway. - - xemacs is an open list for discussion and bug reporting for - XEmacs. This mailing list is bi-directionally gatewayed with the - USENET newsgroup comp.emacs.xemacs. - -xemacs-announce@xemacs.org XEmacs Announcements. - - xemacs-announce is a read-only, low volume list for announcements - concerning the XEmacs project and new releases of the XEmacs - software. - -xemacs-beta@xemacs.org XEmacs Beta Testers. - - xemacs-beta is an open list for bug reports and general - communication about beta versions of XEmacs. - -xemacs-build-reports@xemacs.org XEmacs Build Report Submissions. - - xemacs-build-reports is an open list for submission of build-reports - on beta versions of XEmacs. For information on what the - build-reports should contain, please see the `etc/BETA' file which - is included in each beta distribution. - -xemacs-cvs@xemacs.org XEmacs CVS Commit Notices. - - xemacs-cvs is a read-only list for notices and information on what - has been committed to the XEmacs CVS trees, by whom, and for - what. (For more information on the XEmacs CVS Archive: - http://cvs.xemacs.org/.) - -xemacs-mule@xemacs.org XEmacs International Extensions. - - xemacs-mule is an open mailing list for discussion of International - extensions to XEmacs including Mule, XIM, I18n issues, etc, and is - not confined to developmental issues. This list is not restricted - to English, postings in all languages are welcome. - -xemacs-nt@xemacs.org XEmacs on Windows NT/98/95. - - xemacs-nt is a developer's only mailing list and is intended for - people who wish to work actively on the porting of XEmacs to - Microsoft Windows NT and Microsoft Windows 98/95. - -xemacs-patches@xemacs.org XEmacs Patch Submissions. - - xemacs-patches is an open, moderated list for submission of patches - to the XEmacs distribution and its packages. Anyone may subscribe or - submit to xemacs-patches, but all submissions are reviewed by the - list moderator before they are distributed to the list. Discussion - is not appropriate on xemacs-patches. - -xemacs-users-ja@xemacs.org XEmacs (Japanese). - - xemacs-users-ja is an open list for discussion and bug reporting for - XEmacs. Japanese is the preferred language of discussion. It is not - gated to comp.emacs.xemacs or the xemacs list. For fastest - response, bugs not specifically related to Japanese or Mule features - should be reported on xemacs (in English). - -xemacs-beta-ja@xemacs.org XEmacs Beta (Japanese). - - xemacs-beta-ja is an open list for bug reports and general - communication about beta versions of XEmacs, especially features - related to Mule and Japanese-handling. Japanese is the preferred - language of discussion. Bugs not specifically related to Japanese or - Mule features should be reported on xemacs-beta (in English). Please - consider sending bug reports on Mule to xemacs-mule, in English. - -The most up to date information on the mailing lists can always be -found at http://www.xemacs.org/. - -Subscriptions: - -Subscription to all the lists is accomplished by sending an e-mail -message to LISTNAME-request@xemacs.org with `subscribe' (without the -quotes) as the BODY of the message. - -To unsubscribe, send an e-mail to LISTNAME-request@xemacs.org with -`unsubscribe' (without the quotes) as the BODY of the message. - -List Archives: - -A browsable and searchable archive of these lists is available at -http://www.xemacs.org/list-archives/. - -Problems: - -Any comments, questions, or complaints about the lists should be -brought to the attention of the XEmacs Mailing List Manager -. - ------------------------------------------------------------------------ - - GNU Project Electronic Mailing Lists and gnUSENET Newsgroups: - -The XEmacs project is separate from and not managed by the GNU -project. The latest information about the GNU project mailing lists -can be found at ftp://ftp.gnu.org/gnu/GNUinfo/MAILINGLISTS - -Please do NOT send messages about problems with XEmacs to the FSF GNU -Emacs newsgroups and mailing lists unless you are sure that the -problem you are reporting is a problem with both versions of GNU -Emacs. People who aren't subscribed to the XEmacs mailing list most -likely are not interested in hearing about problems with it. - diff -r 7edc33019aa4 -r b7b90f750a78 etc/MORE.STUFF --- a/etc/MORE.STUFF Mon Jan 31 20:01:50 2005 +0000 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000 @@ -1,52 +0,0 @@ -More Neat Stuff for your Emacs -*-Outline-*- - -This file describes GNU Emacs programs and resources that are maintained -by other people. Some of these may become part of the Emacs distribution -in the future. - -* The LCD archive - -There is a large collection of Emacs Lisp code available for FTP at -archive.cis.ohio-state.edu; it is actively maintained by Dave Brennan - and Dave Sill . - -To get started using this archive, do: - - ftp archive.cis.ohio-state.edu - -Once you're in FTP, do - - cd pub/gnu/emacs/elisp-archive - bin - get lispdir.el.Z - get LCD-datafile.Z - -and exit. Then do: - - compress -d *.Z - -The lispdir.el package will help you search for useful packages in the -LCD-datafile, which is a list of the archive constants. It will even -fetch them for you on command. - -* Eric Ludlam's etalk system - -Eric Ludlam has written a C program and Emacs Lisp code to do Internet talk -through an Emacs window. The package also includes Emacs Lisp code which -assists you in using talk to play a number of different interactive games. - -This system seems to be quite nicely put together and is well documented -with a texinfo file that you can integrate into Emacs's own on-line help. -It's too large and specialized to include in the Emacs distribution, though. - -Sources of this system are available for FTP at - - nic.umass.edu 128.119.166.14 - -Look under pub/contrib. As of March 23 1993, there are two relevant files: - - pub/contrib/etalk0.6B.tar.Z --- sources of the talk system - pub/contrib/egames0.6B.tar.Z --- more game-support files - -We don't know whether this can use the additional features in GNU talk. - diff -r 7edc33019aa4 -r b7b90f750a78 etc/MOTIVATION --- a/etc/MOTIVATION Mon Jan 31 20:01:50 2005 +0000 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000 @@ -1,176 +0,0 @@ -STUDIES FIND REWARD OFTEN NO MOTIVATOR - -Creativity and intrinsic interest diminish if task is done for gain - -By Alfie Kohn -Special to the Boston Globe -[reprinted with permission of the author - from the Monday 19 January 1987 Boston Globe] - -In the laboratory, rats get Rice Krispies. In the classroom the top -students get A's, and in the factory or office the best workers get -raises. It's an article of faith for most of us that rewards promote -better performance. - -But a growing body of research suggests that this law is not nearly as -ironclad as was once thought. Psychologists have been finding that -rewards can lower performance levels, especially when the performance -involves creativity. - -A related series of studies shows that intrinsic interest in a task - -the sense that something is worth doing for its own sake - typically -declines when someone is rewarded for doing it. - -If a reward - money, awards, praise, or winning a contest - comes to -be seen as the reason one is engaging in an activity, that activity -will be viewed as less enjoyable in its own right. - -With the exception of some behaviorists who doubt the very existence -of intrinsic motivation, these conclusions are now widely accepted -among psychologists. Taken together, they suggest we may unwittingly -be squelching interest and discouraging innovation among workers, -students and artists. - -The recognition that rewards can have counter-productive effects is -based on a variety of studies, which have come up with such findings -as these: Young children who are rewarded for drawing are less likely -to draw on their own that are children who draw just for the fun of -it. Teenagers offered rewards for playing word games enjoy the games -less and do not do as well as those who play with no rewards. -Employees who are praised for meeting a manager's expectations suffer -a drop in motivation. - -Much of the research on creativity and motivation has been performed -by Theresa Amabile, associate professor of psychology at Brandeis -University. In a paper published early last year on her most recent -study, she reported on experiments involving elementary school and -college students. Both groups were asked to make "silly" collages. -The young children were also asked to invent stories. - -The least-creative projects, as rated by several teachers, were done -by those students who had contracted for rewards. "It may be that -commissioned work will, in general, be less creative than work that is -done out of pure interest," Amabile said. - -In 1985, Amabile asked 72 creative writers at Brandeis and at Boston -University to write poetry. Some students then were given a list of -extrinsic (external) reasons for writing, such as impressing teachers, -making money and getting into graduate school, and were asked to think -about their own writing with respect to these reasons. Others were -given a list of intrinsic reasons: the enjoyment of playing with -words, satisfaction from self-expression, and so forth. A third group -was not given any list. All were then asked to do more writing. - -The results were clear. Students given the extrinsic reasons not only -wrote less creatively than the others, as judged by 12 independent -poets, but the quality of their work dropped significantly. Rewards, -Amabile says, have this destructive effect primarily with creative -tasks, including higher-level problem-solving. "The more complex the -activity, the more it's hurt by extrinsic reward," she said. - -But other research shows that artists are by no means the only ones -affected. - -In one study, girls in the fifth and sixth grades tutored younger -children much less effectively if they were promised free movie -tickets for teaching well. The study, by James Gabarino, now -president of Chicago's Erikson Institute for Advanced Studies in Child -Development, showed that tutors working for the reward took longer to -communicate ideas, got frustrated more easily, and did a poorer job in -the end than those who were not rewarded. - -Such findings call into question the widespread belief that money is -an effective and even necessary way to motivate people. They also -challenge the behaviorist assumption that any activity is more likely -to occur if it is rewarded. Amabile says her research "definitely -refutes the notion that creativity can be operantly conditioned." - -But Kenneth McGraw, associate professor of psychology at the -University of Mississippi, cautions that this does not mean -behaviorism itself has been invalidated. "The basic principles of -reinforcement and rewards certainly work, but in a restricted context" -- restricted, that is, to tasks that are not especially interesting. - -Researchers offer several explanations for their surprising findings -about rewards and performance. - -First, rewards encourage people to focus narrowly on a task, to do it -as quickly as possible and to take few risks. "If they feel that -'this is something I have to get through to get the prize,' they're -going to be less creative," Amabile said. - -Second, people come to see themselves as being controlled by the -reward. They feel less autonomous, and this may interfere with -performance. "To the extent one's experience of being -self-determined is limited," said Richard Ryan, associate psychology -professor at the University of Rochester, "one's creativity will be -reduced as well." - -Finally, extrinsic rewards can erode intrinsic interest. People who -see themselves as working for money, approval or competitive success -find their tasks less pleasurable, and therefore do not do them as -well. - -The last explanation reflects 15 years of work by Ryan's mentor at the -University of Rochester, Edward Deci. In 1971, Deci showed that -"money may work to buy off one's intrinsic motivation for an activity" -on a long-term basis. Ten years later, Deci and his colleagues -demonstrated that trying to best others has the same effect. Students -who competed to solve a puzzle quickly were less likely than those who -were not competing to keep working at it once the experiment was over. - -Control plays role - -There is general agreement, however, that not all rewards have the -same effect. Offering a flat fee for participating in an experiment - -similar to an hourly wage in the workplace - usually does not reduce -intrinsic motivation. It is only when the rewards are based on -performing a given task or doing a good job at it - analogous to -piece-rate payment and bonuses, respectively - that the problem -develops. - -The key, then, lies in how a reward is experienced. If we come to -view ourselves as working to get something, we will no longer find -that activity worth doing in its own right. - -There is an old joke that nicely illustrates the principle. An -elderly man, harassed by the taunts of neighborhood children, finally -devises a scheme. He offered to pay each child a dollar if they would -all return Tuesday and yell their insults again. They did so eagerly -and received the money, but he told them he could only pay 25 cents on -Wednesday. When they returned, insulted him again and collected their -quarters, he informed them that Thursday's rate would be just a penny. -"Forget it," they said - and never taunted him again. - -Means to and end - -In a 1982 study, Stanford psychologist Mark L. Lepper showed that any -task, no matter how enjoyable it once seemed, would be devalued if it -were presented as a means rather than an end. He told a group of -preschoolers they could not engage in one activity they liked until -they first took part in another. Although they had enjoyed both -activities equally, the children came to dislike the task that was a -prerequisite for the other. - -It should not be surprising that when verbal feedback is experienced -as controlling, the effect on motivation can be similar to that of -payment. In a study of corporate employees, Ryan found that those who -were told, "Good, you're doing as you /should/" were "significantly -less intrinsically motivated than those who received feedback -informationally." - -There's a difference, Ryan says, between saying, "I'm giving you this -reward because I recognize the value of your work" and "You're getting -this reward because you've lived up to my standards." - -A different but related set of problems exists in the case of -creativity. Artists must make a living, of course, but Amabile -emphasizes that "the negative impact on creativity of working for -rewards can be minimized" by playing down the significance of these -rewards and trying not to use them in a controlling way. Creative -work, the research suggests, cannot be forced, but only allowed to -happen. - -/Alfie Kohn, a Cambridge, MA writer, is the author of "No Contest: The -Case Against Competition," recently published by Houghton Mifflin Co., -Boston, MA. ISBN 0-395-39387-6. / diff -r 7edc33019aa4 -r b7b90f750a78 etc/ORDERS --- a/etc/ORDERS Mon Jan 31 20:01:50 2005 +0000 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000 @@ -1,4343 +0,0 @@ - - -Note: this file describes how you order software from the Free Software -Foundation directly. Information on getting XEmacs can be found in -the file DISTRIB. - - - -The actual order form follows the descriptions of media contents. - -Most of this file is excerpted from the January 1996 GNU's Bulletin. - -Please send suggestions for improvements to gnu@prep.ai.mit.edu or the postal -address at the end of the order form. Thank You. - ------------------------------------------------------------------------------ - - -FSF Order Form with Descriptions January, 1996 - - - -Free Software Foundation, Inc. Telephone: +1-617-542-5942 -59 Temple Place - Suite 330 Fax: (including Japan) +1-617-542-2652 -Boston, MA 02111-1307 USA Electronic mail: `gnu@prep.ai.mit.edu' - - ------------------------------------------------------------------------------ - - - -There are some sections (e.g. ``Forthcoming GNUs'' and ``How to Get GNU -Software'') which are not in this Order Form file. If you wish to see them, -ask gnu@prep.ai.mit.edu for the complete June, 1995 GNU's Bulletin. - - - -Table of Contents ------------------ - - Donations Translate Into Free Software - Cygnus Matches Donations! - Free Software Redistributors Donate - Help from Free Software Companies - Major Changes in GNU Software and Documentation - The Deluxe Distribution - GNU Documentation - GNU Software - Program/Package Cross Reference - Tapes - Languages Tape - Lisps and Emacs Tape - Utilities Tape - Scheme Tape - X11 Tapes - Berkeley 4.4BSD-Lite Tape - VMS Emacs and VMS Compiler Tapes - CD-ROMs - Pricing of the GNU CD-ROMs - December 1995 Compiler Tools Binaries CD-ROM - December 1994 Compiler Tools Binaries CD-ROM - December 1993 Compiler Tools Binaries CD-ROM - Source Code CD-ROMs - December 1995 Source Code CD-ROMs - June 1995 Source Code CD-ROM - May 1994 Source Code CD-ROM - November 1993 Source Code CD-ROM - MS-DOS Book with CD-ROM - Debian GNU/Linux Book with CD-ROM - MS-DOS Diskettes - DJGPP Diskettes - Emacs Diskettes - Selected Utilities Diskettes - Windows Diskette - Tape & CD-ROM Subscription Service - FSF T-shirt - Free Software Foundation Order Form - - ------------------------------------------------------------------------------ - - - -Donations Translate Into Free Software -************************************** - -If you appreciate Emacs, GNU CC, Ghostscript, and other free software, you -may wish to help us make sure there is more in the future--remember, -*donations translate into more free software!* - -Your donation to us is tax-deductible in the United States. We gladly accept -*any* currency, although the U.S. dollar is the most convenient. - -If your employer has a matching gifts program for charitable donations, -please arrange to: add the FSF to the list of organizations for your -employer's matching gifts program; and have your donation matched (note *Note -Cygnus Matches Donations!::). If you do not know, please ask your personnel -department. - -Circle amount you are donating, cut out this form, and send it with your -donation to: - - Free Software Foundation, Inc. - 59 Temple Place - Suite 330 - Boston, MA 02111-1307 - USA - - - $500 $250 $100 $50 Other $________ - - Other currency:________ - - -You can charge a donation to any of Carte Blanche, Diner's Club, JCB, -MasterCard, Visa, or American Express. Charges may also be faxed to -+1-617-542-2652. - - Card type: __________________ Expiration Date: _____________ - - Account Number: _____________________________________________ - - Cardholder's Signature: _____________________________________ - - Name: _______________________________________________________ - - Street Address: _____________________________________________ - - City/State/Province: ________________________________________ - - Zip Code/Postal Code/Country: _______________________________ - - - -Cygnus Matches Donations! -************************* - -To encourage cash donations to the Free Software Foundation, Cygnus Support -will continue to contribute corporate funds to the FSF to accompany gifts by -its employees, and by its customers and their employees. - -Donations payable to the Free Software Foundation should be sent by eligible -persons to Cygnus Support, which will add its gifts and forward the total to -the FSF each quarter. The FSF will provide the contributor with a receipt to -recognize the contribution (which is tax-deductible on U.S. tax returns). -For more information, please contact Cygnus: - - Cygnus Support - 1937 Landings Drive - Mountain View, CA 94043 - USA - - Telephone: 415-903-1400 - +1-800-Cygnus1 (-294-6871) - Fax: 415-903-0122 - Electronic-Mail: `info@cygnus.com' - FTP: `ftp.cygnus.com' - WWW: `http://www.cygnus.com/' - - - -Free Software Redistributors Donate -*********************************** - -The SNOW 2.1 CD producers added the words "Includes $5 donation to the FSF" -to the front of their CD. Potential buyers will know just how much of the -price is for the FSF & how much is for the redistributor. - -The Sun Users Group Deutschland & ASCII Corporation (Japan) have added -donations to the FSF to the price of their next GNU software CD-ROMs. - -Austin Code Works, a free software redistributor, supports free software -development by giving the FSF 20% of the selling price for the GNU software -CDs they produce & sell. - -Walnut Creek CDROM & Info Magic, free software redistributors, are also -giving us part of their selling price. - -TOHDO-SHA is donating 400 yen to the FSF for each copy of `The GNU Emacs Lisp -Reference Manual, Japanese Edition' sold at bookstores in Japan. - -CQ Publishing made a large donation from the sales of their GAWK book in -Japanese. - -In the long run, the success of free software depends on how much new free -software people develop. Free software distribution offers an opportunity to -raise funds for such development in an ethical way. These redistributors -have made use of the opportunity. Many others let it go to waste. - -You can help promote free software development by convincing for-a-fee -redistributors to contribute--either by doing development themselves or by -donating to development organizations (the FSF and others). - -The way to convince distributors to contribute is to demand and expect this -of them. This means choosing among distributors partly by how much they give -to free software development. Then you can show distributors they must -compete to be the one who gives the most. - -To make this work, you must insist on numbers that you can compare, such as, -"We will give ten dollars to the Foobar project for each disk sold." A vague -commitment, such as "A portion of the profits is donated," doesn't give you a -basis for comparison. Even a precise fraction "of the profits from this -disk" is not very meaningful, since creative accounting and unrelated -business decisions can greatly alter what fraction of the sales price counts -as profit. - -Also, press developers for firm information about what kind of development -they do or support. Some kinds make much more long-term difference than -others. For example, maintaining a separate version of a GNU program -contributes very little; maintaining a program on behalf of the GNU Project -contributes much. Easy new ports contribute little, since someone else would -surely do them; difficult ports such as adding a new CPU to the GNU compiler -or Mach contribute more; major new features and programs contribute the most. - -By establishing the idea that supporting further development is "the proper -thing to do" when distributing free software for a fee, we can assure a -steady flow of resources for making more free software. - - - -Help from Free Software Companies -********************************* - -When choosing a free software business, ask those you are considering how -much they do to assist free software development, e.g., by contributing money -to free software development or by writing free software improvements -themselves for general use. By basing your decision partially on this -factor, you can help encourage those who profit from free software to -contribute to its growth. - -Wingnut (SRA's special GNU support group) regularly donates a part of its -income to the FSF to support the development of new GNU programs. Listing -them here is our way of thanking them. Wingnut has made a pledge to donate -10% of their income to the FSF, and has purchased several Deluxe Distribution -packages in Japan. Also see *Note Cygnus Matches Donations!::. - - Wingnut Project - Software Research Associates, Inc. - 1-1-1 Hirakawa-cho, Chiyoda-ku - Tokyo 102, Japan - - Phone: (+81-3)3234-2611 - Fax: (+81-3)3942-5174 - E-mail: `info-wingnut@sra.co.jp' - WWW: `http://www.sra.co.jp/public/sra/product/wingnut/' - - - -Major Changes in GNU Software and Documentation -*********************************************** - - * A New FSF T-shirt! (*Note FSF T-shirt::) - - We have a new T-shirt. This design was inspired by the cover of the - `GNU Emacs Lisp Reference Manual'. - - * GNU Emacs 19.30 (*Note GNU Software::) - - We have just released Emacs 19.30. New features include support for menu - bars on text-only terminals, a total rewrite of GNUS, multiple frames on - Windows NT and Windows 95, & many others. - - * New Programs on the Tapes (*Note GNU Software::) - - `gettext' is now on the *Note Languages Tape::. Termutils & Midnight - Commander have been added to the *Note Utilities Tape::. CLX has been - added to the *Note Lisps/Emacs Tape::. Newer versions of many of our - programs & manuals have been placed on all the media we distribute. - - * New Source Code CD! - - We have just released the December 1995 Source Code CD-ROMs (Edition 7). - Due to increasing amounts of GNU Software, the Source Code CD is now a - two disc set--the price remains unchanged! The new programs included - are: apache, CLX, Elisp archive, `ffcall', `gettext', GN, Gnans, - `gnuserv', Hyperbole, Midnight Commander, Oaklisp, SIPP, SNePS, Spinner, - W3, and `xgrabsc'. *Note GNU Software::, for more information about - these packages. Also on the CD-ROMs are full distributions of MIT X11R6 - (both our Required & Optional distributions), MIT Scheme 7.3, Emacs - 19.30, GCC 2.7.1, and current versions of all other GNU Software. For - more information, see *Note December 1995 Source Code CD-ROMs::. - - * New Compiler Tools CD-ROM - - We have a new edition of the Compiler Tools Binaries CD-ROM with updated - versions of much of its software. It contains executables of the GNU - compiler tools for some systems that don't normally come with a - compiler. This allows users of those systems to compile their own - software without having to buy a proprietary compiler. - - We hope to include more systems with each update of this CD-ROM. If you - can help build binaries for new systems or have one to suggest, please - contact us at either address on page 1. For more information, see *Note - Compiler Tools Binaries CD-ROM::. - - * New/Updated Manuals since Last Bulletin (*Note Documentation::) - - We have a new manual: `The GNU Emacs Lisp Reference Manual, Japanese - Edition' - the FSF would like to thank the team of over 30 Japanese who - did the translation. These new editions include bug fixes and - additional information: `The GNU Emacs Lisp Reference Manual', `GNU - Make', `Bison', `Programming in Emacs Lisp: An Introduction', and `The - Termcap Manual'. - - * Older FSF CD-ROMs Available at a Reduced Price - - While supplies last, older versions of our CD-ROMs are available at a - reduced price. Note that the newest version has bug fixes and - improvements that the older versions do not. See the *note Free - Software Foundation Order Form::.. - - * GNU Software Works on MS-DOS (Also *note GNU Software::.) - - GNU Emacs 19 and many other GNU programs have been ported to MS-DOS for - i386/i486/Pentium machines. We ship binaries & sources on the *Note - DJGPP Diskettes::; *Note Emacs Diskettes::; *Note Selected Utilities - Diskettes::; & the *Note Compiler Tools Binaries CD-ROM::. We will ship - binaries & sources on the *Note MS-DOS Book with CD-ROM::, when it is - available. - - * The FSF Takes Credit Cards - - We take these credit cards: Carte Blanche, Diner's Club, MasterCard, JCB, - Visa, and American Express. Please note that we are charged about 5% of - an order's total amount in credit card processing fees. Please consider - paying by check instead or adding on a 5% donation to make up the - difference. - - - -The Deluxe Distribution -*********************** - -The Free Software Foundation has been asked repeatedly to create a package -that provides executables for all of our software. Normally we offer only -sources. In addition to providing binaries with the source code, the Deluxe -Distribution includes a complete set of our printed manuals and reference -cards. - -The FSF Deluxe Distribution contains the binaries and sources to hundreds of -different programs including GNU Emacs, the GNU C Compiler, the GNU Debugger, -the complete X Window System, and all the GNU utilities. - -We will make a Deluxe Distribution for most machines/operating systems. We -may be able to send someone to your office to do the compilation, if we can't -find a suitable machine close to us. However, we can only compile the -programs that already support your chosen machine/system - porting is a -separate matter (to commission a port, consult the GNU Service Directory; -details in *Note Free Software Support::). Compiling all these programs -takes time; a Deluxe Distribution for an unusual machine will take longer to -produce than one for a common machine. Please contact the FSF Office with -any questions. - -We supply the software in one of these tape formats in Unix `tar' format: -1600 or 6250bpi 1/2in reel, Sun DC300XLP 1/4in cartridge - QIC24, IBM RS/6000 -1/4in c.t. - QIC 150, Exabyte 8mm c.t., or DAT 4mm c.t. If your computer -cannot read any of these, please contact us to see if we can handle your -format. - -The manuals included are one each of the `Bison', `Calc', `GAWK', `GNU C -Compiler', `GNU C Library', `GDB', `Flex', `GNU Emacs Lisp Reference', -`Programming in Emacs Lisp: An Introduction', `Make', `Texinfo', & `Termcap' -manuals; six copies of the `GNU Emacs' manual; and a packet of ten reference -cards each for Emacs, Bison, Calc, Flex, & GDB. - -Every Deluxe Distribution also has a copy of the latest editions of our -CD-ROMs that have sources of our software & compiler tool binaries for some -systems. The MS-DOS CD is in ISO 9660 format. The other CDs are in ISO 9660 -format with Rock Ridge extensions. - -The price of the Deluxe Distribution is $5000 (shipping included). These -sales provide enormous financial assistance to help the FSF develop more free -software. To order, please fill out the "Deluxe Distribution" section on the -*note Free Software Foundation Order Form::. and send it to: - - Free Software Foundation, Inc. - 59 Temple Place - Suite 330 - Boston, MA 02111-1307 - USA - - Telephone: +1-617-542-5942 - Fax (including Japan): +1-617-542-2652 - Electronic mail: gnu@prep.ai.mit.edu - - - -GNU Documentation -***************** - -GNU is dedicated to having quality, easy-to-use online & printed -documentation. GNU manuals are intended to explain underlying concepts, -describe how to use all the features of each program, & give examples of -command use. GNU manuals are distributed as Texinfo source files, which -yield both typeset hardcopy via the TeX document formatting system and online -hypertext display via the menu-driven Info system. Source for these manuals -comes with our software; here are the manuals that we publish as printed -books. See the *note Free Software Foundation Order Form::., to order them. - -Most GNU manuals are bound as soft cover books with "lay-flat" bindings. -This allows you to open them so they lie flat on a table without creasing the -binding. They have an inner cloth spine and an outer cardboard cover that -will not break or crease as an ordinary paperback will. Currently, the -`GDB', `Emacs', `Emacs Lisp Reference', `Programming in Emacs Lisp: An -Introduction', `GAWK', `Make', `Bison', & `Texinfo' manuals have this -binding. The other GNU manuals also lie flat when opened, using a GBC or -Wire-O binding. All our manuals are 7in by 9.25in except the 8.5in by 11in -`Calc' manual. - -The edition number of the manual and version number of the program listed -after each manual's name were current at the time this Bulletin was published. - -`Debugging with GDB' (Edition 4.12 for Version 4.14) tells how to run your -program under GNU Debugger control, examine and alter data, modify a -program's flow of control, and use GDB through GNU Emacs. - -The `GNU Emacs Manual' (11th Edition for Version 19.29) describes editing with -GNU Emacs. It explains advanced features, including outline mode and regular -expression search; how to use special programming modes to write languages -like C++ and TeX; how to use the `tags' utility; how to compile and correct -code; how to make your own keybindings; and other elementary customizations. - -`Programming in Emacs Lisp: An Introduction' (Edition 1.04) is for people who -are not necessarily interested in programming, but who do want to customize -or extend their computing environment. If you read it in Emacs under Info -mode, you can run the sample programs directly. - -`The GNU Emacs Lisp Reference Manual' (Edition 2.4 for Version 19.29) and -`The GNU Emacs Lisp Reference, Japanese Edition' (Japanese DRAFT Revision -1.0, from English Edition 2.4 for Version 19.29) covers this programming -language in depth, including data types, control structures, functions, -macros, syntax tables, searching/matching, modes, windows, keymaps, byte -compilation, and the operating system interface. - -`The GAWK Manual' (Edition 0.16 for Version 2.16) tells how to use the GNU -implementation of `awk'. It is written for those who have never used `awk' -and describes the features of this powerful string and record manipulation -language. - -The `Make Manual' (Edition 0.49 for Version 3.74) describes GNU `make', a -program used to rebuild parts of other programs. The manual tells how to -write "makefiles", which specify how a program is to be compiled and how its -files depend on each other. Included are an introductory chapter for novice -users and a section about automatically generated dependencies. - -The `Flex' manual (Edition 1.03 for Version 2.3.7) teaches you to write a -lexical scanner definition for the `flex' program to create a C++ or C-coded -scanner that recognizes the patterns defined. You need no prior knowledge of -scanners. - -The `Bison' manual (December 1993 Edition for Version 1.23) teaches you how -to write context-free grammars for the Bison program that convert into -C-coded parsers. You need no prior knowledge of parser generators. - -`Using and Porting GNU CC' (September 1994 Edition for Version 2.6) tells how -to run, install, and port the GNU C Compiler to new systems. It lists new -features and incompatibilities of GCC, but people not familiar with C will -still need a good reference on the C programming language. It also covers -G++. We are doing limited copier runs of this manual until it becomes more -stable. - -The `Texinfo' manual (Edition 2.21 for Version 3) explains the markup -language that produces our online Info documentation & typeset hardcopies. -It tells you how to make tables, lists, chapters, nodes, indexes, cross -references, & how to catch mistakes. This second edition describes over 50 -new commands. - -`The Termcap Manual' (2nd Edition for Version 1.2), often described as "twice -as much as you ever wanted to know about termcap," details the format of the -termcap database, the definitions of terminal capabilities, and the process -of interrogating a terminal description. This manual is primarily for -programmers. - -The `C Library Reference Manual' (Edition 0.06 for Version 1.09) describes -the library's facilities, including both what Unix calls "library functions" -& "system calls." We are doing small copier runs of this manual until it -becomes more stable. Please send fixes to `bug-glibc-manual@prep.ai.mit.edu'. - -The `Emacs Calc Manual' (Edition 2.02 for Version 2.02) is both a tutorial -and a reference manual. It tells how to do ordinary arithmetic, how to use -Calc for algebra, calculus, and other forms of mathematics, and how to extend -Calc. - - - -GNU Software -************ - -All our software is available via FTP; see *Note How to Get GNU Software::. -We also offer software on various media and printed documentation: - - * *Note CD-ROMs::. - - * *Note Tapes::. - - * *Note MS-DOS Diskettes::. - - * *Note Documentation::, which includes manuals and reference cards. - -In these articles describing the contents of each medium, the version number -listed after each program name was current when we published this Bulletin. -When you order a distribution tape, diskette, or newer CD-ROM, some of the -programs may be newer and therefore the version number higher. See the *note -Free Software Foundation Order Form::., for ordering information. - -Some of the contents of our tape and FTP distributions are compressed. We -have software on our tapes and FTP sites to uncompress these files. Due to -patent troubles with `compress', we use another compression program, `gzip'. -(Such prohibitions on software development are fought by the League for -Programming Freedom; *note What Is the LPF::., for details.) - -GNU `make' is on several of our tapes because some system vendors supply no -`make' utility at all and some native `make' programs lack the `VPATH' -feature essential for using the GNU configure system to its full extent. The -GNU `make' sources have a shell script to build `make' itself on such systems. - -We welcome all bug reports and enhancements sent to the appropriate -electronic mailing list (*note Free Software Support::.). - - - -Configuring GNU Software ------------------------- - -We are using, Autoconf, a uniform scheme for configuring GNU software -packages in order to compile them (see "Autoconf" below, in this article). -The goal is to have all GNU software support the same alternatives for naming -machine and system types. - -Ultimately, it will be possible to configure and build the entire system all -at once, eliminating the need to configure each individual package separately. - -You can also specify both the host and target system to build -cross-compilation tools. Most GNU programs now use Autoconf-generated -configure scripts. - - - -GNU Software currently available --------------------------------- - -For future programs and features, see *Note Forthcoming GNUs::. - -Key to cross reference: - - - BinCD - December 1994 Binaries CD-ROM - - DjgpD - Djgpp Diskettes - - DosBC - MS-DOS Book with CD-ROM - - EmcsD - Emacs Diskettes - - LangT - Languages Tape - - LiteT - 4.4BSD-Lite Tape - - LspEmcT - Lisps/Emacs Tape - - SchmT - Scheme Tape - - SrcCD - December 1995 Source CD-ROMs - - UtilD - Selected Utilities Diskettes - - UtilT - Utilities Tape - - VMSCmpT - VMS Compiler Tape - - VMSEmcsT - VMS Emacs Tape - - WdwsD - Windows Diskette - - X11OptT - X11 Optional Tape - - X11ReqT - X11 Required Tape - -[FSFman] shows that we sell a manual for that package. [FSFrc] shows we sell -a reference card for that package. To order them, see the *note Free -Software Foundation Order Form::.. *Note Documentation::, for more -information on the manuals. Source code for each manual or reference card is -included with each package. - - * `acm' (SrcCD, UtilT) - - `acm' is a LAN-oriented, multiplayer aerial combat simulation that runs - under the X Window System. Players engage in air to air combat against - one another using heat seeking missiles and cannons. We are working on - a more accurate simulation of real airplane flight characteristics. - - * apache (SrcCD) - - Apache is an HTTP server designed as a plug-in replacement for version - 1.3 or 1.4 of the NCSA server. It fixes numerous bugs in the NCSA - server and includes many frequently requested new features, and has an - API which allows it to be extended to meet users' needs more easily. - - * Autoconf (SrcCD, UtilT) - - Autoconf produces shell scripts which automatically configure source code - packages. These scripts adapt the packages to many kinds of Unix-like - systems without manual user intervention. Autoconf creates a script for - a package from a template file which lists the operating system features - which the package can use, in the form of `m4' macro calls. Autoconf - requires GNU `m4' to operate, but the resulting configure scripts it - generates do not. - - * BASH (SrcCD, UtilT) - - GNU's shell, BASH (Bourne Again SHell), is compatible with the Unix `sh' - and offers many extensions found in `csh' and `ksh'. BASH has job - control, `csh'-style command history, command-line editing (with Emacs - and `vi' modes built-in, and the ability to rebind keys) via the - `readline' library. BASH conforms to the POSIX 1003.2-1992 standard. - - * `bc' (DosBC, SrcCD, UtilT) - - `bc' is an interactive algebraic language with arbitrary precision - numbers. GNU `bc' follows the POSIX 1003.2-1992 standard, with several - extensions including multi-character variable names, an `else' - statement, and full Boolean expressions. The RPN calculator `dc' is now - distributed as part of the same package, but GNU `bc' is not implemented - as a `dc' preprocessor. - - * BFD (BinCD, DjgpD, DosBC, LangT, SrcCD) - - The Binary File Descriptor library allows a program which operates on - object files (e.g., `ld' or GDB) to support many different formats in a - clean way. BFD provides a portable interface, so that only BFD needs to - know the details of a particular format. One result is that all - programs using BFD will support formats such as a.out, COFF, and ELF. - BFD comes with Texinfo source for a manual (not yet published on paper). - - At present, BFD is not distributed separately; it is included with - packages that use it. - - * Binutils (BinCD, DjgpD, DosBC, LangT, SrcCD; `gas' only on VMSCmpT) - - Binutils includes these programs: `ar', `c++filt', `demangle', `gas', - `gprof', `ld', `nlmconv', `nm', `objcopy', `objdump', `ranlib', `size', - `strings', & `strip'. - - Binutils version 2 uses the BFD library. The GNU assembler, `gas', - supports the a29k, Alpha, H8/300, H8/500, HP-PA, i386, i960, m68k, m88k, - MIPS, NS32K, SH, SPARC, Tahoe, Vax and Z8000 CPUs, and attempts to be - compatible with many other assemblers for UNIX and embedded systems. It - can produce mixed C-and-assembly listings, and includes a macro facility - similar to that in some other assemblers. GNU's linker `ld' emits - source-line numbered error messages for multiply-defined symbols and - undefined references, and interprets a superset of AT&T's Linker Command - Language, which gives control over where segments are placed in memory. - `nlmconv' converts object files into Novell NetWare Loadable Modules. - `objdump' can disassemble code for most of the CPUs listed above, and - can display other data (e.g., symbols and relocations) from any file - format read by BFD. - - * Bison (BinCD,DjgpD,DosBC,LangT,SrcCD,VMSCmpT)[FSFman,FSFrc] - - Bison is an upwardly compatible replacement for the parser generator - `yacc'. Texinfo source for the `Bison Manual' and reference card are - included. *Note Documentation::. - - A recent policy change allows non-free programs to use Bison-generated - parsers. *Note Conditions for Using Bison::. - - * C Library (BinCD, LangT, SrcCD) [FSFman] - - The GNU C library supports ANSI C-1989, POSIX 1003.1-1990 and most of the - functions in POSIX 1003.2-1992. It is upwardly compatible with 4.4BSD - and includes many System V functions, plus GNU extensions. - - The C Library performs many functions of the Unix system calls in the - GNU/Hurd. Mike Haertel has written a fast `malloc' which wastes less - memory than the old GNU version. The GNU regular-expression functions - (`regex' and `rx') now nearly conform to the POSIX 1003.2 standard. - - GNU `stdio' lets you define new kinds of streams, just by writing a few - C functions. The `fmemopen' function uses this to open a stream on a - string, which can grow as necessary. You can define your own `printf' - formats to use a C function you have written. For example, you can - safely use format strings from user input to implement a `printf'-like - function for another programming language. Extended `getopt' functions - are already used to parse options, including long options, in many GNU - utilities. - - The C Library runs on Sun-3 (SunOS 4.1), Sun-4 (SunOS 4.1 or Solaris 2), - HP 9000/300 (4.3BSD), SONY News 800 (NewsOS 3 or 4), MIPS DECstation - (Ultrix 4), DEC Alpha (OSF/1), i386/i486/Pentium (System V, SVR4, BSD, - SCO 3.2, & SCO ODT 2.0), Sequent Symmetry i386 (Dynix 3), & SGI (Irix - 4). *Note Forthcoming GNUs::. Texinfo source for the - `GNU C Library Reference Manual' is included (*note Documentation::.. - - * C++ Library (BinCD, DjgpD, DosBC, LangT, SrcCD) - - The GNU C++ library (libg++) contains an extensive collection of C++ - "forest" classes, an IOStream library for input/output routines, and - support tools for use with G++. Supported classes include: Obstacks, - multiple-precision Integers and Rationals, Complex numbers, arbitrary - length Strings, BitSets, and BitStrings. - - The distribution also includes the libstdc++ library. This implements - library facilities defined by the forthcoming ANSI/ISO C++ standard, - including a port of the Standard Template Library. - - * Calc (DosBC, LspEmcT, SrcCD) [FSFman, FSFrc] - - Calc (written by Dave Gillespie in Emacs Lisp) is an extensible, advanced - desk calculator & mathematical tool that runs as part of GNU Emacs. You - can use Calc just as a simple four-function calculator, but it has many - more features including: choice of algebraic or RPN (stack-based) entry; - logarithmic, trigonometric, & financial functions; arbitrary precision; - complex numbers; vectors; matrices; dates; times; infinities; sets; - algebraic simplification; differentiation & integration. It outputs to - `gnuplot', & comes with source for a manual & reference card (*note - Documentation::.). - - * `cfengine' (SrcCD, UtilT) - - `cfengine' is used for maintaining site-wide configuration of a - heterogeneous Unix network using a simple high level language. Its - appearance is similar to `rdist', but also allows many more operations - to be performed automatically. See Mark Burgess, "A Site Configuration - Engine", `Computing Systems', Vol. 8, No. 3 (ask `office@usenix.org' how - to get a copy). - - * Chess (SrcCD, UtilT, WdwsD) - - GNU Chess enables most modern computers to play a full game of chess. It - supports a plain terminal interface, a curses interface, and a spiffy X - Window interface via `xboard'. - - Improvements this past year include fixes to the game analyzer, book, & - hash table; smartening up draw and mate; improved thinking on opponent's - time; Autoconf installation; a makefile for Windows NT compilation; - forward pruning; unlimited quiescence captures; improved evaluation; - improved null & time control logic; & repetition-detection. - - GNU Chess was originated by Stuart Cracraft. Improvements & rewrites are - from John Stanback, Cha Kong Sian, Mike McGann, and many others. - - Send bugs to `bug-gnu-chess@prep.ai.mit.edu' & general comments to - `info-gnu-chess@prep.ai.mit.edu'. - - * CLISP (LspEmcT, SrcCD) - - CLISP is a Common Lisp implementation by Bruno Haible and Michael Stoll. - It mostly supports the Lisp described by `Common LISP: The Language (2nd - edition)' and the ANSI Common Lisp standard. CLISP includes an - interpreter, a byte-compiler, a large subset of CLOS, a foreign language - interface, and, for some machines, a screen editor. The user interface - language (English, German, French) is choosable at run time. Major - packages that run in CLISP include CLX & Garnet. CLISP needs only 2 MB - of memory & runs on many microcomputers (including MS-DOS systems, OS/2, - Windows NT, Amiga 500-4000, Acorn RISC PC) & Unix-like systems - (GNU/Linux, Sun4, SVR4, SGI, HP-UX, DEC Alpha, NeXTStep, & others). - - * Common Lisp **Note Forthcoming GNUs::* (LspEmcT, SrcCD) - - GNU Common Lisp (GCL, formerly known as Kyoto Common Lisp) is a compiler - & interpreter for Common Lisp. GCL is very portable & extremely - efficient on a wide class of applications, & compares favorably in - performance with commercial Lisps on several large theorem-prover & - symbolic algebra systems. GCL supports the CLtL1 specification but is - moving towards the proposed ANSI standard. - - GCL compiles to C & then uses the native optimizing C compiler (e.g., - GCC). A function with a fixed number of args & one value turns into a C - function of the same number of args, returning one value--so GCL is - maximally efficient on such calls. Its conservative garbage collector - gives great freedom to the C compiler to put Lisp values in registers. - It has a source level Lisp debugger for interpreted code & displays - source code in an Emacs window. Its profiler (based on the C profiling - tools) counts function calls & the time spent in each function. - - There is now a built-in interface to the Tk widget system. It runs in a - separate process, so users may monitor progress on Lisp computations or - interact with running computations via a windowing interface. - - There is also an Xlib interface via C (xgcl-2). CLX runs with GCL, as - does PCL (see "PCL" later in this article). *Note Forthcoming GNUs::, - for plans regarding GCL or for recent developments. - - GCL version 2.2 is released under the GNU Library General Public License. - - * CLX (LspEmcT, SrcCD) - - CLX is an X Window interface library for GCL. - - * `cpio' (DosBC, SrcCD, UtilD, UtilT) - - `cpio' is an archive program with all the features of SVR4 `cpio', - including support for the final POSIX 1003.1 `ustar' standard. `mt', a - program to position magnetic tapes, is included with `cpio'. - - * CVS (SrcCD, UtilT) - - CVS, the Concurrent Version System, manages software revision & release - control at a multi-developer, multi-directory, multi-group site. It - works best with RCS versions 4 and above, but will parse older RCS - formats, losing some of CVS's fancier features. (See Berliner, Brian, - "CVS-II: Parallelizing Software Development," `Proceedings of the Winter - 1990 USENIX Association Conference'; ask `office@usenix.org' how to get - a copy.) - - * DejaGnu (LangT, SrcCD) - - DejaGnu is a framework to test programs with a single front end for all - tests. The framework's flexibility & consistency makes it easy to write - tests. - - DejaGnu comes with `expect', which runs scripts to conduct dialogs with - programs. - - * Diffutils (DjgpD, DosBC, SrcCD, UtilT) - - GNU `diff' compares files showing line-by-line changes in several - flexible formats. It is much faster than traditional Unix versions. The - Diffutils package contains `diff', `diff3', `sdiff', & `cmp'. Recent - improvements include more consistent handling of character sets and a - new `diff' option to do all input/output in binary; this is useful on - some non-POSIX hosts. Plans for the Diffutils package include support - for internationalization (e.g., error messages in Chinese) and for some - non-Unix PC environments. - - * DJGPP (BinCD, DjgpD, DosBC) - - DJ Delorie has ported GCC/G++ (see "GCC" in this article) to i386s - running MS-DOS. DJGPP has a 32-bit i386 DOS extender with a symbolic - debugger; development libraries; & ports of Bison, `flex', & Binutils. - Full source code is provided. It needs at least 5MB of hard disk space - to install & 512K of RAM to use. It supports SVGA (up to 1024x768), XMS - & VDISK memory allocation, `himem.sys', VCPI (e.g., QEMM, DESQview, & - 386MAX), & DPMI (e.g., Windows 3.x, OS/2, QEMM, & QDPMI). - - The FSF offers it on the *Note Compiler Tools Binaries CD-ROM::, and on - the *Note DJGPP Diskettes::. FTP from `oak.oakland.edu' in - `/simtel/vendors/djgpp/' (or another SimTel mirror site). - - To join a DJGPP users mailing list, ask - `djgpp-request@sun.soe.clarkson.edu'. - - * `dld' (LangT, SrcCD) - - `dld' is a dynamic linker written by W. Wilson Ho. Linking your program - with the `dld' library allows you to dynamically load object files into - the running binary. Currently supported are VAX (Ultrix), Sun 3 (SunOS - 3.4 & 4.0), SPARC (SunOS 4.0), Sequent Symmetry (Dynix), & Atari ST. - - * `doschk' (DosBC, SrcCD, UtilT) - - This program is a utility to help software developers ensure that their - source file names are distinguishable on System V platforms with - 14-character filenames and on MS-DOS systems with 8+3 character - filenames. - - * `ecc' (LangT, SrcCD) - - `ecc' is a Reed-Solomon error correction checking program, which can - correct three byte errors in a block of 255 bytes and detect more severe - errors. Contact `paulf@stanford.edu' for more information. - - * `ed' (SrcCD, UtilT) - - `ed' is the standard text editor. It is line-oriented and can be used - interactively or in scripts. - - * Elib (DosBC, LspEmcT, SrcCD) - - Elib is a small library of Emacs Lisp functions, including routines for - using AVL trees and doubly-linked lists. - - * Elisp archive (SrcCD) - - This is a snapshot of Ohio State's GNU Emacs Lisp FTP Archive. FTP it - from `archive.cis.ohio-state.edu' in `/pub/gnu/emacs/elisp-archive'. - - * Emacs **Note Forthcoming GNUs:: for future plans.* - - In 1975, Richard Stallman developed the first Emacs, an extensible, - customizable real-time display editor & computing environment. GNU Emacs - is his second implementation. It offers true Lisp--smoothly integrated - into the editor--for writing extensions & provides an interface to the X - Window System. It runs on Unix, MS-DOS, & Windows NT. In addition to - its powerful native command set, Emacs has extensions which emulate the - editors vi & EDT (Digital's VMS editor). Emacs has many other features - which make it a full computing support environment. Source for the `GNU - Emacs Manual' & a reference card comes with the software. Sources for - the `GNU Emacs Lisp Reference Manual' & `Programming in Emacs Lisp: An - Introduction' are distributed in separate packages. *Note - Documentation::. - - * Emacs 18 (LspEmcT, SrcCD, VMSEmcsT) [FSFrc] - - Emacs 18.59 is the last release of version 18 from the FSF. We no longer - maintain it. It supports these Unix systems that Emacs 19 doesn't - support (please help port Emacs 19 to these systems): Alliant FX/80, - Altos 3068, Amdahl (UTS), AT&T (3Bs & 7300 PC), CCI 5/32 & 6/32, - Celerity, Digital (VAX VMS), Dual, Encore (APC, DPC, & XPC), HLH Orion - (original & 1/05), ISI (Optimum V, 80386), Masscomp, NCR Tower 32 (SVR2 - & SVR3), Nixdorf Targon 31, Nu (TI & LMI), pfa50, Plexus, Prime EXL, - Stride (system rel. 2), Tahoe, Tandem Integrity S2, Tektronix 16000, - Triton 88, Ustation E30 (SS5E), Whitechapel (MG1), & Wicat. - - * Emacs 19 (DosBC, EmcsD, LspEmcT, SrcCD) [FSFman(s), FSFrc] - - Emacs 19 works with character-only terminals & with the X Window System - (with or without an X toolkit). New features in Emacs 19 include: - multiple X windows ("frames" to Emacs), with a separate X window for the - minibuffer or a minibuffer attached to each X window; property lists - associated with regions of text in a buffer; multiple fonts & colors - defined by those properties; simplified/improved processing of function - keys, mouse clicks, and mouse movement; X selection processing, - including clipboard selections; hooks to be run if the point or mouse - moves outside a certain range; menu bars and popup menus defined by - keymaps; scrollbars; before- and after-change hooks; a source-level - debugger for Emacs Lisp programs; floating point numbers; improved - buffer allocation, including returning storage to the system when a - buffer is killed; interfacing with the X resource manager; many updated - libraries; integrated support for version control systems (RCS, CVS, & - SCCS); Autoconf based configuration; and support for European character - sets. - - Recent features include the ability to open frames on more than one X - display from a single Emacs job, operation on MS-DOS, MS Windows, and - Windows NT, displaying multiple views of an outline at the same time, - support for the Athena & Motif widgets, version control support for CVS - and for multiple branches, text properties for formatting text, commands - to edit text properties and save them in files, and GNU-standard - long-named command line options. - - Emacs 19.30 works on: Acorn RISC (RISCiX); Alliant FX/2800 (BSD); Alpha - (OSF/1); Apollo (DomainOS); Bull DPX/2 2nn & 3nn (SysV.3) & sps7 - (SysV.2); Clipper; Convex (BSD); Cubix QBx (SysV); Data General Aviion - (DGUX); DEC MIPS (Ultrix 4.2, OSF/1, not VMS); Elxsi 6400 (SysV); Gould - Power Node & NP1 (4.2 & 4.3BSD); Harris Night Hawk 1200, 3000, 4000 & - 5000 (cxux); Honeywell XPS100 (SysV); HP 9000 series 200, 300, 700, 800 - (but not 500) (4.3BSD; HP-UX 7, 8, 9); Intel i386/i486/Pentium - (GNU/Linux, 386BSD, AIX, BSDI/386, FreeBSD, Esix, ISC, MS-DOS (*note - MS-DOS Diskettes::., & *Note MS-DOS Book with CD-ROM::), NetBSD, - SCO3.2v4, Solaris, SysV, Xenix, WindowsNT); IBM RS/6000 (AIX 3.2) & - RT/PC (AIX, BSD); Motorola Delta 147 & 187 (SysV.3, SysV.4, m88kbcs); - National Semiconductor 32K (Genix); NeXT (BSD, Mach 2 w/ NeXTStep 3.0); - Paragon (OSF/1); Prime EXL (SysV); Pyramid (BSD); Sequent Symmetry (BSD, - ptx); Siemens RM400 & RM600 (SysV); SGI Iris 4D (Irix 4.x & 5.x); Sony - News/RISC (NewsOS); Stardent i860 (SysV); Sun 3 & 4, SPARC 1, 1+, 2, 10, - Classic (SunOS 4.0, 4.1, Solaris 2.0-2.3); Tadpole 68k (SysV); Tektronix - XD88 (SysV.3) & 4300 (BSD); & Titan P2 & P3 (SysV). - - Other configurations supported by Emacs 18 should work with few changes - in Emacs 19; as users tell us more about their experiences with different - systems, we will augment the list. Also see *Note Forthcoming GNUs::. - - * `es' (SrcCD, UtilT) - - `es' is an extensible shell (based on `rc') with first class functions, - lexical scope, exceptions and rich return values (i.e., functions can - return values other than just numbers). `es''s extensibility comes from - the ability to modify and extend the shell's built-in services, such as - path searching and redirection. Like `rc', it is great for both - interactive use and scripting, particularly since its quoting rules are - much less baroque than the C and Bourne shells. - - * `f2c' (LangT, SrcCD) - - `f2c' converts Fortran-77 source into C or C++, which can be compiled - with GCC or G++. Get bug fixes by FTP from site `netlib.att.com' or by - email from `netlib@research.att.com'. See the file - `/netlib/f2c/readme.Z' for a summary. Also see the GNU Fortran item - later in this article, and in *Note Forthcoming GNUs::. - - * `ffcall' (SrcCD) - - `ffcall' is a C library for implementing foreign function calls in - embedded interpreters by Bill Triggs and Bruno Haible. It allows C - functions with arbitrary argument lists and return types to be called or - emulated (callbacks). - - * Fileutils (DosBC, SrcCD, UtilT) - - The Fileutils work on files: `chgrp', `chmod', `chown', `cp', `dd', `df', - `dir', `du', `install', `ln', `ls', `mkdir', `mkfifo', `mknod', `mv', - `rm', `rmdir', `sync', `touch', & `vdir'. - - * Findutils (DosBC, SrcCD, UtilT) - - `find' is frequently used both interactively and in shell scripts to - find files which match certain criteria and perform arbitrary operations - on them. Also included are `locate', which scans a database for file - names that match a pattern, and `xargs', which applies a command to a - list of files. - - * Finger (SrcCD, UtilT) - - GNU Finger has more features than other finger programs. For sites with - many hosts, a single host may be designated as the finger "server" host - and other hosts at that site configured as finger "clients". The server - host collects information about who is logged in on the clients. To - finger a user at a GNU Finger site, a query to any of its client hosts - gets useful information. GNU Finger supports many customization - features, including user output filters and site programmable output for - special target names. - - * `flex' (BinCD, DjgpD, DosBC, LangT, SrcCD, UtilD) [FSFman, FSFrc] - - `flex' is a replacement for the `lex' scanner generator. `flex' was - written by Vern Paxson of the Lawrence Berkeley Laboratory and generates - far more efficient scanners than `lex' does. Sources for the `Flex - Manual' and reference card are included (*note Documentation::.). - - * Fortran (`g77') **Note Forthcoming GNUs::* (LangT, SrcCD) - - GNU Fortran (`g77'), developed by Craig Burley, is available for public - beta testing on the Internet. For now, `g77' produces code that is - mostly object-compatible with `f2c' & uses the same run-time library - (`libf2c'). - - * Fontutils (SrcCD, UtilT) - - The Fontutils convert between font formats, create fonts for use with - Ghostscript or TeX (starting with a scanned type image & converting the - bitmaps to outlines), et al. It includes: `bpltobzr', `bzrto', - `charspace', `fontconvert', `gsrenderfont', `imageto', `imgrotate', - `limn', & `xbfe'. - - * GAWK (DosBC, LangT, SrcCD) [FSFman] - - GAWK is upwardly compatible with the latest POSIX specification of - `awk'. It also provides several useful extensions not found in other - `awk' implementations. Texinfo source for the `GAWK Manual' comes with - the software (*note Documentation::.). - - * GCC (BinCD, DjgpD, DosBC, LangT, SrcCD, VMSCmpT) [FSFman] - - Version 2 of the GNU C Compiler supports the languages C, C++, and - Objective-C; the source file name suffix or a compiler option selects - the language. Objective-C support was donated by NeXT. The runtime - support needed to run Objective-C programs is now distributed with GCC - (this does not include any Objective-C classes aside from `object', but - see "GNUStep" in *Note Forthcoming GNUs::). As much as possible, G++ is - kept compatible with the evolving draft ANSI standard, but not with - `cfront' (AT&T's compiler), which has been diverging from ANSI. - - The GNU C Compiler is a fairly portable optimizing compiler which - performs automatic register allocation, common sub-expression - elimination, invariant code motion from loops, induction variable - optimizations, constant propagation and copy propagation, delayed - popping of function call arguments, tail recursion elimination, - integration of inline functions and frame pointer elimination, - instruction scheduling, loop unrolling, filling of delay slots, leaf - function optimization, optimized multiplication by constants, a certain - amount of common subexpression elimination (CSE) between basic blocks - (though not all of the supported machine descriptions provide for - scheduling or delay slots), a feature for assigning attributes to - instructions, and many local optimizations that are automatically - deduced from the machine description. - - GCC can open-code most arithmetic on 64-bit values (type `long long - int'). It supports extended floating point (type `long double') on the - 68k; other machines will follow. - - GCC supports full ANSI C, traditional C, & GNU C extensions (including: - nested functions support, nonlocal gotos, & taking the address of a - label). - - GCC can generate a.out, COFF, ELF, & OSF-Rose files when used with a - suitable assembler. It can produce debugging information in these - formats: BSD stabs, COFF, ECOFF, ECOFF with stabs, & DWARF. - - GCC generates code for many CPUs, including the a29k, Alpha ARM AT&T - DSP1610 Clipper Convex cN Elxsi Fujitsu Gmicro i370, i860, i960, - MIL-STD-1750a, MIPS, ns32k, PDP-11, Pyramid, ROMP, RS/6000, SH, SPUR, - Tahoe, VAX, & we32k. Position-independent code is generated for the - Clipper, Hitachi H8/300, HP-PA (1.0 & 1.1), i386/i486/Pentium, m68k, - m88k, SPARC, & SPARClite. - - Operating systems supported include: GNU/Hurd, GNU/Linux, ACIS, AIX, AOS, - BSD, Clix, Concentrix, Ctix, DG/UX, Dynix, FreeBSD, Genix, HP-UX, Irix, - ISC, Luna, LynxOS, Minix, NetBSD, NewsOS, NeXTStep, OS/2, OSF, OSF-Rose, - RISCOS, SCO, Solaris 2, SunOS 4, System/370, SysV, Ultrix, Unos, VMS, & - Windows/NT. - - Using the configuration scheme for GCC, building a cross-compiler is as - easy as building a native compiler. - - Version 1 of GCC, G++, & libg++ are no longer maintained. - - Texinfo source for the `Using and Porting GNU CC' manual, is included - with GCC (*note Documentation::.). - - *Note Forthcoming GNUs::, for plans for later releases of GCC. - - * GDB (BinCD, DjgpD, DosBC, LangT, SrcCD) [FSFman, FSFrc] - - GDB, the GNU DeBugger, is a source-level debugger for C, C++, & Fortran. - - GDB can debug both C and C++ programs, and will work with executables - produced by many different compilers; however, C++ debugging will have - some limitations if you do not use GCC. - - GDB has a command line user interface, and Emacs has a GDB mode. Two X - interfaces (not distributed or maintained by the FSF) are: `gdbtk' (FTP - it from `ftp.cygnus.com' in directory `/pub/gdb'); and `xxgdb' (FTP it - from `ftp.x.org' in directory `/contrib/utilities'). - - Executable files and symbol tables are read via the BFD library, which - allows a single copy of GDB to debug programs with multiple object file - formats (e.g., a.out, COFF, ELF). Other features include a rich command - language, remote debugging over serial lines or TCP/IP, and watchpoints - (breakpoints triggered when the value of an expression changes). - - GDB uses a standard remote interface to a simulator library which (so - far) has simulators for the Hitachi H8/300, H8/500, Super-H, & Zilog - Z8001/2. - - GDB can perform cross-debugging. To say that GDB "targets" a platform - means it can perform native or cross-debugging for it. To say that GDB - can "host" a given platform means that it can be built on it, but cannot - necessarily debug native programs. - - GDB can: - - * "target" & "host": Amiga 3000 (Amix), DEC Alpha (OSF/1), DECstation - 3100 & 5000 (Ultrix), HP 9000/300 (BSD, HP-UX), HP 9000/700 (HP-UX - 9, 10), i386 (GNU/Hurd, GNU/Linux, BSD, FreeBSD, LynxOS, NetBSD, - SCO), IBM RS/6000 (AIX, LynxOS), Motorola Delta m88k (System V, - CX/UX), PC532 (NetBSD), Motorola m68k MVME-167 (LynxOS), NCR 3000 - (SVR4), SGI (Irix V3, V4, V5), SONY News (NewsOS 3.x), SPARC - (LynxOS, NetBSD, Solaris, & SunOS 4.1 ) Sun-3 (SunOS 4.1), & - Ultracomputer (a29k running Sym1). - - * "target", but not "host": AMD 29000 (COFF & a.out), Hitachi H8/300, - Hitachi SH, i386 (a.out, COFF, OS/9000), i960 (Nindy, VxWorks), - m68k/m68332 (a.out, COFF, VxWorks), MIPS (ELF, IDT ecoff), Fujitsu - SPARClite (a.out, COFF), & Z8000. - - * "host", but not "target": IBM RT/PC (AIX), HP/Apollo 68k (BSD), & - Apple Macintosh (MacOS). - - Sources for the manual, `Debugging with GDB', and a reference card are - included (*note Documentation::.). - - * `gdbm' (LangT, SrcCD, UtilD) - - `gdbm' is the GNU replacement for the traditional `dbm' and `ndbm' - libraries. It implements a database using quick lookup by hashing. - `gdbm' does not ordinarily make sparse files (unlike its Unix and BSD - counterparts). - - * `gettext' (LangT, SrcCD) - - The GNU `gettext' tool set contains everything maintainers need to - internationalize a package for messages, tools that help translators - localize messages to their native language, once a package has been - internationalized. *Note Help the GNU Translation Project::. - - * Ghostscript (DosBC, SrcCD, UtilT) - - The GNU release of Ghostscript is an interpreter for the Postscript - graphics language (*note Forthcoming GNUs::., for future plans). - - The current version of GNU Ghostscript is 2.6.2. Features include the - ability to use the fonts provided by the platform on which Ghostscript - runs (X Window System & Microsoft (MS) Windows), resulting in much - better-looking screen displays; improved text file printing (like - `enscript'); a utility to extract the text from a Postscript language - document; a much more reliable (and faster) MS Windows implementation; - support for MS C/C++ 7.0; drivers for many new printers ( e.g. the - SPARCprinter), & for TIFF/F (Fax) file format; many more Postscript Level - 2 facilities, including most of the color space facilities (but not - patterns); & the ability to switch between Level 1 & Level 2 - dynamically. Version 2.6.2 adds a LaserJet 4 driver & several important - bug fixes to version 2.6.1. - - Ghostscript executes commands in the Postscript language by writing - directly to a printer, drawing on an X window, or writing to files for - printing later or manipulating with other graphics programs. - - Ghostscript includes a C-callable graphics library (for client programs - that do not want to deal with the Postscript language). It also supports - i386/i486/Pentiums running MS-DOS with EGA, VGA or SuperVGA graphics (but - please do *not* ask the FSF staff any questions about this; we do not - use MS-DOS). - - * Ghostview (DosBC, SrcCD, UtilT) - - Tim Theisen, `ghostview@cs.wisc.edu', created Ghostview, a previewer for - multi-page files with an X Window interface. Ghostview & Ghostscript - work together; Ghostview creates a viewing window & Ghostscript draws in - it. - - * GIT (SrcCD, UtilT) - - GIT is a set of interactive tools: an extensible file system browser, an - ASCII/hex file viewer, a process viewer/killer, & other related - utilities & shell scripts. It can be used to increase the speed & - efficiency of many daily tasks, such as copying & moving files & - directories, invoking editors, compressing/uncompressing files, creating - & expanding archives, compiling programs, sending mail, etc. It looks - nice, has colors (if the standard ANSI color sequences are supported), & - is user-friendly. - - * `gmp' **Note Forthcoming GNUs::* (LangT, SrcCD) - - GNU `mp' is a library for arbitrary precision arithmetic on signed - integers and rational numbers. It has a rich set of functions with a - regular interface. - - * GN (SrcCD) - - GN is a gopher/HTTP server. It recognizes whether the request came from - an HTTP (World Wide Web) or gopher client and responds accordingly. - - * Gnans (SrcCD) - - Gnans is a program (and language) for the numerical study of - deterministic and stochastic dynamical systems. The dynamical systems - may evolve in continuous or discrete time. Gnans has graphical & - command line interfaces. - - * GNATS (SrcCD, UtilT) - - GNATS (GNats: A Tracking System, not to be confused with GNAT, The GNU - Ada Translator) is a bug-tracking system. It is based upon the paradigm - of a central site or organization which receives problem reports and - negotiates their resolution by electronic mail. Although it has been - used primarily as a software bug-tracking system so far, it is - sufficiently generalized that it could be used for handling system - administration issues, project management, or any number of other - applications. - - * `gnuplot' (SrcCD, UtilT, WdwsD) - - `gnuplot' is an interactive program for plotting mathematical - expressions and data. It plots both curves (2 dimensions) & surfaces (3 - dimensions). Curiously, it was neither written nor named for the GNU - Project; the name is a coincidence. Various GNU programs use `gnuplot'. - - * `gnuserv' (LspEmcT, SrcCD) - - `gnuserv' is a enhanced version of Emacs' `emacsclient' program. It - lets the user direct a running Emacs to edit files or evaluate arbitrary - Emacs Lisp constructs from another process. - - * GnuGo (SrcCD, UtilT) - - GnuGo plays the game of Go (Wei-Chi); version 1.2 was released with minor - changes for portability, but it is not yet very sophisticated. - - * `gperf' (LangT, SrcCD) - - `gperf' generates perfect hash tables. The C version is in package - cperf. The C++ version is in libg++. Both produce hash functions in - either C or C++. - - * Graphics (SrcCD, UtilT) - - GNU Graphics produces x-y plots from ASCII or binary data. It outputs - in Postscript, Tektronix 4010 compatible, and Unix device-independent - "plot" formats. It has a previewer for the X Window System. Features - include a `spline' interpolation program; examples of shell scripts - using `graph' and `plot'; a statistics toolkit; and output in TekniCAD - TDA and ln03 file formats. Email bugs or queries to Rich Murphey, - `Rich@lamprey.utmb.edu'. - - * grep (DosBC, SrcCD, UtilT) - - This package has GNU `grep', `egrep', and `fgrep', which find lines that - match entered patterns. They are much faster than the traditional Unix - versions. - - * Groff (DjgpD, DosBC, SrcCD, UtilT) - - Groff is a document formatting system based on a device-independent - version of `troff' & includes: `eqn', `nroff', `pic', `refer', `tbl', - `troff'; the `man', `ms', & `mm' macros; & drivers for Postscript, TeX - `dvi' format, and typewriter-like devices. Groff's `mm' macro package - is almost compatible with the DWB `mm' macros with several extensions. - Also included is a modified version of the Berkeley `me' macros and an - enhanced version of the X11 `xditview' previewer. A driver for the - LaserJet 4 series of printers is currently in test. Written in C++, - these programs can be compiled with GNU C++ Version 2.5 or later. - - Groff users are encouraged to contribute enhancements. Most needed are - complete Texinfo documentation, a `grap' emulation (a `pic' preprocessor - for typesetting graphs), a page-makeup postprocessor similar to `pm' - (see `Computing Systems', Vol. 2, No. 2; ask `office@usenix.org' how to - get a copy), and an ASCII output class for `pic' to integrate `pic' with - Texinfo. Questions and bug reports from users who have read the - documentation provided with Groff can be sent to - `bug-groff@prep.ai.mit.edu'. - - * `gzip' (DjgpD, DosBC, LangT, LspEmcT, SrcCD, UtilT) - - `gzip' can expand LZW-compressed files but uses another, unpatented - algorithm for compression which generally produces better results. It - also expands files compressed with System V's `pack' program. - - * `hello' (DosBC, SrcCD, UtilT) - - The GNU `hello' program produces a familiar, friendly greeting. It - allows non-programmers to use a classic computer science tool which would - otherwise be unavailable to them. Because it is protected by the GNU - General Public License, users are free to share and change it. `hello' - is also a good example of a program that meets the GNU coding standards. - - Like any truly useful program, `hello' contains a built-in mail reader. - - * `hp2xx' (SrcCD, UtilT) - - GNU `hp2xx' reads HP-GL files, decomposes all drawing commands into - elementary vectors, and converts them into a variety of vector and raster - output formats. It is also an HP-GL previewer. Currently supported - vector formats include encapsulated Postscript, Uniplex RGIP, Metafont, - various special TeX-related formats, and simplified HP-GL (line drawing - only) for imports. Raster formats supported include IMG, PBM, PCX, & - HP-PCL (including Deskjet & DJ5xxC support). Previewers work under X11 - (Unix), OS/2 (PM & full screen), & MS-DOS (SVGA, VGA, & HGC). - - * HylaFAX (SrcCD, UtilT) - - HylaFAX (once named FlexFAX) is a facsimile system for Unix systems. It - supports sending, receiving, & polled retrieval of facsimile, as well as - transparent shared data use of the modem. - - Details are available on the World Wide Web at: - `http://www.vix.com/hylafax/'. - - * Hyperbole (LspEmcT, SrcCD) - - Hyperbole, written by Bob Weiner in Emacs Lisp, is an open, efficient, - programmable information management & hypertext system, intended for - everyday work on any platform supported by Emacs. - - * `indent' (DosBC, LangT, SrcCD, UtilD) - - GNU `indent' formats C source code into the GNU indentation style. It - also has options to output BSD, K&R, or your own special style. GNU - `indent' is more robust & provides more functionality than other such - programs, including handling C++ comments. It runs on a number of - systems, including DOS & VMS. - - The next version will also format C++ source code. - - * Ispell (DosBC, SrcCD, UtilT) - - Ispell is an interactive spell checker that suggests "near misses" to - replace unrecognized words. System & user-maintained dictionaries for - multiple languages can be used. Standalone & Emacs interfaces are - available. - - Previously, the FSF had its own version of Ispell ("Ispell 4.0"), but - has dropped it for a parallel branch that has had more development - ("Ispell 3.1"). (Ispell 3 was an earlier release by the original Ispell - author, but others have since made it more sophisticated.) - - * JACAL *Not available from the FSF except by FTP* - - JACAL is a symbolic mathematics system for the manipulation and - simplification of algebraic equations and expressions. New in JACAL is - multivariate factoring from Michael Thomas `(mjt@octavia.anu.edu.au)'. - See JACAL's documentation at `http://www-swiss.ai.mit.edu/~jaffer/'. - - JACAL is written in Scheme using the SLIB portable Scheme Library. It - comes with SCM, an IEEE P1178 & R4RS compliant version of Scheme written - in C. SCM runs on Amiga, Atari-ST, MS-DOS, OS/2, NOS/VE, Unicos, VMS, - Unix, & similar systems. - - The FSF is not distributing JACAL on any physical media. To get an IBM - PC floppy disk with the freely redistributable source & executable - files, send $99.00 to: - - Aubrey Jaffer - 84 Pleasant Street - Wakefield, MA 01880-1846 - USA - - * `less' (DosBC, SrcCD, UtilD, UtilT) - - `less' is a display paginator similar to `more' and `pg', but with - various features (such as the ability to scroll backwards) that most - pagers lack. - - * `m4' (DosBC, SrcCD, UtilD, UtilT) - - GNU `m4' is an implementation of the traditional Unix macro processor. - It is mostly SVR4 compatible, although it has some extensions (e.g., - handling more than 9 positional parameters to macros). `m4' also has - built-in functions for including files, running shell commands, doing - arithmetic, etc. - - * `make' (BinCD,DjgpD,DosBC,LangT,LspEmcT,SrcCD,UtilD,UtilT)[FSFman] - - GNU `make' supports POSIX 1003.2 and has all but a few obscure features - of the BSD and System V versions of `make'. GNU extensions include long - options, parallel compilation, flexible implicit pattern rules, - conditional execution, & powerful text manipulation functions. Texinfo - source for the `Make Manual' comes with the program (*note - Documentation::.). - - * MandelSpawn (SrcCD, UtilT) - - A parallel Mandelbrot generation program for the X Window System. - - * Midnight Commander (`mc') (SrcCD, UtilT) - - The Midnight Commander is a user friendly and colorful Unix file manager - and shell, useful to novice and guru alike. It has a built-in virtual - file system that allows the user to manipulate files inside tar files - (both regular and compressed) or files on remote machines using the FTP - protocol. - - * `mkisofs' (SrcCD, UtilT) - - `mkisofs' is a pre-mastering program to generate an ISO 9660 file system. - It takes a snapshot of a directory tree, and makes a binary image which - corresponds to an ISO 9660 file system when written to a block device. - - It can also generate the System Use Sharing Protocol records of the Rock - Ridge Interchange Protocol (used to further describe the files in an ISO - 9660 file system to a Unix host; it provides information such as longer - filenames, uid/gid, permissions, and device nodes). - - Also included is `cdwrite', which can take an image from `mkisofs' and - write it to a Phillips CD recorder system attached to a GNU/Linux system. - - * mtools (SrcCD, UtilT) - - mtools is a set of public domain programs to allow Unix systems to read, - write, and manipulate files on an MS-DOS file system (usually a - diskette). - - * MULE (DosBC, EmcsD, LspEmcT, SrcCD) - - MULE is a MULtilingual Enhancement to GNU Emacs. MULE text buffers can - contain a mix of characters from many languages including: Japanese, - Chinese, Korean, Vietnamese, Thai, modern European languages (including - Greek & Russian), Arabic, & Hebrew. MULE also provides input methods - for all of them. MULE is being merged into GNU Emacs. *Note GNU & - Other Free Software in Japan::, for more information about MULE. - - * `ncurses' (LangT, SrcCD) - - `ncurses' is an implementation of the Unix `curses' library for - developing screen based programs that are terminal independent. - - * NetHack (SrcCD, UtilT) - - NetHack is a Rogue-like adventure game supporting character & X displays. - - * NIH Class Library (LangT, SrcCD) - - The NIH Class Library (once known as "OOPS", Object-Oriented Program - Support) is a portable collection of C++ classes (similar to those in - Smalltalk-80) written in C++ by Keith Gorlen of the National Institutes - of Health (NIH). - - * `nvi' (SrcCD, UtilT) - - `nvi' is a free implementation of the `vi'/`ex' Unix editor. It has - most of the functionality of the original `vi'/`ex', except "open" mode - & the `lisp' option, which will be added. Enhancements over `vi'/`ex' - include split screens with multiple buffers, handling 8-bit data, - infinite file & line lengths, tag stacks, infinite undo, & extended - regular expressions. It runs under GNU/Linux, BSD, NetBSD, FreeBSD, - BSDI, AIX, HP-UX, DGUX, IRIX, PSF, PTX, Solaris, SunOS, Ultrix, and - Unixware, & should port easily to other systems. - - * Oaklisp (SrcCD) - - Oaklisp is a fast, portable, object-oriented Scheme with first class - types. - - * Objective-C Library **Note Forthcoming GNUs::* (LangT, SrcCD) - - Our Objective-C Class Library (`libobjects') has general-purpose, - non-graphical Objective-C objects written by Andrew McCallum & other - volunteers. It includes collection classes for using groups of objects - & C types, I/O streams, coders for formatting objects & C types to - streams, ports for network packet transmission, distributed objects - (remote object messaging), string classes, exceptions, pseudo-random - number generators, & time handling facilities. It also includes the - foundation classes for the GNUStep project; over 70 of them have already - been implemented. The library is known to work on i386/i486/Pentiums, - m68k, SPARC, MIPS, HPPA, & RS/6000. Send queries & bug reports to - `mccallum@gnu.ai.mit.edu'. - - * OBST (LangT, SrcCD) - - OBST is a persistent object management system with bindings to C++. - OBST supports incremental loading of methods. Its graphical tools - require the X Window System. It features a hands-on tutorial including - sample programs. It compiles with G++, and should install easily on - most Unix platforms. - - * Octave (LangT, SrcCD) - - Octave is a high-level language similar to MATLAB, primarily intended - for numerical computations. It has a convenient command line interface - for solving linear & nonlinear problems numerically. - - Octave does arithmetic for real and complex scalars and matrices, solves - sets of nonlinear algebraic equations, integrates systems of ordinary - differential & differential-algebraic equations, and integrates - functions over finite & infinite intervals. Two- & three-dimensional - plotting is available using `gnuplot'. - - Send queries and bug reports to: `bug-octave@bevo.che.wisc.edu'. - - Texinfo source is included for a 220+ page Octave manual, not yet - published by the FSF. - - * Oleo (SrcCD, UtilT) - - Oleo is a spreadsheet program (better for you than the more expensive - spreadsheets). It supports the X Window System and character-based - terminals, and can output Embedded Postscript renditions of spreadsheets. - Keybindings should be familiar to Emacs users and are configurable. - Oleo supports multiple variable-width fonts when used under the X Window - System or outputting to Postscript devices. - - * `p2c' (LangT, SrcCD) - - `p2c' is Dave Gillespie's Pascal-to-C translator. It inputs many - different dialects (HP, ISO, Turbo, VAX, et al.) and generates readable, - maintainable, portable C. - - * `patch' (DosBC, SrcCD, UtilT) - - `patch' is our version of Larry Wall's program to take `diff''s output - and apply those differences to an original file to generate the modified - version. - - * PCL (LspEmcT, SrcCD) - - PCL is a free implementation of a large subset of CLOS, the Common Lisp - Object System. It runs under both GCL and CLISP, mentioned above. - - * `perl' (DosBC, LangT, SrcCD) - - Larry Wall's `perl' combines the features and capabilities of `sed', - `awk', `sh', and C. It also provides interfaces to the Unix system - calls and many C library routines. - - * `pine' (SrcCD, UtilT) - - `pine' is a friendly menu-driven electronic mail manager and user - interface . - - * `ptx' **Note Forthcoming GNUs::* (SrcCD, UtilD, UtilT) - - GNU `ptx' is our version of the traditional permuted index generator. - It handles multiple input files at once, produces TeX compatible output, - and generates readable "KWIC" (KeyWords In Context) indexes without - using `nroff'. - - It does not yet handle input files that do not fit in memory all at once. - - * `rc' (SrcCD, UtilT) - - `rc' is a shell that features a C-like syntax (much more so than `csh') - and far cleaner quoting rules than the C or Bourne shells. It's - intended to be used interactively, but is also great for writing - scripts. It inspired the shell `es'. - - * RCS (SrcCD, UtilD, UtilT) - - RCS, the Revision Control System, is used for version control & - management of software projects. Used with GNU `diff', RCS can handle - binary files (executables, object files, 8-bit data, etc). RCS now - conforms to GNU configuration standards and to POSIX 1003.1b-1993. Also - see the CVS item above. - - * `recode' **Note Forthcoming GNUs::* (SrcCD, UtilT) - - GNU `recode' converts files between character sets and usages. When - exact transliterations are not possible, it may delete the offending - characters or fall back on approximations. This program recognizes or - outputs nearly 150 different character sets and is able to transliterate - files between almost any pair. Most RFC 1345 character sets are - supported. - - * `regex' (LangT, SrcCD) - - The GNU regular expression library supports POSIX.2, except for - internationalization features. It is included in many GNU programs which - do regular expression matching & is available separately. An alternate - regular expression package, `rx', is faster than `regex' in most cases & - will replace `regex' over time. - - * `rx' (LangT, SrcCD) - - Tom Lord has written `rx', a new regular expression library which is - faster than the older GNU `regex' library. It is now being distributed - with `sed' and `tar'. `rx' will be used in the next releases of `m4' - and `ptx'. - - * SAOimage (SrcCD, UtilT) - - SAOimage is an X-based astronomical image viewer. It reads data images - and displays them with a pseudocolor colormap. There is full interactive - control of the colormap, reading, and writing of colormaps, etc. - - * Scheme *For more information, see *Note Scheme Tape::* (SrcCD, SchmT) - - * `screen' (SrcCD, UtilT) - - `screen' is a terminal multiplexer that runs several separate "screens" - (ttys) on a single character-based terminal. Each virtual terminal - emulates a DEC VT100 plus several ISO 2022 and ISO 6429 (ECMA 48, ANSI - X3.64) functions, including color. Arbitrary keyboard input translation - is also supported. `screen' sessions can be detached and resumed later - on a different terminal type. Output in detached sessions is saved for - later viewing. - - * `sed' (DjgpD, DosBC, SrcCD, UtilD, UtilT) - - `sed' is a stream-oriented version of `ed'. It comes with the `rx' - library. - - * Sharutils (SrcCD, UtilT) - - `shar' makes so-called shell archives out of many files, preparing them - for transmission by electronic mail services; `unshar' helps unpack - these shell archives after reception. `uuencode' and `uudecode' are - POSIX compliant implementations of a pair of programs to transform files - into a format that can be safely transmitted across a 7-bit ASCII link. - - * Shellutils (DosBC, SrcCD, UtilT) - - They are: `basename', `date', `dirname', `echo', `env', `expr', `false', - `groups', `hostname', `id', `logname', `nice', `nohup', `pathchk', - `printenv', `printf', `pwd', `sleep', `stty', `su', `tee', `test', - `true', `tty', `uname', `users', `who', `whoami', & `yes'. - - * Shogi (SrcCD, UtilT) - - Shogi is a Japanese game similar to Chess; a major difference is that - captured pieces can be returned into play. - - GNU Shogi is a variant of GNU Chess; it implements the same features & - similar heuristics. As a new feature, sequences of partial board - patterns can be introduced to help the program play toward specific - opening patterns. It has both character and X display interfaces. - - It is primarily supported by Matthias Mutz on behalf of the FSF. - - * SIPP (SrcCD) - - SIPP is a library for creating photorealistic renderings of 3D scenes. - A scene is built up of objects which can be transformed with rotation, - translation, and scaling. The objects form hierarchies where each object - can have arbitrarily many subobjects and subsurfaces. A surface is a - number of connected polygons which are rendered with either Phong, - Gouraud, or flat shading. The library supports programmable shaders and - texture mapping with textures in up to 3 dimensions and automatic - interpolation of texture coordinates. A scene can be illuminated by an - arbitrary number of light sources. The lights from some of them are - capable of casting shadows of objects. - - * Smalltalk *Also see *Note Forthcoming GNUs::* (LangT,SrcCD) - - GNU Smalltalk is an interpreted object-oriented programming language - system written in highly portable C. It has been ported to many Unix, - DOS, & other OSes. Features include a binary image save capability, the - ability to call user-written C code with parameters, an Emacs editing - mode, a version of the X protocol invocable from Smalltalk, optional - byte-code compilation and/or execution tracing, & automatically loaded - per-user initialization files. It implements all of the classes & - protocol in the book "Smalltalk-80: The Language", except for the - graphic user interface (GUI) related classes. - - * SNePS (SrcCD) - - SNePS is the Semantic Network Processing System. It is an - implementation of a fully intensional theory of propositional knowledge - representation and reasoning. SNePS runs under CLISP or GCL. - - * Spinner (SrcCD) - - Spinner is a modularized, object oriented, non-forking World Wide Web - server with high performance and throughput. - - * Superopt (LangT, SrcCD) - - Superopt is a function sequence generator that uses an exhaustive - generate-and-test approach to find the shortest instruction sequence for - a given function. You provide a function as input, a CPU to generate - code for, and how many instructions you want. Its use in GCC is - described in the `ACM SIGPLAN PLDI'92 Proceedings'. It supports: SPARC, - m68k, m68020, m88k, IBM POWER and PowerPC, AMD 29k, Intel x86 and 960, - Pyramid, DEC Alpha, Hitachi SH, & HP-PA. - - * `tar' (DosBC, SrcCD, UtilT) - - GNU `tar' includes multi-volume support, the ability to archive sparse - files, compression/decompression, remote archives, and special features - that allow `tar' to be used for incremental and full backups. GNU `tar' - uses an early draft of the POSIX 1003.1 `ustar' format which is - different from the final version. This will be corrected in the future. - - * Termcap Library (SrcCD, UtilT) [FSFman] - - The GNU Termcap library is a drop-in replacement for `libtermcap.a' on - any system. It does not place an arbitrary limit on the size of Termcap - entries, unlike most other Termcap libraries. Included is source for the - `Termcap Manual' in Texinfo format (*note Documentation::.). - - * Termutils (SrcCD, UtilT) - - The Termutils package contains programs for controlling terminals. - `tput' is a portable way for shell scripts to use special terminal - capabilities. `tabs' is a program to set hardware terminal tab settings. - - * TeX (DosBC, SrcCD) - - TeX is a document formatting system that handles complicated - typesetting, including mathematics. It is GNU's standard text formatter. - - The University of Washington maintains & supports a tape distribution of - TeX for Unix systems. The core material is Karl Berry's `web2c' TeX - package. Sources are available via anonymous ftp; retrieval - instructions are in `/pub/tex/unixtex.ftp' on `ftp.cs.umb.edu'. If you - receive any installation support from the University of Washington, - consider sending them a donation. - - To order a full distribution written in `tar' on either a 1/4inch - 4-track QIC-24 cartridge or a 4mm DAT cartridge, send $210.00 to: - - Pierre A. MacKay - Department of Classics - DH-10, Denny Hall 218 - University of Washington - Seattle, WA 98195 - USA - - Electronic-Mail: `mackay@cs.washington.edu' - Telephone: +1-206-543-2268 - - Please make checks payable to: `University of Washington'. Do not - specify any other payee. That causes accounting problems. Checks must - be in U.S. dollars, drawn on a U.S. bank. Only prepaid orders can be - handled. Overseas sites: please add to the base cost $20.00 to ship via - air parcel post or $30.00 to ship via courier. Please check with the - above for current prices & formats. - - * Texinfo (DjgpD,DosBC,LangT,LspEmcT,SrcCD,UtilD,UtilT)[FSFman] - - Texinfo is a set of utilities (`makeinfo', `info', `texi2dvi', - `texindex', `tex2patch', & `fixfonts') which generate both printed - manuals & online hypertext documentation (called "Info"), & can read - online Info documents. Version 3 has both Emacs Lisp & standalone - programs written in C or shell script. Texinfo mode for Emacs enables - easy editing & updating of Texinfo files. Source for the `Texinfo - Manual' is included (*note Documentation::.). - - * Textutils (DosBC, SrcCD, UtilT) - - The Textutils programs manipulate textual data. They include: `cat', - `cksum', `comm', `csplit', `cut', `expand', `fmt', `fold', `head', - `join', `md5sum', `nl', `od', `paste', `pr', `sort', `split', `sum', - `tac', `tail', `tr', `unexpand', `uniq', and `wc'. - - * Tile Forth (LangT, SrcCD) - - Tile Forth is a 32-bit implementation of the Forth-83 standard written - in C, allowing it to be easily ported to new systems and extended with - any C-function (graphics, windowing, etc). - - Many documented Forth libraries are available, including ones for - top-down parsing, multi-threads, & object oriented programming. - - * `time' (SrcCD, UtilT) - - `time' reports (usually from a shell) the user, system, & real time used - by a process. On some systems it also reports memory usage, page - faults, etc. - - * `ucblogo' (LangT, SrcCD) - - `ucblogo' implements the classic teaching language, Logo. - - * UUCP (SrcCD, UtilT) - - GNU's UUCP system (written by Ian Lance Taylor) supports the `f', `g', - `v' (all window & packet sizes), `G', `t', `e', Zmodem, & two new - bidirectional (`i' & `j') protocols. With a BSD sockets library, it can - make TCP connections. With TLI libraries, it can make TLI connections. - Source is included for a manual (not yet published by the FSF). - - * W3 (LspEmcT, SrcCD) - - W3 (written by William Perry in Emacs Lisp) is an extensible, advanced - World Wide Web browser that runs as part of GNU Emacs. It understands - many protocols: FTP, gopher, HTML, SMTP, Telnet, WAIS, et al. - - * `wdiff' (DosBC, SrcCD, UtilT) - - `wdiff' is a front-end to GNU `diff'. It compares two files, finding - the words deleted or added to the first to make the second. It has many - output formats and works well with terminals and pagers. `wdiff' is - very useful when two texts differ only by a few words and paragraphs - have been refilled. - - * X11 *For details, see *Note X11 Tapes::* (SrcCD, X11OptT, X11ReqT) - - * `xboard', `xshogi' (SrcCD, UtilT) - - `xboard' is an X Window interface to GNU Chess. `xshogi' is an X Window - interface to GNU Shogi. They use the R4 Athena widgets and Xt - Intrinsics to provide an interactive referee for managing a game between - a user & a computer opponent, or between two computers. You can also use - `xboard' without GNU Chess to play through games in files or to play - through games manually (force mode); in this case, moves aren't - validated. - - * `xgrabsc' (SrcCD) - - `xgrabsc' is a screen capture program similar to `xwd' but providing - more ways of selecting the part of the screen to capture and different - types of output: Postscript, color Postscript, xwd, bitmap, pixmap, and - puzzle. - - * `Ygl' (SrcCD, UtilT) - - `Ygl' emulates a subset of SGI's GL (Graphics Language) library under - X11 on GNU/Linux with XFree, AIX 3.2, ConvexOS, HP-UX, SunOS, et al. It - has most two-dimensional graphics routines, the queue device & query - routines, double buffering, RGB mode with dithering, FORTRAN bindings, - at al. - - - -Program/Package Cross Reference -******************************* - -Here is a list of what package each GNU program or library is in. You can FTP -the current list in the file `/pub/gnu/ProgramIndex' from a GNU FTP host -(listed in *Note How to Get GNU Software::). - - * a2p perl - * a2x xopt - * ac bsd44 - * accton bsd44 - * ackpfd phttpd - * acl bsd44 - * acm acm - * acms acm - * addftinfo Groff - * adventure bsd44 - * afm2tfm TeX - * amd bsd44 - * ansitape bsd44 - * AnswerGarden xopt - * apply bsd44 - * appres xreq - * apropos bsd44 - * ar Binutils - * arithmetic bsd44 - * arp bsd44 - * atc bsd44 - * autoconf Autoconf - * autoheader Autoconf - * autoreconf Autoconf - * autoscan Autoconf - * autoupdate Autoconf - * auto_box xopt - * auto_box xreq - - * b2m Emacs - * backgammon bsd44 - * bad144 bsd44 - * badsect bsd44 - * banner bsd44 - * basename Shellutils - * bash BASH - * battlestar bsd44 - * bc bc - * bcd bsd44 - * bdes bsd44 - * bdftops Ghostscript - * beach_ball xopt - * beach_ball xreq - * beach_ball2 xopt - * bibtex TeX - * biff bsd44 - * bison Bison - * bitmap xreq - * boggle bsd44 - * bpltobzr Fontutils - * bugfiler bsd44 - * buildhash Ispell - * bzrto Fontutils - - * c++ GCC - * c++filt Binutils - * c2ph perl - * ca100 xopt - * caesar bsd44 - * cal bsd44 - * calendar bsd44 - * canfield bsd44 - * cat Textutils - * cbars wdiff - * cc GCC - * cc1 GCC - * cc1obj GCC - * cc1plus GCC - * cccp GCC - * cdwrite mkisofs - * cfengine cfengine - * cgi Spinner - * charspace Fontutils - * checknr bsd44 - * chess bsd44 - * chflags bsd44 - * chgrp Fileutils - * ching bsd44 - * chmod Fileutils - * chown Fileutils - * chpass bsd44 - * chroot bsd44 - * ci RCS - * cksum Textutils - * cktyps g77 - * clisp CLISP - * clri bsd44 - * cmail xboard - * cmmf TeX - * cmodext xopt - * cmp Diffutils - * co RCS - * col bsd44 - * colcrt bsd44 - * colrm bsd44 - * column bsd44 - * comm Textutils - * compress bsd44 - * comsat bsd44 - * connectd bsd44 - * cp Fileutils - * cpicker xopt - * cpio cpio - * cpp GCC - * cppstdin perl - * cribbage bsd44 - * crock xopt - * csh bsd44 - * csplit Textutils - * ctags Emacs - * ctwm xopt - * cu UUCP - * cut Textutils - * cvs CVS - * cvscheck CVS - * cvtmail Emacs - * cxterm xopt - - * d Fileutils - * date Shellutils - * dc bc - * dd Fileutils - * ddd DDD - * delatex TeX - * demangle Binutils - * descend CVS - * detex TeX - * df Fileutils - * dhtppd phttpd - * diff Diffutils - * diff3 Diffutils - * digest-doc Emacs - * dipress bsd44 - * dir Fileutils - * dirname Shellutils - * dish xopt - * disklabel bsd44 - * diskpart bsd44 - * dld dld - * dm bsd44 - * dmesg bsd44 - * doschk doschk - * dox xopt - * du Fileutils - * dump bsd44 - * dump mkisofs - * dumpfs bsd44 - * dvi2tty TeX - * dvicopy TeX - * dvips TeX - * dvitype TeX - - * ecc ecc - * echo Shellutils - * ed ed - * edit-pr GNATS - * editres xreq - * edquota bsd44 - * eeprom bsd44 - * egrep grep - * emacs Emacs - * emacsclient Emacs - * emacsserver Emacs - * emacstool Emacs - * emu xopt - * env Shellutils - * eqn Groff - * error bsd44 - * es es - * esdebug es - * etags Emacs - * ex nvi - * expand Textutils - * expect DejaGnu - * expr Shellutils - * exterm xopt - - * f2c f2c - * factor bsd44 - * fakemail Emacs - * false Shellutils - * fastboot bsd44 - * fax2ps HylaFAX - * faxalter HylaFAX - * faxanswer HylaFAX - * faxcover HylaFAX - * faxd HylaFAX - * faxd.recv HylaFAX - * faxmail HylaFAX - * faxquit HylaFAX - * faxrcvd HylaFAX - * faxrm HylaFAX - * faxstat HylaFAX - * fc f2c - * fdraw xopt - * ffe g77 - * fgrep grep - * file bsd44 - * find Findutils - * find2perl perl - * finger Finger - * fingerd Finger - * fish bsd44 - * fixfonts Texinfo - * fixinc.svr4 GCC - * fixincludes GCC - * flex flex - * flex++ flex - * fmt bsd44 - * fold Textutils - * font2c Ghostscript - * fontconvert Fontutils - * forth Tile Forth - * forthicon Tile Forth - * forthtool Tile Forth - * fortune bsd44 - * fpr bsd44 - * freq Ispell - * freqtbl Ispell - * from bsd44 - * fsck bsd44 - * fsplit bsd44 - * fstat bsd44 - * ftp bsd44 - * ftpd bsd44 - - * g++ GCC - * gas Binutils - * gawk GAWK - * gcc GCC - * gcore bsd44 - * gdb GDB - * genclass libg++ - * gettext gettext - * getty bsd44 - * gftodvi TeX - * gftopk TeX - * gftype TeX - * ghostview Ghostview - * git GIT - * gitaction GIT - * gitcmp GIT - * gitkeys GIT - * gitmatch GIT - * gitmount GIT - * gitps GIT - * gitredir GIT - * gitrgrep GIT - * gitview GIT - * gitwipe GIT - * gn GN - * gnans Gnans - * gnanslator Gnans - * gnats GNATS - * gnuchess Chess - * gnuchessc Chess - * gnuchessn Chess - * gnuchessr Chess - * gnuchessx Chess - * gnuclient gnuserv - * gnudoit gnuserv - * gnupdisp Shogi - * gnuplot gnuplot - * gnuplot_x11 gnuplot - * gnuserv gnuserv - * gnushogi Shogi - * gnushogir Shogi - * gnushogix Shogi - * go GnuGo - * gpc xopt - * gpc xreq - * gperf cperf - * gperf libg++ - * gprof Binutils - * graph Graphics - * grep grep - * grodvi Groff - * groff Groff - * grops Groff - * grotty Groff - * groups Shellutils - * gs Ghostscript - * gsbj Ghostscript - * gsdj Ghostscript - * gslj Ghostscript - * gslp Ghostscript - * gsnd Ghostscript - * gsrenderfont Fontutils - * gunzip gzip - * gwm xopt - * gzexe gzip - * gzip gzip - - * h2ph perl - * h2pl perl - * hack bsd44 - * hangman bsd44 - * head Textutils - * hello hello - * hexdump bsd44 - * hexl Emacs - * hostname Shellutils - * hp2xx hp2xx - * hterm xopt - * htmlencode phttpd - * httpd apache - * httpdecode phttpd - - * i18nOlwmV2 xopt - * i2mif xopt - * ico xopt - * ico xreq - * id Shellutils - * ident RCS - * ifconfig bsd44 - * ifnames Autoconf - * ImageMagick xopt - * imageto Fontutils - * iman xopt - * imgrotate Fontutils - * indent indent - * indxbib Groff - * inetd bsd44 - * info Texinfo - * inimf TeX - * init bsd44 - * initex TeX - * inn bsd44 - * install Fileutils - * iostat bsd44 - * isodiag mkisofs - * isodump mkisofs - * ispell Ispell - * ixterm xopt - * ixx xopt - - * join Textutils - * jot bsd44 - * jove bsd44 - - * kdestroy bsd44 - * kdump bsd44 - * kermit bsd44 - * kgames xopt - * kgmon bsd44 - * kill bsd44 - * kinit bsd44 - * kinput2 xopt - * klist bsd44 - * kpasswdd bsd44 - * ksrvtgt bsd44 - * kterm xopt - * ktrace bsd44 - - * lam bsd44 - * larn bsd44 - * lasergnu gnuplot - * last bsd44 - * lastcomm bsd44 - * latex TeX - * lclock xopt - * ld Binutils - * leave bsd44 - * less less - * lesskey less - * libavcall.a ffcall - * libbfd.a Binutils - * libbfd.a GDB - * libbzr.a Fontutils - * libc.a C Library - * libcompat.a bsd44 - * libcurses.a bsd44 - * libcurses.a ncurses - * libdcurses.a ncurses - * libedit.a bsd44 - * libF77.a f2c - * libF77.a g77 - * libg++.a libg++ - * libgdbm.a gdbm - * libgf.a Fontutils - * libgmp.a gmp - * libgnanslib Gnans - * libI77.a f2c - * libI77.a g77 - * libkvm.a bsd44 - * libm.a bsd44 - * libncurses.a ncurses - * libnihcl.a NIHCL - * libnihclmi.a NIHCL - * libnihclvec.a NIHCL - * libnls.a xreq - * libobjects.a libobjects - * liboctave.a Octave - * liboldX.a xreq - * libpbm.a Fontutils - * libPEXt.a xopt - * libpk.a Fontutils - * libresolv.a bsd44 - * librpc.a bsd44 - * libsipp.a SIPP - * libtcl.a DejaGnu - * libtelnet.a bsd44 - * libterm.a bsd44 - * libtermcap.a Termcap - * libtfm.a Fontutils - * libutil.a bsd44 - * libvacall.a ffcall - * libWc.a xopt - * libwidgets.a Fontutils - * libX.a xreq - * libXau.a xreq - * libXaw.a xreq - * libXcp.a xopt - * libXcu.a xopt - * libXdmcp.a xreq - * libXmp.a xopt - * libXmu.a xreq - * libXO.a xopt - * libXop.a xopt - * libXp.a xopt - * libXpex.a xopt - * libXt.a xopt - * libXt.a xreq - * libXwchar.a xopt - * liby.a bsd44 - * libYgl.a Ygl - * limn Fontutils - * listres xopt - * listres xreq - * lkbib Groff - * ln Fileutils - * locate Findutils - * lock bsd44 - * logcvt-ip2n phttpd - * logger bsd44 - * login bsd44 - * logname Shellutils - * logo ucblogo - * lookbib Groff - * lorder bsd44 - * lpr bsd44 - * ls Fileutils - - * m4 m4 - * mail bsd44 - * mail-files Sharutils - * mailshar Sharutils - * make make - * make-docfile Emacs - * make-path Emacs - * makeindex TeX - * makeinfo Texinfo - * MakeTeXPK TeX - * man bsd44 - * man-macros Groff - * mattrib mtools - * maze xopt - * maze xreq - * mazewar xopt - * mc mc - * mcd mtools - * mcopy mtools - * mcserv mc - * mdel mtools - * mdir mtools - * me-macros Groff - * merge RCS - * mesg bsd44 - * mf TeX - * mformat mtools - * mft TeX - * mgdiff xopt - * mh bsd44 - * mille bsd44 - * mkcache GN - * mkdep bsd44 - * mkdir Fileutils - * mkfifo Fileutils - * mkisofs mkisofs - * mklocale bsd44 - * mkmanifest mtools - * mkmf bsd44 - * mkmodules CVS - * mknod Fileutils - * mkstr bsd44 - * mlabel mtools - * mm-macros Groff - * mmd mtools - * monop bsd44 - * more bsd44 - * morse bsd44 - * mount bsd44 - * mountd bsd44 - * movemail Emacs - * mprof bsd44 - * mrd mtools - * mread mtools - * mren mtools - * ms-macros Groff - * msgcmp gettext - * msgfmt gettext - * msgmerge gettext - * msgs bsd44 - * msgunfmt gettext - * mst Smalltalk - * mt cpio - * mterm xopt - * mtree bsd44 - * mtype mtools - * mule MULE - * muncher xopt - * mv Fileutils - * mvdir Fileutils - * mwrite mtools - - * nethack NetHack - * netstat bsd44 - * newfs bsd44 - * nfsd bsd44 - * nfsiod bsd44 - * nfsstat bsd44 - * nice Shellutils - * nl Textutils - * nlmconv Binutils - * nm Binutils - * nohup Shellutils - * notify HylaFAX - * nroff Groff - * number bsd44 - - * objc GCC - * objcopy Binutils - * objdump Binutils - * objective-c GCC - * obst-boot OBST - * obst-CC OBST - * obst-cct OBST - * obst-cgc OBST - * obst-cmp OBST - * obst-cnt OBST - * obst-cpcnt OBST - * obst-csz OBST - * obst-dir OBST - * obst-dmp OBST - * obst-gen OBST - * obst-gsh OBST - * obst-init OBST - * obst-scp OBST - * obst-sil OBST - * obst-stf OBST - * oclock xreq - * octave Octave - * od Textutils - * oleo Oleo - * ora-examples xopt - - * p2c p2c - * pagesize bsd44 - * palette xopt - * pascal bsd44 - * passwd bsd44 - * paste Textutils - * patch patch - * patgen TeX - * pathalias bsd44 - * pathchk Shellutils - * pax bsd44 - * pbmplus xopt - * perl perl - * pfbtops Groff - * phantasia bsd44 - * phttpd phttpd - * pic Groff - * pico pine - * pig bsd44 - * pine pine - * ping bsd44 - * pixedit xopt - * pixmap xopt - * pktogf TeX - * pktype TeX - * plaid xopt - * plot2fig Graphics - * plot2plot Graphics - * plot2ps Graphics - * plot2tek Graphics - * pltotf TeX - * pollrcvd HylaFAX - * pom bsd44 - * pooltype TeX - * portmap bsd44 - * ppt bsd44 - * pr Textutils - * pr-addr GNATS - * pr-edit GNATS - * primes bsd44 - * printenv Shellutils - * printf Shellutils - * protoize GCC - * proxygarb Spinner - * ps bsd44 - * ps2ascii Ghostscript - * ps2epsi Ghostscript - * ps2fax HylaFAX - * psbb Groff - * pstat bsd44 - * psycho xopt - * ptester phttpd - * ptx ptx - * pubdic+ xopt - * puzzle xopt - * puzzle xreq - * pwd Shellutils - * pyramid xopt - - * query-pr GNATS - * quiz bsd44 - * quot bsd44 - * quota bsd44 - * quotacheck bsd44 - * quotaon bsd44 - - * rain bsd44 - * random bsd44 - * ranlib Binutils - * rbootd bsd44 - * rc rc - * rcp bsd44 - * rcs RCS - * rcs-to-cvs CVS - * rcs2log Emacs - * rcsdiff RCS - * rcsfreeze RCS - * rcsmerge RCS - * rdist bsd44 - * reboot bsd44 - * recode recode - * recvstats HylaFAX - * red ed - * refer Groff - * remsync Sharutils - * renice bsd44 - * repquota bsd44 - * restore bsd44 - * rev bsd44 - * rexecd bsd44 - * rlog RCS - * rlogin bsd44 - * rlogind bsd44 - * rm Fileutils - * rmail bsd44 - * rmdir Fileutils - * rmt cpio - * rmt tar - * robots bsd44 - * rogue bsd44 - * route bsd44 - * routed bsd44 - * rr xopt - * rs bsd44 - * rsh bsd44 - * rshd bsd44 - * runtest DejaGnu - * runtest.exp DejaGnu - * ruptime bsd44 - * rwho bsd44 - * rwhod bsd44 - - * s2p perl - * sail bsd44 - * saoimage SAOimage - * savecore bsd44 - * sc bsd44 - * sccs bsd44 - * sccs2rcs CVS - * scdisp xopt - * screen screen - * script bsd44 - * scsiformat bsd44 - * sctext xopt - * sdiff Diffutils - * sed sed - * send-pr GNATS - * sendfax HylaFAX - * sendmail bsd44 - * sgi2fax HylaFAX - * sgn GN - * sh bsd44 - * shar Sharutils - * shinbun xopt - * shogi Shogi - * showfont xopt - * showmount bsd44 - * shutdown bsd44 - * size Binutils - * sj3 xopt - * sjxa xopt - * slattach bsd44 - * sleep Shellutils - * sliplogin bsd44 - * snake bsd44 - * snftobdf xopt - * soelim Groff - * sort Textutils - * sos2obst OBST - * spider xopt - * split Textutils - * startslip bsd44 - * stf OBST - * strings Binutils - * strip Binutils - * stty Shellutils - * su Shellutils - * sum Textutils - * superopt Superopt - * swapon bsd44 - * sync bsd44 - * sysctl bsd44 - * syslogd bsd44 - * systat bsd44 - - * tabs Termutils - * tac Textutils - * tail Textutils - * taintperl perl - * talk bsd44 - * talkd bsd44 - * tangle TeX - * tar tar - * tbl Groff - * tcl DejaGnu - * tclsh DejaGnu - * tcopy bsd44 - * tcp Emacs - * tee Shellutils - * tek2plot Graphics - * telnet bsd44 - * telnetd bsd44 - * test Shellutils - * test-g++ DejaGnu - * test-tool DejaGnu - * tetris bsd44 - * tex TeX - * tex3patch Texinfo - * texi2dvi Texinfo - * texindex Texinfo - * texspell TeX - * textfmt HylaFAX - * tfmtodit Groff - * tftopl TeX - * tftp bsd44 - * tftpd bsd44 - * tgrind TeX - * time time - * timed bsd44 - * timer Emacs - * timex xopt - * tip bsd44 - * tkpostage xopt - * tn3270 bsd44 - * touch Fileutils - * tput Termutils - * tr Textutils - * traceroute bsd44 - * transcript HylaFAX - * transfig xopt - * trek bsd44 - * trn3 bsd44 - * troff Groff - * trpt bsd44 - * trsp bsd44 - * true Shellutils - * tset bsd44 - * tsort bsd44 - * tty Shellutils - * ttygnans Gnans - * tunefs bsd44 - * tupdate gettext - * tvtwm xopt - * twm xreq - - * ul bsd44 - * ulpc Spinner - * umount bsd44 - * uname Shellutils - * uncompress gzip - * unexpand Textutils - * unifdef bsd44 - * unify wdiff - * uniq Textutils - * unprotoize GCC - * unshar Sharutils - * unvis bsd44 - * update bsd44 - * updatedb Findutils - * users Shellutils - * uuchk UUCP - * uucico UUCP - * uuconv UUCP - * uucp UUCP - * uucpd bsd44 - * uudecode Sharutils - * uudir UUCP - * uuencode Sharutils - * uulog UUCP - * uuname UUCP - * uupick UUCP - * uurate UUCP - * uusched UUCP - * uustat UUCP - * uuto UUCP - * uux UUCP - * uuxqt UUCP - - * v Fileutils - * vacation bsd44 - * vandal xopt - * vcdiff Emacs - * vdir Fileutils - * vftovp TeX - * vgrind bsd44 - * vi nvi - * viewres xopt - * viewres xreq - * vine xopt - * vipw bsd44 - * virmf TeX - * virtex TeX - * vis bsd44 - * vmstat bsd44 - * vptovf TeX - - * w bsd44 - * waisgn GN - * wakeup Emacs - * wall bsd44 - * wargames bsd44 - * wc Textutils - * wdiff wdiff - * weave TeX - * what bsd44 - * whatis bsd44 - * whereis bsd44 - * who Shellutils - * whoami Shellutils - * whois bsd44 - * window bsd44 - * winterp xopt - * wish DejaGnu - * worm bsd44 - * worms bsd44 - * write bsd44 - * wump bsd44 - - * x11perf xreq - * x2p perl - * xalarm xopt - * xancur xopt - * xargs Findutils - * xauth xreq - * xbfe Fontutils - * xbiff xopt - * xbiff xreq - * xboard xboard - * xboing xopt - * xbuffy3 xopt - * xcalc xopt - * xcalc xreq - * xcalendar xopt - * xcdplayer xopt - * xcell xopt - * xclipboard xreq - * xclock xreq - * xcmdmenu xopt - * xcms xopt - * xcmsdb xreq - * xcmstest xreq - * xco xopt - * xcolorize xopt - * xcolors xopt - * xconsole xreq - * xcrtca xopt - * xdaliclock xopt - * xdiary xopt - * xditview Groff - * xditview xopt - * xditview xreq - * xdm xreq - * xdpyinfo xreq - * xdu xopt - * xdvi TeX - * xdvi xopt - * xdvorak xopt - * xearth xopt - * xed xopt - * xedit xopt - * xedit xreq - * xev xopt - * xev xreq - * xexit xopt - * xeyes xopt - * xeyes xreq - * xfd xreq - * xfed xopt - * xfedor xopt - * xfeoak xopt - * xferstats HylaFAX - * xfig xopt - * xfontsel xopt - * xfontsel xreq - * xforecast xopt - * xgas xopt - * xgas xreq - * xgc xopt - * xgc xreq - * xgettext gettext - * xhearts xopt - * xhelp xopt - * xhost xreq - * xinit xreq - * xkeycaps xopt - * xkill xreq - * xlax xopt - * xlayout xopt - * xlbiff xopt - * xless xopt - * xload xopt - * xload xreq - * xlogin xopt - * xlogo xreq - * xlsatoms xreq - * xlsclients xreq - * xlsfonts xreq - * xmag xreq - * xmail xopt - * xmailbox xopt - * xmailwatcher xopt - * xman xopt - * xman xreq - * xmandel xopt - * xmessage xopt - * xmeter xopt - * xmh xreq - * xmh-icons xopt - * xmh.editor xopt - * xmodmap xreq - * xmon xopt - * xmove xopt - * xmphone xopt - * xpd xopt - * xphoon xopt - * xpipeman xopt - * xplot Graphics - * xpostit xopt - * xpr xopt - * xpr xreq - * xprompt xopt - * xproof xopt - * xprop xreq - * xpserv xopt - * xrdb xreq - * xrefresh xreq - * xrsh xopt - * xrubik xopt - * xrunclient xopt - * xscope xopt - * xscreensaver xopt - * xsession xopt - * xset xreq - * xsetroot xreq - * xshogi xshogi - * xstdcmap xreq - * xstr bsd44 - * xtalk xopt - * xterm xreq - * xterm_color xopt - * xtetris xopt - * xTeXcad.13 xopt - * xtiff xopt - * xtree xopt - * xtv xopt - * xwd xreq - * xwininfo xreq - * xwud xreq - - * yacc bsd44 - * yes Shellutils - * youbin xopt - * yow Emacs - - * zcat gzip - * zcmp gzip - * zdiff gzip - * zforce gzip - * zgrep gzip - * zmore gzip - * znew gzip - - * [ Shellutils - - - -Tapes -***** - -We offer Unix source code on tapes in `tar' format on these media: - - * 4mm DAT cartridge tape. - - * 8mm Exabyte cartridge tape. - - * Sun DC300XLP QIC-24 1/4in cartridge (readable on some other systems). - - * Hewlett-Packard 16-track DC600HC 1/4in cartridge tape. - - * IBM RS/6000 QIC-150 1/4in cartridge (readable on some other systems). - - * 1600bpi 9-track 1/2in reel tape. - -The contents of the various tapes for Unix systems are the same; only the -media are different. For prices, see the *note Free Software Foundation -Order Form::.. Source code for the manuals & reference cards is included -(*note Documentation::.). - -Some of the files on the tapes are compressed with `gzip' to allow more files -on each tape. Refer to the top-level `README' file at the beginning of each -tape for instructions on uncompressing them. `uncompress' and `unpack' *do -not work*! - - - -Languages Tape --------------- - -This tape contains programming tools: compilers, interpreters and, related -programs (parsers, translators, debuggers, linkers, etc.). - - * Binutils 2.6 - * Bison 1.24 - * C Library 1.09 - * cperf 2.1a - * DejaGnu 1.2 - * dld 3.2.3 - * ecc 1.2.1 - * f2c 1995.02.24 - * flex 2.5.2 - * g77 0.5.17 - * GAWK 2.15.6 - * GCC/G++/Objective-C 2.7.2 - * GDB 4.15.1 - * gdbm 1.7.3 - * gettext 0.10 - * gmp 1.3.2 - * gzip 1.2.4 - * indent 1.9.1 - * libg++ 2.7.1 - * libobjects 0.1.3 - * make 3.74 - * ncurses 1.9.4 - * NIHCL 3.1.4 - * OBST 3.4.3 - * Octave 1.1.1 - * p2c 1.20 - * perl 4.036 - * perl 5.001 - * regex 0.12 - * rx 0.05 - * Smalltalk 1.1.1 - * Superopt 2.5 - * Texinfo 3.6 - * Tile Forth 2.1 - * ucblogo 3.3 - - - -Lisps/Emacs Tape ----------------- - -This tape has Common Lisp systems and libraries, GNU Emacs, assorted -extensions that work with Emacs, manuals, & a few other important utilities. - - * Calc 2.02c - * CLISP 1995.12.04 - * CLX 5.02 - * Common Lisp 2.2 - * Elib 0.06 - * Emacs 18.59 - * Emacs 19.28 - * Emacs 19.30 - * GNU Emacs Lisp Reference Manual Ed. 1.03 for Version 18 - * GNU Emacs Lisp Reference Manual Ed. 2.4 for Version 19.29 - * gnuserv 2.1alpha - * gzip 1.2.4 - * Hyperbole 4.01 - * make 3.74 - * MULE 2.3 - * PCL 2.2 - * Programming in Emacs Lisp: An Introduction Ed. 1.04 - * Texinfo 3.6 - * W3 2.2.25 - - - -Utilities Tape --------------- - -This tape consists mostly of smaller utilities and miscellaneous applications. - - * acm 4.7 - * Autoconf 2.7 - * BASH 1.14.5 - * bc 1.03 - * cfengine 1.2.14 - * cfengine 1.2.22 - * Chess 4.0.pl75 - * cpio 2.3 - * CVS 1.6 - * Diffutils 2.7 - * doschk 1.1 - * ed 0.2 - * es 0.84 - * Fileutils 3.12 - * Findutils 4.1 - * Finger 1.37 - * Fontutils 0.6 - * Ghostscript 2.6.2 - * Ghostview 1.5 - * Ghostview for Windows 1.0 - * GIT 4.3.6 - * GNATS 3.2 - * GnuGo 1.2 - * gnuplot 3.5 - * Graphics 0.17 - * grep 2.0 - * Groff 1.10 - * gzip 1.2.4 - * hello 1.3 - * hp2xx 3.1.4 - * HylaFAX 3.0.0 - * Ispell 3.1.20 - * less 2.9.0 - * m4 1.4 - * make 3.74 - * MandelSpawn 0.07 - * mc 3.0 - * mkisofs 1.04 - * mm 1.07 - * mtools 2.0.7 - * NetHack 3.1.3 - * nvi 1.34 - * Oleo 1.6 - * patch 2.1 - * pine 3.91 - * ptx 0.4 - * rc 1.4 - * RCS 5.7 - * readline 2.0 - * recode 3.4 - * SAOimage 1.16 - * screen 3.7.1 - * sed 2.05 - * Sharutils 4.2 - * Shellutils 1.12 - * Shogi 1.2.3 - * tar 1.11.8 - * Termcap 1.3 - * Termutils 2.0 - * Texinfo 3.6 - * Textutils 1.13 - * time 1.6 - * UUCP 1.06.1 - * wdiff 0.5 - * xboard 3.4.pl0 - * xshogi 1.2.03 - * Ygl 3.0.3 - - - -Scheme Tape ------------ - -Scheme is a simplified, lexically-scoped dialect of Lisp. It was designed at -MIT and other universities to teach students the art of programming and to -research new parallel programming constructs and compilation techniques. - -This tape now has MIT Scheme 7.3, which conforms to the "Revised^4 Report On -the Algorithmic Language Scheme" (MIT AI Lab Memo 848b), for which TeX source -is included. It is written partly in C, but is presently hard to bootstrap. -Binaries that can be used to bootstrap it exist for: HP 9000 series 300, 400, -700, & 800 (running HP-UX 9.0), NeXT (NeXT OS 2 or 3.2), DEC Alpha (OSF/1), -IBM RS/6000 (AIX), Sun-3 or Sun-4 (SunOS 4.1), DECstation 3100/5100 (Ultrix -4.0), Sony NeWS-3250 (NEWS OS 5.01), & Intel i386 (MS-DOS, Windows 3.1 or NT). -If your system is not on this list & you don't enjoy the bootstrap challenge, -see "JACAL" in *Note GNU Software::. - - - -X11 Tapes ---------- - -The two X11 tapes contain Version 11, Release 6 of the X Window System. The -first tape has all of the core software, documentation, & some contributed -clients. We call this the "required" X tape since it is necessary for -running X or Emacs under X. The second, "optional" tape has contributed -libraries & toolkits, the Andrew User Interface System, games, etc. - -The X11 Required tape also contains all fixes and patches released to date. -We update this tape as new fixes and patches are released for programs on -both tapes. *Note Tape & CD-ROM Subscription Service::. - -While supplies last, we will distribute X11R5 on the *Note November 1993 -Source Code CD-ROM::. - - - -Berkeley 4.4BSD-Lite Tape -------------------------- - -The "4.4BSD-Lite" release is the last from the Computer Systems Research -Group at the University of California at Berkeley. It has most of the BSD -software system, except for a few files that remain proprietary. It is much -more complete than the previous "Net2" release. - - - -VMS Emacs and VMS Compiler Tapes --------------------------------- - -We offer two VMS tapes. One has just GNU Emacs 18.59 (none of the other -software on the *Note Lisps/Emacs Tape::, is included). The other has GCC -2.3.3, Bison 1.19 (to compile GCC), `gas' 1.38 (to assemble GCC's output), and -some library and include files (none of the other software on the *Note -Languages Tape::, is included). We are not aware of a GDB port for VMS. -Both VMS tapes have DEC VAX executables from which you can bootstrap, as the -DEC VMS C compiler cannot compile GCC. We do not have executables for DEC -Alpha VMS systems. Please do not ask us to devote effort to VMS support, -because it is peripheral to the GNU Project. - - - -CD-ROMs -******* - -We offer these CD-ROMs: - - * Several editions of our *Note Source Code CD-ROMs::. - - * *Note December 1995 Compiler Tools Binaries CD-ROM::. - - * *Note December 1994 Compiler Tools Binaries CD-ROM::. - - * *Note December 1993 Compiler Tools Binaries CD-ROM::. - - * *Note MS-DOS Book with CD-ROM::. - - * *Note Debian GNU/Linux Book with CD-ROM::. - -Our CD-ROMs are in ISO 9660 format & can be mounted as a read-only file -system on most computers. If your driver supports it you can mount each CD -with "Rock Ridge" extensions (the MS-DOS CD-ROM is only in ISO 9660 format), -& it will look just like an ordinary Unix file system, rather than one full -of truncated & otherwise mangled names that fit vanilla ISO 9660. - -You can build most of the software without copying the sources off the CD. -You only need enough disk space for object files and intermediate build -targets. - - - -Pricing of the GNU CD-ROMs --------------------------- - -If a business or organization is ultimately paying, the December 1995 Source -CDs costs $240. It costs $60 if you, an individual, are paying out of your -own pocket. The December 1995 Compiler Tools Binaries CD-ROM costs $220 for -a business or organization, and $55 for an individual. - - - -What do the individual and company prices mean? -............................................... - -The software on our disks is free; anyone can copy it and anyone can run it. -What we charge for is the physical disk and the service of distribution. - -We charge two different prices depending on who is buying. When a company or -other organization buys the December 1995 Source CD-ROMs, we charge $240. -When an individual buys the same CD-ROM, we charge just $60. This -distinction is not a matter of who is allowed to use the software. In either -case, once you have a copy, you can distribute as many copies as you wish and -there's no restriction on who can have or run them. The price distinction is -entirely a matter of what kind of entity pays for the CD. - -You, the reader, are certainly an individual, not a company. If you are -buying a disk "in person", then you are probably doing so as an individual. -But if you expect to be reimbursed by your employer, then the disk is really -for the company; so please pay the company price and get reimbursed for it. -We won't try to check up on you--we use the honor system--so please cooperate. - -Buying CDs at the company price is very helpful for GNU; just -140 Source CDs at that price support an FSF programmer or tech writer for a -year. - - - -Why is there an individual price? -................................. - -In the past, our distribution tapes have been ordered mainly by companies. -The CD at the price of $240 provides them with all of our software for a much -lower price than they would previously have paid for six different tapes. To -lower the price more would cut into the FSF's funds very badly and decrease -the software development we can do. - -However, for individuals, $240 is too high a price; hardly anyone could -afford that. So we decided to make CDs available to individuals at the lower -price of $60. - - - -Is there a maximum price? -......................... - -Our stated prices are minimum prices. Feel free to pay a higher price if you -wish to support GNU development more. The sky's the limit; we will accept as -high a price as you can offer. Or simply give a donation (tax-deductible in -the U.S.) to the Free Software Foundation, a tax-exempt public charity. - - - -December 1995 Compiler Tools Binaries CD-ROM --------------------------------------------- - -We now have the third edition of our CD-ROM that has binaries and complete -sources for GNU compiler tools for some systems which lack a compiler. This -enables the people who use these systems to compile GNU and other free -software without having to buy a proprietary compiler. You can also use -these GNU tools to compile your own C/C++/Objective-C programs. Older -editions of this CD are available while supplies last at a reduced price; see -the *note Free Software Foundation Order Form::.. - -We hope to have more systems on each update of this CD. If you can help -build binaries for new systems (especially those that don't come with a C -compiler), or have one to suggest, please contact us at the addresses on page -1. - -These packages: - - * DJGPP 1.12m4 from GCC 2.6.3 - * GCC/G++/Objective-C 2.7.1 - * GNU C Library 1.09 - * GDB 4.15.1 - * Binutils 2.6 - * Bison 1.24 - * Emacs 19.29 (MS-DOS only) - * Flex 2.5.2 - * Make 3.74 - * libg++ 2.7.1 - -On these platforms: - - * `i386-msdos' - * `hppa1.0-hp-hpux9' - * `sparc-sun-solaris2' - * `sparc-sun-sunos4.1' - - - -December 1994 Compiler Tools Binaries CD-ROM --------------------------------------------- - -We still have the 2nd edition of our CD-ROM that contains executables for GNU -compiler tools for some systems which lack a compiler. This enables the -people who use these systems to compile GNU and other free software without -having to buy a proprietary compiler. You can also use the GNU compilation -system to compile your own C/C++/Objective-C programs. - -We hope to have more systems on each update of this CD. If you can help -build binaries for new systems (especially those that don't come with a C -compiler), or have one to suggest, please contact us at the addresses on -page 1. - -These packages: - - *DJGPP 1.12.m2 from GCC 2.6.0 - *GCC/G++/Objective-C 2.6.2 - *GNU C Library 1.09 - *GDB 4.13 - *Binutils 2.5.2 - *Bison 1.22 - *Emacs 19.26 (MS-DOS only) - *Flex 2.4.7 - *Make 3.72.1 - *libg++ 2.6.1 - -On these platforms: - - *`i386-msdos' - *`hppa1.1-hp-hpux9' - *`sparc-sun-solaris2' - *`sparc-sun-sunos4.1' - - - -December 1993 Compiler Tools Binaries CD-ROM ---------------------------------------------- - -We still have the 1st edition of our CD-ROM that contains executables for GNU -compiler tools for some systems which lack a compiler. This will allow users -of those systems to compile GNU and other free software without having to buy -a proprietary compiler. - -The CD-ROM is in ISO 9660 format and can be mounted as a read-only file -system on most operating systems. If your driver supports it you can mount -the CD-ROM with "Rock Ridge" extensions and it will look just like an -ordinary Unix file system, rather than one full of truncated and otherwise -mangled names that fit the vanilla ISO 9660 specifications. - -We hope to have more systems included with each update of this CD-ROM. If -you can help build binaries for new systems (especially for systems that -don't come with a C compiler), or have a system to suggest, please contact us -at either address on the front cover. - -These programs: - - * DJGPP 1.11.m1 - - * GCC/G++/Objective C 2.5.7 - - * GDB 4.11 - - * GAS 2.2 - - * Binutils 2.3 - - * Bison 1.22 - - * Flex 2.4.5 - - * Make 3.70 - - * libg++ 2.5.3 - -For these platforms: - - * `i386-msdos' - - * `hppa1.1-hp-hpux9' - - * `sparc-sun-solaris2' - - * `sparc-sun-sunos4.1' - - - -Source Code CD-ROMs -------------------- - -We have several versions of our Source Code CD-ROMs available, including: - - * *Note December 1995 Source Code CD-ROMs::, the newest release, has - programs, bug fixes, & improvements not on the other CDs. - - * *Note June 1995 Source Code CD-ROM::. - - * *Note May 1994 Source Code CD-ROM::.. - - * *Note November 1993 Source Code CD-ROM::. - - * May 1993 Source Code CD-ROM, see the *note Free Software Foundation - Order Form::.. - - * October 1992 Source Code CD-ROM, see the *note Free Software Foundation - Order Form::.. - -The older Source CDs are available while supplies last at a reduced price -(please note that the December 1994 Source CD is permanently out of stock). -All the Source CDs have Texinfo source for the GNU manuals listed in *Note -Documentation::. - -The VMS tapes' contents are *not* included. Many programs that are only on -MS-DOS diskettes & not on the tapes are also *not* included. The MIT Scheme -& X11 Optional tapes' contents are *not* on the older Source CDs. *Note -Tapes:: & *Note MS-DOS Diskettes::. - -There are no precompiled programs on these Source CDs. You will need a C -compiler (programs which need some other interpreter or compiler normally -provide the C source for a bootstrapping program). We ship C compiler -binaries for some systems on the *Note Compiler Tools Binaries CD-ROM::. - - - -December 1995 Source Code CD-ROMs -................................. - -The 7th edition of our Source CD is out! Due to increasing amounts of GNU -Software, the Source Code CD is now a two disc set--the price remains -unchanged! It contains these packages, & some manuals that are not part of -packages: - - * acm 4.7 - * apache 0.8.8 - * Autoconf 2.7 - * BASH 1.14.5 - * bc 1.03 - * Binutils 2.5.2 - * Binutils 2.6 - * Bison 1.24 - * C Library 1.09 - * Calc 2.02c - * cfengine 1.2.21 - * Chess 4.0.pl75 - * CLISP 1995.08.12 - * Common Lisp 2.2 - * cperf 2.1a - * cpio 2.3 - * CVS 1.6 - * DDD 1.3b - * DejaGnu 1.2.9 - * Diffutils 2.7 - * dld 3.2.3 - * doschk 1.1 - * ecc 1.2.1 - * ed 0.2 - * Elib 0.07 - * Elisp archive - * Emacs 18.59 - * Emacs 19.28 - * Emacs 19.29 - * Emacs 19.30 - * es 0.84 - * f2c 1995.11.18 - * ffcall 1.0 - * Fileutils 3.12 - * Findutils 4.1 - * Finger 1.37 - * flex 2.5.2 - * Fontutils 0.6 - * g77 0.5.17 - * GAWK 2.15.6 - * GCC/G++/Objective C 2.7.1 - * GDB 4.15.1 - * gdbm 1.7.3 - * gettext 0.9a - * Ghostscript 2.6.2 - * Ghostview 1.5 - * Ghostview for Windows 1.0 - * GIT 4.3.7 - * gmp 1.3.2 - * GN 2.23 - * Gnans 1.5 - * GNATS 3.2 - * GNU Emacs Lisp Reference Manual, Ed. 1.03 for Version 18.59 - * GNU Emacs Lisp Reference Manual, Ed. 2.4 for Version 19.29 - * GnuGo 1.2 - * gnuplot 3.5 - * gnuserv 2.1alpha - * Graphics 0.17 - * grep 2.0 - * Groff 1.09 - * gzip 1.2.4 - * hello 1.3 - * hp2xx 3.1.4 - * HylaFAX v3.0pl0 - * Hyperbole 4.01 - * indent 1.9.1 - * Ispell 3.1.20 - * less 290 - * libg++ 2.7.1 - * libobjects 0.1.3 - * m4 1.4 - * make 3.74 - * mc 3.0 - * MIT Scheme 7.3 - * mkisofs 1.04GNU - * mtools 2.0.7 - * MULE 2.3 - * ncurses 1.9.7a - * NetHack 3.1.3 - * NIHCL 3.1.4 - * nvi 1.34 - * Oaklisp 93.07.23 - * OBST 3.4.3 - * Octave 1.1.1 - * Oleo 1.6 - * p2c 1.20 - * patch 2.1 - * perl 4.036 - * perl 5.001 - * phttpd 0.99.68 - * pine 3.91 - * Programming in Emacs Lisp: An Introduction, Ed. 1.04 - * ptx 0.4 - * rc 1.4 - * RCS 5.7 - * recode 3.4 - * regex 0.12 - * rx 0.05 - * SAOimage 1.08 - * screen 3.7.1 - * sed 2.05 - * Sharutils 4.1 - * Shellutils 1.12 - * Shogi 1.2p03 - * SIPP 3.1 - * Smalltalk 1.1.1 - * SNePS 2.3.1 - * Spinner 1.0b11 - * Superopt 2.5 - * tar 1.11.8 - * Termcap 1.3 - * TeX 3.145 - * Texinfo 3.6 - * Textutils 1.13 - * Tile Forth 2.1 - * time 1.6 - * tput 1.0 - * ucblogo 3.3 - * UUCP 1.06.1 - * W3 2.2.25 - * wdiff 0.5 - * X11R6 - * xboard 3.3.pl3 - * xgrabsc 2.41 - * xshogi 1.2p03 - * Ygl 3.0.2 - - - -June 1995 Source Code CD-ROM -............................ - -We still have the 6th edition of our Source CD at a reduced price while -supplies last. Not all FSF distributed software is included (*note Source -Code CD-ROMs::.). It contains these packages, and some manuals that are not -part of packages: - - * acm 4.7 - * Autoconf 2.4 - * BASH 1.14.5 - * bc 1.03 - * Binutils 2.5.2 - * Bison 1.24 - * C Library 1.09 - * Calc 2.02c - * cfengine 1.0.4 - * Chess 4.0.pl74 - * CLISP 1995.04.25 - * Common Lisp 2.1 - * cperf 2.1a - * cpio 2.3 - * CVS 1.3 - * DejaGnu 1.2 - * Diffutils 2.7 - * dld 3.2.3 - * doschk 1.1 - * ecc 1.2.1 - * ed 0.2 - * elib 0.06 - * Emacs 18.59 - * Emacs 19.28 - * Emacs 19.29 - * GNU Emacs Lisp Reference Manual Ed. 1.03 for Version 18 - * GNU Emacs Lisp Reference Manual Ed. 2.4 for Version 19.29 - * es 0.84 - * f2c 1995.02.24 - * Fileutils 3.12 - * Findutils 4.1 - * Finger 1.37 - * flex 2.5.2 - * Fontutils 0.6 - * g77 0.5.15 - * GAWK 2.15.6 - * GCC/G++/Objective C 2.6.3 - * GCC/G++/Objective C 2.7.0 - * GDB 4.14 - * gdbm 1.7.3 - * Ghostscript 2.6.2 - * Ghostview 1.5 - * Ghostview for Windows 1.0 - * GIT 4.3.6 - * gmp 1.3.2 - * GNATS 3.2 - * GnuGo 1.1 - * gnuplot 3.5 - * Graphics 0.17 - * grep 2.0 - * Groff 1.09 - * gzip 1.2.4 - * hello 1.3 - * hp2xx 3.1.4 - * HylaFAX 3.0.pl0 - * indent 1.9.1 - * Ispell 3.1.18 - * less 2.90 - * libg++ 2.6.2 - * libg++ 2.7.0 - * libobjects 0.1.3 - * m4 1.4 - * make 3.74 - * MandelSpawn 0.07 - * mkisofs 1.03GNU - * mtools 2.0.7 - * MULE 2.2 - * ncurses 1.9.1 - * NetHack 3.1.3 - * NIHCL 3.1.4 - * nvi 1.34 - * OBST 3.4.3 - * Octave 1.1.1 - * Oleo 1.6 - * p2c 1.20 - * patch 2.1 - * PCL 2.1 - * perl 4.036 - * perl 5.001 - * pine 3.91 - * Programming in Emacs Lisp: An Introduction Ed. 1.03 for Version 19 - * ptx 0.4 - * rc 1.4 - * RCS 5.7 - * recode 3.4 - * regex 0.12 - * rx 0.05 - * screen 3.6.2 - * sed 2.05 - * Sharutils 4.1 - * Shellutils 1.12 - * Shogi 1.2p03 - * Smalltalk 1.1.1 - * Superopt 2.5 - * tar 1.11.8 - * Termcap 1.2 - * TeX 3.1415 - * Texinfo 3.6 - * Textutils 1.12 - * Tile Forth 2.1 - * time 1.6 - * tput 1.0 - * ucblogo - * UUCP 1.05 - * wdiff 0.5 - * X11R6 - * xboard 3.2.pl2 - * xshogi 1.2p03 - * Ygl 2.9.5 - - - -May 1994 Source Code CD-ROM -........................... - -We still have the 4th edition of our Source CD, at a reduced price. This -CD has Edition 2.3 for version 19 of the `GNU Emacs Lisp Reference Manual' & -some additional software; not all FSF distributed software is included (see -``Source Code CD-ROMs''). It contains the following packages: - *acm 4.5 - *Autoconf 1.10 - *BASH 1.13.5 - *bc 1.02 - *Binutils 2.3 - *Bison 1.22 - *C Library 1.08 - *Calc 2.02c - *Chess 4.0.69 - *CLISP 1994.01.08 - *Common Lisp 1.0 - *cpio 2.3 - *CVS 1.3 - *dc 0.2 - *DejaGnu 1.2 - *Diffutils 2.6 - *dld 3.2.3 - *doschk 1.1 - *ecc 1.2.1 - *ed 0.1 - *elib 0.06 - *Emacs 18.59 - *Emacs 19.23 - *es 0.84 - *f2c 1994.04.14 - *Fileutils 3.9 - *find 3.8 - *finger 1.37 - *flex 2.4.6 - *Fontutils 0.6 - *GAS 1.36.utah - *GAS 2.2 - *Gawk 2.15.4 - *GCC 2.5.8 - *GDB 4.12 - *gdbm 1.7.1 - *Ghostscript 2.6.1 - *Ghostview 1.5 - *Ghostview for Windows 1.0 - *gmp 1.3.2 - *GNATS 3.2 - *GnuGo 1.1 - *gnuplot 3.5 - *gperf 2.1a - *Graphics 0.17 - *grep 2.0 - *Groff 1.09 - *gzip 1.2.4 - *hello 1.3 - *hp2xx 3.1.4 - *indent 1.9.1 - *ispell 4.0 - *libg++ 2.5.3 - *m4 1.1 - *Make 3.71 - *MandelSpawn 0.07 - *mtools 2.0.7 - *MULE 1.0 - *NetFax 3.2.1 - *Nethack 3.1.3 - *NIHCL 3.0 - *nvi 1.11 - *Octave 1.0 - *Oleo 1.5 - *p2c 1.20 - *patch 2.1 - *PCL 1993.03.18 - *perl 4.036 - *ptx 0.3 - *rc 1.4 - *RCS 5.6.0.1 - *recode 3.3 - *regex 0.12 - *screen 3.5.2 - *sed 2.05 - *shellutils 1.9.4 - *Shogi 1.1.02 - *Smalltalk 1.1.1 - *Superopt 2.3 - *tar 1.11.2 - *Termcap 1.2 - *TeX 3.1 - *Texinfo 3.1 - *Textutils 1.9.1 - *Tile Forth 2.1 - *time 1.6 - *tput 1.0 - *UUCP 1.05 - *uuencode 1.0 - *wdiff 0.04 - *X11R6 - *xboard 3.0.9 - *xshogi 1.2.02 - - - -November 1993 Source Code CD-ROM -................................ - -We still have the 3rd edition of our Source CD, at a reduced price, while -supplies last. It was the last Source Code CD to contain X11R5. This CD has -Edition 2.2 for version 19 of the `GNU Emacs Lisp Reference Manual' & some -additional software; not all FSF distributed software is included (*note -Source Code CD-ROMs::.). It contains these packages: - - * acm 3.1 - * Autoconf 1.7 - * BASH 1.13.4 - * bc 1.02 - * Binutils 1.9 2.3 - * Bison 1.22 - * C Library 1.06.7 - * Calc 2.02b - * Chess 4.0p62 - * CLISP 93.11.08 - * cpio 2.3 - * CVS 1.3 - * dc 0.2 - * DejaGnu 1.0.1 - * Diffutils 2.6 - * dld 3.2.3 - * doschk 1.1 - * ecc 1.2.1 - * elib 0.06 - * Emacs 18.59 - * Emacs 19.21 - * es 0.84 - * f2c 1993.04.28 - * Fileutils 3.9 - * find 3.8 - * Finger 1.37 - * flex 2.3.8 - * Fontutils 0.6 - * GAS 1.36.utah - * GAS 1.38.1 - * GAS 2.2 - * GAWK 2.15.3 - * GCC/G++/Objective C 2.5.4 - * GDB 4.11 - * gdbm 1.7.1 - * Ghostscript 2.6.1 - * Ghostview 1.5 - * Ghostview for Windows 1.0 - * gmp 1.3.2 - * GNATS 3.01 - * GnuGo 1.1 - * gnuplot 3.5 - * cperf 2.1a - * Graphics 0.17 - * grep 2.0 - * Groff 1.08 - * gzip 1.2.4 - * hello 1.3 - * hp2xx 3.1.3a - * indent 1.8 - * Ispell 4.0 - * less 177 - * libg++ 2.5.1 - * m4 1.1 - * make 3.69.1 - * MandelSpawn 0.06 - * mtools 2.0.7 - * MULE 1.0 - * NetFax 3.2.1 - * NetHack 3.1.3 - * NIHCL 3.0 - * Oleo 1.5 - * p2c 1.20 - * patch 2.1 - * PCL 93.03.18 - * perl 4.036 - * ptx 0.3 - * rc 1.4 - * RCS 5.6.0.1 - * recode 3.2.4 - * regex 0.12 - * screen 3.5.2 - * sed 1.18 2.03 - * Shellutils 1.9.1 - * Shogi 1.1p02 - * Smalltalk 1.1.1 - * Superopt 2.3 - * tar 1.11.2 - * Termcap 1.2 - * TeX 3.1 - * Texinfo 3.1 - * Tile Forth 2.1 - * time 1.6 - * time 1.6 - * tput 1.0 - * UUCP 1.04 - * uuencode 1.0 - * wdiff 0.04 - * X11R5 - - - -MS-DOS Book with CD-ROM ------------------------ - -We are working on our first book describing GNU Software for MS-DOS, but we -do not know when it will be finished. It will include a CD-ROM with all the -sources & binaries on the MS-DOS Diskettes and more. - -Please do NOT contact us about this book until we announce it on our mailing -lists (to subscribe, ask `info-gnu-request@prep.ai.mit.edu'), because it just -slows us down. - - - -Debian GNU/Linux Book with CD-ROM ---------------------------------- - -We are working on our first book describing Debian GNU/Linux but we do not -know when it will be finished. Please do NOT contact us about this book -until we announce it on our mailing lists (ask -`info-gnu-request@prep.ai.mit.edu' to subscribe), because it just slows us -down. - -A CD will be inside the book with sources & binaries for Debian GNU/Linux, -which is a complete operating system for i386/i486/Pentium. It is a -GNU/Linux system--that is to say, a variant GNU system which uses Linux as -the kernel. (All the systems now available that use the Linux kernel are -GNU/Linux systems, see item "Linux" in *Note Free Software for -Microcomputers::.) - -Debian is being developed by Ian Murdock and the Debian Association in -conjunction with the Free Software Foundation. We are distributing it as an -interim measure until the GNU kernel (the Hurd) is ready for users. - -For details on Debian & how to help, see URL: `http://www.debian.org/' or -FTP, `/pub/gnu/GNUinfo/DEBIAN' from a GNU FTP host (*note How to Get GNU -Software::.). FTP Debian under `/debian' from `ftp.debian.org'. - - - -MS-DOS Diskettes -**************** - -The FSF distributes some of the GNU software ported to MS-DOS, on 3.5inch -1.44MB diskettes. These disks have both sources and executables. - - - -DJGPP Diskettes ---------------- - -We offer DJGPP on 30 diskettes. For further details, see *Note GNU -Software::. The DJGPP diskettes contain the following: - - * Binutils 2.5.2 - * Bison 1.22 - * Diffutils 2.6 - * DJGPP 1.12m4 - * flex 2.4.7 - * GCC/G++ 2.6.3 - * GDB 4.12 - * Groff 1.09 - * gzip 1.24 - * libg++ 2.6.2 - * make 3.71 - * patch 2.1 - * sed 1.18 - * Texinfo 3.1 - - - -Emacs Diskettes ---------------- - -Two versions of GNU Emacs are included on the Emacs diskettes we distribute: -GNU Emacs version 19.29 handles 8-bit character sets; the other, MULE version -2.2, handles 16-bit character sets including Kanji. - - - -Selected Utilities Diskettes ----------------------------- - -The GNUish MS-DOS Project ported GNU software to PC compatibles. Though -GNUish is no longer active, users still ask for these ports done some years -ago. We offer these ports on five diskettes. In general, the ports run on -8086/80286-based 16-bit machines; an 80386 is not required. Some are -necessarily missing features. - -Included are: `cpio', `diff', `find', `flex', `gdbm', `grep', `indent', -`less', `m4', `make', `ptx', RCS, `sed', `shar', `sort', & Texinfo. - - - -Windows Diskette ----------------- - -We offer GNU Chess and `gnuplot' for Microsoft Windows on a single diskette. - - - -Tape & CD-ROM Subscription Service -********************************** - -If you do not have net access, our subscription service enables you to stay -current with the latest GNU developments. For a one-time cost equivalent to -three tapes or CD-ROMs (plus shipping in some cases), we will ship you four -new versions of the tape of your choice or the Source Code CD-ROM. The tapes -are sent each quarter; the CD-ROMs are sent as they are issued (currently -twice a year, but we hope to make it more frequent). - -Regularly, we will send you a new version of a Lisps/Emacs, Languages, -Utilities, or X Window System (X11R6) Required tape, or the Source CD-ROM. -The MIT Scheme and X Window System Optional tapes are not changed often -enough to warrant quarterly updates. We do not yet know if we will be -offering subscriptions to the Compiler Tools Binaries or our new Books with -CD-ROM. - -Since Emacs 19 is on the Lisps/Emacs Tape and the Source CD-ROM, a -subscription to either is an easy way to keep current with Emacs 19 as it -evolves. - -A subscription is an easy way to keep up with the regular bug fixes to the X -Window System. We update the X11R6 Required tape as fixes and patches are -issued throughout the year. Each edition of the *Note Source Code CD-ROMs::, -also has updated sources for the required part of the X Window System. - -Please note: In two cases, you must pay 4 times the normal shipping required -for a single order when you pay for each subscription. If you're in Alaska, -Hawaii, or Puerto Rico you must add $20.00 for shipping for each -subscription. If you're outside of U.S., Canada, and Puerto Rico, you must -add $80.00 for each subscription. See "Unix and VMS Software" and "Shipping -Instructions" on the *note Free Software Foundation Order Form::.. - - - -FSF T-shirt -*********** - -There is a GNU & improved T-shirt. The front has the GNU Emacs Lisp code -`(USE 'GNU)' with "`()'" being the dancing parentheses from the cover of our -`GNU Emacs Lisp Reference Manual' (drawn by Berkeley, CA artist Etienne -Suvasa). The back of the shirt is still imprinted with the Preamble to the -GNU General Public License. - -These shirts come in two colors, Natural & Black. Natural is an off-white, -unbleached, undyed, environment-friendly cotton, printed with black ink, & is -great for tye-dyeing or displaying as is. Black is printed with white ink & -is perfect for late night hacking. All shirts are thick 100% cotton, & come -in sizes M, L, XL, & XXL. GNU shirts often create spontaneous friendships at -technical conferences and on major university campuses! (They also make -great gifts!) - - - -Free Software Foundation Order Form -*********************************** - -All items are distributed with permission to copy and to redistribute. -Texinfo source for each manual and source for each reference card is on -the appropriate tape, diskette, or CD-ROM; the prices for these magnetic -media do not include printed documentation. All items are provided on -an ``as is'' basis, with no warranty of any kind. Please allow six -weeks for delivery (though it won't usually take that long). - - - PRICE AND CONTENTS MAY CHANGE WITHOUT NOTICE AFTER June 30, 1996. - - - -Unix and VMS Software ---------------------- - -These tapes in the formats indicated (*note Tapes::., for contents): - - Please circle the dollar amount for each tape you order. - - Reel to Sun (1) HP IBM (2) Exabyte DAT - reel RS/6000 - Unix tar Unix tar Unix tar Unix tar Unix tar Unix tar - 9-track QIC-24 16-track QIC-150 - 1600 bpi DC300XLP DC600HC DC600A - 1/2" reel 1/4" c.t. 1/4" c.t. 1/4" c.t. 8mm c.t. 4mm c.t. - - (c.t. = cartridge tape) - -Lisps/Emacs $200 $210 $230 $215 $205 $225 - -Languages $200 $210 $230 $215 $205 $225 - -Utilities $200 $210 $230 $215 $205 $225 - -4.4BSD-Lite $200 $210 $230 $215 $205 $225 - -Scheme $200 $210 $230 $215 $205 $225 - -X11R6-Required $200 $210 $230 $215 $205 $225 - -X11R6-Optional $200 $210 $230 $215 $205 $225 - - (1) Sun tapes can be read on some other Unix systems. - (2) IBM RS/6000 tapes can be read on some other Unix systems. - - -Subscriptions, 4 updates for one year (*note Tape & CD-ROM Subscription Service::.): - -Emacs $600 $630 $690 $645 $615 $675 - -Languages $600 $630 $690 $645 $615 $675 - -Utilities $600 $630 $690 $645 $615 $675 - -X11R6-Required $600 $630 $690 $645 $615 $675 - - Subtotal $ ______ Please put total of the above circled amounts here. - - -These 1600 bpi reel-to-reel 9 track 1/2" tapes, in VMS BACKUP format (aka -interchange format) (*note VMS Emacs and VMS Compiler Tapes::.): - -____ @ $195 = $ ______ VMS Emacs, GNU Emacs source & executables only. - -____ @ $195 = $ ______ VMS Compiler, GCC, GAS, and Bison source and - executables only. - - -FSF Deluxe Distribution -....................... -(Please call with any questions. *note Deluxe Distribution::. for machine, -operating system, and media types.): - - -____ @ $5000 = $ ______ The Deluxe Distribution, with manuals, etc. - -Machine: _____________________________________________________________________ - -Operating system: ____________________________________________________________ - -Media type: __________________________________________________________________ - -Version of X Windows System to build: _______________________________________ - - - -CD-ROMs, in ISO 9660 format (*note CD-ROMs::.): -.............................................. - - -GNU Source Code CD-ROMs, Version 7 with X11R6 (*note December 1995 Source Code CD-ROMs::.): - -____ @ $240 = $ ______ for corporations and other organizations. - -____ @ $ 60 = $ ______ for individuals. - - -Subscriptions, next 4 updates, of the Source Code CD-ROM, in ISO 9660 format -(*note Tape & CD-ROM Subscription Service::.): - -____ @ $720 = $ ______ for corporations and other organizations. - -____ @ $180 = $ ______ for individuals. - - -GNU Compiler Tools Binaries CD-ROM, Version 3, December 1995 Edition -(*note Compiler Tools Binaries CD-ROM::.): - -____ @ $220 = $ ______ for corporations and other organizations. - -____ @ $55 = $ ______ for individuals. - - - -MS-DOS Software ---------------- - -The following sources and executables for MS-DOS, on 3.5" 1.44MB diskettes -(*note MS-DOS Diskettes::.): - -____ @ $ 90 = $ ______ Emacs diskettes, GNU Emacs, for 80386 and up. - -____ @ $ 80 = $ ______ DJGPP diskettes, GCC version 2, and other tools - for 80386 and up (also on the - *note Compiler Tools Binaries CD-ROM::.). - -____ @ $ 85 = $ ______ Selected Utilities diskettes, 8086 and up. - -____ @ $ 40 = $ ______ Windows diskette: GNU Chess and gnuplot for - Microsoft Windows. - - -Manuals -------- - -These manuals (*note Documentation::.). The latest version of each manual -will be shipped. Please call if you want a specific version. - -____ @ $ 25 = $ ______ GNU Emacs version manual, with a reference card. - -____ @ $ 50 = $ ______ GNU Emacs Lisp Reference manual, in two volumes. - -____ @ $ 60 = $ ______ GNU Emacs Lisp Reference, Japanese Edition. - -____ @ $ 50 = $ ______ Using and Porting GNU CC. - -____ @ $ 50 = $ ______ GNU C Library Reference Manual. - -____ @ $ 50 = $ ______ GNU Emacs Calc manual, with a reference card. - -____ @ $ 20 = $ ______ Programming in Emacs Lisp: An Introduction. - -____ @ $ 20 = $ ______ Debugging with GDB, with a reference card. - -____ @ $ 25 = $ ______ GAWK manual. - -____ @ $ 20 = $ ______ Make manual. - -____ @ $ 20 = $ ______ Bison manual, with a reference card. - -____ @ $ 20 = $ ______ Flex manual, with a reference card. - -____ @ $ 20 = $ ______ Texinfo manual. - -____ @ $ 15 = $ ______ Termcap manual. - - - -Reference Cards ---------------- - -The following reference cards, in packets of ten. For single copies please -call. - -____ @ $ 10 = $ ______ GNU Emacs version 19 reference cards. - -____ @ $ 10 = $ ______ GNU Emacs Calc reference cards. - -____ @ $ 10 = $ ______ GDB reference cards. - -____ @ $ 10 = $ ______ Bison reference cards. - -____ @ $ 10 = $ ______ Flex reference cards. - - - -T-shirts --------- - -GNU/FSF T-shirts, thick 100% cotton (*note FSF T-shirt::.): - -____ @ $ 15 = $ ______ Size M ____ natural ____ black. - -____ @ $ 15 = $ ______ Size L ____ natural ____ black. - -____ @ $ 15 = $ ______ Size XL ____ natural ____ black. - -____ @ $ 15 = $ ______ Size XXL ____ natural ____ black. - - - -Older Items ------------ - -Older items are only available while supplies last. - -____ @ $ 5 = $ ______ GNU Emacs version 18 reference cards, in packets - of ten. - - -Please fill in the number of each older CD-ROM you order: - - for for - corporations individuals: - and other - organizations: - -GNU Compiler Tools Binaries CD-ROM - December 1994 Edition (Version 2) ____________ ____________ - -GNU Compiler Tools Binaries CD-ROM - December 1993 Edition (Version 1) ____________ ____________ - - -Please note that the December 1994 Source CD is permanently out of stock. - -GNU Source Code CD-ROM - June 1995 edition with X11R6 ____________ ____________ - -GNU Source Code CD-ROM - May 1994 edition with X11R6 ____________ ____________ - -GNU Source Code CD-ROM - November 1993 edition with X11R5 ____________ ____________ - -GNU Source Code CD-ROM - May 1993 edition with X11R5 ____________ ____________ - -GNU Source Code CD-ROM - October 1992 edition with X11R5 ____________ ____________ - - -Please put the total count and cost of the above older CD-ROMs here: - -____ @ $ 80 = $ ______ for corporations and other organizations. - -____ @ $ 20 = $ ______ for individuals. - - ====== - - Subtotal $ ______ - - - -Tax and Shipping Costs ----------------------- - - + $ ______ For addresses in Massachusetts: add 5% sales tax - or give tax exempt number. There is no sales tax - on T-shirts. - + $ ______ Shipping fee for addresses in Alaska, Hawaii, or - Puerto Rico: - $ 5.00 base charge; - + $ 5.00 for *each* Emacs Calc or Emacs Lisp - Reference manual ($ 5.00 * #ofMans); - + $ 20.00 for *each* tape subscription or CD - subscription ($20.00 * #ofSubs); - + $ 1.00 for *each* item other then the above - (shipping for all other items = - $ 1.00 * #ofOtherItems). - + $ ______ Shipping fee for most Foreign Destinations: (Please - do *not* use this formula for addresses in China, - Guam, Indonesia, Israel, Malaysia, New Zealand, - Philippines, and Thailand. Please fax, - or call for an exact shipping quote.) - $ 20.00 base charge for orders to other - addresses outside of U.S., Canada, & Puerto Rico: - + $ 80.00 for *each* tape subscription or CD - subscription ($ 80.00 * #ofSubs); - + $ 10.00 for *each* of the other items in the - order ($ 10.00 * #ofItems). - + $ ______ Optional (tax-deductible in the U.S.) donation. - ------ We suggest 5% if paying by credit card. - - TOTAL $ ______ We pay for shipping via UPS ground transportation in - the contiguous 48 states and Canada. For very - large orders, ask about actual shipping costs for - that order. - - - -Shipping Information --------------------- - -Name: ________________________________________________________________________ - -Mail Stop/Dept. Name: ________________________________________________________ - -Organization: ________________________________________________________________ - -Street Address: ______________________________________________________________ - -City/State/Province: _________________________________________________________ - -Zip Code/Postal Code/Country: ________________________________________________ - -Telephone number in case of a problem with your order. -For international orders, please include a Fax number. _______________________ - - ------------------------------------------------------------------------------- -| | -| Orders filled only upon receipt of check, money order, or credit card | -| order in U.S. dollars. Unpaid orders will be returned to the sender. | -| We do not have the staff to handle the billing of unpaid orders. Please | -| help keep our lives simple by including your payment with your order. | -| | ------------------------------------------------------------------------------- - - - -For orders from outside the U.S.: ---------------------------------- - -You are responsible for paying all duties, tariffs, and taxes. If you -refuse to pay the charges, the shipper will return or abandon the order. - - - --------------------------------------------------------------------------- - | | - | Please make checks payable to the ``Free Software Foundation''. | - | | - --------------------------------------------------------------------------- - - - -For Credit Card Orders: ------------------------ - -The Free Software Foundation takes these credit cards: Carte Blanche, -Diner's Club, JCB, MasterCard, Visa, or American Express. Please note that -we are charged about 5% of an order's total amount in credit card -processing fees. Please consider paying by check instead, or adding on a 5% -donation to make up the difference. To place a credit card order, please -give us this information: - - -Card type: ___________________________________________________________________ - -Account Number: ______________________________________________________________ - -Expiration Date: _____________________________________________________________ - -Cardholder's Signature: ______________________________________________________ - - - ------------------------------------------------------------------------------- -| | -| If you wish to pay by wire transfer or you are a reseller, please | -| call or write us for details. | -| | ------------------------------------------------------------------------------- - - - Please mail orders to: Free Software Foundation - 59 Temple Place -- Suite 330 - Boston, MA 02111 -PRICES AND CONTENTS MAY CHANGE +1-617-542-5942 -WITHOUT NOTICE AFTER June 30, 1996. Fax (including Japan): +1-617-542-2652 - -Version: January 1996 ASCII etc/ORDERS - ------------------------------------------------------------------------------ - -local variables: -mode: text -fill-column: 78 -end: diff -r 7edc33019aa4 -r b7b90f750a78 etc/ORDERS.EUROPE --- a/etc/ORDERS.EUROPE Mon Jan 31 20:01:50 2005 +0000 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000 @@ -1,6 +0,0 @@ -The Free Software Foundation does not currently have a distributor in -Europe. - -Please use the file etc/ORDERS in the GNU Emacs distribution or the -ftpable file prep.ai.mit.edu:/pub/gnu/GNUinfo/ORDERS to order from the -FSF in the United States. diff -r 7edc33019aa4 -r b7b90f750a78 etc/ORDERS.JAPAN --- a/etc/ORDERS.JAPAN Mon Jan 31 20:01:50 2005 +0000 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000 @@ -1,246 +0,0 @@ - - -Note: this file describes how you order software from the Free Software -Foundation directly. Information on getting XEmacs can be found in -the file DISTRIB. - - - GNU ORDER FORM FOR JAPAN - -Prices and contents may change without notice after June 30, 1996. - - Item Unit Price Quantity Item Price - ---------------------------------------- ---------- -------- ---------- -* indicates New or Substantially Updated items. - -* Compiler Tools Binaries CD-ROM December '95 Y32,000 ________ __________ - Edition, Version 3, if a corporation or other - organization is ultimately paying. - -* Compiler Tools Binaries CD-ROM December '95 Y8,000 ________ __________ - Edition, Version 3, if an individual is - ultimately paying. - -* Source Code CD-ROM December '95 Edition, Y40,000 ________ __________ - Version 7, with X11R6, if a corporation or - other organization is ultimately paying. - -* Source Code CD-ROM December '95 Edition, Y10,000 ________ __________ - Version 7, with X11R6, if an individual is - ultimately paying. - - Source Code CD-ROM November '93 Edition, Y40,000 ________ __________ - Version 3, with X11R5, if a corporation or other - organization is ultimately paying (while supplies last). - - Source Code CD-ROM November '93 Edition, Y10,000 ________ __________ - Version 3, with X11R5, if an individual is - ultimately paying (while supplies last). - - Subscription to next four editions of the Y125,000 ________ __________ - Source Code CD-ROMs. (There is no subscription - yet to the Compiler Tools Binaries CD-ROM.) - -* Source Code on Tape Y30,000 ________ __________ - (per tape; see the next page for more details.) - - Emacs manual, with reference card Y3,700 ________ __________ - (Eleventh Edition for Version 19.29) - -* Programming in Emacs Lisp, An Introduction Y3,100 ________ __________ - (Edition 1.04) - -* Emacs Lisp Reference manual, in two volumes Y7,100 ________ __________ - (Edition 2.4 for Version 19.29) - -* Emacs Lisp Reference, Japanese Edition manual Y8,000 ________ __________ - (Japanese DRAFT Revision 1.0, Dec 1995, - from English Edition 2.4 for Version 19.29) - - Emacs Calc manual, with reference card Y7,400 ________ __________ - (Edition 2.02 for Version 2.02) - - Using and Porting GNU CC manual Y7,100 ________ __________ - (September 1994 Edition for Version 2.6) - - GNU C Library Reference manual Y7,400 ________ __________ - (Edition 0.06 for Version 1.09) - - Debugging with GDB manual, with reference card Y3,100 ________ __________ - (Edition 4.12 for Version 4.14) - - Texinfo manual (Edition 2.21 for Version 3) Y2,800 ________ __________ - - Termcap manual (Second Edition for Version 1.2) Y2,100 ________ __________ - - Bison manual, with reference card Y2,100 ________ __________ - (December 1993 Edition for Version 1.23) - -* Gawk manual (Edition 1.0 for Version 3.0) Y3,700 ________ __________ - -* Make manual (Edition 0.49 for Version 3.74) Y2,800 ________ __________ - - Flex manual, with reference card Y2,100 ________ __________ - (Edition 1.03 for Version 2.3.7) - - Packet of ten Emacs 19 reference cards Y1,500 ________ __________ - - Packet of ten Emacs 18 reference cards Y1,500 ________ __________ - (while supplies last) - - Packet of ten GDB reference cards Y1,500 ________ __________ - - Packet of ten Emacs Calc reference cards Y1,500 ________ __________ - - Packet of ten Bison reference cards Y1,500 ________ __________ - - Packet of ten Flex reference cards Y1,500 ________ __________ - - FSF T-shirt (size M) Y5,000 ________ __________ - Color: Natural or Black (circle) - - FSF T-shirt (size L) Y5,000 ________ __________ - Color: Natural or Black (circle) - - FSF T-shirt (size XL) Y5,000 ________ __________ - Color: Natural or Black (circle) - - FSF T-shirt (size XXL) Y5,000 ________ __________ - Color: Natural or Black (circle) - - Shipping Y1,500 - - Optional donation--help the FSF write more free software! __________ - - Total __________ - -The following is your shipping label. Please write clearly using Romaji. -All orders must be prepaid. See the next page for payment instructions. - - Name: ___________________________________________________________________ - - Company: ________________________________________________________________ - - Address: ________________________________________________________________ - -Please also provide the following information in case there is a problem -with your order. - - Telephone: ________________ Fax: ________________ E-Mail: _________________ - - ____ Please add my name to the mailing list for future FSF events in - Japan. I prefer to be notified by: ______ fax _____ e-mail - - ____ Please send me information regarding the GNU corporate deluxe - software and documentation package. - - ____ My company is interested in becoming a corporate sponsor of the FSF. - - ____ I am interested in working as a volunteer for the FSF. - -Prices and contents may change without notice after June 30, 1996. - - Version: January 1996 ASCII etc/ORDERS.JAPAN - - Free Software Foundation FAX 001-1-617-542-2652 - 59 Temple Place - Suite 330 Voice 001-1-617-542-5942 - Boston, MA 02111-1307 E-mail gnu@prep.ai.mit.edu - U.S.A. - - - GNU ORDER FORM ADDITIONAL INSTRUCTIONS - -You can fax your order directly to 001-1-617-542-2652. Inquires may -be made to gnu@prep.ai.mit.edu. Orders may also be sent by ordinary -mail to: - - Free Software Foundation - 59 Temple Place - Suite 330 - Boston, MA 02111-1307 - U.S.A. - -Orders may be prepaid either by credit card or by bank transfer. The credit -cards we accept are JCB, Visa, MasterCard, Diner's Club, Carte Blanche, and -American Express. Please provide your card type, expiration date, account -number, and your signature. Bank transfer payments should be made to the -following account: - - Bank: Sanwa Bank - Branch: Azabu Branch (#620) - Account name: Free Software Foundation - Account number: 3683216 - -Prices and contents may change without notice after June 30, 1996. All -software and publications are distributed with permission to copy and to -redistribute. Texinfo source for each manual is on the Source Code CD-ROM -and/or on the appropriate tape. We will ship the latest version of each -manual, unless you instruct us otherwise. - -The minimum order amount (before postage) is Y5,000. The FSF regrets that it -cannot fill orders for smaller amounts. Please contact the FSF directly by -telephone at 001-1-617-542-5942 or by fax at 001-1-617-542-2652 prior to -placing any orders for greater than Y500,000. - -The FSF offers a deluxe package to Japanese corporations which consists of -source code in your preferred format, a set of custom binaries for -your preferred architecture and operating system, and a complete documentation -set with reference cards. Purchasers of the corporate deluxe package will -also receive invitations to future private presentations conducted by Richard -Stallman in Japan. The price for the corporate deluxe package is Y1,000,000. -For more information, contact the FSF directly. - -Software may also be ordered on magnetic tape. The following tape titles are -available: - * Lisps/Emacs - * Languages - * Utilities - * Scheme - * 4.4BSD-Lite - * X11R6-Required - X11R6-Optional - X11R5-Required - X11R5-Optional - -The following tape formats are available: - - Generic Unix tar 9-track 1600bpi 1/2" reel tape - - Generic Unix tar DAT 4mm cartridge tape - - Generic Unix tar Exabyte 8mm cartridge tape - - Sun Unix tar QIC-24 DC300XLP 1/4" cartridge tape - (may also be read on other systems) - - HP Unix tar 16-track DC600HC 1/4" cartridge tape - - IBM RS/6000 Unix tar QIC-150 DC600A 1/4" cartridge tape - (may also be read on other systems) - - VMS backup 9-track 1600bpi 1/2" reel tape - (only two titles: GNU Emacs and GCC/GAS/Bison) - -Please indicate your desired tape titles and formats on a separate sheet of -paper and fax that along with your order. If you need information regarding -which programs are on which tapes, please consult the Japanese edition of the -January 1996 GNU Bulletin. If you do not have a copy of the Japanese edition -of the GNU Bulletin, please contact the FSF. - -For T-shirt orders, please circle desired color. - -Richard Stallman regrets that he cannot autograph items ordered by mail. -If time permits, he will autograph items purchased at or brought to -speaking engagements. - -All sales are final. - -Prices and contents may change without notice after June 30, 1996. - - Please do not fax this page. - - For use in Japan only. - - Free Software Foundation - 59 Temple Place - Suite 330 - Boston, MA 02111-1307 - U.S.A. diff -r 7edc33019aa4 -r b7b90f750a78 etc/PACKAGES --- a/etc/PACKAGES Mon Jan 31 20:01:50 2005 +0000 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000 @@ -1,419 +0,0 @@ - -*- Outline -*- -This file is in Outline mode. It is best viewed under XEmacs. - -Press C-c C-o (Ctrl+c Ctrl+o) now to see a list of headings. - To expand a heading: Put the cursor on the heading and press C-c C-s -To collapse a heading: Press C-c C-d - -For general XEmacs navigation tips: Press C-h t - -Description of available packages -================================= -Up-to-date as of Jul 31, 2003. - -** Normal Packages -================== -A very broad collection of elisp packages. - -*** Sun -Support for Sparcworks. - -*** ada -Ada language support. - -*** apel -A Portable Emacs Library. Used by XEmacs MIME support. - -*** auctex -Basic TeX/LaTeX support. - -*** bbdb -The Big Brother Data Base: a rolodex-like database program. - -*** build -Build XEmacs from within (UNIX, Windows). - -*** c-support -Basic single-file add-ons for editing C code. - -*** calc -Emacs calculator. - -*** calendar -Calendar and diary support. - -*** cc-mode -C, C++, Objective-C, Java, CORBA IDL, Pike and AWK language support. - -*** clearcase -New Clearcase Version Control for XEmacs (UNIX, Windows). - -*** clearcase -Support for the Clearcase version control system. - -*** cookie -"Fortune cookie"-style messages. Includes Spook (suspicious phrases) -and Yow (Zippy quotes). - -*** crisp -Crisp/Brief emulation. - -*** debug -GUD, gdb, dbx debugging support. - -*** dictionary -Interface to RFC2229 dictionary servers. - -*** dired -The DIRectory EDitor is for manipulating, and running commands on -files in a directory. - -*** docbookide -DocBook editing support. - -*** ecb -Emacs source code browser. - -*** ecrypto -Crypto functionality in Emacs Lisp. - -*** edebug -An Emacs Lisp debugger. - -*** ediff -Interface over GNU patch. - -*** edit-utils -Miscellaneous editor extensions, you probably need this. - -*** edt -DEC EDIT/EDT emulation. - -*** efs -Treat files on remote systems the same as local files. - -*** eieio -Enhanced Implementation of Emacs Interpreted Objects. - -*** elib -Portable Emacs Lisp utilities library. - -*** emerge -Another interface over GNU patch. - -*** erc -ERC is an Emacs InternetRelayChat client. - -*** escreen -Multiple editing sessions withing a single frame (like screen). - -*** eshell -Command shell implemented entirely in Emacs Lisp. - -*** ess -ESS: Emacs Speaks Statistics. - -*** eterm -Terminal emulation. - -*** eudc -Emacs Unified Directory Client (LDAP, PH). - -*** footnote -Footnoting in mail message editing modes. - -*** forms -Forms editing support (obsolete, use Widget instead). - -*** fortran-modes -Fortran support. - -*** fortran-modes -Fortran language support. - -*** frame-icon -Set up mode-specific icons for each frame under XEmacs. - -*** fsf-compat -GNU Emacs compatibility files. - -*** games -Tetris, Sokoban, and Snake. - -*** general-docs -General documentation. Presently, empty. - -*** gnats -XEmacs bug reports. - -*** gnus -The Gnus Newsreader and Mailreader. - -*** haskell-mode -Haskell editing support. - -*** hm--html-menus -HTML editing. - -*** hyperbole -Hyperbole: The Everyday Info Manager. - -*** ibuffer -Advanced replacement for buffer-menu. - -*** idlwave -Editing and Shell mode for the Interactive Data Language. - -*** igrep -Enhanced front-end for Grep. - -*** ilisp -Front-end for interacting with Inferior Lisp (external lisps). - -*** ispell -Spell-checking with GNU ispell. - -*** jde -Integrated Development Environment for Java. - -*** liece -IRC (Internet Relay Chat) client for Emacs. Note, this package is -deprecated and will be removed, use riece instead. - -*** mail-lib -Fundamental lisp files for providing email support. - -*** mailcrypt -Support for messaging encryption with PGP. - -*** mew -Messaging in an Emacs World; a MIME-based email program. - -*** mh-e -The XEmacs Interface to the MH Mail System. - -*** mine -Elisp implementation of the game 'Minehunt'. - -*** misc-games -Other amusements and diversions. - -*** mmm-mode -Support for Multiple Major Modes within a single buffer. - -*** net-utils -Miscellaneous Networking Utilities. - -*** ocaml -Objective Caml editing support. - -*** oo-browser -OO-Browser: The Multi-Language Object-Oriented Code Browser. - -*** ocaml -Objective Caml editing support. - -*** os-utils -Miscellaneous single-file O/S utilities, for printing, archiving, -compression, remote shells, etc. - -*** pc -PC style interface emulation. - -*** pcl-cvs -CVS frontend. - -*** pcomplete -Provides programmatic completion. - -*** perl-modes -Perl support. - -*** pgg -Emacs interface to various PGP implementations. - -*** prog-modes -Support for various programming languages. - -*** ps-print -Printing functions and utilities. - -*** psgml -Validated HTML/SGML editing. - -*** psgml-dtds -A collection of DTDs for psgml. Note that this package is deprecated -and will be removed in the future, most likely Q2/2003. Instead of using -this, you should install needed DTDs yourself. - -*** python-modes -Python language support. - -*** reftex -Emacs support for LaTeX cross-references, citations. - -*** riece -IRC (Internet Relay Chat) client for Emacs. - -*** rmail -An obsolete Emacs mailer. If you do not already use it don't start. - -*** ruby-modes -Ruby support. - -*** sasl -Simple Authentication and Security Layer (SASL) library. - -*** scheme -Front-end support for Inferior Scheme. - -*** semantic -Semantic bovinator (Yacc/Lex for XEmacs). Includes Senator. - -*** sgml -SGML/Linuxdoc-SGML editing. - -*** sh-script -Support for editing shell scripts. - -*** sieve -Manage Sieve email filtering scripts. - -*** slider -User interface tool. - -*** sml-mode -SML editing support. - -*** sounds-au -XEmacs Sun sound files. - -*** sounds-wav -XEmacs Microsoft sound files. - -*** speedbar -Provides a separate frame with convenient references. - -*** strokes -Mouse enhancement utility. - -*** supercite -An Emacs citation tool for News & Mail messages. - -*** texinfo -XEmacs TeXinfo support. - -*** text-modes -Miscellaneous support for editing text files. - -*** textools -Miscellaneous TeX support. - -*** time -Display time & date on the modeline. - -*** tm -Emacs MIME support. Not needed for gnus >= 5.8.0. - -*** tooltalk -Support for building with Tooltalk. - -*** tpu -DEC EDIT/TPU support. - -*** tramp -Remote shell-based file editing. This is similar to EFS or Ange-FTP, -but works with rsh/ssh and rcp/scp. - -*** vc -Version Control for Free systems. - -*** vc-cc -Version Control for ClearCase (UnFree) systems. - -*** vhdl -Support for VHDL. - -*** view-process -A Unix process browsing tool. - -*** viper -VI emulation support. - -*** vm -An Emacs mailer. - -*** w3 -A Web browser. - -*** x-symbol -Semi WYSIWYG for LaTeX, HTML, etc, using additional fonts. - -*** xemacs-base -Fundamental XEmacs support, you almost certainly need this. - -*** xemacs-devel -XEmacs Lisp developer support. This package contains utilities for -supporting Lisp development. It is a single-file package so it may be -tailored. - -*** xlib -Emacs interface to X server. - -*** xslide -XSL editing support. - -*** xslt-process -A minor mode for (X)Emacs which allows running an XSLT processor on a -buffer. - -*** xwem -X Emacs Window Manager. - -*** zenirc -ZENIRC IRC Client. - -** Mule Support (mule) -====================== -MULti-lingual Enhancement. Support for world scripts such as -Latin, Arabic, Cyrillic, Chinese, Japanese, Greek, Hebrew etc. -To use these packages your XEmacs must be compiled with Mule -support. - -*** edict -MULE: Lisp Interface to EDICT, Kanji Dictionary. - -*** egg-its -MULE: Wnn (4.2 and 6) support. SJ3 support. - -*** latin-unity -MULE: find single ISO 8859 character set to encode a buffer. - -*** latin-unity -Unify character sets in a buffer. When characters belong to disjoint -character sets, this attempts to translate the characters so -that they belong to one character set. If the buffer coding system is -not sufficient, this suggests different coding systems. - -*** leim -MULE: Quail. All non-English and non-Japanese language support. - -*** locale -MULE: Localized menubars and localized splash screens. - -*** lookup -Dictionary support. (This isn't an English dictionary program) - -*** mule-base -MULE: Basic Mule support, required for building with Mule. - -*** mule-ucs -MULE: Extended coding systems (including Unicode) for XEmacs. - -*** mule-ucs -Extended coding systems (including Unicode) for XEmacs. - -*** skk -Another Japanese Language Input Method. Can be used without a -separate process running as a dictionary server. - diff -r 7edc33019aa4 -r b7b90f750a78 etc/README --- a/etc/README Mon Jan 31 20:01:50 2005 +0000 +++ b/etc/README Mon Jan 31 20:08:52 2005 +0000 @@ -3,40 +3,21 @@ of interest to XEmacs users, some programs used by or with XEmacs, and the file of on-line documentation for XEmacs. -BETA Information about Beta versions -CHARSETS Character set descriptions -CODING-STANDARDS XEmacs C & Lisp coding standards -CODINGS Character set codings -COOKIES Urban Legend, or True Story? :-) COPYING GNU Public License -COPYING.LIB Library GNU Public License -DEBUG Hints on how to debug XEmacs -DISTRIB How to obtain copies of XEmacs and Emacs +ChangeLog ChangeLog for etc/ +ETAGS.EBNF Description of TAGS file format Emacs.ad Sample Resource file -FTP XEmacs FTP Mirrors -GNU GNU Manifesto -GOATS Complete XEmacs internals documentation +HELLO Hello in many languages (Mule test file) InstallGuide Fast track to installation -LPF Information about the League for Programming Freedom -MACHINES List of known machines configurations (OLD) -MAILINGLISTS List of available Mailing lists -MORE.STUFF List of useful unbundled packages -NEWS XEmacs 21.4 release information -ORDERS -ORDERS.EUROPE -ORDERS.JAPAN Order forms for GNU software -PACKAGES List of packages available for 21.4 release +NEWS XEmacs 21.5 release information +ONEWS Older release information +OONEWS Even older release information README This file -README.HYPERBOLE -README.OO-BROWSER How to obtain Hyperbole and the OO-Browser -SERVICE How to obtain paid support for free software -TERMS Information about termcap entries TUTORIAL Tutorial for first time users (English version) TUTORIAL.* Tutorials in non-English languages +VEGETABLES XEmacs 21.5 code names XKeysymDB X Keysym Database with Motif bindings -aliases.sh Useful shell aliases cbx.png "Created by XEmacs" logo -check_cygwin_setup.sh Script to check for presence of Cygwin ctags.1 Ctags man page custom/ Images used in Custom mode editclient.sh Either start up XEmacs or connect to a running one @@ -44,18 +25,15 @@ emacsstrs.sco Special files for running on an SCO console eos/ Images for EOS support (GUD) etags.1 Etags man page -gnu.xbm -gnu.xpm Image of a Gnu. gnuattach.1 Gnuattach man page gnuclient.1 Gnuclient man page gnudoit.1 Gnudoit man page gnuserv.1 Gnuserv man page gnuserv.README Original README file from gnuserv -gnusref.tex Gnus reference card gray1.xbm Gray bitmap -ms-kermit -ms-kermit-7bit Files for running XEmacs through kermit -photos/*.Z Various pictures of XEmacs developers +idd/ ? +package-index.LATEST.gpg ? +photos/* Various pictures of XEmacs developers recycle.xpm recycle2.xpm Two versions of oversized Recycle cursor refcard.ps.gz Postscript version of XEmacs reference card @@ -63,19 +41,18 @@ sample.Xdefaults (legacy -- to be removed) sample.Xresources Example ~/.Xresources file sample.init.el Example ~/.xemacs/init.el file -sink.xbm A Gnu icon sparcworks/ Support files for Sparcworks tests/ Testcases for external widget -time/ Image files for display-time toolbar/ Image files for the toolbar trash.xpm Garbage can icon +unicode/ Unicode conversion tables xemacs-beta.xpm XEmacs Beta logo +xemacs-enhanced.png "XEmacs-enhanced" logo xemacs-fe.sh XEmacs frontend driver xemacs-icon.xpm xemacs-icon2.xbm xemacs-icon2.xpm xemacs-icon3.xpm Various versions of an XEmacs WM icon -xemacs-ja.1 Japanese XEmacs man page xemacs.1 XEmacs man page xemacs.xbm xemacs.xpm XEmacs logo used on the splash screen diff -r 7edc33019aa4 -r b7b90f750a78 etc/README.HYPERBOLE --- a/etc/README.HYPERBOLE Mon Jan 31 20:01:50 2005 +0000 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000 @@ -1,12 +0,0 @@ -Hyperbole is a suite of tools for enhancing productivity. - -Hyperbole has been packaged as of 2003-07-01, and is available in an -XEmacs package archive mirror near you. If this file has not been -updated recently, please ask about status on xemacs-beta@xemacs.org, -and remind us to update this file. - -The most recent upstream version of this package is available from -SourceForge, http://projects.sourceforge.net/hyperbole/. There -apparently is no longer any commercial support, but you might query -the owner of the SourceForge project (at the time of this writing, Bob -Weiner ). diff -r 7edc33019aa4 -r b7b90f750a78 etc/README.OO-BROWSER --- a/etc/README.OO-BROWSER Mon Jan 31 20:01:50 2005 +0000 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000 @@ -1,12 +0,0 @@ -The OO-Browser is a tool for examining object oriented code. - -The OO-Browser is a candidate for XEmacs packaging as of 2003-07-01, -and may be available in an XEmacs package archive mirror near you. If -this file has not been updated recently, please ask about status on -xemacs-beta@xemacs.org, and remind us to update this file. - -The most recent upstream version of this package is available from -SourceForge, http://projects.sourceforge.net/oo-browser/. There -apparently is no longer any commercial support, but you might query -the owner of the SourceForge project (at the time of this writing, Bob -Weiner ). diff -r 7edc33019aa4 -r b7b90f750a78 etc/SERVICE --- a/etc/SERVICE Mon Jan 31 20:01:50 2005 +0000 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000 @@ -1,1407 +0,0 @@ --*- text -*- -GNU Service Directory ---------------------- - -This is a list of people who have asked to be listed as offering -support services for GNU software, including GNU Emacs, for a fee -or in some cases at no charge. - -The information comes from the people who asked to be listed; -we do not include any information we know to be false, but we -cannot check out any of the information; we are transmitting it to -you as it was given to us and do not promise it is correct. -Also, this is not an endorsement of the people listed here. -We have no opinions and usually no information about the abilities of -any specific person. We provide this list to enable you to contact -service providers and decide for yourself whether to hire one. - -Before FSF will list your name in the GNU Service Directory, we ask -that you agree informally to the following terms: - -1. You will not restrict (except by copyleft) the use or distribution -of any software, documentation, or other technical information you -supply anyone in the course of modifying, extending, or supporting GNU -software. This includes any information specifically designed to -ameliorate the use of GNU software. - -2. You will not take advantage of contact made through the Service -Directory to advertise an unrelated business (e.g., sales of -non-GNU-related proprietary information). You may spontaneously -mention your availability for general consulting, but you should not -promote a specific unrelated business unless the client asks. - -Please include some indication of your rates, because otherwise users -have nothing to go by. Please put each e-mail address inside "<>". -Please put nothing else inside "<>". Thanks! - -For a current copy of this directory, or to have yourself listed, ask: - service@gnu.org - -** Please keep the entries in this file alphabetical ** - -Aaronsen Group, Ltd. -600 Grant St. -Suite 5345 -Pittsburgh, PA 15219 US -+1 412 391 6000 voice -+1 412 391 6006 fax -http://www.aaronsen.com/gnu - -The Aaronsen Group provides several levels of service in the free software -arena, from simple configuration and installation to large extensions and -new development. We specialize in unique applications, but have the -experience to handle all manner of prospects, from database-backed -web-sites to high-end multiprocessor clusters. - -Our service area covers the US, with key offices in Pittsburgh, PA; San -Jose, CA; and New York, NY. - -We are available for both hourly work (at $450 per hour, some qualified -discounts are available) and fixed-price projects. Work is done on the -client site, at our offices, or remote via Internet or telephone -connection. - -Updated: 2002-04-18 - -ACT Europe -8 rue de Milan -75009 Paris -+33 1 49 70 67 16 -+33 1 49 70 05 52 fax -www.act-europe.com - -ACT Europe, developer and maintainer of the Ada 95 GNAT Pro -Development Environment, specializes in project support and consulting -for users of GNAT Pro. - -GNAT Pro, based on GNU/GCC technology, is the most widely used Ada 95 -development environment, and the ideal solution in environments where -efficient and reliable code is critical. GNAT Pro is available on the -widest number of platforms, from Unix workstations and PCs to bare -boards and embedded systems. - -ACT Europe offers full Ada 95 solutions and is continuously enhancing -and developing programming tools, debuggers and integrated development -environments. - -We believe the Ada market and your project will best benefit from an -open, non-proprietary technology, we have made all our products Open -Source software by adopting the licensing policy of the Free Software -Foundation. This means that all components of the GNAT technology, -including the run-time, come with sources. - -Highest-quality, responsive support is a key ingredient in complex and -reliable Ada software products. GNAT Pro, the leading Ada 95 -development system, is the only Ada solution that comes with -outstanding support. Please visit www.act-europe.com for further -details of our products and services or contact us at - - -UPDATED: 2004-02-13 - -Ada Core Technologies -104 Fifth Avenue, 15th Fl. -New York, NY 10011 -+1 212 620 7300 -+1 212 807 0162 fax -www.gnat.com - -Ada Core Technologies, developer and maintainer of the Ada 95 GNAT Pro -Development Environment, specializes in project support and consulting -for users of GNAT Pro. - -GNAT Pro, based on GNU/GCC technology, is the most widely used Ada 95 -development environment, and the ideal solution in environments where -efficient and reliable code is critical. GNAT Pro is available on the -widest number of platforms, from Unix workstations and PCs to bare -boards and embedded systems. - -Ada Core Technologies offers full Ada 95 solutions and is continuously -enhancing and developing programming tools, debuggers and integrated -development environments. - -We believe the Ada market and your project will best benefit from an -open, non-proprietary technology, we have made all our products Open -Source software by adopting the licensing policy of the Free Software -Foundation. This means that all components of the GNAT technology, -including the run-time, come with sources. - -Highest-quality, responsive support is a key ingredient in complex and -reliable Ada software products. GNAT Pro, the leading Ada 95 -development system, is the only Ada solution that comes with -outstanding support. Please visit www.gnat.com for further details of -our products and services or contact us at - -UPDATED: 2004-02-13 - -Alcôve ------- - -Alcôve, Centre Paris Pleyel, 153 bld Anatole France -93200 Saint-Denis France - -Email: - -Web: http://www.alcove.com -Tél.: +33 1 49 22 68 00 -Fax: +33 1 49 22 68 01 - -Founded in 1996, Alcôve's main purpose is to promote and support the -use of GNU/Linux and OSS on the European market. -Expertise in OSS innovation is the foundation of all Alcôve's -activities. -We provide key accounts and leading businesses in the field of IT with : - - Consultancy - Engineering - Training - Support - Technical watching brief - OSS Certification - Validation - Guarantee - Drivers for the linux kernel - Company directory and unified messaging - Linux Firewall Security Package - -Keys: support services, consulting, open source software, GNU/Linux, -Apache, Perl, GNU, Samba, Zope, Imp, OpenLDAP - -Average daily rate, depending on the job : 1000 euros. - -Updated: 2002-06-12 - -Allegro Consultants, Inc. -1072 De Anza Blvd., Suite B101 -San Jose, CA 95129-3532 -USA -+1 408 252-2330 voice -+1 408 252-2334 fax -http://www.gccsupport.com - -Allegro Consultants, Inc, in association with DIS International, is -now offering annual support contracts covering the GNU Compiler -Collection and related tools, including the GCC C and C++ compilers -for MPE/iX. - -The free GCC C and C++ compilers have been available on MPE/iX for -several years now, and are used for mission-critical applications by -many organizations including Hewlett-Packard. Until now, assistance -was available only from Mark Klein of DIS on a limited, voluntary -basis. Mark is the person who originally ported GCC to the HP e3000, -and he continues to maintain the software and port new versions. - -Support contracts start at $1,995.00/year for an organization -(unlimited number of HP e3000 computer systems) with two designated -callers. Additional options are available for large organizations who -need to designate more than two authorized callers, or who want the -additional security of 24x7 coverage. - -Updated: 2002-04-18 - -Amazonia Computing - - -http://www.efn.com/~rick - -5050 Donald St -Eugene, OR 97405 -541-485-7264 - - -I provide development and technical support for free software -and open source systems including embedded programming, GNU/Linux, the -GNU development suite... - -I have over 10 years experience building and maintaining systems ranging -from medical patient monitoring systems to Linux device drivers for -custom PCI plug in cards. - -Rates range from $85.00/hr to $90/hr USD. Will work for a lower rate -if in involves working in either Brazil, Vietnam, Indonesia, or Cuba. -I am also willing to work on fixed price contracts. - -Updated: 2002-04-22 - -Dipl.-Inform. Gerd Aschemann -Martinstr. 81f -D-64285 Darmstadt -Tel.: +49 173 3264070 -http://www.aschemann.net/ - -- Consultant - + Unix Network and System Administration - + Distributed Systems and Middleware Infrastructures -- former System Administrator (UNIX and NT) at CS Department, TU Darmstadt, Germany -- 22 years working in the CS field, System administration on different platforms -- 15 years with UNIX/Networking/FreeWare/GNU/X11 -- 12 years courses on Operating Systems and Distributed Systems -- Lectures on System and Network Administration -- Platforms: Solaris, GNU/Linux, SunOS, Ultrix, HP-UX, Digital Unix, AIX, SCO, FreeBSDs -- Distributed Platforms and Information Systems (CORBA, WWW, Java, SOAP) - -Rates are at 100,-- EUR (~90 US$) per hour minimum, depending on the job. -I am willing to travel for sufficiently large jobs. - -Updated: 2002-04-23 - -Baker Research, Ltd. -P. O. Box 4057, Leesburg, VA 20177 -Phone: (703) 999-6719 (Voice) -Web: http://www.baker-research.com -email: -Rate: $75.00/hr to $150.00/hr, or fixed-price projects. - -Services: - --Full-lifecycle software development - --Database design and migration - --Programming (C/C++, tcl/tk, bash, perl) - --Custom backup and archival systems - --GNU/Linux system installation, configuration, and management - --Customization of systems for user needs - --Software product evaluation and recommendation - --Cluster systems support - -Installation, configuration, and management - -MPI and Myrinet support - --Data acquisition, management, visualization, and archival - -Updated: 2004-05-13 - -Don Barry, Ph.D. -Ithaca, NY - -Astrophysicist with extensive and varied hacker background. Substantial -expertise in mathematical modeling, instrument interface, low-level and -high-level hardware control, statistical analysis, automated/mathematical -typesetting. Also fluent in opto/electro/mechanical design. I try to find -solutions using free software when possible and specialize in GNU/Linux -platforms. Degrees also in chemistry and mathematics. - -Speak: C, APL, Fortran, J, Perl, Emacs Lisp, IDL, variety of machine -languages from CDC CYBER (!) to x86 families, TeX/LaTeX, sendmail, and -quite a few others. Experience on platforms from PDP to present. - -Rates: $75--$150 per hour + travel (if required) depending on the needs of -the project, the level of support and availability required, and its -interest to me. - -Services: consulting, design, porting, lecturing, support, project definition, -system implementation. - -Updated: 2002-04-18 - -James Craig Burley -97 Arrowhead Circle -Ashland, MA 01721 -Email: -Web: http://world.std.com/~burley/ - -Expertise (mainly Development and Maintenance): - Compilers for Imperative Languages (author of GNU Fortran, aka g77) - Operating System Kernels - Tools/Utilities - Microcode (mainly VLIW) and Assembler - Software-Development-System Architecture (including APIs, IDEs) - Debugging - Documentation Authoring and Project Management - -Experience: - Programming Languages such as C, Fortran - Operating Systems such as Unix, GNU/Linux, Solaris, HP-UX - Assembler/Microcode Languages -- RISC (such as SPARC), CISC, VLIW - Scripting Languages - API Design, Documentation, and Use - -Rate: $200/hour - -Updated: 2002-04-18 - - C2V Michel Delval - 82 bd Haussmann Jean-Alain Le Borgne - 75008 Paris - France - Tel (33 1) 40.08.07.07 - Fax (33 1) 43.87.35.99 - http://www.c2v.com/freesoft.htm - e-mail: - - Services: we offer source or source+binary distribution, - installation, training, maintenance, technical support, - consulting, specific development and followup on the GNU software - development environment: Emacs, gcc/g++, binutils, gas, gdb. - - Porting on new platforms, and professionally developing software - with the GNU tools in the Unix/X11 environment since they were - first available. - - Experience: GNU C Compilation toolchain for the SGS-Thomson D950 - and ST20 DSP chips. - - GNU C compilation toolchain (cross-compiler, compiler, linker, - assembler, debugger) for SparcV7 ERC32 based space systems - (Sextant Avionique / Alcatel Espace). - - Feasability study, analysis and prototyping of a complete - compilation toolchain based on the GNU programming tools for the - CSEM RISC microprocessor family. - - Rates: from 800 Euros/day to 120 000 Euros/year, 40% discount for - educational institutions, add taxes and expenses. Ask for list. - -Updated: 2002-04-25 - -Cendio Systems AB -Teknikringen 3 -SE-583 30 Linkoping -SWEDEN -+46 13 21 46 00 voice -+46 13 21 47 00 fax -http://www.cendio.com/ - -Cendio Systems develops, implements and integrates solutions based on -Open Source Software. We also develop and market the Fuego -Firewall(TM), an award winning and easy-to-use firewall, based on -GNU/Linux. - -We offer professional services, including support, maintenance, -integration and development in the following areas: - -* Embedded Linux -* Client/Server Solutions GNU/Linux/BSD -* Professional Training GNU/Linux, certifications from SAIR Linux/GNU -* Open Source Strategy -* Development/Adaptation of free software - -Cendio Systems have deep roots in Linkoping University, and was -founded 1992 as Signum Support. Our headquarters resides in Mjardevi -Science Park in Linkoping and we have an office in Stockholm. We are -currently about fifty employees at both locations. - -Cendio Systems won the Lotus 'Tux Award' at LotusSphere 2000 for "the -partner who best exemplifies a unique dedication to Lotus and Linux -technologies and has successfully executed their vision in the -marketplace." - -Cendio Systems have the following certifications and memberships: - -Association of Computing Machinery, Professional Membership -COMPAQ System Specialist (Intel and Alpha Systems) -Embedded Linux Consortium, Founding Member -IBM Value Added Reseller (Netfinity) -IBM Solution Provider (RS/6000) -SAIR GNU/Linux, Accredited Center for education -SGI Systems Integrator - -Rates: Please request our price list. - -Updated: 2001-05-09 - -CodeSourcery, LLC -9978 Granite Point Ct -Granite Bay, CA 95746 -(916) 791-8304 -http://www.codesourcery.com - -CodeSourcery specializes in customization of, enhancements to, and -support for all GNU software. We have particular experience in the -field of programming tools, and have been responsible for many -features in the GNU C and C++ compilers including the implementation -of member templates and type-based alias analysis. Mark Mitchell, one -of our co-founders, is a co-maintainer of the GNU Compiler Collection. - -We also have experience with GNU tools ranging from emacs to binutils -to gdb to autoconf, and are willing to work on any and all free -software projects. - -Please see our web page at www.codesourcery.com for more information -about our products, services, and prices. - -Updated: 2002-04-19 - -Stuart Cracraft -25682 Cresta Loma -Laguna Niguel, CA, 92607, USA -Phone: 949-347-8106 -Rate: negotiable - -Consultation topics: -Entire GNU suite - porting, compilation, installation, -user-training, administrator-training - -Method: via any combination of telephone, dialup, Internet, in-person, email. - -Experience: supporting GNU since project inception, original port of -GNU Emacs to Sun Solaris, original author of GNU Emacs online tutorial. -Expertise in C, Emacs Lisp, Perl, Expect, Oracle, Informix, SunOS, Solaris, -NIS, NFS, system-monitoring via paging. Unix System and Database -administration or development. - -Updated: 2002-04-20 - -Bruce Dawson - -CodeMeta, Inc. -London, NH USA -800-354-2209 - -Specializing in GNU tools such as CVS, gnats, bash, gawk, fileutils... - -Services: - - o 800 phone support. - - o Modification and development. - - o Training. - -Rate: Fixed rate deliverables or $110/hour for hourly work. - -http://www.codemeta.com - -Updated: 2002-04-23 - -DSS Distributed Systems Software, Inc. -3253 Georgia St. -Richmond, British Columbia V7E 2R4 http://www.dss.bc.ca -CANADA (604) 270-9559 - -GNU-related services: - We specialize in support for GCC (mainly C and C++), including porting, - retargeting, and customizing. - Also, GNU and other free software that falls within our areas of expertise. - -Expertise: - DSS provides software design, implementation, and consulting services for: - o Client/Server architectures - Including web-based systems, Apache web server customization, CGI, - server-side processing, JavaScript, automatic web page generation - o E-Security, including PKI and SSL - o Directory systems, including X.500 and LDAP - o High-performance and special-purpose distributed systems and databases - o Computer networking and communication protocols - Internet protocols such as TCP/IP and UDP, development of custom protocols - o Creating and customizing "small", embedded, and special-purpose programming - languages - -Rates: - Consulting rates are $65-$200 USD per hour, plus - applicable taxes. Fixed-cost projects are also possible. - -Updated: 2002-06-27 - -Gord Eagle -Box 325 http://fig.org/gord/ -Lumsden, SK S0G 3C0 Voice: (306) 731-3011 -CANADA - -I will gladly help novice and intermediate computer users to install, -understand, and use free software, whether or not I have prior -experience with that software. I know my limitations well, and will -freely give other contacts if I cannot solve your problem myself. - -I have over 5 years of experience with several of the major free OSes: -GNU/Linux (Debian, Red Hat), NetBSD, FreeBSD, and GNU/Hurd. Some of -my specialties are networking, Emacs, Automake, Autoconf, C, Perl, and -shell script programming. - -My rates are negotiable depending on the task: usually $40-$60 -(Canadian) per hour. Flat rates preferred. - -Updated: 2002-04-18 - -John W. Eaton -, - -Experience: Original author and current maintainer of GNU Octave - (http://www.octave.org). - - Derivatives of the Unix man utility that I wrote in 1990 - are currently distributed with several GNU/Linux systems. - - Improved GNU Make's support for VPATH and object - libraries on VMS systems. - - Various other enhancements and bug fixes for other free - software tools. - - I have more than 19 years experience programming various - languages and systems, more than 14 years as a user and - system mangler of Unix systems, including Ultrix, SunOS, - AIX, HP/UX, BSD, IRIX, Digital Unix, and GNU/Linux. - Long-time user of GNU tools on all these platforms. - -Programming: Octave, Matlab, C++, C, Fortran, Emacs Lisp, TeX/LaTeX, - AWK, M4, Autoconf, Make, Lex & YACC, Unix shell - programming, etc. - -Services: Anything related to programming and extending Octave. - Porting, installation, and customization of GNU/Linux and - GNU tools. Unix system administration. - -Rates: $100/hour + travel and expenses (if required). Will - consider travel for short periods and/or sufficiently - interesting jobs, but prefer to work via the net or email. - Lower rates for non-profits. - -Updated: 2002-04-19 - -Noah Friedman -6114 La Salle Ave. #739 -Oakland, CA 94611-2802 - -Author of several Emacs Lisp packages and parts of Emacs, as well as -numerous network and unix system utilities. Co-maintained GNU Texinfo and -Autoconf for a couple of years. Experienced unix systems engineer. -FSF employee Feb 1991--Sep 1994. - -I can design and implement relational database services; perform -installation, porting, and enhancement of all GNU software and any other -free software, especially for linux- and unix-derived systems; design -high-capacity hardware-redundant servers for production environments; -provide consulting on the use of version control management. - -Fees negotiable, averaging $100-$150/hour. I can work in the California -bay area or anywhere accessible on the Internet. For larger jobs I may be -willing to travel. - -Updated: 2002-04-19 - -Ronald F. Guilmette -RG Consulting -1751 East Roseville Pkwy. #1828 -Roseville, CA 95661 -Tel: +1 916 786 7945 -FAX: +1 916 786 5311 -http://www.monkeys.com/ - -Services: Development & porting of GNU software development tools. - -GNU Contributions: - Invented, designed, and implemented the protoize and - unprotoize tools supplied with GCC2. - - Designed and developed all code to support the generation - of Dwarf symbolic debugging information for System V Release - 4 in GCC2. - - Performed original port of GNU compilers to SVr4 system. - - Finished port of GNU compilers to Intel i860 RISC - processor. - -Experience: 15+ years UNIX systems experience; 15+ years working on - compilers and related tools. - - 10+ years working professionally on GCC, G++, and GDB under - contract to various firms including the Microelectronics - and Computer Technology Corporation (MCC), Data General (DG), - Network Computing Devices (NCD), and Intel Corp. - -Other qualifications: - Developer of commercial C and C++ compiler test suites. - - Former vice-chairman of UNIX International Programming - Languages Special Interest Group (UI/PLSIG). - - Bachelor's and a Master's degrees, both in Computer Science. - -Rates: Variable depending upon contract duration. Call for quote. - -Updated: 2002-05-04 - -IDEALX -15-17 avenue de ségur -75007 Paris -France - -Tel - +33144420000 Fax - +33144420001 -http://www.IDEALX.com, http://www.IDEALX.org - -IDEALX is involved in the development of Open Source solutions,and -ensures their deployment and maintenance. - -IDEALX also contributes to the community, by producing its own -Open Source components such as : IDX-PKI (a 100% Open Source -Public Key Infrastructure) see :http://idx-pki.idealx.com - -Development -Technical support -Technology watch -Consulting -Engineering -Training - -Rates - Variable - -Updated: 2002-07-22 - -Ehud Karni -Israel - -Support of Emacs & Emacs lisp, GNU/Linux, Cygwin. - -Fee: $75/hour. - -Updated: 2002-04-20 - -Bradley M. Kuhn - -http://www.ebb.org/bkuhn - -I am available for part-time system administration, software development -and training. I have extensive experience with system administration of -GNU/Linux systems and Free Software development. I have also taught -courses in C++ and Perl. As an employee of the FSF, I have a unique -perspective on the free software community. - -Please visit my homepage for more information on my background and skills. -My resume is also available there. - -I am available for both 1099 and W2 on-site contracting in the Boston, MA, -USA metropolitan area, as well as remote consulting via dialup or Internet -connection anywhere in the USA. I am not interested in relocation. -However, temporary (two week maximum) jobs with paid expenses at other -locations will be considered. - -My rate varies greatly (between $25-$60/hour) depending on the -circumstances. Rates for non-profit organizations will be on the lower end -of the spectrum if I support your cause. - -Updated: 2002-04-20 - -Greg Lehey -LEMIS -PO Box 460 -Echunga SA 5153 -Australia - -Phone: +61-8-8388-8286 -Fax: +61-8-8388-8725 -Mobile: +61-418-838-708 -Mail - -Services: Supply, porting, installation, consultation on all GNU -products. - -Experience: 30 years OS and compiler experience, ports of most GNU -products. Author of ported software CD-ROM for UNIX System V.4.2, -"Porting UNIX Software" (O'Reilly), "Installing and Running FreeBSD" -and "The Complete FreeBSD" (both Walnut Creek). - -Rates: Choice of AUD 300 per hour or hotline rates AUD 6 per minute. -Outside Australia, $US 180 per hour or $US 3.50 per minute. Quick, -well prepared questions by mail may be free. - -Updated: 2002-04-21 - -Alan Lehotsky -Quality Software Management -634 West St -Carlisle, MA 01741 - -Phone: (978)287-0435 -Fax: (978)287-0436 - -Services: - - Support for GNU compilers, including rehost/retarget - - GNU Binutils rehost/retarget. - - cgen/sim - - Perl internals hacking - - General system software work (SW tools, O/S, device drivers) - - runtime library (especially floating point) - - project management - - software process improvement - -Experience: 20+ years of design and implementation of optimizing - compilers. "Mr. Bliss" at Digital in the 70's and early - 80's. Experience with Motorola 68k, PowerPC, SPARC, Intel - x86 and IA64 (Merced), MIPS, NS32K, ADI SHARC DSP, VAX, PDP-11, - PDP-10. Wrote or maintained compilers for Ada, BLISS, C, C++, - FORTRAN, Pascal, Modula/2, O/S experience includes Unix (OSF/1, - SunOS, Solaris, AIX, HP/UX), VAX/VMS, Windows/NT, MacOS. - - 8 years experience with GCC internals, including major changes to - support 8 bit bytes on word-address Analog Devices SHARC DSP and - general support of PowerPC code generation. Retargetted gcc/binutils - cross-tools to ASIC used in optical switch. Retargeted gcc to 8 bit "internet toaster" - micro-computer. - -References available. - -Rates: $110/hr. - fixed price possible for well-defined deliverables. - -Updated: 2002-04-18 - -Reuven M. Lerner -Lerner Communications Consulting Ltd. -PO Box 518 -Modi'in 71700 -Israel - -Phone: 08-973-2225 (within Israel) - +972-8-973-2225 (outside of Israel) - -Fax: 08-973-0477 (within Israel) - +972-8-973-0477 (outside of Israel) - -WWW: http://www.lerner.co.il - -We specialize in writing custom Web and Internet applications. In -particular: - -- We create database-backed Web sites using Perl, Tcl, Python, Java, - Apache, mod_perl, OpenACS, Zope, MySQL, and PostgreSQL. - -- We offer support and service for system administrators who need help - with their GNU/Linux systems. - -- We offer training in a variety of programming languages (Perl, Tcl, - Python, and Java) and in GNU/Linux administration. - -Consulting rates: $110/hour, or $85/hour for non-profits. (Our rates -drop when we're hired on retainer or for projects that last longer -than one week.) - -Updated: 2002-04-18 - -Richard Levitte -Levitte Programming -Spannvägen 38, I -S-168 35 Bromma -Sweden -Tel.nr.: +46 (8) 26 52 47 (there is an answering machine) -Cellular: +46 (708) 26 53 44 (there is an answering machine) -e-mail: - -What I do: - I work with various free software packages, mostly GNU ones, - for Unix and VMS (the latter both on VAX and Alpha). I've - been porting GNU Emacs to VMS between spring 1991 and - somewhere in 1998. I've ported a bunch of other GNU programs - as well. I maintain GNU vmslib. - For further info, see http://www.lp.se/~levitte/prof/resume.html - -Programs supported: - To a varying degree (ranging from extension and porting to - installation and simple questions) at the time of updating - this entry: - - GNU vmslib, emacs, autoconf, zip, diffutils, m4, patch, - texinfo, C/C++; on both VMS and Unix. - - Other GNU programs to a small degree; on Unix. - For further info, look at http://www.lp.se/products/gnu.html - -Experience: - Fluent in TeX/LaTeX and many programming languages. - Modified key elements in Emacs (e.g., memory and process - management) to work transparently on VMS. I have very good - knowledge in the VMS operating system. I'm also knowledged in - the a few Unix flavors. - Well knowledged in cryptography as well as the development of - the PKIX standards (both based on X.500 and RFC 2459) and - involved protocols (SSL, OCSP, CMS, ...) - For further info, see http://www.lp.se/~levitte/prof/resume.html - -Your Rate: - $75-$100/hour (750-1000 SEK in sweden), plus expenses. My - rates are negotiable, depending on how interesting the project - is to me. - -Updated: 2002-04-18 - -Moss - Card Consulting Inc -16360 Broadway Avenue -Building A, Suite 103-104 -Cleveland OH 44137 USA - -www.mosscard.com -+1 216 587 4343 -+1 216 587 4342 Fax - -This dynamic Cleveland company offers the following services: -- installation and configuration for SGI machines -- Cross-platform development using wxWindows under GNU\Linux -- Programming (C/C++,tcsh) -- Compiler development using CORBA and gcc -- Real-time Cross-Platform Development -- Consulting -- Engineering -- Staff Augmentation - -We are Cleveland's first GNU\Linux developers, and one of our company's -members has just launched NASA's first cross development tool. - -Our rates vary from ($50 - $400) USD depending on the nature of the project. - -Updated 2004-2-23 - - NetGuide Scandinavia AB - Tankeg=E5ngen 4 - S-417 56 G=F6teborg, Sweden - +46 31 50 79 00 voice - +46 31 50 79 39 fax - http://www.netg.se - -NetGuide Scandinavia AB is a company that does consultant jobs and holds -courses in the fields of Unix software, TCP/IP networking and Internet -applications. The people behind NetGuide Scandinavia AB have many years of -general Unix experience, both as system administrators and as -programmers, and also extensive experience in maintaining the GNU -programs; in administration as well as finding and fixing bugs. - -Services offered: - - - Installation and customizing GNU and other free software. We will - make free software as easy to install and use as shrink wrapped - programs. - - Service and support subscriptions. - - Warranty protection. - - Customization and porting. - - Subscriptions to new versions which we will send monthly or with - any other interval. - - Finding, recommending and investigating free software in any - area of the customers choice. - - Regular consulting. - - Support on Internet service software, especially the free - - Support on GNU/Linux. - - Freeware based courses in Unix usage, C, C++, or any GNU tools - - Rates: For courses, contact us for a quote, - For consulting, $60-120/hour, depending on contract length. - -Updated: 2000-12-13 - -Network Theory Ltd -15 Royal Park -Bristol -United Kingdom -Tel: +44 117 3179309 -Fax: +44 117 9048108 -http://www.network-theory.co.uk/gsl/ - -We provide software maintenance contracts for commercial users of the -GNU Scientific Library. - -We can also provide general numerical consulting for all types of -scientific and quantitative applications. - -Rate: $1495/year (950 ukp) for base maintenance contract. - -Updated: 2004-04-26 - -Thien-Thi Nguyen -Solana Free Software -ttn@glug.org -San Diego, CA, USA - -Service: General Consulting and Hacking on all things GNU - Resume: http://www.glug.org/people/ttn/resume.html - Rates: no job too small, everything negotiable - -Updated: 2002-04-20 - -David Nicol -Post office box 45163 -Kansas City, Missouri 64171 - -http://www.tipjar.com/dnconsult - -Unix, GNU/Linux, Perl installation, C, C++, Lisp, Perl programming. - -CGI programming. - -Installation, porting. - -Specification development, design, implementation, documentation. - -Rate: $60/hour, or fixed contract. On-site support available in -greater Kansas City area. - -Updated: 2002-04-23 - -Jonas Oberg (TeX: Jonas \"Oberg -Rimfrostgatan 95 Rimfrostgatan 95 -S-418 40 Goteborg S-418 40 G\"oteborg -Sweden Sweden) - -Phone: +46-733-423962 -E-mail: - -I offer support for most GNU software including the GNU -Hurd and also do system administration on GNU systems. -I can do free software development and have a good -understanding of automake, autoconf, flex, bison, guile, -texinfo and much more. Rates around USD$100. - -Updated: 2002-04-22 - -Francesco Potortì -Via S.Stefano, 8 -56123 Pisa, Italy -Tel. (050)560671 - -Emacs: installation and maintenance, training and tutorials, - customisation, extensions, troubleshooting. Author of some of - the packages in the emacs distribution, has made the porting - of emacs to the Motorola Delta architecture. - -Other: installation and maintenance of GNU software. Experience with - hylafax, RCS, gperf, etags, smail, indent, diff, gawk, gcc, - screen. Is the current maintainer of etags. - -Rates: 100 E/hour. - Prefer e-mail communication to telephone. - -Qualifications: Electronic Engineering degree, Pisa. Full time - researcher in CNUCE-CNR. - Familiar with elisp programming, porting of C programs, - low-level TCP/IP programming for embedded systems. - -Updated: 2002-06-28 - -Rodolphe Quiedeville -1 Quai Martin -56400 Auray -France -Tel (33 1) 613796341 -http://rodolphe.quiedeville.org/ - -Experience: Original author and current maintainer of the Lolix project - can be found at http://www.lolix.com - - I have more than 5 years experience on free software - system administration. - -Programming: PHP, Perl, Unix shell - -Services: Anything related to free software network and system administration. - -Updated: 2002-07-01 - -Red Hat, Inc. - -1325 Chesapeake Terrace -Sunnyvale, CA 94089 USA -Toll free: 866-2REDHAT ext. 3005 -+1 408 542 9600 voice -+1 408 542 9699 fax - -GNUPro Tools -Red Hat provides supported and maintained versions of gcc, g++, gdb -with GUI, GNU linker and GNU macro assembler. In addition, Red Hat -provides these GNU software development tools for well over many -popular host-target configurations. Support includes bug fixes and -semi-annual releases of the toolset. Each release is regression -tested and includes substantial improvements and additions to the -current release. Support is available through Incident support -packages, or Unlimited support for specific user groups. GNUPro is -available with standard, custom, and vintage toolchains for both -native and embedded application development. New target processors -are being added regularly. Rates for support for standard products -start at $12,500. - -Embedded Linux -Red Hat offers Red Hat Embedded Linux to companies looking for an open -source and royalty-free runtime solution. Red Hat Embedded Linux -currently supports certain ARM, StrongARM, and MIPS families of -processors. Embedded Linux supports multiple graphics APIs, is -compliant with POSIX APIs and thread support, can be configured as low -as 512k memory footprint including TCP/IP and NFS built into the -kernel, and supports journaling and transparent compression in -filesystems. Support for new processors is available via Red Hat -Professional Services. - -Updated: 2001-05-16 - -Relogic AB -Pipersgatan 26 -Box 868 -SE-112 28 Stockholm -SWEDEN - -web http://www.relogic.se -e-mail info@relogic.se -phone +46 708 800 000 -fax +46 708 800 580 - -Relogic provides experienced unix developers that know and love GNU -products. We can take on anything from single contractor support to -full scale projects. We know all programming languages and all Unix -dialects. - -Updated: 2002-04-19 - -RON's Datacom Co., Ltd. -79, DongWu Ave., -Wuhan, Hubei Province -430040 China P.R. -Tel +1370-113-0868(mobile) +86-27-83222108(office), Fax +86-27-83222108 -http://www.rons.net.cn -info@mail.rons.net.cn - -Ron's Datacom publishes the truly free ( the "free" in freedom) -monthly periodical --- FREE SOFTWARE Magazine(FSM), offering a series -of free software training courses entitled "Hackerdom", including: - -- Working with GNU Emacs; -- Programming in Emacs Lisp; -- Using and Porting GNU CC; -- Flex and Bison; -- Debugging with GDB; -- Device Driver Development with GNU AS and C; -- Shell Programming with BASH; -- GNU Building Tools: Make, Automake, Autoconf, M4; -- Typesetting and Layout Designing in TeX and PostScript; -- Parsing XML Documents. -- Source Code Version Management with CVS; -- GNU Awk and Sed; - -RON's Datacom Typesetting Workshop offers professional typesetting service -for both academic and commericial publishers, and solutions for building -the modern electronic publishing system with industrial strength. - -Hong Feng gives speeches to the public about the philosophy of free -software, and importance of freedom, suggestions for curriculum -reforms of computing science department in the universities and colleges. - -Please visit our website (www.rons.net.cn) for more details. - -Updated: 2002-05-12 - -Phillip Rulon -122 Blossom Rd. -Westport, MA 02790 -USA -508.672.3007 - - -15 years experience with GNU systems and tools. Available for any free -software project. Most useful for network design and construction or -dynamic web development. Very good Debian, Perl, and Apache. - -Boston, travel OK. -$100/hr, flat rate possible. - -Updated: 2002-06-28 - -Sankhya Technologies Private Limited, -III FLoor, #30-15-58 "Silver Willow", -Dabagardens, Visakhapatnam - 530 020 -INDIA -Tel: +91 891 5542665 -Fax: +91 891 5542666 -http://www.sankhya.com/info/services/gnu/gnu.html - -SANKHYA Development is a package of software engineering services -structured around select technologies in the areas of Compilers, -Assemblers and Linkers, Debuggers. Our rich experience with such -technologies enables us to deliver competitive software development -services to you, customized to your specific requirements. - -Sankhya offers competitive and cost-effective GNU maintenance and -support services for gcc, binutils, libtools and gdb. GNU Development -and Maintenance focuses on providing C, C++ compiler development, -assembler and linker development, debugger development, and compiler -optimizations. For semiconductor and chip design companies we offer -annual maintenance packages, and for software developers we offer -annual support packages. Following services are provided for gcc, -binutils, libtools and gdb, - - * Retargeting gcc, binutils, libtools and gdb for new processor - architectures, including RISC, CISC, VLIW or DSP architectures. - * Implementing processor specific optimizations. - * Annual Developer Support for developers. - * Maintenance packages for CPU/SoC vendors. We offer variety of - development/maintenance packages. - -UPDATED: 2004-02-13 - -Sparkle Computer Co Ltd - -email: -web: www.sparkle-cc.co.uk - -Specialists in software development and networks in London and -South-East England, primarily using open source tools. - - - Network security implementation using iptables, snort - - Network security testing using nmap and nessus - - Web services infrastruture with apache, tomcat, perl, jboss - - Software development in C, C++, java, perl - - Databases including MySQL and PostgreSQL. - - Mail services with sendmaill, MailScanner, spamassassin and virus - scanners - - Windows file and print services with Samba - -Development, configuration and consultancy services at 600 -(pounds)/day. Fixed price negotiable. Managed administration and -monitoring negotiable. - -Updated: 2002-07-01 - -Andre Spiegel -Dipl.-Inform. -Berlin, Germany - -Maintainer of the GNU Emacs version control package (VC). - -I can provide consulting and practical help for the installation and -administration of GNU/Linux systems, in particular Debian. Also -knowledgeable on many other Unix derivates, and network technology. -Installation, porting and customization of GNU software is possible; I -have programming experience in C, C++, Java, and Emacs Lisp, among -others. Expertise in version control using RCS or CVS. I also give -seminars on the above subjects. - -Rates: 75 EUR/hr (US$ 70) - -Updated: 2002-04-22 - -Name: Julian Stacey -Location: Muenchen, Deutschland (Munich, Germany). -Qualifications: University Degree, BSc Hons Computers & Cybernetics, 1980. -Resume: http://bim.bsn.com/~jhs/stacey/ (includes phone number). -Rate: 80 - 100 Euros / Hour. -Specialisation: Unix (Pref. BSD or Linux), C, X-Windows, FSF tools, firewalls, - systems engineering, hardware interfacing, real time/embedded, - custom design & porting. No { Emacs, Cobol, Microsoft }. -Net Consulting: Link speed: DSL @ 768 K bit/s. -Free Sources: BSD, X-Windows, XFree86, FSF; Personal sources on web. -Free GCC-1.40: For Symmetric Computer Systems Model 375 (native cc is broken). -Languages: I am English. Ich verstehe Deutsch. Je comprend Francais, - (lentment!). Use Hoch Deutsch, not Bayerisch, Spell slowly - & clearly, Use single digits, no inverted digit pairs etc. -Contact: State aprox. amount of days/months you want to purchase - professional consultancy .. OR .. Note I am NOT a free help - desk ! Please post your questions to a newsgroup, for those - with more time, knowledge, & inclination than I. - -Updated: 2002-04-19 - -Richard M. Stallman -545 Tech Sq, Rm 425 -Cambridge, MA 02139 - -Emacs: anything whatever -Is anyone interested in courses in using or extending GNU Emacs? - -Original inventor of Emacs and main author of GNU Emacs and GCC. - -Rates: $6/min or $250/hr. - -Updated: 2002-04-19 - -Static Free Software -4119 Alpine Road -Portola Valley, Ca 94028 -(650) 851-2927 -http://www.staticfreesoft.com - -Static Free Software developed and supports the "Electric VLSI Design -System". Steven Rubin, the founder of the company and author of -Electric, is available for enhancements, support, and training. - -Please see our web page at www.staticfreesoft.com for more information -about our products, services, and prices. - -Updated: 2002-04-19 - -Tommy Stiansen -Skeielia 112 -5238 Raadal -Norway - -+ 47 92 40 42 00 -+ 47 55 22 12 17 -ts@pcias.no - -Special fields: -Unix, GNU/Linux, Perl installation, C, C++, Lisp, Perl programming. -CGI programming. -Installation, porting. -Specification development, design, implementation, documentation. -Firewalls, security analysis. Porting Windows platforms to GNU/Linux. -Teaching, preaching GNU/Linux / unix and Telecom. -15 years experience with GNU systems and tools. -Most useful for network design and construction or -dynamic web development. Expert in Apache, php, Mysql, Telecom related, -C, Lisp, Perl. - -Updated: 2002-04-18 - -Swing Digital Ltd. -15-17 Middle Street -Brighton -BN1 1AL -United Kingdom -Tel +44 (0) 1273 20 11 66 -Fax +44 (0) 1273 20 11 68 -http://www.swingdigital.com - -Swing Digital actively supports the development of the GNU.FREE -Internet Voting system. Through this support we have gained the -unique expertise to support, install and run GUN.FREE-based Internet -votes. We are also available in a consultancy basis to offer advice -for organisations wishing to run GNU.FREE themselves. - -Our consultancy fees start at 900 Euro (550 UK pounds) per day. We -are also able to securely host Internet Votes, prices on application. - -Updated: 2002-04-19 - -Kayvan A. Sylvan -Sylvan Associates, Inc. -879 Lewiston Drive -San Jose, CA 95136-1517 -Phone: (408) 978-1407 -Fax: (408) 978-0472 - -I will help you port, install and customize GNU Emacs, GCC, G++, GNUmake, -bison, and other GNU tools on almost any architecture and operating -system. Questions answered. GNU C/C++, Java and lisp hacking available. - -I will also do ongoing support and periodic upgrades if you get on my GNU -software subscription list. - -Rates: $100-$125/hour, depending on type and quantity of work. -Substantial discounts for long-term contracts and also for educational or -non-profit institutions. - -Experience: Many different Unix systems (2.9BSD to 4.4BSD, Xenix, SVR3 and -SVR4, Solaris, Linux, FreeBSD). Systems programming and system -administration on all brands of Unix. - -Kernel hacking experience. Lots of porting experience. - -Updated: 2002-04-18 - -Alfredo Tomasini -, - -GNU/Linux Intel desktop/laptop installation, setup, and networking. -Installation of GNU tools on SunOS and GNU/Linux. -Sed and Gawk script development. - -Languages: English and Italian. - -Fee: $50/hour. - -Updated: 2002-04-19 - -Tksoft Inc. -Papinkatu 19 -06100, Porvoo -Finland -+358 40 570 9900 - -http://www.tksoft.com/ - -Software development services for GNU programs. -We can modify and fix GNU software. -We will also develop new software under the GNU license. - -10 years of experience in linux and other GNU software. - -We speak Finnish, Japanese and English. - -Updated: 2004-05-13 - -Leonard H. Tower Jr. -36 Porter Street -Somerville, MA 02143-2313 -USA -+1-617-623-7739 - -Will work on most GNU, GPLed, and Open Source software. -Installation, handholding, trouble shooting, extensions, teaching, etc. - -Rates: $ 250.00/hour + travel + expenses. Fixed fee quotes available. - Negotiable for non-profits. - -Experience: Have hacked on over a dozen architectures in many languages. Have -system mothered too many varieties of Unixes. Assisted rms with the front end -of GCC and its back-end support. Installed and worked with many GNU -programs including GNU Emacs. Resume available on request. - -Updated: 2002-04-18 - -Xetpoint Oy -P.O. Box 43, FIN-33961 Pirkkala, Finland - -Email: -Web: http://www.xetpoint.fi/ - -Services: -- GNU/Linux system installation, configuration and maintenance -- GNU/Linux system administration -- GNU/Linux consultation and support -- GNU/Linux and free software customization -- Network administration -- Free software development and integration -- Training -- Security analysis - -Rates: 80 EUR/hour or fixed contract. - -Updated: 2004-02-13 - -Wasabi Systems - -500 E. Main St., Suite 1520 -Norfolk, VA 23510 -+1 757 248-9601 voice -+1 509 461-7283 fax -http://www.wasabisystems.com/ - -Wasabi Systems provides service and support for the popular GNU -development tools, as service packages and as stand-alone software -distributions. We provide cross-compilers and cross-debuggers to be -used for developing all types of embedded systems. We specialize in -optimizing the GNU tools for particular targets, and in providing -support for standardized tools to be used on multiple types of hosts -for multiple types of targets. We provide first- and/or second- tier -support for you and/or your end-users. - -Support is available in a variety of packages, with a base rate of -$200/hour. - -Updated: 2004-03-02 - -Jody Winston -xprt Computer Consulting, Inc. -731 Voyager -Houston, TX, 77062 -(281) 480-UNIX, - -We have supported, installed, and used the entire GNU software suite -for over 10 years on many different Unix platforms. We have written -character device drivers and proc file systems for custom hardware -running on GNU/Linux. We have developed extensions for tcl and Python. -In addition, we have developed a custom X11 server and X input -extensions. Our consulting rate is $150.00 US dollars per hour, -negotiable, plus a per diem for out of town work. - -Updated: 2002-04-19 - -The Written Word -Web: http://thewrittenword.com -Email: info@thewrittenword.com -Tel: (800) 372-7476 - -The Written Word provides CDs of pre-compiled Open Source applications -on popular UNIX variants. Clients can purchase a one-time CD set -($149/set), or a subscription, which provides four quarterly releases. -Two types of subscription are available: "media only" ($550/year), or -"media and updates" ($1459/year). The "media and updates" -subscription entitles the subscriber, via a web site, to patches, -security fixes, new releases to existing packages, new packages, -online documentation, and changelog information, between releases, and -a central bug tracking system for all packages. - -Updated: 2000-11-27 - - -For a current copy of this directory, or to have yourself listed, ask: - service@gnu.org - -A current version should be available on our web site at: - http://www.gnu.org/prep/service.html - -** Please keep the entries in this file alphabetical ** diff -r 7edc33019aa4 -r b7b90f750a78 etc/TERMS --- a/etc/TERMS Mon Jan 31 20:01:50 2005 +0000 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000 @@ -1,229 +0,0 @@ -This file describes what you must or might want to do to termcap entries -to make terminals work properly and efficiently with Emacs. Information -on likely problems with specific types of terminals appears at the end -of the file. - -*** What you want in a terminal *** - -Vital -1. Easy to compute suitable padding for. -2. Never ever sends ^S/^Q unless you type them, at least in one mode. - -Nice for speed -1. Supports insert/delete of multiple lines in one command. -2. Same for multiple characters, though doing them one by -one is usually fast enough except on emulators running on -machines with bitmap screens. - -Nice for usability -1. Considerably more than 24 lines. -2. Meta key (shift-like key that controls the 0200 bit -in every character you type). - -*** New termcap strings *** - -Emacs supports certain termcap strings that are not described in the -4.2 manual but appear to be standard in system V. The one exception -is `cS', which I invented. - -`AL' insert several lines. Takes one parameter, the number of - lines to be inserted. You specify how to send this parameter - using a %-construct, just like the cursor positions in the `cm' - string. - -`DL' delete several lines. One parameter. - -`IC' insert several characters. One parameter. - -`DC' delete several characters. One parameter. - -`rp' repeat a character. Takes two parameters, the character - to be repeated and the number of times to repeat it. - Most likely you will use `%.' for sending the character - to be repeated. Emacs interprets a padding spec with a * - as giving the amount of padding per repetition. - - WARNING: Many terminals have a command to repeat the - *last character output* N times. This means that the character - will appear N+1 times in a row when the command argument is N. - However, the `rp' string's parameter is the total number of - times wanted, not one less. Therefore, such repeat commands - may be used in an `rp' string only if you use Emacs's special - termcap operator `%a-c\001' to subtract 1 from the repeat count - before substituting it into the string. It is probably safe - to use this even though the Unix termcap does not accept it - because programs other than Emacs probably won't look for `rp' - anyway. - -`cs' set scroll region. Takes two parameters, the vertical - positions of the first line to include in the scroll region - and the last line to include in the scroll region. - Both parameters are origin-zero. The effect of this - should be to cause a following insert-line or delete-line - not to move lines below the bottom of the scroll region. - - This is not the same convention that Emacs version 16 used. - That is because I was led astray by unclear documentation - of the meaning of %i in termcap strings. Since the termcap - documentation for `cs' is also unclear, I had to deduce the - correct parameter conventions from what would make the VT-100's - `cs' string work properly. From an incorrect assumption about - %i, I reached an incorrect conclusion about `cs', but the result - worked correctly on the VT100 and ANSII terminals. In Emacs - version 17, both `cs' and %i work correctly. - - The version 16 convention was to pass, for the second parameter, - the line number of the first line beyond the end of the - scroll region. - -`cS' set scroll region. Differs from `cs' in taking parameters - differently. There are four parameters: - 1. Total number of lines on the screen. - 2. Number of lines above desired scroll region. - 3. Number of lines below (outside of) desired scroll region. - 4. Total number of lines on the screen, like #1. - This is because an Ambassador needs the parameters like this. - -`cr', `do', `le' - Emacs will not attempt to use ^M, ^J or ^H for cursor motion - unless these capabilities are present and say to use those - characters. - -`km' Says the terminal has a Meta key. - -Defining these strings is important for getting maximum performance -from your terminal. - -Make sure that the `ti' string sets all modes needed for editing -in Emacs. For example, if your terminal has a mode that controls -wrap at the end of the line, you must decide whether to specify -the `am' flag in the termcap entry; whichever you decide, the `ti' -string should contain commands to set the mode that way. -(Emacs also sends the `vs' string after the `ti' string. -You can put the mode-setting commands in either one of them.) - -*** Specific Terminal Types *** - -Watch out for termcap entries for Ann Arbor Ambassadors that -give too little padding for clear-screen. 7.2 msec per line is right. -These are the strings whose padding you probably should change: - :al=1*\E[L:dl=1*\E[M:cd=7.2*\E[J:cl=7.2*\E[H\E[J: -I have sometimes seen `\E[2J' at the front of the `ti' string; -this is a clear-screen, very slow, and it can cause you to get -Control-s sent by the terminal at startup. I recommend removing -the `\E[2J' from the `ti' string. -The `ti' or `vs' strings also usually need stuff added to them, such as - \E[>33;52;54h\E[>30;37;38;39l -You might want to add the following to the `te' or `ve' strings: - \E[>52l\E[>37h -The following additional capabilities will improve performance: - :AL=1*\E[%dL:DL=1*\E[%dM:IC=4\E[%d@:DC=4\E[%dP:rp=1*%.\E[%a-c\001%db: -If you find that the Meta key does not work, make sure that - :km: -is present in the termcap entry. - -Watch out for termcap entries for VT100's that fail to specify -the `sf' string, or that omit the padding needed for the `sf' and `sr' -strings (2msec per line affected). What you need is - :sf=2*^J:sr=2*\EM:cs=\E[%i%d;%dr: - -The Concept-100 and Concept-108 have many modes that `ti' strings -often fail to initialize. If you have problems on one of these -terminals, that is probably the place to fix them. These terminals -can support an `rp' string. - -Watch out on HP terminals for problems with standout disappearing on -part of the mode line. These problems are due to the absence of -:sg#0: which some HP terminals need. - -The vi55 is said to require `ip=2'. - -The Sun console should have these capabilities for good performance. - :AL=\E[%dL:DL=\E[%dM:IC=\E[%d@:DC=\E[%dP: - -The vt220 needs to be set to vt220 mode, 7 bit, space parity -in order to work fully with TERM=vt220. - -If you are using a LAT terminal concentrator, you need to issue these -commands to turn off flow control: - - set port flow control disable - define port flow control disable - -On System V, in the terminfo database, various terminals may have -the `xt' flag that should not have it. `xt' should be present only -for the Teleray 1061 or equivalent terminal. - -In particular, System V for the 386 often has `xt' for terminal type -AT386 or AT386-M, which is used for the console. You should delete -this flag. Here is how: - -You can get a copy of the terminfo "source" for at386 using the -command: `infocmp at386 >at386.tic'. Edit the file at386.tic and remove -the `xt' flag. Then compile the new entry with: `tic at386.tic'. - -It is also reported that these terminal types sometimes have the wrong -reverse-scroll string. It should be \E[T, but sometimes is given as \E[S. - -Here is what watserv1!maytag!focsys!larry recommends for these terminals: - -# This copy of the terminfo description has been fixed. -# The suggestions came from a number of usenet postings. -# -# Intel AT/386 for color card with monochrome display -# -AT386-M|at386-m|386AT-M|386at-m|at/386 console, - am, bw, eo, xon, - cols#80, lines#25, - acsc=``a1fxgqh0jYk?lZm@nEooppqDrrsstCu4vAwBx3yyzz{{||}}~~, - bel=^G, blink=\E[5m, bold=\E[1m, cbt=\E[Z, - clear=\E[2J\E[H, - cr=\r, cub=\E[%p1%dD, cub1=\E[D, cud=\E[%p1%dB, - cud1=\E[B, cuf=\E[%p1%dC, cuf1=\E[C, - cup=\E[%i%p1%02d;%p2%02dH, cuu=\E[%p1%dA, cuu1=\E[A, - dch=\E[%p1%dP, dch1=\E[P, dl=\E[%p1%dM, dl1=\E[1M, - ech=\E[%p1%dX,ed=\E[J, el=\E[K, el1=\E[1K\E[X, flash=^G, home=\E[H, - hpa=\E[%i%p1%dG, ich=\E[%p1%d@, ich1=\E[1@, il=\E[%p1%dL, il1=\E[1L, - ind=\E[S, indn=\E[%p1%dS, invis=\E[9m, - is2=\E[0;10;38m, kbs=\b, kcbt=^], kclr=\E[2J, - kcub1=\E[D, kcud1=\E[B, kcuf1=\E[C, kcuu1=\E[A, - kdch1=\E[P, kend=\E[Y, kf1=\EOP, kf10=\EOY, kf11=\EOZ, - kf12=\EOA, kf2=\EOQ, kf3=\EOR, kf4=\EOS, kf5=\EOT, - kf6=\EOU, kf7=\EOV, kf8=\EOW, kf9=\EOX, khome=\E[H, - kich1=\E[@, knp=\E[U, kpp=\E[V, krmir=\E0, rev=\E[7m, ri=\E[T, - rin=\E[%p1%dT, rmacs=\E[10m, rmso=\E[m, rmul=\E[m, - sgr=\E[10m\E[0%?%p1%p3%|%t;7%;%?%p2%t;4%;%?%p4%t;5%;%?%p6%t;1%;%?%p9%t;12%;%?%p7%t;9%;m, - sgr0=\E[0;10m, smacs=\E[12m, smso=\E[7m, smul=\E[4m, - -# -# AT&T 386 color console -# -AT386|at386|386AT|386at|at/386 console, - colors#8, ncv#3, pairs#64, - is2=\E[0;10;39m, - op=\E[0m, - setb=\E[%?%p1%{0}%=%t40m - %e%p1%{1}%=%t44m - %e%p1%{2}%=%t42m - %e%p1%{3}%=%t46m - %e%p1%{4}%=%t41m - %e%p1%{5}%=%t45m - %e%p1%{6}%=%t43m - %e%p1%{7}%=%t47m%;, - setf=\E[%?%p1%{0}%=%t30m - %e%p1%{1}%=%t34m - %e%p1%{2}%=%t32m - %e%p1%{3}%=%t36m - %e%p1%{4}%=%t31m - %e%p1%{5}%=%t35m - %e%p1%{6}%=%t33m - %e%p1%{6}%=%t33m - %e%p1%{7}%=%t37m%;, - use=at386-m, -# -# Color console version that supports underline but maps blue -# foreground color to cyan. -# -AT386-UL|at386-ul|386AT-UL|386at-ul|at/386 console, - is2=\E[0;10;38m, - use=at386, diff -r 7edc33019aa4 -r b7b90f750a78 etc/aliases.ksh --- a/etc/aliases.ksh Mon Jan 31 20:01:50 2005 +0000 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000 @@ -1,60 +0,0 @@ -### aliases.ksh --- Useful shortcuts for XEmacs source hackers - -# Copyright (C) 1998 Free Software Foundation, Inc. - -# Author: Steve Baur -# Keywords: internal - -# This file is part of XEmacs. - -# XEmacs is free software; you can redistribute it and/or modify it -# under the terms of the GNU General Public License as published by -# the Free Software Foundation; either version 2, or (at your option) -# any later version. - -# XEmacs is distributed in the hope that it will be useful, but -# WITHOUT ANY WARRANTY; without even the implied warranty of -# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU -# General Public License for more details. - -# You should have received a copy of the GNU General Public License -# along with XEmacs; see the file COPYING. If not, write to -# the Free Software Foundation, Inc., 59 Temple Place - Suite 330, -# Boston, MA 02111-1307, USA. - -# Shortcuts for sh-derived Unix shells (ksh, zsh, bash) - -# From Steve Baur -# Run temacs as XEmacs -function runtemacs -{ - if [ ! -x temacs ]; then - echo "Must be in temacs source directory to run temacs." - return 1; - fi - - ./temacs -batch -l loadup.el run-temacs "$@" -} - -# From Adrian Aichner -# Convenience function for running build-report -function mak -{ - make "$@" 2>&1 | tee beta.err -} -# export -f mak - -# From Karl Hegbloom -# igrep from the shell command line -function listargs -{ - for arg in "$@"; do - echo " \"$arg\"" - done -} - -function igrep -{ - exp="$1"; shift - gnudoit -q "(igrep nil \"$exp\" '($(listargs "$@")))" -} diff -r 7edc33019aa4 -r b7b90f750a78 etc/check_cygwin_setup.sh --- a/etc/check_cygwin_setup.sh Mon Jan 31 20:01:50 2005 +0000 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000 @@ -1,193 +0,0 @@ -#! bash - -yorn() -{ - echo -n " [y/n] " - read YN junk - if [ "$YN" = "n" ] - then - return -1; - else - return 0; - fi -} - -echo -n "checking for cygwin..." - -if ! uname -v -then - echo "couldn't find uname please add cygwin to your path." - exit -1 -fi - -OSversion="`uname -v | sed 's/^\(.\).*$/\1/'`" - -shell=`type sh | sed 's/sh is //'` -distdir=`dirname $shell | sed 's!^//\(.\)/\(.*\)!\1:/\2!'` - -echo "cygwin installed in $distdir" - -echo "checking paths ..." - -if [ ! -d "/bin" ]; then - echo "You don't have a /bin directory. Would you like to mount cygwin as /bin ?" - if yorn; then - mkdir /bin - mount -b $distdir /bin - fi -#this appears bogus. --ben -#elif [ "$distdir" != "/bin" ]; then -# echo "Warning: you have /bin but it's not the cygwin installation." -fi - -if [ ! -d "/tmp" ]; then - echo -n "You don't have /tmp - create it?" - if yorn; then - mkdir /tmp - fi -else - echo "you have /tmp" -fi - -if [ ! -d "/etc" ]; then - echo -n "You don't have /etc - create it?" - if yorn; then - mkdir /etc - fi -else - echo "you have /etc" -fi - -if [ -d "/etc" ] -then - if [ ! -f "/etc/termcap" ]; then - echo -n "You don't have /etc/termcap - create it?" - if yorn; then - if [ ! -f "$distdir/../etc/termcap" ] - then - distdir=`mount | grep "$distdir" | sed -e "s/ .*$//"` - echo "Retrieving termcap from $distdir/../etc" - fi - if [ -f "$distdir/../etc/termcap" ] - then - cp "$distdir/../etc/termcap" /etc - else - echo "Error: can't find termcap file" - fi - fi - else - echo "you have /etc/termcap" - fi - - if [ ! -f "/etc/passwd" ]; then - echo -n "You don't have /etc/passwd - create it?" - if yorn; then - if [ "$OS" = "Windows_NT" ] - then - echo -n "Running on NT, create domain or local password file [d/l] " - read DL junk - if [ "$DL" = "d" ] - then - mkpasswd -d > /etc/passwd - else - mkpasswd -l > /etc/passwd - fi - else - echo "Please enter your userid e.g. andyp" - read userid junk - echo "Please enter your user name e.g. Andy Piper" - read username junk - echo "Administrator::500:513:::/bin/sh" > /etc/passwd - echo "$userid::1000:513:$username::/bin/sh" >> /etc/passwd - fi - fi - else - echo "you have /etc/passwd" - userid=`id | sed -e "s/[^(]*(\([^)]*\)).*/\1/"` - fi - - echo "userid is $userid" - - if [ ! -f "/etc/group" ]; then - echo -n "You don't have /etc/group - create it?" - if yorn; then - if [ "$OS" = "Windows_NT" ] - then - echo -n "Running on NT, create domain or local group file [d/l] " - read DL junk - if [ "$DL" = "d" ] - then - mkgroup -d > /etc/group - else - mkgroup -l > /etc/group - fi - else - echo "None::513:" > /etc/group - echo "Everyone::0:" >> /etc/group - fi - fi - else - echo "you have /etc/group" - fi - -# this is bogus. i have no hosts file and no problems. --ben -# if [ ! -f "/etc/hosts" ]; then -# echo -n "You don't have /etc/hosts - create it?" -# if yorn; then -# mname=`uname -n` -# echo "Machine name is $mname" -# echo -n "Please enter your ip address " -# read mipaddr junk -# echo "$mname $mipaddr" > /etc/hosts -# echo "localhost 127.0.0.1" >> /etc/hosts -# fi -# else -# echo "you have /etc/hosts" -# fi -else - echo "Can't create /etc files because /etc does not exist" -fi - -echo "checking environment ..." - -if [ "$HOME" = "" ]; then - echo -n "HOME is not set, rectify?" - if yorn; then - if [ "$OS" = "Windows_NT" ] - then - echo "please enter your home path [/winnt/profiles/$userid]" - read HOME junk - if [ "$HOME" = "" ]; then - HOME="/winnt/profiles/$userid" - fi - else - echo "please enter your home path [/]" - read HOME junk - if [ "$HOME" = "" ]; then - HOME="/" - fi - fi - - echo "HOME=$HOME; export HOME" >> $HOME/.bashrc - fi -else - echo "HOME is $HOME" -fi - -if [ "$TERM" != "ansi" -a "$TERM" != "linux" ]; then - echo -n "TERM is not set to linux or ansi, rectify?" - if yorn; then - echo "TERM=linux; export TERM" >> $HOME/.bashrc - fi -else - echo "TERM is $TERM" -fi - -if echo $CYGWIN | grep -w tty > /dev/null; then - echo "CYGWIN is $CYGWIN" -else - echo "CYGWIN does not contain \"tty\"; you may experience problems with -subprocess or terminal handling. To rectify this add CYGWIN=tty to -your environment. (Note this cannot be done in bash as it needs to be -read when cygwin1.dll initializes.)" -fi diff -r 7edc33019aa4 -r b7b90f750a78 etc/chr.png Binary file etc/chr.png has changed diff -r 7edc33019aa4 -r b7b90f750a78 etc/chrm.png Binary file etc/chrm.png has changed diff -r 7edc33019aa4 -r b7b90f750a78 etc/gnu.xbm --- a/etc/gnu.xbm Mon Jan 31 20:01:50 2005 +0000 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000 @@ -1,33 +0,0 @@ -#define gnu_width 50 -#define gnu_height 50 -static unsigned char gnu_bits[] = { - 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, - 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xef, 0xff, 0xff, 0xff, 0xff, 0xff, - 0xff, 0x9f, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0x1f, 0xfe, 0xff, 0xff, - 0xff, 0xff, 0xff, 0x7f, 0xfc, 0xff, 0xff, 0xf7, 0xff, 0xff, 0xff, 0xf1, - 0xff, 0xff, 0xf3, 0xff, 0x8f, 0xff, 0xe1, 0xff, 0xff, 0xf9, 0x3f, 0x22, - 0xfe, 0xcb, 0xff, 0xff, 0xf8, 0xc3, 0xf8, 0xfc, 0xcb, 0xff, 0x7f, 0xfc, - 0xe0, 0xf9, 0xf9, 0xdb, 0xff, 0x7f, 0xfc, 0xf0, 0xfb, 0xf3, 0xd9, 0xff, - 0x3f, 0x7e, 0xf8, 0xff, 0xf7, 0xcc, 0xff, 0x9f, 0x3e, 0x1c, 0x7f, 0x44, - 0xce, 0xff, 0xcf, 0x1e, 0xcc, 0x01, 0x00, 0xe7, 0xff, 0xef, 0x0e, 0xce, - 0x38, 0x1c, 0xe0, 0xff, 0xef, 0x0e, 0x27, 0xfe, 0xfa, 0xc3, 0xff, 0xef, - 0x7c, 0x93, 0xff, 0xe5, 0xbf, 0xff, 0xef, 0x99, 0xc9, 0xab, 0x2a, 0x00, - 0xff, 0xcf, 0xc3, 0x24, 0x54, 0xc5, 0xd5, 0xff, 0x9f, 0x7f, 0x16, 0xab, - 0xca, 0xff, 0xff, 0x1f, 0x1f, 0x93, 0x46, 0x95, 0xff, 0xff, 0x7f, 0xc8, - 0x49, 0x99, 0x8a, 0xff, 0xff, 0xff, 0xf0, 0x49, 0x4b, 0x95, 0xff, 0xff, - 0xff, 0xf9, 0x4c, 0x88, 0x8a, 0xff, 0xff, 0xff, 0x1e, 0xe6, 0x58, 0x95, - 0xff, 0xff, 0x3f, 0x00, 0xe6, 0xb7, 0x0a, 0xff, 0xff, 0xbf, 0x8a, 0xea, - 0x50, 0x15, 0xff, 0xff, 0xff, 0x8f, 0xca, 0x99, 0x2a, 0xff, 0xff, 0xff, - 0xa7, 0x95, 0x7f, 0x15, 0xff, 0xff, 0xff, 0x23, 0x55, 0x7f, 0x2a, 0xfe, - 0xff, 0xff, 0x63, 0xd8, 0xfc, 0x14, 0xfe, 0xff, 0xff, 0x43, 0x9a, 0xfb, - 0x2b, 0xfe, 0xff, 0xff, 0xc3, 0xaa, 0x12, 0x94, 0xfc, 0xff, 0xff, 0xc1, - 0x32, 0xd5, 0xc1, 0xfd, 0xff, 0xff, 0x81, 0x46, 0xd5, 0x47, 0xfc, 0xff, - 0xff, 0x83, 0x6c, 0xc2, 0x6e, 0xfc, 0xff, 0xff, 0x83, 0x89, 0x88, 0x69, - 0xfe, 0xff, 0xff, 0x07, 0x92, 0x09, 0x3b, 0xfe, 0xff, 0xff, 0x07, 0x22, - 0x01, 0x3c, 0xfe, 0xff, 0xff, 0x0f, 0x4e, 0x02, 0x03, 0xfe, 0xff, 0xff, - 0x2f, 0xd0, 0x18, 0x3e, 0xff, 0xff, 0xff, 0x3f, 0xb0, 0x19, 0x9e, 0xff, - 0xff, 0xff, 0x7f, 0x00, 0x09, 0x80, 0xff, 0xff, 0xff, 0x7f, 0x01, 0xe3, - 0xc1, 0xff, 0xff, 0xff, 0xff, 0x05, 0xe0, 0xff, 0xff, 0xff, 0xff, 0xff, - 0x07, 0xf0, 0xff, 0xff, 0xff, 0xff, 0xff, 0x5f, 0xfd, 0xff, 0xff, 0xff, - 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, - 0xff, 0xff}; diff -r 7edc33019aa4 -r b7b90f750a78 etc/gnu.xpm --- a/etc/gnu.xpm Mon Jan 31 20:01:50 2005 +0000 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000 @@ -1,67 +0,0 @@ -/* XPM */ -/*****************************************************************************/ -/* GNU Emacs bitmap conv. to pixmap by Przemek Klosowski (przemek@nist.gov) */ -/*****************************************************************************/ -static char * image_name [] = { -/**/ -"50 50 7 1", -/**/ -" s mask c none", -"B c blue", -"x c black", -": c sandy brown", -"+ c saddle brown", -"' c grey", -". c white", -" ", -" ", -" x ", -" :x ", -" :::x ", -" ::x ", -" x ::x ", -" x: xxx :::x ", -" x: xxx xxx:xxx x::x ", -" x:: xxxx::xxx:::::xx x::x ", -" x:: x:::::::xx::::::xx x::x ", -" x:: xx::::::::x:::::::xx xx::x ", -" x:: xx::::::::::::::::::x xx::xx ", -" x::x xx:::::xxx:::::::xxx:xxx xx:::xx ", -" x:::x xx:::::xx...xxxxxxxxxxxxxxx:::xx ", -" x:::x xx::::::xx..xxx...xxxx...xxxxxxxx ", -" x:::x x::::::xx.xxx.......x.x.......xxxx ", -" x:::xx x:::x::xx.xx..........x.xx.........x ", -" x::::xx::xx:::x.xx....''''x'x'x''.xxx.....x ", -" xx::::xxxx::xx.xx.xxxx.'''''''.xxx xxxx ", -" xx::::::::xx..x.xxx..'''''''''.xx ", -" xxx:::::xxx..xx.xx.xx.xxx.'''''.xx ", -" xxx::xx...xx.xx.BBBB..xx''''''xx ", -" xxxx.....xx.xxBB:BB.xx'''''''xx ", -" xx.....xx...x.BBBx.xxx''''''xx ", -" x....xxxx..xx...xxx''''''''''xx ", -" x..xxxxxx..x.......x..''''''''xx ", -" x.x xxx.x.x.x...xxxx.'''''''''xx ", -" x xxx.x.x.xx...xx..'''''''''xx ", -" xx.x..x.x.xx........''''''''x ", -" xx'.xx.x.x.x.x.......'''''''''x ", -" xx'..xxxx..x...x.......'''''''x ", -" xx''.xx.x..xx...x.......'''.xxx ", -" xx''..x.x.x.x.x.xx.xxxxx.'.xx+xx ", -" xx''..x.xx..xx.x.x.x+++xxxxx+++x ", -" xx'''.x..xxx.x.x.x.x+++++xxx+xxx ", -" xx''.xx..x..xx.xxxx++x+++x++xxx ", -" xx''..xx.xxx.xxx.xxx++xx+x++xx ", -" xx'''.xx.xx..xx.xxxx++x+++xxx ", -" xx'''.xxx.xx.xxxxxxxxx++++xxx ", -" xx''...xx.xx.xxxxxx++xxxxxxx ", -" xx''''..x..xxx..xxxx+++++xx ", -" xx''''..x..xx..xxxx++++xx ", -" xxx'''''x.xx.xxxxxxxxxxx ", -" xxx'''''..xxx xxxxx ", -" xxxx''''xxxx ", -" xxx'''xxx ", -" xxxxx ", -" ", -" " -}; - diff -r 7edc33019aa4 -r b7b90f750a78 etc/ms-kermit --- a/etc/ms-kermit Mon Jan 31 20:01:50 2005 +0000 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000 @@ -1,167 +0,0 @@ -;;; This file is designed for an 8-bit connection. -;;; Use the file ms-kermit-7bit if you have a 7-bit connection. - -;; Meta key mappings for EMACS -;; By Robert Earl (rearl@watnxt3.ucr.edu) -;; May 13, 1990 -;; -;; WARNING: -;; requires an 8-bit path to host. many dialups and lans won't pass the -;; eighth bit by default and may require a special command to turn this -;; off. `screen' is known to mask the eighth bit of input as well. - -set term controls 8-bit -set translation key off - -;; control keys -set key \3449 \128 ;; m-c-@ -set key \3358 \129 ;; m-c-a -set key \3376 \130 ;; m-c-b -set key \3374 \131 ;; m-c-c -set key \3360 \132 ;; m-c-d -set key \3346 \133 ;; m-c-e -set key \3361 \134 ;; m-c-f -set key \3362 \135 ;; m-c-g -set key \3342 \136 ;; m-bs -set key \3363 \136 ;; m-c-h (sends same code as above) -set key \2469 \137 ;; m-tab -set key \3351 \137 ;; m-c-i (same as above) -set key \3364 \138 ;; m-c-j -set key \3365 \139 ;; m-c-k -set key \3366 \140 ;; m-c-l -;set key \3378 \141 ;; m-c-m -set key \2332 \141 ;; m-ret (sends same code as above) -set key \3377 \142 ;; m-c-n -set key \3352 \143 ;; m-c-o -set key \3353 \144 ;; m-c-p -set key \3344 \145 ;; m-c-q -set key \3347 \146 ;; m-c-r -set key \3359 \147 ;; m-c-s -set key \3348 \148 ;; m-c-t -set key \3350 \149 ;; m-c-u -set key \3375 \150 ;; m-c-v -set key \3345 \151 ;; m-c-w -set key \3373 \152 ;; m-c-x -set key \3349 \153 ;; m-c-y -set key \3372 \154 ;; m-c-z - -;; misc keys -;set key \3354 \155 ;; m-c-[ -set key \2305 \155 ;; m-esc (sends same as above) -set key \3371 \156 ;; m-c-\ -set key \3355 \157 ;; m-c-] -set key \3453 \158 ;; m-c-^ -set key \3458 \159 ;; m-c-_ - -;; \160 is conspicuously missing here-- -;; alt-spc doesn't generate a distinct scan code... -;; neither do shift-spc and ctrl-spc. -;; no idea why. - -set key \2936 \161 ;; m-! -set key \2856 \162 ;; m-" -set key \2938 \163 ;; m-# -set key \2939 \164 ;; m-$ -set key \2940 \165 ;; m-% -set key \2942 \166 ;; m-& -set key \2344 \167 ;; m-' -set key \2944 \168 ;; m-( -set key \2945 \169 ;; m-) -set key \2943 \170 ;; m-* -set key \2947 \171 ;; m-+ -set key \2355 \172 ;; m-, -set key \2434 \173 ;; m-- -set key \2356 \174 ;; m-. -set key \2357 \175 ;; m-/ - -;; number keys -set key \2433 \176 ;; m-0 -set key \2424 \177 ;; m-1 -set key \2425 \178 -set key \2426 \179 -set key \2427 \180 -set key \2428 \181 -set key \2429 \182 -set key \2430 \183 -set key \2431 \184 -set key \2432 \185 ;; m-9 - -set key \2855 \186 ;; m-: -set key \2343 \187 ;; m-; -set key \2867 \188 ;; m-< -set key \2435 \189 ;; m-= -set key \2868 \190 ;; m-> -set key \2869 \191 ;; m-? -set key \2937 \192 ;; m-@ - -;; shifted A-Z -set key \2846 \193 ;; m-A -set key \2864 \194 -set key \2862 \195 -set key \2848 \196 -set key \2834 \197 -set key \2849 \198 -set key \2850 \199 -set key \2851 \200 -set key \2839 \201 -set key \2852 \202 -set key \2853 \203 -set key \2854 \204 -set key \2866 \205 -set key \2865 \206 -set key \2840 \207 -set key \2841 \208 -set key \2832 \209 -set key \2835 \210 -set key \2847 \211 -set key \2836 \212 -set key \2838 \213 -set key \2863 \214 -set key \2833 \215 -set key \2861 \216 -set key \2837 \217 -set key \2860 \218 ;; m-Z - -set key \2330 \219 ;; m-[ -set key \2347 \220 ;; m-\ -set key \2331 \221 ;; m-] -set key \2941 \222 ;; m-^ -set key \2946 \223 ;; m-_ -set key \2345 \224 ;; m-` - -;; lowercase a-z -set key \2334 \225 ;; m-a -set key \2352 \226 -set key \2350 \227 -set key \2336 \228 -set key \2322 \229 -set key \2337 \230 -set key \2338 \231 -set key \2339 \232 -set key \2327 \233 -set key \2340 \234 -set key \2341 \235 -set key \2342 \236 -set key \2354 \237 -set key \2353 \238 -set key \2328 \239 -set key \2329 \240 -set key \2320 \241 -set key \2323 \242 -set key \2335 \243 -set key \2324 \244 -set key \2326 \245 -set key \2351 \246 -set key \2321 \247 -set key \2349 \248 -set key \2325 \249 -set key \2348 \250 ;; m-z - -;; more shifted misc. keys -set key \2842 \251 ;; m-{ -set key \2859 \252 ;; m-| -set key \2843 \253 ;; m-} -set key \2857 \254 ;; m-~ -set key \2318 \255 ;; m-del - - diff -r 7edc33019aa4 -r b7b90f750a78 etc/ms-kermit-7bit --- a/etc/ms-kermit-7bit Mon Jan 31 20:01:50 2005 +0000 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000 @@ -1,312 +0,0 @@ -;;; This file is designed for 7-bit connections. -;;; Use the file ms-kermit if you have an 8-bit connection. - -;;; This kermit script maps the IBM-PC keyboard for use with Gnu Emacs. -;;; The ALT key is used to generate Meta characters and, in conjunction -;;; with the CTRL key, Control-Meta characters. A few other useful -;;; mappings are also performed. -;;; Andy Lowry, May 1989 - -;;; Exchange ESC and backquote... tilde stays put (shift-backquote) -set key \27 ` -set key ` \27 - -;;; BACKSPACE deletes backward one character -set key scan \270 \127 - -;;; The following mappings affect certain special keys... all the keys -;;; are duplicated on the numeric keypad when NUM LOCK is off, but -;;; the keypad versions are NOT mapped (string definition space too small -;;; for that) - -;;; INSERT toggles overwrite mode -set key scan \4434 \27xoverwrite-mode\13 -;;; HOME moves point to beginning of buffer -set key scan \4423 \27< -;;; PAGE-UP scrolls backward one screen -set key scan \4425 \27v -;;; DELETE deletes one character *forward* -set key scan \4435 \4 -;;; END moves point to end of buffer -set key scan \4431 \27> -;;; PAGE-DOWN scrolls forward one screen -set key scan \4433 \22 -;;; ARROW keys move in the appropriate directions -set key scan \4424 \16 -set key scan \4427 \2 -set key scan \4432 \14 -set key scan \4429 \6 - -;;; META versions of all the printing characters except uppercase -;;; letters are generated by using the ALT key. The definition string -;;; consists of an ESC character followed by the META-ized character. -;;; The characters are listed roughly left-to-right and top-to-bottom -;;; as they appear on the keyboard -set key scan \2345 \27` -set key scan \2424 \27\o61 ; need to use char code, since digit -set key scan \2425 \27\o62 ; would not terminate '\27' -set key scan \2426 \27\o63 -set key scan \2427 \27\o64 -set key scan \2428 \27\o65 -set key scan \2429 \27\o66 -set key scan \2430 \27\o67 -set key scan \2431 \27\o70 -set key scan \2432 \27\o71 -set key scan \2433 \27\o60 -set key scan \2434 \27\45 -set key scan \2435 \27= -set key scan \2857 \27~ -set key scan \2936 \27! -set key scan \2937 \27@ -set key scan \2938 \27# -set key scan \2939 \27$ -set key scan \2940 \27% -set key scan \2941 \27^ -set key scan \2942 \27& -set key scan \2943 \27* -set key scan \2944 \27( -set key scan \2945 \27) -set key scan \2946 \27_ -set key scan \2947 \27+ -set key scan \2469 \27\9 -set key scan \2320 \27q -set key scan \2321 \27w -set key scan \2322 \27e -set key scan \2323 \27r -set key scan \2324 \27t -set key scan \2325 \27y -set key scan \2326 \27u -set key scan \2327 \27i -set key scan \2328 \27o -set key scan \2329 \27p -set key scan \2330 \27[ -set key scan \2842 \27{ -set key scan \2331 \27] -set key scan \2843 \27} -set key scan \2347 \27\ -set key scan \2859 \27| -set key scan \2334 \27a -set key scan \2335 \27s -set key scan \2336 \27d -set key scan \2337 \27f -set key scan \2338 \27g -set key scan \2339 \27h -set key scan \2340 \27j -set key scan \2341 \27k -set key scan \2342 \27l -set key scan \2343 \27\59 -set key scan \2855 \27: -set key scan \2344 \27' -set key scan \2856 \27" -set key scan \2348 \27z -set key scan \2349 \27x -set key scan \2350 \27c -set key scan \2351 \27v -set key scan \2352 \27b -set key scan \2353 \27n -set key scan \2354 \27m -set key scan \2355 \27, -set key scan \2867 \27< -set key scan \2356 \27. -set key scan \2868 \27> -set key scan \2357 \27/ -set key scan \2869 \27? - -;;; CONTROL-META characters are generated by using both the CTRL and -;;; ALT keys simultaneously. All the lowercase letters are included. -;;; The definition string consists of an ESC character followed by -;;; the control character corresponding to the letter. -set key scan \3344 \27\17 -set key scan \3345 \27\23 -set key scan \3346 \27\5 -set key scan \3347 \27\18 -set key scan \3348 \27\20 -set key scan \3349 \27\25 -set key scan \3350 \27\21 -set key scan \3351 \27\9 -set key scan \3352 \27\15 -set key scan \3353 \27\16 -set key scan \3358 \27\1 -set key scan \3359 \27\19 -set key scan \3360 \27\4 -set key scan \3361 \27\6 -set key scan \3362 \27\7 -set key scan \3363 \27\8 -set key scan \3364 \27\10 -set key scan \3365 \27\11 -set key scan \3366 \27\12 -set key scan \3372 \27\26 -set key scan \3373 \27\24 -set key scan \3374 \27\3 -set key scan \3375 \27\22 -set key scan \3376 \27\2 -set key scan \3377 \27\14 -set key scan \3378 \27\13 - -end of msiem2.ini ------------------- - -msiema.hlp ------------ -Date: Wed, 14 Sep 88 05:20:08 GMT -From: spolsky@YALE.ARPA -Subject: Using MS kermit 2.31 with emacs -Keywords: MS-DOS Kermit 2.31, EMACS, Meta Key - -If you are using kermit (version 2.31 only) with emacs on a mainframe, the -following file may help you. It assigns all the Alt-keys so that the Alt key -may be used as a "Meta" shift, e.g. Alt-x produces M-x, etc. Note that it -will distinguish correctly between upper and lower case and accepts all -printables. (If anybody has the patience to do the Meta-Ctrl combinations, -please post them!) This actually sends "escapes" so you don't need 8 bits. -This file also sets up the cursor keys to behave as expected. - -On extended keyboards (the ones with a separate cursor pad, like PS/2s) you -also get assignments for Page Up/Down, Home, End, Insert, Delete, etc. - -Please let me know if you find any problems with this. - -Joel Spolsky bitnet: spolsky@yalecs uucp: ...!yale!spolsky -Yale University arpa: spolsky@yale.edu voicenet: 203-436-1483 - -[Ed. - Thanks, Joel! Your key definitions file has been put in the kermit -distribution area as msiema.ini ("ms" for MS-Kermit, "i" because it's an -initialization file, "ema" for EMACS), along with this message as msiema.hlp.] - -end of msiema.hlp ------------------ - - -msiema.ini ------------- -; Emacs keyboard layout for Kermit 2.31 -; by Joel Spolsky, Yale Univ. Save this in a file, then -; initialize it by issuing the kermit command -; take filename -; It will set up the keyboard to allow ALT to be used -; as a meta-key, and will allow cursor keys to be used -; with emacs. - -; First, define all the ALT keys to send ESC+key -; to simulate "meta" - -set key \2320 \27q ;; letters: unshifted -set key \2321 \27w -set key \2322 \27e -set key \2323 \27r -set key \2324 \27t -set key \2325 \27y -set key \2326 \27u -set key \2327 \27i -set key \2328 \27o -set key \2329 \27p -set key \2334 \27a -set key \2335 \27s -set key \2336 \27d -set key \2337 \27f -set key \2338 \27g -set key \2339 \27h -set key \2340 \27j -set key \2341 \27k -set key \2342 \27l -set key \2348 \27z -set key \2349 \27x -set key \2350 \27c -set key \2351 \27v -set key \2352 \27b -set key \2353 \27n -set key \2354 \27m -set key \2832 \27Q ;; letters: shifted -set key \2833 \27W -set key \2834 \27E -set key \2835 \27R -set key \2836 \27T -set key \2837 \27Y -set key \2838 \27U -set key \2839 \27I -set key \2840 \27O -set key \2841 \27P -set key \2846 \27A -set key \2847 \27S -set key \2848 \27D -set key \2849 \27F -set key \2850 \27G -set key \2851 \27H -set key \2852 \27J -set key \2853 \27K -set key \2854 \27L -set key \2860 \27Z -set key \2861 \27X -set key \2862 \27C -set key \2863 \27V -set key \2864 \27B -set key \2865 \27N -set key \2866 \27M -set key \2857 \27\126 ; ALT + ~ ;; special symbols begin here -set key \2345 \27\96 ; ALT + ` -set key \2936 \27\33 ; ALT + ! -set key \2937 \27\64 ; ALT + @ -set key \2938 \27\35 ; ALT + # -set key \2939 \27\36 ; ALT + $ -set key \2940 \27\37 ; ALT + % -set key \2941 \27\94 ; ALT + ^ -set key \2942 \27\38 ; ALT + & -set key \2943 \27\42 ; ALT + * -set key \2944 \27\40 ; ALT + ( -set key \2945 \27\41 ; ALT + ) -set key \2946 \27\95 ; ALT + _ -set key \2947 \27\43 ; ALT + + -set key \2842 \27\123 ; ALT + { -set key \2843 \27\125 ; ALT + } -set key \2330 \27\91 ; ALT + [ -set key \2331 \27\93 ; ALT + ] -set key \2859 \27\124 ; ALT + : -set key \2347 \27\92 ; ALT + \ -set key \2867 \27< ; ALT + < -set key \2868 \27> ; ALT + > -set key \2343 \27\59 ; ALT + ; -set key \2855 \27\58 ; ALT + : -set key \2344 \27\39 ; ALT + ' -set key \2856 \27\34 ; ALT + " -set key \2355 \27\44 ; ALT + , -set key \2356 \27\46 ; ALT + . -set key \2357 \27\47 ; ALT + / -set key \2869 \27\63 ; ALT + ? -set key \2424 \27\49 ;; numbers -set key \2425 \27\50 -set key \2426 \27\51 -set key \2427 \27\52 -set key \2428 \27\53 -set key \2429 \27\54 -set key \2430 \27\55 -set key \2431 \27\56 -set key \2432 \27\57 -set key \2433 \27\48 - -;; These 6 special keys for extended (PS/2) keyboards: -set key \4434 \25 ;; Insert is like ^Y - yank from kill ring -set key \4435 \23 ;; Delete is like ^W - kill to ring -set key \4423 \1 ;; Home is ^A -set key \4431 \5 ;; End is ^E -set key \4425 \27V ;; Page up is Esc-V -set key \4433 \22 ;; Page dn is ^v - -set key \328 \16 ;; up cursor is ^P -set key \331 \2 ;; left cursor is ^B -set key \333 \6 ;; right cursor is ^F -set key \336 \14 ;; down cursor is ^N -set key \4427 \2 ;; left cursor on extended kbd -set key \4432 \14 ;; down cursor on extended kbd -set key \4424 \16 ;; up cursor on extended kbd -set key \4429 \6 ;; right cursor on extended kbd - -set key \5491 \27b ;; ctrl-left cursor is M-b -set key \5492 \27f ;; ctrl-right cursor is M-f - -;; move kermit's screen scroll (playback) features to Alt- Home,End,PgUp,PgDn -;; (this is an issue for extended keyboards only) - -set key \2455 \khomscn -set key \2463 \kendscn -set key \2457 \kupscn -set key \2465 \kdnscn diff -r 7edc33019aa4 -r b7b90f750a78 etc/sink.xbm --- a/etc/sink.xbm Mon Jan 31 20:01:50 2005 +0000 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000 @@ -1,33 +0,0 @@ -#define kitchen_sink_width 50 -#define kitchen_sink_height 50 -static unsigned char kitchen_sink_bits[] = { - 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, - 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x10, 0x00, 0x00, 0x00, 0x00, 0x00, - 0x00, 0x60, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0xe0, 0x01, 0x00, 0x00, - 0x00, 0x00, 0x00, 0x80, 0x03, 0x00, 0x00, 0x08, 0x00, 0x00, 0x00, 0x0e, - 0x00, 0x00, 0x0c, 0x00, 0x70, 0x00, 0x1e, 0x00, 0x00, 0x06, 0xc0, 0xdd, - 0x01, 0x34, 0x00, 0x00, 0x07, 0x3c, 0x07, 0x03, 0x34, 0x00, 0x80, 0x03, - 0x1f, 0x06, 0x06, 0x24, 0x00, 0x80, 0x03, 0x0f, 0x04, 0x0c, 0x26, 0x00, - 0xc0, 0x81, 0x07, 0x00, 0x08, 0x33, 0x00, 0x60, 0xc1, 0xe3, 0x80, 0xbb, - 0x31, 0x00, 0x30, 0xe1, 0x33, 0xfe, 0xff, 0x18, 0x00, 0x10, 0xf1, 0x31, - 0xc7, 0xe3, 0x1f, 0x00, 0x10, 0xf1, 0xd8, 0x01, 0x05, 0x3c, 0x00, 0x10, - 0x83, 0x6c, 0x00, 0x1a, 0x40, 0x00, 0x10, 0x66, 0x36, 0x54, 0xd5, 0xff, - 0x00, 0x30, 0x3c, 0xdb, 0xab, 0x3a, 0x2a, 0x00, 0x60, 0x80, 0xe9, 0x54, - 0x35, 0x00, 0x00, 0xe0, 0xe0, 0x6c, 0xb9, 0x6a, 0x00, 0x00, 0x80, 0x37, - 0xb6, 0x66, 0x75, 0x00, 0x00, 0x00, 0x0f, 0xb6, 0xb4, 0x6a, 0x00, 0x00, - 0x00, 0x06, 0xb3, 0x77, 0x75, 0x00, 0x00, 0x00, 0xe1, 0x19, 0xa7, 0x6a, - 0x00, 0x00, 0xc0, 0xff, 0x19, 0x48, 0xf5, 0x00, 0x00, 0x40, 0x75, 0x15, - 0xaf, 0xea, 0x00, 0x00, 0x00, 0x70, 0x35, 0x66, 0xd5, 0x00, 0x00, 0x00, - 0x58, 0x6a, 0x80, 0xea, 0x00, 0x00, 0x00, 0xdc, 0xaa, 0x80, 0xd5, 0x01, - 0x00, 0x00, 0x9c, 0x27, 0x03, 0xeb, 0x01, 0x00, 0x00, 0xbc, 0x65, 0x04, - 0xd4, 0x01, 0x00, 0x00, 0x3c, 0x55, 0xed, 0x6b, 0x03, 0x00, 0x00, 0x3e, - 0xcd, 0x2a, 0x3e, 0x02, 0x00, 0x00, 0x7e, 0xb9, 0x2a, 0xb8, 0x03, 0x00, - 0x00, 0x7c, 0x93, 0x3d, 0x91, 0x03, 0x00, 0x00, 0x7c, 0x76, 0x77, 0x96, - 0x01, 0x00, 0x00, 0xf8, 0x6d, 0xf6, 0xc4, 0x01, 0x00, 0x00, 0xf8, 0xdd, - 0xfe, 0xc3, 0x01, 0x00, 0x00, 0xf0, 0xb1, 0xfd, 0xfc, 0x01, 0x00, 0x00, - 0xd0, 0x2f, 0xe7, 0xc1, 0x00, 0x00, 0x00, 0xc0, 0x4f, 0xe6, 0x61, 0x00, - 0x00, 0x00, 0x80, 0xff, 0xf6, 0x7f, 0x00, 0x00, 0x00, 0x80, 0xfe, 0x1c, - 0x3e, 0x00, 0x00, 0x00, 0x00, 0xfa, 0x1f, 0x00, 0x00, 0x00, 0x00, 0x00, - 0xf8, 0x0f, 0x00, 0x00, 0x00, 0x00, 0x00, 0xa0, 0x02, 0x00, 0x00, 0x00, - 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, - 0x00, 0x00}; diff -r 7edc33019aa4 -r b7b90f750a78 lisp/ChangeLog --- a/lisp/ChangeLog Mon Jan 31 20:01:50 2005 +0000 +++ b/lisp/ChangeLog Mon Jan 31 20:08:52 2005 +0000 @@ -1,3 +1,10 @@ +2005-01-31 Ben Wing + + * help.el: + * help.el (describe-distribution): Go to appropriate FAQ entry. + * help.el (describe-beta): Go to info file. + * help.el (describe-project): Removed. + 2005-01-27 Ben Wing * font-menu.el: diff -r 7edc33019aa4 -r b7b90f750a78 lisp/help.el --- a/lisp/help.el Mon Jan 31 20:01:50 2005 +0000 +++ b/lisp/help.el Mon Jan 31 20:08:52 2005 +0000 @@ -1,7 +1,7 @@ ;;; help.el --- help commands for XEmacs. ;; Copyright (C) 1985, 1986, 1992-4, 1997 Free Software Foundation, Inc. -;; Copyright (C) 2001, 2002 Ben Wing. +;; Copyright (C) 2001, 2002, 2003 Ben Wing. ;; Maintainer: FSF ;; Keywords: help, internal, dumped @@ -696,12 +696,17 @@ (defun describe-distribution () "Display info on how to obtain the latest version of XEmacs." (interactive) - (Help-find-file (locate-data-file "DISTRIB"))) + (save-window-excursion + (info) + (Info-find-node "xemacs-faq" "Q1.1.1")) + (switch-to-buffer "*info*")) (defun describe-beta () "Display info on how to deal with Beta versions of XEmacs." (interactive) - (Help-find-file (locate-data-file "BETA"))) + (save-window-excursion + (info "(beta)Top")) + (switch-to-buffer "*info*")) (defun describe-copying () "Display info on how you may redistribute copies of XEmacs." @@ -713,11 +718,6 @@ (interactive) (describe-bindings nil t)) -(defun describe-project () - "Display info on the GNU project." - (interactive) - (Help-find-file (locate-data-file "GNU"))) - (defun describe-no-warranty () "Display info on all the kinds of warranty XEmacs does NOT have." (interactive) diff -r 7edc33019aa4 -r b7b90f750a78 man/ChangeLog --- a/man/ChangeLog Mon Jan 31 20:01:50 2005 +0000 +++ b/man/ChangeLog Mon Jan 31 20:08:52 2005 +0000 @@ -1,3 +1,112 @@ +2005-01-31 Ben Wing + + * xemacs/help.texi (Misc Help): + Delete references to DISTRIB. Point to FAQ. + + * xemacs/new.texi: + Update sample code for version checking. + + * xemacs/xemacs.texi (Distrib): + * xemacs/xemacs.texi (Intro): + Delete references to DISTRIB. Point directly to web site. + Update stuff referring to GNU Emacs. Delete references to Win-Emacs. + +2005-01-31 Ben Wing + + * Makefile: + * Makefile (info_files): + * Makefile (html_files): + * Makefile (dvi_files): + * Makefile (pdf_files): + * Makefile ($(INFODIR)/beta.info): + Add beta.texi and built files. + + * xemacs-faq.texi (Top): + * xemacs-faq.texi (Introduction): + * xemacs-faq.texi (Q1.0.3): + * xemacs-faq.texi (Q1.0.4): + * xemacs-faq.texi (Q1.0.5): + * xemacs-faq.texi (Q1.0.6): + * xemacs-faq.texi (Q1.1.1): + * xemacs-faq.texi (Q1.1.2): + * xemacs-faq.texi (Q1.1.3): + * xemacs-faq.texi (Q1.1.4): + * xemacs-faq.texi (Q1.2.1): + * xemacs-faq.texi (Q1.2.2): + * xemacs-faq.texi (Q1.2.3): + * xemacs-faq.texi (Q1.2.4): + * xemacs-faq.texi (Q1.2.5): + * xemacs-faq.texi (Q1.2.6): + * xemacs-faq.texi (Q1.2.7): + * xemacs-faq.texi (Q1.2.8): + * xemacs-faq.texi (Q1.2.9): + * xemacs-faq.texi (Q1.2.10): + * xemacs-faq.texi (Q1.2.11): + * xemacs-faq.texi (Q1.2.12): + * xemacs-faq.texi (Q1.2.13): + * xemacs-faq.texi (Q1.3.1): + * xemacs-faq.texi (Q1.3.2): + * xemacs-faq.texi (Q1.3.3): + * xemacs-faq.texi (Q1.3.4): + * xemacs-faq.texi (Q1.3.5): + * xemacs-faq.texi (Q1.3.6): + * xemacs-faq.texi (Q1.3.7): + * xemacs-faq.texi (Q1.3.8): + * xemacs-faq.texi (Q1.4.1): + * xemacs-faq.texi (Q1.4.2): + * xemacs-faq.texi (double-word): New. + * xemacs-faq.texi (Q1.4.3): + * xemacs-faq.texi (Q1.4.4): + * xemacs-faq.texi (Q1.4.5): + * xemacs-faq.texi (Q1.5.1): + * xemacs-faq.texi (Q1.5.2): + * xemacs-faq.texi (Q1.5.3): + * xemacs-faq.texi (Q1.6.1): + * xemacs-faq.texi (Q1.6.2): + * xemacs-faq.texi (Q1.6.3): + * xemacs-faq.texi (Q1.6.4): + * xemacs-faq.texi (Q1.6.5): + * xemacs-faq.texi (Q1.6.6): + * xemacs-faq.texi (Q1.7.1): + * xemacs-faq.texi (Q1.8.1): + * xemacs-faq.texi (Q1.8.2): + * xemacs-faq.texi (Q1.8.3): + * xemacs-faq.texi (Q1.8.4): + * xemacs-faq.texi (Q1.8.5): + * xemacs-faq.texi (Q1.8.6): + * xemacs-faq.texi (Q1.8.7): + * xemacs-faq.texi (Q1.8.8): + * xemacs-faq.texi (Q1.8.9): + * xemacs-faq.texi (Q2.2.1): + * xemacs-faq.texi (Q2.2.2): + * xemacs-faq.texi (Q2.4.2): + * xemacs-faq.texi (Advanced): + * xemacs-faq.texi (Q7.0.1): + * xemacs-faq.texi (Q7.0.2): + * xemacs-faq.texi (Q7.0.3): + * xemacs-faq.texi (Q7.0.4): + * xemacs-faq.texi (Q7.0.5): + * xemacs-faq.texi (Q7.0.6): + * xemacs-faq.texi (Q7.1.1): + * xemacs-faq.texi (Q7.1.2): + * xemacs-faq.texi (Q7.1.3): + * xemacs-faq.texi (Q7.1.4): + * xemacs-faq.texi (Q7.1.5): + * xemacs-faq.texi (Q7.1.6): + * xemacs-faq.texi (Q7.1.7): + * xemacs-faq.texi (Q7.1.8): + * xemacs-faq.texi (Q7.1.9): + * xemacs-faq.texi (Q7.1.10): + * xemacs-faq.texi (Q7.1.11): + * xemacs-faq.texi (Q7.2.1): + * xemacs-faq.texi (Q7.2.2): + * xemacs-faq.texi (Q7.2.3): + * xemacs-faq.texi (Other Packages): + * xemacs-faq.texi (Current Events): + * xemacs-faq.texi (Legacy Versions): + Major overhaul of section 1. Add mailing list info, update + downloading info, add info on CVS, etc. + 2004-10-17 Shyamal Prasad * xemacs/programs.texi (Program Modes): Updated it to reflect diff -r 7edc33019aa4 -r b7b90f750a78 man/Makefile --- a/man/Makefile Mon Jan 31 20:01:50 2005 +0000 +++ b/man/Makefile Mon Jan 31 20:08:52 2005 +0000 @@ -42,6 +42,7 @@ PHOTODIR = ../etc/photos info_files = \ + $(INFODIR)/beta.info \ $(INFODIR)/cl.info \ $(INFODIR)/custom.info \ $(INFODIR)/emodules.info \ @@ -59,6 +60,7 @@ $(INFODIR)/xemacs-faq.info html_files = \ + $(HTMLDIR)/beta.html \ $(HTMLDIR)/cl.html \ $(HTMLDIR)/custom.html \ $(HTMLDIR)/emodules.html \ @@ -76,6 +78,7 @@ $(HTMLDIR)/xemacs-faq.html dvi_files = \ + beta.dvi \ cl.dvi \ custom.dvi \ emodules.dvi \ @@ -93,6 +96,7 @@ xemacs-faq.dvi pdf_files = \ + beta.pdf \ cl.pdf \ custom.pdf \ emodules.pdf \ @@ -237,6 +241,9 @@ new-users-guide/search.texi \ new-users-guide/xmenu.texi +$(INFODIR)/beta.info : beta.texi + $(MAKEINFO) -o $(INFODIR)/beta.info beta.texi + $(INFODIR)/cl.info : cl.texi $(MAKEINFO) -o $(INFODIR)/cl.info cl.texi @@ -340,6 +347,9 @@ ############################################################################ +$(HTMLDIR)/beta.html : beta.texi + $(TEXI2HTML) beta.texi + $(HTMLDIR)/cl.html : cl.texi $(TEXI2HTML_SPLIT) cl.texi diff -r 7edc33019aa4 -r b7b90f750a78 man/beta.texi --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/man/beta.texi Mon Jan 31 20:08:52 2005 +0000 @@ -0,0 +1,946 @@ +\input texinfo @c -*-texinfo-*- + +@c %**start of header +@setfilename ../info/beta.info +@settitle Info on beta versions of XEmacs +@direntry +* Beta: (beta). Info on beta versions of XEmacs. +@end direntry +@c footnotestyle separate +@c paragraphindent 2 +@c %**end of header + +@ifinfo +This file describes info relevant to beta versions of XEmacs. + +Copyright @copyright{} 2005 Ben Wing. + +This file is part of XEmacs. + +XEmacs is free software; you can redistribute it and/or modify it +under the terms of the GNU General Public License as published by the +Free Software Foundation; either version 2, or (at your option) any +later version. + +XEmacs is distributed in the hope that it will be useful, but WITHOUT +ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or +FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License +for more details. + +You should have received a copy of the GNU General Public License +along with XEmacs; see the file COPYING. If not, write to +the Free Software Foundation, Inc., 59 Temple Place - Suite 330, +Boston, MA 02111-1307, USA. +@end ifinfo + +@c Combine indices. +@syncodeindex fn cp +@syncodeindex vr cp +@syncodeindex ky cp +@syncodeindex pg cp +@syncodeindex tp cp + +@setchapternewpage odd +@finalout + +@titlepage +@title Info on beta versions of XEmacs + +@author XEmacs Development Team +@page +@vskip 0pt plus 1fill + +@noindent +Copyright @copyright{} 2005 Ben Wing. @* + +This file is part of XEmacs. + +XEmacs is free software; you can redistribute it and/or modify it +under the terms of the GNU General Public License as published by the +Free Software Foundation; either version 2, or (at your option) any +later version. + +XEmacs is distributed in the hope that it will be useful, but WITHOUT +ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or +FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License +for more details. + +You should have received a copy of the GNU General Public License +along with XEmacs; see the file COPYING. If not, write to +the Free Software Foundation, Inc., 59 Temple Place - Suite 330, +Boston, MA 02111-1307, USA. +@end titlepage +@page + +@ifinfo +@node Top, Introduction, (dir), (dir) +This Info file describes info relevant to beta versions of XEmacs. +@menu +* Introduction:: +* Compiling Beta XEmacs:: +* Packages:: +* Improving XEmacs:: + +@detailmenu + --- The Detailed Node Listing --- + +Introduction + +* Mailing Lists:: +* Beta Release Schedule:: +* Reporting Problems:: +* Getting the Source:: + +Mailing Lists + +* XEmacs Beta Mailing List:: +* XEmacs Patches Mailing List:: +* XEmacs Design Mailing List:: +* List Administrivia:: +* Managing your subscription via the Web:: +* Subscribing by e-mail:: +* Unsubscribing by e-mail:: + +Compiling Beta XEmacs + +* Building an XEmacs from patches:: +* Building XEmacs from a full distribution:: + +Packages + +* Binary package installation:: +* Manual procedures for package management:: +* Building XEmacs and XEmacs packages from scratch:: + +Improving XEmacs + +* Creating patches for submission:: +* Large contributions:: + +Creating patches for submission + +* Patch discussion etiquette:: + +Large contributions + +* Updates to existing packages:: +* New packages:: +* Syncing with GNU Emacs:: + +@end detailmenu +@end menu + +@end ifinfo + +@node Introduction, Compiling Beta XEmacs, Top, Top +@chapter Introduction + +You are running a potentially unstable version of XEmacs. Please do +not report problems with Beta XEmacs to comp.emacs.xemacs. Report +them to @uref{mailto:xemacs-beta@@xemacs.org}, preferably with +@kbd{M-x report-xemacs-bug RET}. + +@menu +* Mailing Lists:: +* Beta Release Schedule:: +* Reporting Problems:: +* Getting the Source:: +@end menu + +@node Mailing Lists, Beta Release Schedule, Introduction, Introduction +@section Mailing Lists + +@menu +* XEmacs Beta Mailing List:: +* XEmacs Patches Mailing List:: +* XEmacs Design Mailing List:: +* List Administrivia:: +* Managing your subscription via the Web:: +* Subscribing by e-mail:: +* Unsubscribing by e-mail:: +@end menu + +@node XEmacs Beta Mailing List, XEmacs Patches Mailing List, Mailing Lists, Mailing Lists +@subsection XEmacs Beta Mailing List + +If you are not subscribed to the XEmacs beta list you should be. +Currently all discussion of development issues, including bug reports +and coding discussion, takes place on the XEmacs Beta mailing list. +Only patches and administrative actions regarding patches are sent +elsewhere (to the XEmacs Patches list). + +@node XEmacs Patches Mailing List, XEmacs Design Mailing List, XEmacs Beta Mailing List, Mailing Lists +@subsection XEmacs Patches Mailing List + +XEmacs Patches records proposed changes to XEmacs, and their +disposition. It is open subscription, and all patches that are +seriously proposed for inclusion in XEmacs should be posted here. You +can follow progress of your patch by subscribing to the mailing list +or in the archives. + +Besides patches, only actions by members of the XEmacs Review Board +should be posted to this list. All discussion should be redirected to +XEmacs Beta or XEmacs Design. + +@node XEmacs Design Mailing List, List Administrivia, XEmacs Patches Mailing List, Mailing Lists +@subsection XEmacs Design Mailing List + +XEmacs Design is for design discussions such as adding major features +or whole modules, or reimplementation of existing functions, to XEmacs. + +@node List Administrivia, Managing your subscription via the Web, XEmacs Design Mailing List, Mailing Lists +@subsection List Administrivia + +In the descriptions below, the word LIST (all uppercase) is a +variable. Substitute "beta", "design", or "patches" as appropriate +(to get "xemacs-beta" as the mailbox for the XEmacs Beta mailing list, +or @uref{http://www.xemacs.org/Lists/#xemacs-beta} for its URL). + +The XEmacs mailing lists are managed by the Mailman mailing list package, +and the usual Mailman commands work. Do not send mailing list requests to +the main address (@uref{mailto:xemacs-LIST@@xemacs.org}), always send them +to @uref{mailto:xemacs-LIST-request@@xemacs.org}. If you have problems with +the list itself, they should be brought to the attention of the XEmacs +Mailing List manager @uref{mailto:list-manager@@xemacs.org} (the same +mailbox, "list-manager", for all lists). All public mailing lists have +searchable archives. The URL is + + @uref{http://list-archive.xemacs.org/xemacs-LIST} + +Note that the xemacs-LIST-admin address is used internally by the +Mailman software; it is NOT a synonym for xemacs-LIST-request. + +@node Managing your subscription via the Web, Subscribing by e-mail, List Administrivia, Mailing Lists +@subsection Managing your subscription via the Web + +Subscription, unsubscription, and options (such as digests and +temporarily suspending delivery) can be accomplished via the web +interface at @uref{http://www.xemacs.org/Lists/#xemacs-LIST}. + +@node Subscribing by e-mail, Unsubscribing by e-mail, Managing your subscription via the Web, Mailing Lists +@subsection Subscribing by e-mail + +Send an email message to @uref{mailto:xemacs-LIST-request@@xemacs.org} with +@samp{subscribe} (without the quotes) as the BODY of the message. + +@node Unsubscribing by e-mail, , Subscribing by e-mail, Mailing Lists +@subsection Unsubscribing by e-mail + +Send an email message to @uref{mailto:xemacs-LIST-request@@xemacs.org} with +@samp{unsubscribe} (without the quotes) as the BODY of the message. + +@node Beta Release Schedule, Reporting Problems, Mailing Lists, Introduction +@section Beta Release Schedule + +We would like to achieve a weekly or fortnightly release cycle (you +know the Open Source model: release early, release often), and in a +perfect world that would indeed be the case. There are at least three +things that often get in the way of that goal: 1) The Release Manager +has a life outside of XEmacs (hard to believe, I know, but true), +2) we like to make releases that will build (at least on the Release +Manager's box), and 3) Murphy likes to throw a spanner in the works +right when you least expect it (Murphy's Law: Whatever can go wrong, +will go wrong). + +If you'd like to keep right up to date and ride the bleeding edge, use +CVS (see @uref{http://www.xemacs.org/Develop/cvsaccess.html}). If you +can't use CVS for some reason and must use FTP, please let us know. +it will make it more likely that we release betas more often. + + +@node Reporting Problems, Getting the Source, Beta Release Schedule, Introduction +@section Reporting Problems + +The best way to get problems fixed in XEmacs is to submit good problem +reports, @kbd{M-x report-xemacs-bug RET} will help you do this (assuming +you have a usable XEmacs). Since this is beta software, problems are +certain to exist. Please read through all of part II of the XEmacs +FAQ for an overview of problem reporting. Other items which are most +important are: + +@enumerate +@item +Do not submit C stack backtraces without line numbers. Since it +is possible to compile optimized with debug information with GCC +it is never a good idea to compile XEmacs without the -g flag. +XEmacs runs on a variety of platforms, and often it is not +possible to recreate problems which afflict a specific platform. +The line numbers in the C stack backtrace help isolate where the +problem is actually occurring. + +@item +Attempt to recreate the problem starting with an invocation of +XEmacs with @code{xemacs -no-autoloads}. Quite often, problems are +due to package interdependencies, and the like. An actual bug +in XEmacs should be reproducible in a default configuration +without loading any special packages (or the one or two specific +packages that cause the bug to appear). If you have trouble +getting anything to work at all with the above invocation, use +@code{xemacs -vanilla} instead. If you need to load your user init +file or the site file to get the problem to occur, then it has +something to do with them, and you should try to isolate the +issue in those files. + +@item +A picture can be worth a thousand words. When reporting an +unusual display, it is generally best to capture the problem in a +screen dump and include that with the problem report. The easiest +way to get a screen dump is to use the xv program and its grab +function. Save the image as a GIF to keep bandwidth requirements +down without loss of information. MIME is the preferred method +for making the image attachments. +@end enumerate + +@node Getting the Source, , Reporting Problems, Introduction +@section Getting the Source + +In addition to the normal tar distribution, XEmacs source is now +available via CVS. Please see + + @uref{http://www.xemacs.org/Develop/cvsaccess.html} + +@node Compiling Beta XEmacs, Packages, Introduction, Top +@chapter Compiling Beta XEmacs + +@menu +* Building an XEmacs from patches:: +* Building XEmacs from a full distribution:: +@end menu + +@node Building an XEmacs from patches, Building XEmacs from a full distribution, Compiling Beta XEmacs, Compiling Beta XEmacs +@section Building an XEmacs from patches + +All beta releases of XEmacs are included with patches from the previous +version in an attempt to keep bandwidth requirements down. Patches +should be applied with the GNU patch program in something like the +following. Let's say you're upgrading XEmacs 21.5-beta9 to XEmacs +21.5-beta10 and you have a full unmodified XEmacs 21.5-beta9 source +tree to work with. Change to the top level directory and issue the +shell command: + +@example +$ gunzip -c /tmp/xemacs-21.5.9-21.5.10.patch.gz | patch -p1 +@end example + +After patching, check to see that no patches were missed by doing + +@example +$ find . -name \*.rej -print +@end example + +Any rejections should be treated as serious problems to be resolved +before building XEmacs. + +After seeing that there were no rejections, issue the commands + +@example +$ ./config.status --recheck +$ make beta > ./beta.err 2>&1 +$ make check > ./xemacs-make-check.err 2>&1 +@end example + +Redirect the output from make to those files because you'll use them +later when you send off a build report with @kbd{M-x build-report RET} + +@node Building XEmacs from a full distribution, , Building an XEmacs from patches, Compiling Beta XEmacs +@section Building XEmacs from a full distribution + +@enumerate +@item +Locate a convenient place where you have at least 100MB of free space +and issue the command + +@example +$ gunzip -c /tmp/xemacs-21.5.10.tar.gz | tar xvf - +@end example + +(or simply @code{tar zxvf /tmp/xemacs-21.5.10.tar.gz} if you use GNU tar). + +@item +cd to the top level directory and issue an appropriate configure +command. + +@item +Run @code{configure}. If you are new, just consider running it with no +options, to see if you can get a succesful build. When you are more +experienced, you should put various flags in. Here is what we suggest: + +@enumerate +@item +It's a good idea to use + +@example +--extra-verbose +--debug +--memory-usage-stats +--error-checking=all +@end example + +These turn on extra debugging info and checks. The last one in particular +will add a great deal of extra error-checking -- which will slow your XEmacs +down somewhat but is likely to catch bugs much sooner and make your bug +reports much more useful. + +@item +You should also strongly consider + +@example +--with-mule +--use-pkcc +--pdump +--with-clash-detection +--with-wmcommand +--with-xfs +@end example + +These turn on optional features, which can always use testing. + +@item +If you have gcc, consider using + +@example +--compiler=gcc +--xemacs-compiler=g++ +@end example + +This will compile XEmacs using g++, which will turn on a lot of additional +error-checking. + +@item +If your packages are not installed under /usr/local, you should add a +line like + +@example +--package-path=~/.xemacs::/xemacs/site-packages:/xemacs/xemacs-packages:/xemacs/mule-packages +@end example + +@item +If you want to build multiple configurations from the same source +tree, make separate build directories for each configuration, run +@code{configure} from the top level of these (currently empty) +directories and use an option like + +@example +--srcdir=/xemacs/source-tree +@end example + +(or wherever your source tree is). This will magically create symlinks and +populate your build directory. + +@item +Use --site-prefixes (or --site-includes and --site-libraries) if you have +some packages that XEmacs can compile with that are located in an unusual +place. For example: + +@example +--site-prefixes=/usr/local/pgsql:/usr/local/BerkeleyDB.4.1 +@end example + +@item +Depending on your build environment, consuder setting or not setting +options for menubars, scrollbars, window systems, native sound, etc. If +you're not sure, leave them out and let configure do the auto-detection. +(If you get bugs compiling GTK, use @code{--with-gtk=no --with-gnome=no}.) + +Part of the configure output is a summary that looks something +like the following. (this summary is also available as the file +'Installation' in the top directory of your build tree, and via +the command @kbd{M-x describe-installation RET}). + +@example +uname -a: Linux eicq 2.4.20 #1 Wed Dec 18 02:14:29 EST 2002 i586 unknown + +./configure '--extra-verbose' '--site-prefixes=/usr/local/pgsql:/usr/local/BerkeleyDB.4.1' '--dynamic=yes' '--with-gtk=no' '--with-gnome=no' '--with-toolbars' '--with-wmcommand' '--with-athena=next' '--with-menubars=lucid' '--with-scrollbars=athena' '--with-dialogs=athena' '--with-widgets=athena' '--with-gif' '--with-sound=native,noesd' '--with-site-lisp=no' '--with-site-modules' '--pdump' '--with-mule' '--with-xfs' '--debug' '--error-checking=all' '--memory-usage-stats' '--use-kkcc' '--with-clash-detection' + + +XEmacs 21.5-b10 "burdock" (+CVS-20030131) configured for `i586-pc-linux'. + + +Compilation / Installation: + Source code location: /usr/local/src/xemacs + Installation prefix: /usr/local + Additional prefixes: /usr/local/pgsql /usr/local/BerkeleyDB.4.1 + Operating system description file: `s/linux.h' + Machine description file: `m/intel386.h' + Compiler: gcc -Wall -Wno-switch -Winline -Wmissing-prototypes -Wsign-compare -Wundef -Wstrict-prototypes -Wshadow -Wmissing-declarations -O1 -ggdb3 -Wall -Wchar-subscripts -Wunused -Wundef -Wshadow -Wsign-compare -Wmissing-declarations -march=k6 + Relocating allocator for buffers: no + GNU version of malloc: yes + - Using Doug Lea's new malloc from the GNU C Library. + +Window System: + Compiling in support for the X window system: + - X Windows headers location: /usr/X11/include + - X Windows libraries location: /usr/X11/lib + - Handling WM_COMMAND properly. + Compiling in support for the Athena widget set: + - Athena headers location: X11/neXtaw + - Athena library to link: neXtaw + Using Lucid menubars. + Using Athena scrollbars. + Using Athena dialog boxes. + Using Athena native widgets. + +TTY: + Compiling in support for ncurses. + Compiling in support for GPM (General Purpose Mouse). + +Images: + Compiling in support for GIF images (builtin). + Compiling in support for XPM images. + Compiling in support for PNG images. + Compiling in support for JPEG images. + Compiling in support for TIFF images. + Compiling in support for X-Face message headers. + +Sound: + Compiling in support for sound (native). + +Databases: + Compiling in support for Berkeley database. + Compiling in support for PostgreSQL. + - Using PostgreSQL header file: libpq-fe.h + - Using PostgreSQL V7 bindings. + +Internationalization: + Compiling in support for Mule (multi-lingual Emacs). + Compiling in support for XIM (X11R5+ I18N input method). + - Using raw Xlib to provide XIM support. + - Using XFontSet to provide bilingual menubar. + +Mail: + Compiling in support for "dot-locking" mail spool file locking method. + +Other Features: + Inhibiting IPv6 canonicalization at startup. + Compiling in support for dynamic shared object modules. + Using the new GC algorithms. + Using the new portable dumper. + Compiling in support for extra debugging code. + WARNING: WARNING: Compiling in support for runtime error checking. + WARNING: XEmacs will run noticeably more slowly as a result. + WARNING: Error checking is on by default for XEmacs beta releases. + WARNING: +@end example +@end enumerate + + +@item +Then... + +@example +$ make > ./beta.err 2>&1 +$ make check > ./xemacs-make-check.err 2>&1 +@end example + +...and you should have a working XEmacs. + +@item +After you have verified that you have a functional editor, fire up +your favorite mail program and send a build report to +@uref{mailto:xemacs-buildreports@@xemacs.org}. + +Preferably this is best done from XEmacs, following these simple steps: + +@enumerate +@kbd{M-x customize-group RET build-report RET} +@kbd{M-x build-report RET} +@end enumerate + +See also +@uref{http://www.xemacs.org/Releases/Public-21.2/tester.html#reporting} + +If you create the report manually by other means, here is what the +build report should include: + +@enumerate +@item +Your hardware configuration (OS version, etc.) + +@item +Version numbers of software in use (X11 version, system library +versions if appropriate, graphics library versions if appropriate). +If you're on a system like Linux, include all the version numbers +you can because chances are it makes a difference. + +@item +The options given to configure + +@item +The configuration report illustrated above + +For convenience all of the above items are placed in a file called +`Installation' in the top level build directory. They are also +available by performing @kbd{M-x describe-installation} inside XEmacs. + +@item +Any other unusual items you feel should be brought to the attention +of the developers. +@end enumerate +@end enumerate + +@node Packages, Improving XEmacs, Compiling Beta XEmacs, Top +@chapter Packages + +[Note: these instructions have been partly updated, but not carefully +reviewed in some time. Caveat tester.] + +Starting with XEmacs 21.1, much of the functionality of XEmacs has +been unbundled into "the packages." For more information about the +package system, see the Info nodes on Packages (in the XEmacs User +Manual) and on Packaging (in the Lisp Reference). + +When bootstrapping XEmacs, you may need to manually install some +packages (at least xemacs-base and efs). These packages are available +by FTP at @uref{ftp://ftp.xemacs.org/pub/xemacs/packages/}. + +@menu +* Binary package installation:: +* Manual procedures for package management:: +* Building XEmacs and XEmacs packages from scratch:: +@end menu + +@node Binary package installation, Manual procedures for package management, Packages, Packages +@section Binary package installation + +Prerequisite: XEmacs 21.0-b1. + +Binary packages are complete entities that can be untarred at the top +level of an XEmacs package hierarchy and work at runtime. To install files +in this directory, run the command @kbd{M-x package-admin-add-binary-package} +and fill in appropriate values to the prompts. + +@node Manual procedures for package management, Building XEmacs and XEmacs packages from scratch, Binary package installation, Packages +@section Manual procedures for package management + +Prerequisite: XEmacs 21.0 + +When adding and deleting files from a lisp directory the +auto-autoloads.el (global symbols) and custom-load.el (Customization +groups) must be kept in synch. Assuming one is manipulating a +directory called `lisp-utils', the command to rebuild the +auto-autoloads.el file is: + +@example +xemacs -vanilla -batch \ + -eval \("setq autoload-package-name \"lisp-utils\""\) \ + -f batch-update-directory lisp-utils +@end example + +The command to rebuild the custom-load.el file is: + +@example +xemacs -vanilla -batch -f Custom-make-dependencies lisp-utils +@end example + +To byte-compile both of these files the command is: + +@example +xemacs -vanilla -batch -f batch-byte-compile \ + lisp-utils/auto-autoloads.el lisp-utils/custom-load.el +@end example + +Of course, being a beta tester, you'd be aware that it is much easier +to manage your XEmacs packages with PUI. + +@node Building XEmacs and XEmacs packages from scratch, , Manual procedures for package management, Packages +@section Building XEmacs and XEmacs packages from scratch + +To build everything completely from scratch isn't hard, just time +consuming. + +@subheading Step 1 - grab the sources (core and packages) + +@example +$ cvs -d :pserver:cvs@@cvs.xemacs.org:/pack/xemacscvs login + [password: "cvs" (sans quotes)] + +$ cvs -d :pserver:cvs@@cvs.xemacs.org:/pack/xemacscvs co -d xemacs-21.5 xemacs + +$ cvs -d :pserver:cvs@@cvs.xemacs.org:/pack/xemacscvs co packages +@end example + +@subheading Step 2 - build XEmacs + +@example +$ cd xemacs-21.5 +$ ./configure [options...] +$ make > ./beta.err 2>&1 +$ make check > ./xemacs-make-check.err 2>&1 +@end example + +And optionally: + +@example +$ make install > ./xemacs-make-install.err 2>&1 +@end example + +@subheading Step 3 - build and install the packages + +@example +$ cd packages +$ cp Local.rules.template Local.rules +@end example + +Then edit Local.rules to suit your needs/environment +(@pxref{Local.rules file,,, xemacs, XEmacs User's Manual}) for details +about this file. + +And then: + +@example +$ make install +@end example + +@node Improving XEmacs, , Packages, Top +@chapter Improving XEmacs + +@menu +* Creating patches for submission:: +* Large contributions:: +@end menu + +@node Creating patches for submission, Large contributions, Improving XEmacs, Improving XEmacs +@section Creating patches for submission + +All patches to XEmacs that are seriously proposed for inclusion (eg, +bug fixes) should be mailed to @uref{mailto:xemacs-patches@@xemacs.org}. Each +patch will be reviewed by the patches review board, and will be +acknowledged and added to the distribution, or rejected with an +explanation. Progress of the patch is tracked on the XEmacs Patches +mailing list, which is open subscription. (If a patch is simply +intended to facilitate discussion, "I mean something that works like +this but this is really rough", a Cc to XEmacs Patches is optional, +but doesn't hurt.) + +Patches to XEmacs Lisp packages should be sent to the maintainer of +the package. If the maintainer is listed as `XEmacs Development Team' +patches should be sent to @uref{mailto:xemacs-patches@@xemacs.org}. + +Emailed patches should preferably be sent in MIME format and quoted +printable encoding (if necessary). + +The simplest way to create well-formed patches is to use CVS and +Didier Verna's Patcher library (available as patcher.el in the +xemacs-devel package). Patcher is new and requires some setup, but +most of the core developers are now using it for their own patches. +Patcher also can be configured to create patches for several projects, +and recognize the project from the directory it is invoked in. This +makes it a useful general tool (as long as XEmacs-style patches are +accepted at your other projects, which is likely since they conform to +the GNU standards). + +When making patches by hand, please use the `-u' option, or if your +diff doesn't support it, `-c'. Using ordinary (context-free) diffs +are notoriously prone to error, since line numbers tend to change when +others make changes to the same source file. + +An example of the `diff' usage: + +@example +$ diff -u OLDFILE NEWFILE +@end example + +-or- + +@example +$ diff -c OLDFILE NEWFILE +@end example + +Also, it is helpful if you create the patch in the top level of the +XEmacs source directory: + +@example +$ cp -p lwlib/xlwmenu.c lwlib/xlwmenu.c.orig + hack, hack, hack.... +$ diff -u lwlib/xlwmenu.c.orig lwlib/xlwmenu.c +@end example + +Also note that if you cut & paste from an xterm to an XEmacs mail +buffer you will probably lose due to tab expansion. The best thing to +do is to use an XEmacs shell buffer to run the diff commands, or ... +@kbd{M-x cd} to the appropriate directory, and issue the command +@kbd{C-u M-!} from within XEmacs. + +Patches should be as single-minded as possible. Mammoth patches can +be very difficult to place into the right slot. They are much easier +to deal with when broken down into functional or conceptual chunks. +The patches submitted by Kyle Jones and Hrvoje Niksic are stellar +examples of how to "Do The Right Thing". + +Each patch should be accompanied by an update to the appropriate +ChangeLog file. Guidelines for writing ChangeLog entries is governed +by the GNU coding standards. Please see +@uref{http://www.gnu.org/prep/standards_toc.html} [Change Logs section] +for details. + +Do not submit context diffs (either -c or -u) of ChangeLogs. Because +of the "stack" nature of ChangeLogs (new entries are always pushed on +the top), context diffs will fail to apply more often than they +succeed. Simply cutting and pasting the entry from an Emacs buffer to +the mail buffer (beware of tab expansion!) is probably easiest. The +Patcher library also will set up your ChangeLogs for you, and copy +them to the mail. Context-less unified diffs (-U 0) are also +acceptable. + +@menu +* Patch discussion etiquette:: +@end menu + +@node Patch discussion etiquette, , Creating patches for submission, Creating patches for submission +@subsection Patch discussion etiquette + +If you intend a patch for _application_ to the sources as is, _always_ +post it to xemacs-patches, even if there are minor points you would +like to have discussed by others. Not doing so will resulting in +patches getting "lost". If you expect that the patch will not be +acceptable, but are using it to stimulate discussion, then don't post +to xemacs-patches. Intermediate cases are up to your judgment; +unless you're sure you'll follow up with a "real" patch, better to err +on the side of posting to xemacs-patches. + +Discussion of the _content_ of the patch (ie responses to reviewer +comments beyond "that's right, ok, I'll do it your way") should _always_ +be posted to xemacs-beta or to xemacs-design. If you're not sure +which is more appropriate, send it to xemacs-beta. That is the most +widely read channel. + +If discussion results in a bright idea and you come up with a new +patch, normally you should post it to both mailing lists. The people +discussing on XEmacs Beta will want to know the outcome of the thread, +and you need to submit to XEmacs Patches as the "list of record." + +If the old patch has been applied to CVS, then just submit the new one +as usual. If it has not been applied, then it is best to submit a new +patch against CVS. If possible do this as a reply to the original +patch post, or something following it in the thread. (The point is to +get the original patch post's Message-ID in your References header.) +In this case, also use the keyword SUPERSEDES in the Subject header to +indicate that the old patch is no longer valid, and that this one +replaces it. + +These rules will result in a fair number of cross posts, but we don't +yet have a better way to handle that. + +Note: Developers should never post to xemacs-patches unless there is a +patch in the post. We plan to enforce this with an automatic filter. + +The exceptions are administrative. If you have commit authorization, +then post a short COMMIT notice to xemacs-patches when you commit to +CVS. Members of the Review Board will also post short notices of +administrative action (APPROVE, VETO, QUERY, etc) to xemacs-patches. + +@node Large contributions, , Creating patches for submission, Improving XEmacs +@section Large contributions + +Perhaps you have a whole new mode, or a major synchronization with +upstream for a neglected package, or a synchronization with GNU Emacs +you would like to contribute. We welcome such contributions, but they +are likely to be relatively controversial, generate more comments and +requests for revision, and take longer to integrate. Please be +patient with the process. + +@menu +* Updates to existing packages:: +* New packages:: +* Syncing with GNU Emacs:: +@end menu + +@node Updates to existing packages, New packages, Large contributions, Large contributions +@subsection Updates to existing packages + +If a package has gotten a bit out of date, or even started to bitrot, +we welcome patches to synchronize it with upstream/GNU Emacs versions. +Most packages end up varying somewhat from their GNU origins. See +"Syncing with GNU Emacs" for hints. Note that if you do a reasonably +large amount of syncing with GNU Emacs, you should log this in the +file itself as well as in the ChangeLog. + +If the package is important to you, please consider becoming the +maintainer. (See "New packages", below.) + +@node New packages, Syncing with GNU Emacs, Updates to existing packages, Large contributions +@subsection New packages + +If you have a new mode or other large addition that does not require +changes to the core, please consider submitting it as a package, and +becoming the maintainer. You get direct commit privileges to the +repository for your package, "approval" privileges for your own +patches as well as third party patches to your package, and some +degree of veto power over patches you don't like. In return, you are +expected to maintain friendly liaison with the upstream developer (if +you aren't the upstream developer), keep watch on the XEmacs Patches +list for relevant patches, and be available by email to other +developers for discussion of changes that impact your package. It's +also a pretty standard route to the "core" development group, where we +have plenty of extra work waiting for volunteers. + +You don't have to become the maintainer, but it virtually ensures +rapid acceptance of the package. + +For help in creating new packages, see the (rather sparse) discussions +in the XEmacs User's Guide and the Lisp Reference Manual. The XEmacs +Package Release Engineer (Ville Skyttä @uref{mailto:scop@@xemacs.org} +is currently serving with Norbert Koch @uref{mailto:viteno@@xemacs.org} +assisting; Steve Youngs @uref{mailto:youngs@@xemacs.org} and Stephen +Turnbull @uref{mailto:stephen@@xemacs.org} also can help) are the most +likely sources of advice. + +@node Syncing with GNU Emacs, , New packages, Large contributions +@subsection Syncing with GNU Emacs + +Syncing with GNU Emacs is an important activity. Although each +version has its advantages and areas of concentration, it is very +desirable that common functionality share specifications and APIs. +When porting GNU code to XEmacs, the following points should be given +special attention: + +@itemize @bullet +@item +Recent GNU Emacsen cannot be built without Mule, but XEmacs can. +Make sure your changes do not assume the presence of Mule. + +@item +GNU Emacs nomenclature often differs from that of XEmacs. +Sometimes syncing the names is desirable, other times not. + +@item +GNU Emacs functionality often differs from that of XEmacs. +Syncing functionality is often controversial. +@end itemize + +It is important that you let other developers know that +synchronization has taken place, to what degree, and when. For this +purpose, we use comments of the form + +@example +/* Synched up with: FSF 21.3 by Stephen Turnbull */ +@end example + +in the source file itself, as the last element of the prefatory +material (copyright notice and commentary). Obviously the comment +marker needs to be changed to leading semicolons for Lisp, but +otherwise the format is the same. + +Of course you should note syncing as the purpose in the ChangeLog, +too. But entries get buried deep in the ChangeLog file, and may even +get moved to a separate ChangeLog.OLD file for rarely synched files. + +Rather than dates we use the version of GNU Emacs to sync to. If the +synchronization is partial, add a new comment describing what has +actually been synched, leaving the description of the last full sync +in place. At each full sync, remove all previous synchronization +comments. + +This applies to Lisp that we have broken out into packages, but +remains in the GNU Emacs core, as well to core Lisp in XEmacs. + +@c Print the tables of contents +@contents +@c That's all + +@node Index, , Defining Variables, Top +@unnumbered Index + +@printindex cp + +@bye diff -r 7edc33019aa4 -r b7b90f750a78 man/xemacs-faq.texi --- a/man/xemacs-faq.texi Mon Jan 31 20:01:50 2005 +0000 +++ b/man/xemacs-faq.texi Mon Jan 31 20:08:52 2005 +0000 @@ -7,7 +7,7 @@ @finalout @titlepage @title XEmacs FAQ -@subtitle Frequently asked questions about XEmacs @* Last Modified: $Date: 2004/12/29 05:08:26 $ +@subtitle Frequently asked questions about XEmacs @* Last Modified: $Date: 2005/01/31 20:08:48 $ @sp 1 @author Ben Wing @author Tony Rossini @@ -194,63 +194,77 @@ 1 Introduction, Policy, Credits -1.0: Introduction +1.0: What is XEmacs? * Q1.0.1:: What is XEmacs? * Q1.0.2:: What is the current version of XEmacs? -* Q1.0.3:: Where can I find it? -* Q1.0.4:: Are binaries available? -* Q1.0.5:: How does XEmacs differ from GNU Emacs? -* Q1.0.6:: How much does XEmacs differ? -* Q1.0.7:: Is XEmacs "GNU"? -* Q1.0.8:: What is the correct way to refer to XEmacs and GNU Emacs? -* Q1.0.9:: Why haven't XEmacs and GNU Emacs merged? -* Q1.0.10:: Where can I get help? -* Q1.0.11:: Where are the mailing lists archived? -* Q1.0.12:: How do you pronounce XEmacs? -* Q1.0.13:: What does XEmacs look like? -* Q1.0.14:: Where can I obtain a printed copy of the XEmacs User's Manual? - -1.1: Versions for Different Operating Systems -* Q1.1.1:: Do I need X11 to run XEmacs? -* Q1.1.2:: Is there a port of XEmacs to Microsoft Windows? -* Q1.1.3:: Can I build XEmacs on MS Windows with X support? Do I need to? -* Q1.1.4:: What are Cygwin and MinGW, and do I need them to run XEmacs? -* Q1.1.5:: What are the differences between the various MS Windows emacsen? -* Q1.1.6:: Is there a port of XEmacs to the Macintosh? -* Q1.1.7:: Is there a port of XEmacs to NextStep? -* Q1.1.8:: Is there a port of XEmacs to OS/2? -* Q1.1.9:: How does the port cope with differences in the Windows user interface? - -1.2: Policies -* Q1.2.1:: What is the FAQ editorial policy? -* Q1.2.2:: How do I become a beta tester? -* Q1.2.3:: How do I contribute to XEmacs itself? - -1.3: Credits -* Q1.3.1:: Who wrote XEmacs? -* Q1.3.2:: Who contributed to this version of the FAQ? -* Q1.3.3:: Who contributed to the FAQ in the past? - -1.4: Internationalization -* Q1.4.1:: What is the status of internationalization support aka MULE (including Asian language support)? -* Q1.4.2:: How can I help with internationalization? -* Q1.4.3:: How do I type non-ASCII characters? -* Q1.4.4:: Can XEmacs messages come out in a different language? -* Q1.4.5:: Please explain the various input methods in MULE/XEmacs -* Q1.4.6:: How do I portably code for MULE/XEmacs? -* Q1.4.7:: How about Cyrillic modes? -* Q1.4.8:: Does XEmacs support Unicode? -* Q1.4.9:: How does XEmacs display Unicode? - -1.5: Getting Started -* Q1.5.1:: What is an @file{init.el} or @file{.emacs} and is there a sample one? -* Q1.5.2:: Where do I put my @file{init.el} file? -* Q1.5.3:: Can I use the same @file{init.el} with the other Emacs? -* Q1.5.4:: Any good XEmacs tutorials around? -* Q1.5.5:: May I see an example of a useful XEmacs Lisp function? -* Q1.5.6:: And how do I bind it to a key? -* Q1.5.7:: What's the difference between a macro and a function? -* Q1.5.8:: What is @code{Custom}? +* Q1.0.3:: How do you pronounce XEmacs? +* Q1.0.4:: What does XEmacs look like? +* Q1.0.5:: Who wrote XEmacs? +* Q1.0.6:: Who wrote the FAQ? + +1.1: Getting XEmacs +* Q1.1.1:: Where can I find XEmacs? +* Q1.1.2:: Are binaries available? +* Q1.1.3:: How do I get the bleeding-edge sources? +* Q1.1.4:: Where can I obtain a printed copy of the XEmacs User's Manual? + +1.2: Versions for Different Operating Systems +* Q1.2.1:: Do I need X11 to run XEmacs? +* Q1.2.2:: What versions of Unix does XEmacs run on? +* Q1.2.3:: Is there a port of XEmacs to Microsoft Windows? +* Q1.2.4:: Can I build XEmacs on MS Windows with X support? Do I need to? +* Q1.2.5:: What are Cygwin and MinGW, and do I need them to run XEmacs? +* Q1.2.6:: What are the differences between the various MS Windows emacsen? +* Q1.2.7:: How does the port cope with differences in the Windows user interface? +* Q1.2.8:: Is there a port of XEmacs to the Macintosh? +* Q1.2.9:: Is there a port of XEmacs to MS-DOS? +* Q1.2.10:: Is there a port of XEmacs to OS/2? +* Q1.2.11:: Is there a port of XEmacs to NextStep? +* Q1.2.12:: Is there a port of XEmacs to VMS? + +1.3: Getting Started +* Q1.3.1:: What is an @file{init.el} or @file{.emacs} and is there a sample one? +* Q1.3.2:: Where do I put my @file{init.el} file? +* Q1.3.3:: Can I use the same @file{init.el} with the other Emacs? +* Q1.3.4:: Any good XEmacs tutorials around? +* Q1.3.5:: May I see an example of a useful XEmacs Lisp function? +* Q1.3.6:: And how do I bind it to a key? +* Q1.3.7:: What's the difference between a macro and a function? +* Q1.3.8:: What is @code{Custom}? + +1.4: Getting Help +* Q1.4.1:: Where can I get help? +* Q1.4.2:: Which mailing lists are there? +* Q1.4.2:: Where are the mailing lists archived? +* Q1.4.3:: How can I get two instances of info? +* Q1.4.4:: How do I add new Info directories? + +1.5: Contributing to XEmacs +* Q1.5.1:: How do I submit changes to the FAQ? +* Q1.5.2:: How do I become a beta tester? +* Q1.5.3:: How do I contribute to XEmacs itself? + +1.6: Politics (XEmacs vs. GNU Emacs) +* Q1.6.1:: What is GNU Emacs? +* Q1.6.2:: How does XEmacs differ from GNU Emacs? +* Q1.6.3:: How much does XEmacs differ? +* Q1.6.4:: Is XEmacs "GNU"? +* Q1.6.5:: What is the correct way to refer to XEmacs and GNU Emacs? +* Q1.6.6:: Why haven't XEmacs and GNU Emacs merged? + +1.7: External Packages +* Q1.7.1:: Which external packages are there? + +1.8: Internationalization +* Q1.8.1:: What is the status of internationalization support aka MULE (including Asian language support)? +* Q1.8.2:: How can I help with internationalization? +* Q1.8.3:: How do I type non-ASCII characters? +* Q1.8.4:: Can XEmacs messages come out in a different language? +* Q1.8.5:: Please explain the various input methods in MULE/XEmacs +* Q1.8.6:: How do I portably code for MULE/XEmacs? +* Q1.8.7:: How about Cyrillic modes? +* Q1.8.8:: Does XEmacs support Unicode? +* Q1.8.9:: How does XEmacs display Unicode? 2 Installation and Troubleshooting @@ -473,36 +487,32 @@ 7 Advanced Customization Using XEmacs Lisp -7.0: Online Help -* Q7.0.1:: How can I get two instances of info? -* Q7.0.2:: How do I add new Info directories? - -7.1: Emacs Lisp and @file{init.el} -* Q7.1.1:: What version of Emacs am I running? -* Q7.1.2:: How can I evaluate Emacs-Lisp expressions? -* Q7.1.3:: @code{(setq tab-width 6)} behaves oddly. -* Q7.1.4:: How can I add directories to the @code{load-path}? -* Q7.1.5:: How to check if a lisp function is defined? -* Q7.1.6:: Can I force the output of @code{(face-list)} to a buffer? - -7.2: Emacs Lisp Programming Techniques -* Q7.2.1:: What is the difference in key sequences between XEmacs and GNU Emacs? -* Q7.2.2:: Can I generate "fake" keyboard events? -* Q7.2.3:: Could you explain @code{read-kbd-macro} in more detail? -* Q7.2.4:: What is the performance hit of @code{let}? -* Q7.2.5:: What is the recommended use of @code{setq}? -* Q7.2.6:: What is the typical misuse of @code{setq}? -* Q7.2.7:: I like the @code{do} form of cl, does it slow things down? -* Q7.2.8:: I like recursion, does it slow things down? -* Q7.2.9:: How do I put a glyph as annotation in a buffer? -* Q7.2.10:: @code{map-extents} won't traverse all of my extents! -* Q7.2.11:: My elisp program is horribly slow. Is there an easy way to find out where it spends time? - -7.3: Mathematics -* Q7.3.1:: What are bignums, ratios, and bigfloats in Lisp? -* Q7.3.2:: XEmacs segfaults when I use very big numbers! -* Q7.3.3:: Bignums are really slow! -* Q7.3.4:: Equal bignums don't compare as equal! What gives? +7.0: Emacs Lisp and @file{init.el} +* Q7.0.1:: What version of Emacs am I running? +* Q7.0.2:: How can I evaluate Emacs-Lisp expressions? +* Q7.0.3:: @code{(setq tab-width 6)} behaves oddly. +* Q7.0.4:: How can I add directories to the @code{load-path}? +* Q7.0.5:: How to check if a lisp function is defined? +* Q7.0.6:: Can I force the output of @code{(face-list)} to a buffer? + +7.1: Emacs Lisp Programming Techniques +* Q7.1.1:: What is the difference in key sequences between XEmacs and GNU Emacs? +* Q7.1.2:: Can I generate "fake" keyboard events? +* Q7.1.3:: Could you explain @code{read-kbd-macro} in more detail? +* Q7.1.4:: What is the performance hit of @code{let}? +* Q7.1.5:: What is the recommended use of @code{setq}? +* Q7.1.6:: What is the typical misuse of @code{setq}? +* Q7.1.7:: I like the @code{do} form of cl, does it slow things down? +* Q7.1.8:: I like recursion, does it slow things down? +* Q7.1.9:: How do I put a glyph as annotation in a buffer? +* Q7.1.10:: @code{map-extents} won't traverse all of my extents! +* Q7.1.11:: My elisp program is horribly slow. Is there an easy way to find out where it spends time? + +7.2: Mathematics +* Q7.1.1:: What are bignums, ratios, and bigfloats in Lisp? +* Q7.1.2:: XEmacs segfaults when I use very big numbers! +* Q7.1.3:: Bignums are really slow! +* Q7.1.4:: Equal bignums don't compare as equal! What gives? 8 Other External Packages @@ -537,7 +547,6 @@ 10.0: XEmacs 21.1 * Q10.0.1:: Gnus 5.10 won't display smileys in XEmacs 21.1. - @end detailmenu @end menu @@ -574,66 +583,81 @@ Include @samp{XEmacs FAQ} on the Subject: line. @menu -1.0: Introduction +1.0: What is XEmacs? * Q1.0.1:: What is XEmacs? * Q1.0.2:: What is the current version of XEmacs? -* Q1.0.3:: Where can I find it? -* Q1.0.4:: Are binaries available? -* Q1.0.5:: How does XEmacs differ from GNU Emacs? -* Q1.0.6:: How much does XEmacs differ? -* Q1.0.7:: Is XEmacs "GNU"? -* Q1.0.8:: What is the correct way to refer to XEmacs and GNU Emacs? -* Q1.0.9:: Why haven't XEmacs and GNU Emacs merged? -* Q1.0.10:: Where can I get help? -* Q1.0.11:: Where are the mailing lists archived? -* Q1.0.12:: How do you pronounce XEmacs? -* Q1.0.13:: What does XEmacs look like? -* Q1.0.14:: Where can I obtain a printed copy of the XEmacs User's Manual? - -1.1: Versions for Different Operating Systems -* Q1.1.1:: Do I need X11 to run XEmacs? -* Q1.1.2:: Is there a port of XEmacs to Microsoft Windows? -* Q1.1.3:: Can I build XEmacs on MS Windows with X support? Do I need to? -* Q1.1.4:: What are Cygwin and MinGW, and do I need them to run XEmacs? -* Q1.1.5:: What are the differences between the various MS Windows emacsen? -* Q1.1.6:: Is there a port of XEmacs to the Macintosh? -* Q1.1.7:: Is there a port of XEmacs to NextStep? -* Q1.1.8:: Is there a port of XEmacs to OS/2? -* Q1.1.9:: How does the port cope with differences in the Windows user interface? - -1.2: Policies -* Q1.2.1:: What is the FAQ editorial policy? -* Q1.2.2:: How do I become a beta tester? -* Q1.2.3:: How do I contribute to XEmacs itself? - -1.3: Credits -* Q1.3.1:: Who wrote XEmacs? -* Q1.3.2:: Who contributed to this version of the FAQ? -* Q1.3.3:: Who contributed to the FAQ in the past? - -1.4: Internationalization -* Q1.4.1:: What is the status of internationalization support aka MULE (including Asian language support)? -* Q1.4.2:: How can I help with internationalization? -* Q1.4.3:: How do I type non-ASCII characters? -* Q1.4.4:: Can XEmacs messages come out in a different language? -* Q1.4.5:: Please explain the various input methods in MULE/XEmacs -* Q1.4.6:: How do I portably code for MULE/XEmacs? -* Q1.4.7:: How about Cyrillic modes? -* Q1.4.8:: Does XEmacs support Unicode? -* Q1.4.9:: How does XEmacs display Unicode? - -1.5: Getting Started -* Q1.5.1:: What is an @file{init.el} or @file{.emacs} and is there a sample one? -* Q1.5.2:: Where do I put my @file{init.el} file? -* Q1.5.3:: Can I use the same @file{init.el} with the other Emacs? -* Q1.5.4:: Any good XEmacs tutorials around? -* Q1.5.5:: May I see an example of a useful XEmacs Lisp function? -* Q1.5.6:: And how do I bind it to a key? -* Q1.5.7:: What's the difference between a macro and a function? -* Q1.5.8:: What is @code{Custom}? +* Q1.0.3:: How do you pronounce XEmacs? +* Q1.0.4:: What does XEmacs look like? +* Q1.0.5:: Who wrote XEmacs? +* Q1.0.6:: Who wrote the FAQ? + +1.1: Getting XEmacs +* Q1.1.1:: Where can I find XEmacs? +* Q1.1.2:: Are binaries available? +* Q1.1.3:: How do I get the bleeding-edge sources? +* Q1.1.4:: Where can I obtain a printed copy of the XEmacs User's Manual? + +1.2: Versions for Different Operating Systems +* Q1.2.1:: Do I need X11 to run XEmacs? +* Q1.2.2:: What versions of Unix does XEmacs run on? +* Q1.2.3:: Is there a port of XEmacs to Microsoft Windows? +* Q1.2.4:: Can I build XEmacs on MS Windows with X support? Do I need to? +* Q1.2.5:: What are Cygwin and MinGW, and do I need them to run XEmacs? +* Q1.2.6:: What are the differences between the various MS Windows emacsen? +* Q1.2.7:: How does the port cope with differences in the Windows user interface? +* Q1.2.8:: Is there a port of XEmacs to the Macintosh? +* Q1.2.9:: Is there a port of XEmacs to MS-DOS? +* Q1.2.10:: Is there a port of XEmacs to OS/2? +* Q1.2.11:: Is there a port of XEmacs to NextStep? +* Q1.2.12:: Is there a port of XEmacs to VMS? + +1.3: Getting Started +* Q1.2.13:: +* Q1.3.1:: What is an @file{init.el} or @file{.emacs} and is there a sample one? +* Q1.3.2:: Where do I put my @file{init.el} file? +* Q1.3.3:: Can I use the same @file{init.el} with the other Emacs? +* Q1.3.4:: Any good XEmacs tutorials around? +* Q1.3.5:: May I see an example of a useful XEmacs Lisp function? +* Q1.3.6:: And how do I bind it to a key? +* Q1.3.7:: What's the difference between a macro and a function? +* Q1.3.8:: What is @code{Custom}? + +1.4: Getting Help +* Q1.4.1:: Where can I get help? +* Q1.4.2:: Which mailing lists are there? +* Q1.4.3:: How can I get two instances of info? +* Q1.4.4:: How do I add new Info directories? + +1.5: Contributing to XEmacs +* Q1.4.5:: +* Q1.5.1:: How do I submit changes to the FAQ? +* Q1.5.2:: How do I become a beta tester? +* Q1.5.3:: How do I contribute to XEmacs itself? + +1.6: Politics (XEmacs vs. GNU Emacs) +* Q1.6.1:: What is GNU Emacs? +* Q1.6.2:: How does XEmacs differ from GNU Emacs? +* Q1.6.3:: How much does XEmacs differ? +* Q1.6.4:: Is XEmacs "GNU"? +* Q1.6.5:: What is the correct way to refer to XEmacs and GNU Emacs? +* Q1.6.6:: Why haven't XEmacs and GNU Emacs merged? + +1.7: External Packages +* Q1.7.1:: Which external packages are there? + +1.8: Internationalization +* Q1.8.1:: What is the status of internationalization support aka MULE (including Asian language support)? +* Q1.8.2:: How can I help with internationalization? +* Q1.8.3:: How do I type non-ASCII characters? +* Q1.8.4:: Can XEmacs messages come out in a different language? +* Q1.8.5:: Please explain the various input methods in MULE/XEmacs +* Q1.8.6:: How do I portably code for MULE/XEmacs? +* Q1.8.7:: How about Cyrillic modes? +* Q1.8.8:: Does XEmacs support Unicode? +* Q1.8.9:: How does XEmacs display Unicode? @end menu -@unnumberedsec 1.0: Introduction +@unnumberedsec 1.0: What is XEmacs? @node Q1.0.1, Q1.0.2, Introduction, Introduction @unnumberedsubsec Q1.0.1: What is XEmacs? @@ -667,16 +691,308 @@ and was also the last version without international language support. @node Q1.0.3, Q1.0.4, Q1.0.2, Introduction -@unnumberedsubsec Q1.0.3: Where can I find it? - -The canonical source and binaries can be found at: - -@example -@uref{http://ftp.xemacs.org/pub/xemacs/} -@end example +@unnumberedsubsec Q1.0.3: How do you pronounce XEmacs? + +The most common pronounciation is @samp{Eks eemax}. @node Q1.0.4, Q1.0.5, Q1.0.3, Introduction -@unnumberedsubsec Q1.0.4: Are binaries available? +@unnumberedsubsec Q1.0.4: What does XEmacs look like? + +Screen snapshots are available at +@uref{http://www.xemacs.org/About/Screenshots/index.html} +as part of the XEmacs website. + +@node Q1.0.5, Q1.0.6, Q1.0.4, Introduction +@unnumberedsubsec Q1.0.5: Who wrote XEmacs? + +XEmacs is the result of the time and effort of many people, and the +active developers have changed over time. There are two major +components of the XEmacs effort -- writing the code itself and providing +all the support work (testing the code, releasing beta and final +versions, handling patches, reading bug reports, maintaining the web +site, managing the mailing lists, etc. etc.). Neither component would +work without the other. + +@subheading CODING + +The primary code contributor over the years has been Ben Wing (active +since late 1992). Between 1991 and 1995, large amounts of coding was +contributed by Jamie Zawinski and Chuck Thompson. Many other people +have authored major subsystems or otherwise contributed large amounts of +code, including Andy Piper, Hrvoje Niksic, Jerry James, Jonathan Harris, +Kyle Jones, Martin Buchholz, Michael Sperber, Olivier Galibert, Richard +Mlynarik, Stig, William Perry and plenty of others. + +Primary XEmacs-specific subsystems and their authors: + +@table @asis +@item Objects +@itemize @minus +@item +Conversion from 26-bit to 28-bit pointers and integers, lrecords, lcrecords: Richard Mlynarik, 1994 +@item +Conversion to 32-bit pointers and 31-bit integers: Kyle Jones, Martin Buchholz +@item +Portable dumper, object descriptions: Olivier Galibert +@item +KKCC (new garbage collector), ephemerons, weak boxes: Michael Sperber and students +@item +Random object work (object equal and hash methods, weak lists, lcrecord lists, bit vectors, dynarr, blocktype, opaque, string resizing): Ben Wing +@item +Profiling: Ben Wing +@item +Some byte-compilation and hash-table improvements: Martin Buchholz +@item +Bignum: Jerry James +@end itemize + +@item Internationalization/Mule +@itemize @minus +@item +mostly Ben Wing; many ideas for future work, Stephen Turnbull +@end itemize + +@item I/O +@itemize @minus +@item +Basic event/event-stream implementation: Jamie Zawinski +@item +Most event work since 1994: Ben Wing +@item +Asynchronous stuff (async timeouts, signals, quit-checking): Ben Wing +@item +Process method abstraction, Windows process work: Kirill Katsnelson +@item +Misc-user events, async timeouts, most quit-checking and signal code, most other work since 1994: Ben Wing +@item +Lstreams: Ben Wing +@end itemize + +@item Display +@itemize @minus +@item +Redisplay mechanism: implementation, Chuck Thompson; additional work, lots of people +@item +Glyphs: mostly Ben Wing +@item +Specifiers: Ben Wing +@item +Extents: initial implementation, someone at Lucid; rewrite, 1994, Ben Wing +@item +Widgets: Andy Piper +@item +JPEG/PNG/TIFF image converters: Ben Wing, William Perry, Jareth Hein, others (see comment in @file{glyphs-eimage.c}) +@item +Menus: Jamie Zawinski, someone at Lucid (Lucid menus) +@item +Scrollbars: Chuck Thompson, ??? (Lucid scrollbar) +@item +Multi-device/device-independence work (console/device/etc methods): Ben Wing, prototype by chuck thompson +@item +Faces: first implementation, Jamie Zawinski; second, chuck; third, Ben Wing +@item +Fonts/colors: first implementation, Jamie Zawinski; further work, Ben Wing +@item +Toolbars: implementation, chuck, much interface work, Ben Wing +@item +Gutters, tabs: andy piper +@end itemize + +@item Device subsystems +@itemize @minus +@item +X Windows: Jamie Zawinksi, Ben Wing, others +@item +GTK: William Perry, Malcolm Purvis +@item +MS Windows: initial implementation, Jonathan Harris; some more work, Andy Piper, Ben Wing +@item +TTY: Chuck Thompson, Ben Wing +@item +Cygwin: Andy Piper +@end itemize + +@item Misc +@itemize @minus +@item +Configure: initial porting from fsf, Chuck Thompson; conversion to autoconf 2, much rewriting, Martin Buchholz +@item +Most initialization-related code: Ben Wing +@item +Internals manual, much of Lisp manual: Ben Wing +@item +FSF synching: initial sync with FSF 19, Richard Mlynarik, further work, Ben Wing +@end itemize +@end table + +@subheading SUPPORT + +Currently, support duties are handled by many different people. + +Release managers have been + +@itemize @minus +@item +Stephen Turnbull (April 2001 - January 2003, March 2004 - present, 21.2.47 - 21.4.12, 21.5.2 - 21.5.7, 21.5.17 - present) +@item +Vin Shelton (May 2003 - present, 21.4.13 - present) +@item +Steve Youngs (July 2002 - September 2003, 21.5.8 - 21.5.16) +@item +Martin Buchholz (December 1998, November 1999 - May 2001, 21.2.7 - 21.2.8, 21.2.21 - 21.2.46, 21.5.0 - 21.5.1) +@item +Steve Baur (early 1997 - December 1998, February 1999 - November 1999, 19.15 - 21.2.5, 21.2.9 - 21.2.20) +@item +Andy Piper (December 1998, 21.2.6) +@item +Chuck Thompson (June 1994 - September 1996, 19.11 - 19.14) +@item +Jamie Zawinski (April 1991 - June 1994, 19.0 - 19.10) +@end itemize + +The recent overlapping dates are intentional, since two or three trees +are maintained simultaneously at any point. + +Other major support work: + +@itemize @minus +@item +Adrian Aichner wrote and maintains the web site. +@item +Stephen Turnbull has produced many of the beta and semi-stable releases +and has attempted to be the "face" of XEmacs on the newsgroups and +mailing lists. +@item +Steve Youngs currently produces the beta releases (???). +@item +Steve Youngs, Ville Skytta, and now Norbert Koch have taken turns +maintaining the packages. +@item +Vin Shelton maintains the stable releases. +@item +Testing - #### Norbert, Adrian, ??? +@end itemize + +Portraits and email of some of the major developers: + +@itemize @bullet +@item @email{andy@@xemacs.org, Andy Piper} +@html +
Portrait of Andy Piper
+@end html + +@item @email{ben@@xemacs.org, Ben Wing} +@html +
Portrait of Ben Wing
+@end html + +@item @email{cthomp@@xemacs.org, Chuck Thompson} +@html +
Portrait of Chuck Thompson
+@end html + +@item @email{hniksic@@xemacs.org, Hrvoje Niksic} + +@html +
Portrait of Hrvoje Niksic
+@end html + +@item @email{jwz@@jwz.org, Jamie Zawinski} +@html +
Portrait of Jamie Zawinski
+@end html + +@item @email{martin@@xemacs.org, Martin Buchholz} +@html +
Portrait of Martin Buchholz
+@end html + +@item @email{mly@@adoc.xerox.com, Richard Mlynarik} +@html +
Portrait of Richard Mlynarik
+@end html + +@item @email{stephen@@xemacs.org, Stephen Turnbull} + +@item @email{steve@@xemacs.org, Steve Baur} +@html +
Portrait of Steve Baur
+@end html +@end itemize + +Many other people have contributed to XEmacs; this is partially +enumerated in the @samp{About XEmacs} option in the Help menu. + +@node Q1.0.6, Q1.1.1, Q1.0.5, Introduction +@unnumberedsubsec Q1.0.6: Who wrote the FAQ? + +The current version of this FAQ was created by @email{ben@@xemacs.org, +Ben Wing}. + +Previous contributors to the FAQ include + +@itemize @bullet +@item @email{steve@@xemacs.org, SL Baur} + +@item @email{hniksic@@xemacs.org, Hrvoje Niksic} + +@item @email{binge@@aloft.att.com, Curtis.N.Bingham} + +@item @email{bruncott@@dormeur.inria.fr, Georges Brun-Cottan} + +@item @email{rjc@@cogsci.ed.ac.uk, Richard Caley} + +@item @email{cognot@@ensg.u-nancy.fr, Richard Cognot} + +@item @email{daku@@nortel.ca, Mark Daku} + +@item @email{wgd@@martigny.ai.mit.edu, William G. Dubuque} + +@item @email{eeide@@cs.utah.edu, Eric Eide} + +@item @email{af@@biomath.jussieu.fr, Alain Fauconnet} + +@item @email{cflatter@@nrao.edu, Chris Flatters} + +@item @email{ginsparg@@adra.com, Evelyn Ginsparg} + +@item @email{hall@@aplcenmp.apl.jhu.edu, Marty Hall} + +@item @email{dkindred@@cmu.edu, Darrell Kindred} + +@item @email{dmoore@@ucsd.edu, David Moore} + +@item @email{arup+@@cmu.edu, Arup Mukherjee} + +@item @email{nickel@@prz.tu-berlin.de, Juergen Nickelsen} + +@item @email{powell@@csl.ncsa.uiuc.edu, Kevin R. Powell} + +@item @email{dworkin@@ccs.neu.edu, Justin Sheehy} + +@item @email{stig@@hackvan.com, Stig} + +@item @email{Aki.Vehtari@@hut.fi, Aki Vehtari} +@end itemize + +@unnumberedsec 1.1: Getting XEmacs + +@node Q1.1.1, Q1.1.2, Q1.0.6, Introduction +@unnumberedsubsec Q1.1.1: Where can I find XEmacs? + +To download XEmacs, visit the XEmacs WWW page at +@uref{http://www.xemacs.org/Download/}. The most up-to-date list of +distribution sites can always be found there. Try to pick a site that +is networkologically close to you. If you know of other mirrors of +the XEmacs archives, please send e-mail to +@uref{mailto:webmaster@@xemacs.org} and we will list them here as well. + +The canonical distribution point is ftp.xemacs.org, available either +through HTTP (@uref{http://ftp.xemacs.org/}) or anonymous FTP +(@uref{ftp://ftp.xemacs.org/pub/xemacs/}). + +@node Q1.1.2, Q1.1.3, Q1.1.1, Introduction +@unnumberedsubsec Q1.1.2: Are binaries available? MS Windows binaries are available at @uref{http://www.xemacs.org/Download/win32/} for the native versions @@ -691,8 +1007,790 @@ configure script that is able to automatically detect most aspects of the configuration of your particular system. -@node Q1.0.5, Q1.0.6, Q1.0.4, Introduction -@unnumberedsubsec Q1.0.5: How does XEmacs differ from GNU Emacs? +@node Q1.1.3, Q1.1.4, Q1.1.2, Introduction +@unnumberedsubsec Q1.1.3: How do I get the bleeding-edge sources? + +If you are interested in developing XEmacs, or getting the absolutely most +recent, up-to-the-moment, bleeding-edge source code, you can directly +access the master CVS source tree (read-only, of course, until you ask for +and are granted permission to directly modify portions of the source tree) +at cvs.xemacs.org. Directions on how to access the source tree are located +at @uref{http://www.xemacs.org/Develop/cvsaccess.html}. + +Nightly CVS snapshots are available at +@uref{http://www.dk.xemacs.org/Download/CVS-snapshots/}. + +@node Q1.1.4, Q1.2.1, Q1.1.3, Introduction +@unnumberedsubsec Q1.1.4: Where can I obtain a printed copy of the XEmacs User's Manual? + +Pre-printed manuals are not available. If you are familiar with +TeX, you can generate your own manual from the XEmacs sources. + +HTML and Postscript versions of XEmacs manuals are available from the +XEmacs web site at +@uref{http://www.xemacs.org/Documentation/index.html}. + +@unnumberedsec 1.2: Versions for Different Operating Systems + +@node Q1.2.1, Q1.2.2, Q1.1.4, Introduction +@unnumberedsubsec Q1.2.1: Do I need X11 to run XEmacs? + +No. The name @dfn{XEmacs} is unfortunate in the sense that it is +@strong{not} an X Window System-only version of Emacs. XEmacs has +full color support on a color-capable character terminal. + +@node Q1.2.2, Q1.2.3, Q1.2.1, Introduction +@unnumberedsubsec Q1.2.2: What versions of Unix does XEmacs run on? + +For problems with particular machines and versions of Unix, see the +@file{PROBLEMS} file. + +Much effort has gone into making XEmacs work on as many different +machines, configurations, and compilers as possible. + +Much effort has gone into making XEmacs 64-bit clean. + +Much effort has gone into removing system-specific code, and replacing +such code with autodetection at configure time. + +The XEmacs core should build "out of the box" on most Unix-like systems. + +XEmacs 21.2 was tested and @samp{make check} succeeded on these Unix +configurations as of 2001-02-10: + +@example +alphaev56-dec-osf4.0e (both Compaq C and gcc) +i386-unknown-freebsd4.2 +i386-unknown-netbsdelf1.5 +i586-sco-sysv5uw7.0.1 (both SCO's cc and gcc) +i686-pc-linux-gnu +hppa2.0-hp-hpux10.20 (both HP's ANSI cc and gcc) +mips-sgi-irix6.5 (both MIPSpro cc and gcc) +rs6000-ibm-aix4.3.0.0 (both IBM's xlc and gcc) +sparc-sun-solaris2.6 (both Sun's Forte C and gcc) +sparc-sun-solaris2.7 (both Sun's Forte C and gcc) +sparc-sun-sunos4.1.4 (gcc) +@end example + +Some systems have a dual mode 32-bit/64-bit compiler. On most of +these, XEmacs requires the @samp{--pdump} configure option to build +correctly with the 64-bit version of the compiler. + +@example +mips-sgi-irix6.5, CC="gcc -mabi=64" +mips-sgi-irix6.5, CC="cc -64" +rs6000-ibm-aix4.3.0.0, CC="cc -q64" +@end example + +On most of these systems, XEmacs also builds with a C++ compiler, +but not "out of the box". This feature is only for use by the +maintainers. + +XEmacs 21.2 is known @emph{not} to work on any machines with m680x0 +processors. Sorry, all you sun3 and Unix PC nostalgia buffs out there. + +VMS has never been supported by XEmacs. In fact, all the old VMS code +inherited from Emacs has been removed. Sorry, all you VMS fans out there. + +@node Q1.2.3, Q1.2.4, Q1.2.2, Introduction +@unnumberedsubsec Q1.2.3: Is there a port of XEmacs to Microsoft Windows? + +Yes. Beginning with release 21.0, XEmacs has worked under MS Windows +and is fully-featured and actively developed. A group of dedicated +developers actively maintains and improves the Windows-specific +portions of the code. Some of the core developers, in fact, use +Windows as their only development environment, and some features, such +as printing, actually work better on Windows than native Unix and Mac +OS X. The mailing list at @email{xemacs-winnt@@xemacs.org} is dedicated +to that effort (please use the -request address to +subscribe). (Despite its name, XEmacs actually works on all versions +of Windows.) + +The list name is misleading, as XEmacs supports and has been compiled on +Windows 95, Windows 98, Windows NT, Windows 2000, Windows ME, Windows +XP, and all newer versions of Windows. The MS Windows-specific code is +based on Microsoft Win32 API, and will not work on MS Windows 3.x or on +MS-DOS. + +XEmacs also supports the Cygwin and MinGW development and runtime +environments, where it also uses native Windows code for graphical +features. In addition, under Cygwin it is possible to compile XEmacs +to use an X server (and XFree86 is available as part of the standard +Cygwin installation). + +@node Q1.2.4, Q1.2.5, Q1.2.3, Introduction +@unnumberedsubsec Q1.2.4: Can I build XEmacs on MS Windows with X support? Do I need to? + +Yes, you can, but no you do not need to. In fact, we recommend that you +use a native-GUI version unless you have a specific need for an X +version. + +@node Q1.2.5, Q1.2.6, Q1.2.4, Introduction +@unnumberedsubsec Q1.2.5: What are Cygwin and MinGW, and do I need them to run XEmacs? + +To answer the second part of the question: No, you, you don't need +Cygwin or MinGW to build or to run XEmacs. But if you have them and +want to use them, XEmacs supports these environments. + +(One important reason to support Cygwin is that it lets the MS Windows +developers test out their code in a Unix environment without actually +having to have a Unix machine around. For this reason alone, Cygwin +support is likely to remain supported for a long time in XEmacs. Same +goes for the X support under Cygwin, for the same reasons. MinGW +support, on the other hand, depends on volunteers to keep it up to date; +but this is generally not hard.) + +Cygwin is a set of tools providing Unix-like API on top of Win32. +It makes it easy to port large Unix programs without significant +changes to their source code. It is a development environment as well +as a runtime environment. + +When built with Cygwin, XEmacs supports all display types -- TTY, X & +Win32 GUI, and can be built with support for all three simultaneously. +If you build with Win32 GUI support then the Cygwin version uses the +majority of the Windows-specific code, which is mostly related to +display. If you want to build with X support you need X libraries (and +an X server to display XEmacs on); see @ref{Q2.2.7}. TTY and Win32 GUI +require no additional libraries beyond what comes standard with Cygwin. + +The advantages of the Cygwin version are that it integrates well with +the Cygwin environment for existing Cygwin users; uses configure so +building with different features is very easy; and actively supports X & +TTY. Furthermore, the entire Cygwin environment and compiler are free, +whereas Visual C++ costs money. + +The disadvantage is that it requires the whole Cygwin environment, +whereas the native port requires only a suitable MS Windows compiler. +Also, it follows the Unix filesystem and process model very closely +(some will undoubtedly view this as an advantage). + +See @uref{http://www.cygwin.com/} for more information on +Cygwin. + +MinGW is a collection of header files and import libraries that allow +one to use GCC under the Cygwin environment to compile and produce +exactly the same native Win32 programs that you can using Visual C++. +Programs compiled with MinGW make use of the standard Microsoft runtime +library @file{MSVCRT.DLL}, present on all Windows systems, and look, +feel, and act like a standard Visual-C-produced application. (The only +difference is the compiler.) This means that, unlike a +standardly-compiled Cygwin application, no extra runtime support +(e.g. Cygwin's @file{cygwin1.dll}) is required. This, along with the +fact that GCC is free (and works in a nice Unix-y way in a nice Unix-y +environment, for those die-hard Unix hackers out there), is the main +advantage of MinGW. It is also potentially faster than Cygwin because +it has less overhead when calling Windows, but you lose the POSIX +emulation layer, which makes Unix programs harder to port. (But this is +irrelevant for XEmacs since it's already ported to Win32.) + +See @uref{http://www.mingw.org/} for more information on MinGW. + +@node Q1.2.6, Q1.2.7, Q1.2.5, Introduction +@unnumberedsubsec Q1.2.6: What are the differences between the various MS Windows emacsen? + +XEmacs, Win-Emacs, DOS Emacs, NT Emacs, this is all very confusing. +Could you briefly explain the differences between them? + +Here is a recount of various Emacs versions running on MS Windows: + +@itemize @bullet + +@item +XEmacs + +@itemize @minus + +@item +Beginning with XEmacs 19.12, XEmacs' architecture was redesigned +in such a way to allow clean support of multiple window systems. At +this time the TTY support was added, making X and TTY the first two +"window systems" supported by XEmacs. The 19.12 design is the basis for +the current native MS Windows code. + +@item +Some time during 1997, David Hobley (soon joined by Marc Paquette) +imported some of the NT-specific portions of GNU Emacs, making XEmacs +with X support compile under Windows NT, and creating the "X" port. + +@item +Several months later, Jonathan Harris sent out initial patches to use +the Win32 API, thus creating the native port. Since then, various +people have contributed, including Kirill M. Katsnelson (contributed +support for menubars, subprocesses and network, as well as loads of +other code), Andy Piper (ported XEmacs to Cygwin environment, +contributed Windows unexec, Windows-specific glyphs and toolbars code, +and more), Ben Wing (loads of improvements; primary MS Windows developer +since 2000), Jeff Sparkes (contributed scrollbars support) and many +others. +@end itemize + +@item +NT Emacs + +@itemize @minus + +@item +NT Emacs was an early version of GNU Emacs 19 modified to compile and +run under MS Windows 95 and NT using the native Win32 API. It was +written by Geoff Voelker, and has long since been incorporated into +the mainline GNU Emacs distribution. +@end itemize + +@item +Win-Emacs + +@itemize @minus + +@item +Win-Emacs was a port of Lucid Emacs 19.6 to MS Windows using X +compatibility libraries. Win-Emacs was written by Ben Wing. The MS +Windows code never made it back to Lucid Emacs, and its creator (Pearl +Software) has long since gone out of business. +@end itemize + +@item +GNU Emacs for DOS + +@itemize @minus + +@item +GNU Emacs features support for MS-DOS and DJGPP (D.J. Delorie's DOS +port of GCC). Such an Emacs is heavily underfeatured, because it does +not support long file names, lacks proper subprocesses support, and +is far too big compared with typical DOS editors. +@end itemize + +@item +GNU Emacs compiled with Win32 + +@itemize @minus + +@item +Starting with GNU Emacs 19.30, it has been possible to compile GNU Emacs +under MS Windows using the DJGPP compiler and X libraries. The result +is very similar to GNU Emacs compiled under MS DOS, only it works +somewhat better because it runs in 32-bit mode, makes use of all the +system memory, supports long file names, etc. +@end itemize + +@end itemize + +@node Q1.2.7, Q1.2.8, Q1.2.6, Introduction +@unnumberedsubsec Q1.2.7: How does the port cope with differences in the Windows user interface? + +The XEmacs (and Emacs in general) user interface is pretty different +from what is expected of a typical MS Windows program. How does the MS +Windows port cope with it? + +As a general rule, we follow native MS Windows conventions as much as +possible. 21.4 is a fairly complete Windows application, supporting +native printing, system file dialog boxes, tool tips, etc. In cases +where there's a clear UI conflict, we currently use normal Unix XEmacs +behavior by default, but make sure the MS Windows "look and feel" (mark +via shift-arrow, self-inserting deletes region, Alt selects menu items, +etc.) is easily configurable (respectively: using the variable +@code{shifted-motion-keys-select-region} in 21.4 and above [it's in fact +the default in these versions], or the @file{pc-select} package; using +the @file{pending-del} package; and setting the variable +@code{menu-accelerator-enabled} to @code{menu-force} in 21.4 and above). +In fact, if you use the sample @file{init.el} file as your init file, +you will get all these behaviors automatically turned on. + +In future versions, some of these features might be turned on by +default in the MS Windows environment. + +@node Q1.2.8, Q1.2.9, Q1.2.7, Introduction +@unnumberedsubsec Q1.2.8: Is there a port of XEmacs to the Macintosh? + +Yes. + +XEmacs 21.5 (perhaps 21.4 also?) works on MacOS X, although it certainly +will not feel very much like a Mac application as it has no Mac-specific +code in it. + +There is also a port of XEmacs 19.14 that works on all recent versions +of MacOS, from 8.1 through MacOS X, by @email{pjarvis@@ispchannel.com, +Pitts Jarvis} (recently deceased). It runs in an equivalent of TTY +mode only (one single Macintosh window, 25 colors), but has a large +number of Mac-specific additions. It's available at +@uref{http://homepage.mac.com/pjarvis/xemacs.html}. + +@node Q1.2.9, Q1.2.10, Q1.2.8, Introduction +@unnumberedsubsec Q1.2.9: Is there a port of XEmacs to the Macintosh? + +Yes. + +XEmacs 21.5 (perhaps 21.4 also?) works on MacOS X, although it certainly +will not feel very much like a Mac application as it has no Mac-specific +code in it. + +There is also a port of XEmacs 19.14 that works on all recent versions +of MacOS, from 8.1 through MacOS X, by @email{pjarvis@@ispchannel.com, +Pitts Jarvis} (recently deceased). It runs in an equivalent of TTY +mode only (one single Macintosh window, 25 colors), but has a large +number of Mac-specific additions. It's available at +@uref{http://homepage.mac.com/pjarvis/xemacs.html}. + +@node Q1.2.10, Q1.2.11, Q1.2.9, Introduction +@unnumberedsubsec Q1.2.10: Is there a port of XEmacs to MS-DOS? + +No. We have never supported running on MS-DOS or Windows 3.1, and in +fact have long since deleted all MS-DOS-related code. + +@node Q1.2.11, Q1.2.12, Q1.2.10, Introduction +@unnumberedsubsec Q1.2.11: Is there a port of XEmacs to OS/2? + +No, but Alexander Nikolaev was at one point +working on it. + +@node Q1.2.12, Q1.2.13, Q1.2.11, Introduction +@unnumberedsubsec Q1.2.12: Is there a port of XEmacs to NextStep? + +Carl Edman, apparently no longer at @email{cedman@@princeton.edu}, did +the port of GNU Emacs to NeXTstep and expressed interest in doing the +XEmacs port, but never went any farther. + +@node Q1.2.13, Q1.3.1, Q1.2.12, Introduction +@unnumberedsubsec Q1.2.13: Is there a port of XEmacs to VMS? + +VMS has never been supported by XEmacs. In fact, all the old VMS code +inherited from GNU Emacs has been removed. Sorry, all you VMS fans +out there. + +@unnumberedsec 1.3: Getting Started + +@node Q1.3.1, Q1.3.2, Q1.2.13, Introduction +@unnumberedsubsec Q1.3.1: What is an @file{init.el} or @file{.emacs} and is there a sample one? + +The @file{init.el} or @file{.emacs} file is used to customize XEmacs to +your tastes. Starting in 21.4, the preferred location for the init file +is @file{~/.xemacs/init.el}; in previous versions, it was +@file{~/.emacs}. 21.4 still accepts the old location, but the first +time you run it, it will ask to migrate your file to the new location. +If you answer yes, the file will be moved, and a "compatibility" +@file{.emacs} file will be placed in the old location so that you can +still run older versions of XEmacs, and versions of GNU Emacs, which +expect the old location. The @file{.emacs} file present is just a stub +that loads the real file in @file{~/.xemacs/init.el}. + +No two init files are alike, nor are they expected to be alike, but +that's the point. The XEmacs distribution contains an excellent starter +example in the @file{etc/} directory called @file{sample.init.el} +(starting in 21.4) or @file{sample.emacs} in older versions. Copy this +file from there to @file{~/.xemacs/init.el} (starting in 21.4) or +@file{~/.emacs} in older versions, where @samp{~} means your home +directory, of course. Then edit it to suit. + +You may bring the @file{sample.init.el} or @file{sample.emacs} file into +an XEmacs buffer from the menubar. (The menu entry for it is always +under the @samp{Help} menu, but its location under that has changed in +various versions. Recently, look under the @samp{Samples} submenu.) To +determine the location of the @file{etc/} directory type the command +@kbd{C-h v data-directory @key{RET}}. + +@node Q1.3.2, Q1.3.3, Q1.3.1, Introduction +@unnumberedsubsec Q1.3.2: Where do I put my @file{init.el} file? + +@file{init.el} is the name of the init file starting with 21.4, and is +located in the subdirectory @file{.xemacs/} of your home directory. In +prior versions, the init file is called @file{.emacs} and is located in +your home directory. + +Your home directory under Windows is determined by the @samp{HOME} +environment variable. If this is not set, it defaults to @samp{C:\}. +To set this variable, modify @file{AUTOEXEC.BAT} under Windows 95/98, or +select @samp{Control Panel->System->Advanced->Environment Variables...} +under Windows NT/2000. + +@node Q1.3.3, Q1.3.4, Q1.3.2, Introduction +@unnumberedsubsec Q1.3.3: Can I use the same @file{init.el} with the other Emacs? + +Yes. The sample @file{init.el} included in the XEmacs +distribution will show you how to handle different versions and flavors +of Emacs. + +@node Q1.3.4, Q1.3.5, Q1.3.3, Introduction +@unnumberedsubsec Q1.3.4: Any good XEmacs tutorials around? + +There's the XEmacs tutorial available from the Help Menu under +@samp{Help->Tutorials}, or by typing @kbd{C-h t}. To check whether +it's available in a non-english language, type @kbd{C-u C-h t TAB}, type +the first letters of your preferred language, then type @key{RET}. + +@comment There's an Emacs Lisp tutorial at +@comment +@comment @example +@comment @uref{ftp://prep.ai.mit.edu/pub/gnu/emacs-lisp-intro-1.04.tar.gz}. +@comment @end example +@comment +@comment @email{erik@@petaxp.rug.ac.be, Erik Sundermann} has made a tutorial web +@comment page at +@comment @iftex +@comment @* +@comment @end iftex +@comment @uref{http://petaxp.rug.ac.be/~erik/xemacs/}. + +@node Q1.3.5, Q1.3.6, Q1.3.4, Introduction +@unnumberedsubsec Q1.3.5: May I see an example of a useful XEmacs Lisp function? + +The following function does a little bit of everything useful. It does +something with the prefix argument, it examines the text around the +cursor, and it's interactive so it may be bound to a key. It inserts +copies of the current word the cursor is sitting on at the cursor. If +you give it a prefix argument: @kbd{C-u 3 M-x double-word} then it will +insert 3 copies. + +@lisp +(defun double-word (count) + "Insert a copy of the current word underneath the cursor" + (interactive "*p") + (let (here there string) + (save-excursion + (forward-word -1) + (setq here (point)) + (forward-word 1) + (setq there (point)) + (setq string (buffer-substring here there))) + (while (>= count 1) + (insert string) + (decf count)))) +@end lisp + +The best way to see what is going on here is to let XEmacs tell you. +Put the code into an XEmacs buffer, and do a @kbd{C-h f} with the cursor +sitting just to the right of the function you want explained. Eg. move +the cursor to the SPACE between @code{interactive} and @samp{"*p"} and +hit @kbd{C-h f} to see what the function @code{interactive} does. Doing +this will tell you that the @code{*} requires a writable buffer, and +@code{p} converts the prefix argument to a number, and +@code{interactive} allows you to execute the command with @kbd{M-x}. + +@node Q1.3.6, Q1.3.7, Q1.3.5, Introduction +@unnumberedsubsec Q1.3.6: And how do I bind it to a key? + +To bind to a key do: + +@lisp +(global-set-key "\C-cd" 'double-word) +@end lisp + +Or interactively, @kbd{M-x global-set-key} and follow the prompts. + +@node Q1.3.7, Q1.3.8, Q1.3.6, Introduction +@unnumberedsubsec Q1.3.7: What's the difference between a macro and a function? + +Quoting from the Lisp Reference (a.k.a @dfn{Lispref}) Manual: + +@dfn{Macros} enable you to define new control constructs and other +language features. A macro is defined much like a function, but instead +of telling how to compute a value, it tells how to compute another Lisp +expression which will in turn compute the value. We call this +expression the @dfn{expansion} of the macro. + +Macros can do this because they operate on the unevaluated expressions +for the arguments, not on the argument values as functions do. They can +therefore construct an expansion containing these argument expressions +or parts of them. + +Do not confuse the two terms with @dfn{keyboard macros}, which are +another matter, entirely. A keyboard macro is a key bound to several +other keys. Refer to manual for details. + +@node Q1.3.8, Q1.4.1, Q1.3.7, Introduction +@unnumberedsubsec Q1.3.8: What is @code{Custom}? + +@code{Custom} is a system for customizing XEmacs options. + +You can access @code{Advanced (Customize)} from the @code{Options} menu +or invoking one of customize commands by typing eg. +@kbd{M-x customize}, @kbd{M-x customize-face}, +@kbd{M-x customize-variable} or @kbd{M-x customize-apropos}. + +There is also new @samp{browser} mode for Customize. +Try it out with @kbd{M-x customize-browse} + +@unnumberedsec 1.4: Getting Help + +@node Q1.4.1, Q1.4.2, Q1.3.8, Introduction +@unnumberedsubsec Q1.4.1: Where can I get help? + +Probably the easiest way, if everything is installed, is to use Info, by +pressing @kbd{C-h i}, or looking for an Info item on the +Help Menu. @kbd{M-x apropos} can be used to look for particular commands. + +For items not found in the manual, try reading this FAQ +and reading the Usenet group comp.emacs.xemacs. + +If you choose to post to a newsgroup, @strong{please use +comp.emacs.xemacs}. Please do not post XEmacs related questions to +gnu.emacs.help. + +If you cannot post or read Usenet news, there is a corresponding mailing +list @email{xemacs-news@@xemacs.org} which is available. It can be +subscribed to via the Mailman Web interface or by sending mail to to +@email{xemacs-news-request@@xemacs.org} with @samp{subscribe} in the +body of the message. See also +@uref{http://www.xemacs.org/Lists/#xemacs-news}. To cancel a +subscription, you may use the @email{xemacs-news-request@@xemacs.org} +address or the Web interface. Send a message with a subject of +@samp{unsubscribe} to be removed. + +@node Q1.4.2, Q1.4.3, Q1.4.1, Introduction +@unnumberedsubsec Q1.4.2: Which mailing lists are there? + +For complete, up-to-date info on the lists and how to subscribe, see +@uref{http://www.xemacs.org/Lists/}. + +@table @samp + +@item comp.emacs.xemacs +is a Usenet newsgroup +for XEmacs users to discuss problems and issues that arise +for them. It's not generally an appropriate place to ask +about apparent bugs (use @samp{xemacs-beta}), or future plans +(use @samp{xemacs-design}). + +@item xemacs-announce +is a read-only, low +volume list for announcements concerning the XEmacs project +and new releases of the XEmacs software. + +@item xemacs-beta +is an open list for bug +reports about beta versions of XEmacs. This includes the bug +reports themselves, by both users and developers, as well as +queries, follow-ups, and discussions further determining their +nature and status. This is the primary channel for this kind +of discussion; related code changes will usually not be +applied until they have been discussed here. When such +discussions touch on significant changes to the code (in +particular, structural changes), or on changes to API's or +external functionality, they should be moved to +@samp{xemacs-design}. Requests and proposals for +non-bug-related changes do not belong on @samp{xemacs-beta}, +and should be sent to @samp{xemacs-design} instead. + +@item xemacs-beta-ja +is an open list for bug +reports and design discussion related to Mule features, +including Japanese handling, in beta versions of XEmacs. +Japanese is the preferred language of discussion. For most +timely presentation to reviewers, please consider sending +appropriate discussion to @samp{xemacs-mule} or +@samp{xemacs-design} in English when convenient for +the participants in discussion. When possible, bug reports +not related to Mule (including Japanese) should be reported on +@samp{xemacs-beta} in English. + +@item xemacs-buildreports +is an open list for +submission of build-reports on beta versions of XEmacs. For +information on what the build-reports should contain, please +see the `etc/BETA' file which is included in each beta +distribution. + +@item xemacs-cvs +is a read-only list for notices +and information on what has been committed to the XEmacs CVS +trees, by whom, and for what. + +@item xemacs-design +is an open list for +discussing the design of XEmacs. This includes discussion +about planned and ongoing changes to functionality and API +changes and additions as well as requests for them. This is +the primary channel for this kind of discussion; related code +changes will usually not be applied until they have been +discussed here. This does not include bug reports, which go +to @samp{xemacs-beta}. + +@item xemacs-mule +is an open mailing list for +discussion of International extensions to XEmacs including +Mule, XIM, I18n issues, etc, and is not confined to +developmental issues. This list is not restricted to +English, postings in all languages are welcome. + +@item xemacs-news +is an open list for discussion +and bug reporting for XEmacs. This mailing list is +bi-directionally gatewayed with the USENET newsgroup +comp.emacs.xemacs. + +@item xemacs-nt +is a developers-only mailing +list and is intended for people who wish to work actively on +the porting of XEmacs to Microsoft Windows NT and Microsoft +Windows '95. + +@item xemacs-patches +is an open, moderated +list for submission of patches to the XEmacs distribution +and its packages. Anyone may subscribe or submit to +xemacs-patches, but all submissions are reviewed by the list +moderator before they are distributed to the +list. Discussion is not appropriate on xemacs-patches. + +@item xemacs-users-ja +is an open list for +discussion and bug reporting for XEmacs. Japanese is the +preferred language of discussion. It is not gated to +comp.emacs.xemacs or the @samp{xemacs} list. For +fastest response, bugs not specifically related to Japanese +or Mule features should be reported on +@samp{xemacs-beta} (in English). + +@item xemacs-users-ru +is an open list for +discussion and bug reporting for XEmacs. Russian is the +preferred language of discussion. It is not gated to +comp.emacs.xemacs or the @samp{xemacs} list. For +fastest response, bugs not specifically related to Russian +or Mule features should be reported on +@samp{xemacs-beta} (in English). +@end table + +@node Q1.4.3, Q1.4.4, Q1.4.2, Introduction +@unnumberedsubsec Q1.4.3: Where are the mailing lists archived? + +The archives can be found at @uref{http://list-archive.xemacs.org} + +@node Q1.4.4, Q1.4.5, Q1.4.3, Introduction +@unnumberedsubsec Q1.4.4: How can I get two instances of info? + +Before 21.4, you can't. The @code{info} package does not provide for +multiple info buffers. In 21.4, this should be fixed. #### how? + +@node Q1.4.5, Q1.5.1, Q1.4.4, Introduction +@unnumberedsubsec Q1.4.5: How do I add new Info directories? + +You use something like: + +@lisp +(setq Info-directory-list (cons + (expand-file-name "~/info") + Info-default-directory-list)) +@end lisp + +@email{davidm@@prism.kla.com, David Masterson} writes: + +@quotation +Emacs Info and XEmacs Info do many things differently. If you're trying to +support a number of versions of Emacs, here are some notes to remember: + +@enumerate +@item +Emacs Info scans @code{Info-directory-list} from right-to-left while +XEmacs Info reads it from left-to-right, so append to the @emph{correct} +end of the list. + +@item +Use @code{Info-default-directory-list} to initialize +@code{Info-directory-list} @emph{if} it is available at startup, but not +all Emacsen define it. + +@item +Emacs Info looks for a standard @file{dir} file in each of the +directories scanned from #1 and magically concatenates them together. + +@item +XEmacs Info looks for a @file{localdir} file (which consists of just the +menu entries from a @file{dir} file) in each of the directories scanned +from #1 (except the first), does a simple concatenation of them, and +magically attaches the resulting list to the end of the menu in the +@file{dir} file in the first directory. +@end enumerate + +Another alternative is to convert the documentation to HTML with +texi2html and read it from a web browser like Lynx or W3. +@end quotation + +@unnumberedsec 1.5: Contributing to XEmacs + +@node Q1.5.1, Q1.5.2, Q1.4.5, Introduction +@unnumberedsubsec Q1.5.1: How do I submit changes to the FAQ? + +The FAQ is actively maintained and modified regularly. All links should +be up to date. Unfortunately, some of the information is out of date -- +a situation which the FAQ maintainer is working on. All submissions are +welcome, please e-mail submissions to @email{faq@@xemacs.org, XEmacs FAQ +maintainers}. + +Please make sure that @samp{XEmacs FAQ} appears on the Subject: line. +If you think you have a better way of answering a question, or think a +question should be included, we'd like to hear about it. Questions and +answers included into the FAQ will be edited for spelling and grammar +and will be attributed. Answers appearing without attribution are +either from versions of the FAQ dated before May 1996 or are from +previous FAQ maintainers. Answers quoted from Usenet news articles will +always be attributed, regardless of the author. + +@node Q1.5.2, Q1.5.3, Q1.5.1, Introduction +@unnumberedsubsec Q1.5.2: How do I become a beta tester? + +Send an email message to @email{xemacs-beta-request@@xemacs.org} with +the line @samp{subscribe} in the body of the message. + +Be prepared to get your hands dirty, as beta testers are expected to +identify problems as best they can. + +@node Q1.5.3, Q1.6.1, Q1.5.2, Introduction +@unnumberedsubsec Q1.5.3: How do I contribute to XEmacs itself? + +It depends on the knowledge and time you possess. If you are able, by +all means become a beta tester (@pxref{Q1.5.2}). If you are a +programmer, try to build XEmacs and see if you can improve it. + +Otherwise, you can still help by using XEmacs as your everyday editor +(for pre-built binary versions, @pxref{Q1.1.2}) and reporting bugs you +find to the mailing list. + +Another area where we need help is the documentation: We need good +documentation for building XEmacs and for using it. This FAQ is a +small step in that direction. + +Ben Wing @email{ben@@xemacs.org} writes: + +@quotation +BTW if you have a wish list of things that you want added, you have to +speak up about it! More specifically, you can do the following if you +want a feature added (in increasing order of usefulness): + +@itemize @bullet +@item +Make a posting about a feature you want added. + +@item +Become a beta tester and make more postings about those same features. + +@item +Convince us that you're going to use the features in some cool and +useful way. + +@item +Come up with a clear and well-thought-out API concerning the features. + +@item +Write the code to implement a feature and send us a patch. +@end itemize + +(not that we're necessarily requiring you to write the code, but we can +always hope :) +@end quotation + +@unnumberedsec 1.6: Politics (XEmacs vs. GNU Emacs) + +@node Q1.6.1, Q1.6.2, Q1.5.3, Introduction +@unnumberedsubsec Q1.6.1: What is GNU Emacs? + +GNU Emacs and XEmacs are related open-source text editors. Both +derive from GNU Emacs version 18; the split between the two happened +in 1991 (for comparison, the oldest versions of GNU Emacs date from +1984). For information on GNU Emacs, see +@uref{http://www.gnu.org/software/emacs/emacs.html}. + +@node Q1.6.2, Q1.6.3, Q1.6.1, Introduction +@unnumberedsubsec Q1.6.2: How does XEmacs differ from GNU Emacs? For a detailed description of the differences between GNU Emacs and XEmacs and a detailed history of XEmacs, check out the @@ -850,11 +1948,11 @@ automatically qualify for CVS accounts for their packages. @end table -@node Q1.0.6, Q1.0.7, Q1.0.5, Introduction -@unnumberedsubsec Q1.0.6: How much does XEmacs differ? +@node Q1.6.3, Q1.6.4, Q1.6.2, Introduction +@unnumberedsubsec Q1.6.3: How much does XEmacs differ? RMS has asserted at times that XEmacs is merely a "patch" on top of -GNU Emacs (@pxref{Q1.0.7}). In fact, probably not more than 5% of the +GNU Emacs (@pxref{Q1.6.4}). In fact, probably not more than 5% of the code, if that, remains unchanged, and nearly 14 years of work has gone into XEmacs at this point. (GNU Emacs itself is only than 20 years old, and thus XEmacs has existed as a separate product for over 2/3 of @@ -870,8 +1968,8 @@ This stems from self-imposed licensing restrictions on the part of GNU Emacs -- and almost certainly out of hostility, as well.) -@node Q1.0.7, Q1.0.8, Q1.0.6, Introduction -@unnumberedsubsec Q1.0.7: Is XEmacs "GNU"? +@node Q1.6.4, Q1.6.5, Q1.6.3, Introduction +@unnumberedsubsec Q1.6.4: Is XEmacs "GNU"? RMS insists on the term "GNU XEmacs" and maintains that @@ -884,7 +1982,7 @@ @end quotation In fact, FSF is @emph{not} the copyright holder for most of the code, -as very little unmodified FSF code remains (@pxref{Q1.0.6}). +as very little unmodified FSF code remains (@pxref{Q1.6.3}). Furthermore, RMS's assertion that XEmacs is "GNU" seems rather bizarre to the XEmacs developers given RMS's hostility and general lack of @@ -897,8 +1995,8 @@ non-GNU software projects on the FSF web site, but again XEmacs is not one of them. -@node Q1.0.8, Q1.0.9, Q1.0.7, Introduction -@unnumberedsubsec Q1.0.8: What is the correct way to refer to XEmacs and GNU Emacs? +@node Q1.6.5, Q1.6.6, Q1.6.4, Introduction +@unnumberedsubsec Q1.6.5: What is the correct way to refer to XEmacs and GNU Emacs? Unfortunately even the naming of these two applications has become politicized. Much of this stems from RMS, who has a history of @@ -907,12 +2005,12 @@ Emacs" be used, which are neutral and acceptable to most people. RMS, however, is not willing to accept these terms. He insists that, if his product is called "GNU Emacs", then ours must be called "GNU -XEmacs". (For our opinion of this term, @xref{Q1.0.7}.) On the other +XEmacs". (For our opinion of this term, @xref{Q1.6.4}.) On the other hand, if our product is to be called "XEmacs", as we prefer, then his product must simply be called "Emacs". The intent of this seems clear: RMS wants to make sure the names reflect his view that his version is the "real" Emacs and ours is merely a derivative, -second-class product (@pxref{Q1.0.6}). +second-class product (@pxref{Q1.6.3}). The XEmacs developers hope that you will use the neutral terms "XEmacs" and "GNU Emacs" for these two specific products. "Emacs", on @@ -933,8 +2031,8 @@ to be insulting, so we refrain from using them as much as possible in preference to GNU Emacs.) -@node Q1.0.9, Q1.0.10, Q1.0.8, Introduction -@unnumberedsubsec Q1.0.9: Why haven't XEmacs and GNU Emacs merged? +@node Q1.6.6, Q1.7.1, Q1.6.5, Introduction +@unnumberedsubsec Q1.6.6: Why haven't XEmacs and GNU Emacs merged? There are currently irreconcilable differences in the views about technical, programming, design, organizational and legal matters @@ -1014,655 +2112,425 @@ that often result. Mail your questions to @email{xemacs-beta@@xemacs.org} and @email{emacs-devel@@gnu.org}. -@node Q1.0.10, Q1.0.11, Q1.0.9, Introduction -@unnumberedsubsec Q1.0.10: Where can I get help? - -Probably the easiest way, if everything is installed, is to use Info, by -pressing @kbd{C-h i}, or looking for an Info item on the -Help Menu. @kbd{M-x apropos} can be used to look for particular commands. - -For items not found in the manual, try reading this FAQ -and reading the Usenet group comp.emacs.xemacs. - -If you choose to post to a newsgroup, @strong{please use -comp.emacs.xemacs}. Please do not post XEmacs related questions to -gnu.emacs.help. - -If you cannot post or read Usenet news, there is a corresponding mailing -list @email{xemacs-news@@xemacs.org} which is available. It can be -subscribed to via the Mailman Web interface or by sending mail to to -@email{xemacs-news-request@@xemacs.org} with @samp{subscribe} in the -body of the message. See also -@uref{http://www.xemacs.org/Lists/#xemacs-news}. To cancel a -subscription, you may use the @email{xemacs-news-request@@xemacs.org} -address or the Web interface. Send a message with a subject of -@samp{unsubscribe} to be removed. - -@node Q1.0.11, Q1.0.12, Q1.0.10, Introduction -@unnumberedsubsec Q1.0.11: Where are the mailing lists archived? - -The archives can be found at @uref{http://list-archive.xemacs.org} - -@node Q1.0.12, Q1.0.13, Q1.0.11, Introduction -@unnumberedsubsec Q1.0.12: How do you pronounce XEmacs? - -The most common pronounciation is @samp{Eks eemax}. - -@node Q1.0.13, Q1.0.14, Q1.0.12, Introduction -@unnumberedsubsec Q1.0.13: What does XEmacs look like? - -Screen snapshots are available at -@uref{http://www.xemacs.org/About/Screenshots/index.html} -as part of the XEmacs website. - -@node Q1.0.14, Q1.1.1, Q1.0.13, Introduction -@unnumberedsubsec Q1.0.14: Where can I obtain a printed copy of the XEmacs User's Manual? - -Pre-printed manuals are not available. If you are familiar with -TeX, you can generate your own manual from the XEmacs sources. - -HTML and Postscript versions of XEmacs manuals are available from the -XEmacs web site at -@uref{http://www.xemacs.org/Documentation/index.html}. - -@unnumberedsec 1.1: Versions for Different Operating Systems - -@node Q1.1.1, Q1.1.2, Q1.0.14, Introduction -@unnumberedsubsec Q1.1.1: Do I need X11 to run XEmacs? - -No. The name @dfn{XEmacs} is unfortunate in the sense that it is -@strong{not} an X Window System-only version of Emacs. XEmacs has -full color support on a color-capable character terminal. - -@node Q1.1.2, Q1.1.3, Q1.1.1, Introduction -@unnumberedsubsec Q1.1.2: Is there a port of XEmacs to Microsoft Windows? - -Yes. Beginning with release 21.0, XEmacs has worked under MS Windows -and is fully-featured and actively developed. A group of dedicated -developers actively maintains and improves the Windows-specific -portions of the code. Some of the core developers, in fact, use -Windows as their only development environment, and some features, such -as printing, actually work better on Windows than native Unix and Mac -OS X. The mailing list at @email{xemacs-winnt@@xemacs.org} is dedicated -to that effort (please use the -request address to -subscribe). (Despite its name, XEmacs actually works on all versions -of Windows.) - -The list name is misleading, as XEmacs supports and has been compiled on -Windows 95, Windows 98, Windows NT, Windows 2000, Windows ME, Windows -XP, and all newer versions of Windows. The MS Windows-specific code is -based on Microsoft Win32 API, and will not work on MS Windows 3.x or on -MS-DOS. - -XEmacs also supports the Cygwin and MinGW development and runtime -environments, where it also uses native Windows code for graphical -features. In addition, under Cygwin it is possible to compile XEmacs -to use an X server (and XFree86 is available as part of the standard -Cygwin installation). - -@node Q1.1.3, Q1.1.4, Q1.1.2, Introduction -@unnumberedsubsec Q1.1.3: Can I build XEmacs on MS Windows with X support? Do I need to? - -Yes, you can, but no you do not need to. In fact, we recommend that you -use a native-GUI version unless you have a specific need for an X -version. - -@node Q1.1.4, Q1.1.5, Q1.1.3, Introduction -@unnumberedsubsec Q1.1.4: What are Cygwin and MinGW, and do I need them to run XEmacs? - -To answer the second part of the question: No, you, you don't need -Cygwin or MinGW to build or to run XEmacs. But if you have them and -want to use them, XEmacs supports these environments. - -(One important reason to support Cygwin is that it lets the MS Windows -developers test out their code in a Unix environment without actually -having to have a Unix machine around. For this reason alone, Cygwin -support is likely to remain supported for a long time in XEmacs. Same -goes for the X support under Cygwin, for the same reasons. MinGW -support, on the other hand, depends on volunteers to keep it up to date; -but this is generally not hard.) - -Cygwin is a set of tools providing Unix-like API on top of Win32. -It makes it easy to port large Unix programs without significant -changes to their source code. It is a development environment as well -as a runtime environment. - -When built with Cygwin, XEmacs supports all display types -- TTY, X & -Win32 GUI, and can be built with support for all three simultaneously. -If you build with Win32 GUI support then the Cygwin version uses the -majority of the Windows-specific code, which is mostly related to -display. If you want to build with X support you need X libraries (and -an X server to display XEmacs on); see @ref{Q2.2.7}. TTY and Win32 GUI -require no additional libraries beyond what comes standard with Cygwin. - -The advantages of the Cygwin version are that it integrates well with -the Cygwin environment for existing Cygwin users; uses configure so -building with different features is very easy; and actively supports X & -TTY. Furthermore, the entire Cygwin environment and compiler are free, -whereas Visual C++ costs money. - -The disadvantage is that it requires the whole Cygwin environment, -whereas the native port requires only a suitable MS Windows compiler. -Also, it follows the Unix filesystem and process model very closely -(some will undoubtedly view this as an advantage). - -See @uref{http://www.cygwin.com/} for more information on -Cygwin. - -MinGW is a collection of header files and import libraries that allow -one to use GCC under the Cygwin environment to compile and produce -exactly the same native Win32 programs that you can using Visual C++. -Programs compiled with MinGW make use of the standard Microsoft runtime -library @file{MSVCRT.DLL}, present on all Windows systems, and look, -feel, and act like a standard Visual-C-produced application. (The only -difference is the compiler.) This means that, unlike a -standardly-compiled Cygwin application, no extra runtime support -(e.g. Cygwin's @file{cygwin1.dll}) is required. This, along with the -fact that GCC is free (and works in a nice Unix-y way in a nice Unix-y -environment, for those die-hard Unix hackers out there), is the main -advantage of MinGW. It is also potentially faster than Cygwin because -it has less overhead when calling Windows, but you lose the POSIX -emulation layer, which makes Unix programs harder to port. (But this is -irrelevant for XEmacs since it's already ported to Win32.) - -See @uref{http://www.mingw.org/} for more information on MinGW. - -@node Q1.1.5, Q1.1.6, Q1.1.4, Introduction -@unnumberedsubsec Q1.1.5: What are the differences between the various MS Windows emacsen? - -XEmacs, Win-Emacs, DOS Emacs, NT Emacs, this is all very confusing. -Could you briefly explain the differences between them? - -Here is a recount of various Emacs versions running on MS Windows: - -@itemize @bullet - -@item -XEmacs - -@itemize @minus - -@item -Beginning with XEmacs 19.12, XEmacs' architecture was redesigned -in such a way to allow clean support of multiple window systems. At -this time the TTY support was added, making X and TTY the first two -"window systems" supported by XEmacs. The 19.12 design is the basis for -the current native MS Windows code. - -@item -Some time during 1997, David Hobley (soon joined by Marc Paquette) -imported some of the NT-specific portions of GNU Emacs, making XEmacs -with X support compile under Windows NT, and creating the "X" port. - -@item -Several months later, Jonathan Harris sent out initial patches to use -the Win32 API, thus creating the native port. Since then, various -people have contributed, including Kirill M. Katsnelson (contributed -support for menubars, subprocesses and network, as well as loads of -other code), Andy Piper (ported XEmacs to Cygwin environment, -contributed Windows unexec, Windows-specific glyphs and toolbars code, -and more), Ben Wing (loads of improvements; primary MS Windows developer -since 2000), Jeff Sparkes (contributed scrollbars support) and many -others. -@end itemize - -@item -NT Emacs - -@itemize @minus - -@item -NT Emacs was an early version of GNU Emacs 19 modified to compile and -run under MS Windows 95 and NT using the native Win32 API. It was -written by Geoff Voelker, and has long since been incorporated into -the mainline GNU Emacs distribution. -@end itemize - -@item -Win-Emacs - -@itemize @minus - -@item -Win-Emacs was a port of Lucid Emacs 19.6 to MS Windows using X -compatibility libraries. Win-Emacs was written by Ben Wing. The MS -Windows code never made it back to Lucid Emacs, and its creator (Pearl -Software) has long since gone out of business. -@end itemize - -@item -GNU Emacs for DOS - -@itemize @minus - -@item -GNU Emacs features support for MS-DOS and DJGPP (D.J. Delorie's DOS -port of GCC). Such an Emacs is heavily underfeatured, because it does -not support long file names, lacks proper subprocesses support, and -is far too big compared with typical DOS editors. -@end itemize - -@item -GNU Emacs compiled with Win32 - -@itemize @minus - -@item -Starting with GNU Emacs 19.30, it has been possible to compile GNU Emacs -under MS Windows using the DJGPP compiler and X libraries. The result -is very similar to GNU Emacs compiled under MS DOS, only it works -somewhat better because it runs in 32-bit mode, makes use of all the -system memory, supports long file names, etc. -@end itemize - -@end itemize - -@node Q1.1.6, Q1.1.7, Q1.1.5, Introduction -@unnumberedsubsec Q1.1.6: Is there a port of XEmacs to the Macintosh? - -Yes. - -XEmacs 21.5 (perhaps 21.4 also?) works on MacOS X, although it certainly -will not feel very much like a Mac application as it has no Mac-specific -code in it. - -There is also a port of XEmacs 19.14 that works on all recent versions -of MacOS, from 8.1 through MacOS X, by @email{pjarvis@@ispchannel.com, -Pitts Jarvis} (recently deceased). It runs in an equivalent of TTY -mode only (one single Macintosh window, 25 colors), but has a large -number of Mac-specific additions. It's available at -@uref{http://homepage.mac.com/pjarvis/xemacs.html}. - -@node Q1.1.7, Q1.1.8, Q1.1.6, Introduction -@unnumberedsubsec Q1.1.7: Is there a port of XEmacs to NextStep? - -Carl Edman, apparently no longer at @email{cedman@@princeton.edu}, did -the port of GNU Emacs to NeXTstep and expressed interest in doing the -XEmacs port, but never went any farther. - -@node Q1.1.8, Q1.1.9, Q1.1.7, Introduction -@unnumberedsubsec Q1.1.8: Is there a port of XEmacs to OS/2? - -No, but Alexander Nikolaev is working on it. - -@node Q1.1.9, Q1.2.1, Q1.1.8, Introduction -@unnumberedsubsec Q1.1.9: How does the port cope with differences in the Windows user interface? - -The XEmacs (and Emacs in general) user interface is pretty different -from what is expected of a typical MS Windows program. How does the MS -Windows port cope with it? - -As a general rule, we follow native MS Windows conventions as much as -possible. 21.4 is a fairly complete Windows application, supporting -native printing, system file dialog boxes, tool tips, etc. In cases -where there's a clear UI conflict, we currently use normal Unix XEmacs -behavior by default, but make sure the MS Windows "look and feel" (mark -via shift-arrow, self-inserting deletes region, Alt selects menu items, -etc.) is easily configurable (respectively: using the variable -@code{shifted-motion-keys-select-region} in 21.4 and above [it's in fact -the default in these versions], or the @file{pc-select} package; using -the @file{pending-del} package; and setting the variable -@code{menu-accelerator-enabled} to @code{menu-force} in 21.4 and above). -In fact, if you use the sample @file{init.el} file as your init file, -you will get all these behaviors automatically turned on. - -In future versions, some of these features might be turned on by -default in the MS Windows environment. - -@unnumberedsec 1.2: Policies - -@node Q1.2.1, Q1.2.2, Q1.1.9, Introduction -@unnumberedsubsec Q1.2.1: What is the FAQ editorial policy? - -The FAQ is actively maintained and modified regularly. All links should -be up to date. Unfortunately, some of the information is out of date -- -a situation which the FAQ maintainer is working on. All submissions are -welcome, please e-mail submissions to @email{faq@@xemacs.org, XEmacs FAQ -maintainers}. - -Please make sure that @samp{XEmacs FAQ} appears on the Subject: line. -If you think you have a better way of answering a question, or think a -question should be included, we'd like to hear about it. Questions and -answers included into the FAQ will be edited for spelling and grammar -and will be attributed. Answers appearing without attribution are -either from versions of the FAQ dated before May 1996 or are from -previous FAQ maintainers. Answers quoted from Usenet news articles will -always be attributed, regardless of the author. - -@node Q1.2.2, Q1.2.3, Q1.2.1, Introduction -@unnumberedsubsec Q1.2.2: How do I become a beta tester? - -Send an email message to @email{xemacs-beta-request@@xemacs.org} with -the line @samp{subscribe} in the body of the message. - -Be prepared to get your hands dirty, as beta testers are expected to -identify problems as best they can. - -@node Q1.2.3, Q1.3.1, Q1.2.2, Introduction -@unnumberedsubsec Q1.2.3: How do I contribute to XEmacs itself? - -It depends on the knowledge and time you possess. If you are able, by -all means become a beta tester (@pxref{Q1.2.2}). If you are a -programmer, try to build XEmacs and see if you can improve it. - -Otherwise, you can still help by using XEmacs as your everyday editor -(for pre-built binary versions, @pxref{Q1.0.4}) and reporting bugs you -find to the mailing list. - -Another area where we need help is the documentation: We need good -documentation for building XEmacs and for using it. This FAQ is a -small step in that direction. - -Ben Wing @email{ben@@xemacs.org} writes: - -@quotation -BTW if you have a wish list of things that you want added, you have to -speak up about it! More specifically, you can do the following if you -want a feature added (in increasing order of usefulness): - -@itemize @bullet -@item -Make a posting about a feature you want added. - -@item -Become a beta tester and make more postings about those same features. - -@item -Convince us that you're going to use the features in some cool and -useful way. - -@item -Come up with a clear and well-thought-out API concerning the features. - -@item -Write the code to implement a feature and send us a patch. -@end itemize - -(not that we're necessarily requiring you to write the code, but we can -always hope :) -@end quotation - -@unnumberedsec 1.3: Credits - -@node Q1.3.1, Q1.3.2, Q1.2.3, Introduction -@unnumberedsubsec Q1.3.1: Who wrote XEmacs? - -XEmacs is the result of the time and effort of many people, and the -active developers have changed over time. There are two major -components of the XEmacs effort -- writing the code itself and providing -all the support work (testing the code, releasing beta and final -versions, handling patches, reading bug reports, maintaining the web -site, managing the mailing lists, etc. etc.). Neither component would -work without the other. - -@subheading CODING - -The primary code contributor over the years has been Ben Wing (active -since late 1992). Between 1991 and 1995, large amounts of coding was -contributed by Jamie Zawinski and Chuck Thompson. Many other people -have authored major subsystems or otherwise contributed large amounts of -code, including Andy Piper, Hrvoje Niksic, Jerry James, Jonathan Harris, -Kyle Jones, Martin Buchholz, Michael Sperber, Olivier Galibert, Richard -Mlynarik, Stig, William Perry and plenty of others. - -Primary XEmacs-specific subsystems and their authors: +@unnumberedsec 1.7: External Packages + +@node Q1.7.1, Q1.8.1, Q1.6.6, Introduction +@unnumberedsubsec Q1.7.1: Which external packages are there? + +@subheading Normal Packages + +A very broad collection of elisp packages. @table @asis -@item Objects -@itemize @minus -@item -Conversion from 26-bit to 28-bit pointers and integers, lrecords, lcrecords: Richard Mlynarik, 1994 -@item -Conversion to 32-bit pointers and 31-bit integers: Kyle Jones, Martin Buchholz -@item -Portable dumper, object descriptions: Olivier Galibert -@item -KKCC (new garbage collector), ephemerons, weak boxes: Michael Sperber and students -@item -Random object work (object equal and hash methods, weak lists, lcrecord lists, bit vectors, dynarr, blocktype, opaque, string resizing): Ben Wing -@item -Profiling: Ben Wing -@item -Some byte-compilation and hash-table improvements: Martin Buchholz -@item -Bignum: Jerry James -@end itemize - -@item Internationalization/Mule -@itemize @minus -@item -mostly Ben Wing; many ideas for future work, Stephen Turnbull -@end itemize - -@item I/O -@itemize @minus -@item -Basic event/event-stream implementation: Jamie Zawinski -@item -Most event work since 1994: Ben Wing -@item -Asynchronous stuff (async timeouts, signals, quit-checking): Ben Wing -@item -Process method abstraction, Windows process work: Kirill Katsnelson -@item -Misc-user events, async timeouts, most quit-checking and signal code, most other work since 1994: Ben Wing -@item -Lstreams: Ben Wing -@end itemize - -@item Display -@itemize @minus -@item -Redisplay mechanism: implementation, Chuck Thompson; additional work, lots of people -@item -Glyphs: mostly Ben Wing -@item -Specifiers: Ben Wing -@item -Extents: initial implementation, someone at Lucid; rewrite, 1994, Ben Wing -@item -Widgets: Andy Piper -@item -JPEG/PNG/TIFF image converters: Ben Wing, William Perry, Jareth Hein, others (see comment in @file{glyphs-eimage.c}) -@item -Menus: Jamie Zawinski, someone at Lucid (Lucid menus) -@item -Scrollbars: Chuck Thompson, ??? (Lucid scrollbar) -@item -Multi-device/device-independence work (console/device/etc methods): Ben Wing, prototype by chuck thompson -@item -Faces: first implementation, Jamie Zawinski; second, chuck; third, Ben Wing -@item -Fonts/colors: first implementation, Jamie Zawinski; further work, Ben Wing -@item -Toolbars: implementation, chuck, much interface work, Ben Wing -@item -Gutters, tabs: andy piper -@end itemize - -@item Device subsystems -@itemize @minus -@item -X Windows: Jamie Zawinksi, Ben Wing, others -@item -GTK: William Perry, Malcolm Purvis -@item -MS Windows: initial implementation, Jonathan Harris; some more work, Andy Piper, Ben Wing -@item -TTY: Chuck Thompson, Ben Wing -@item -Cygwin: Andy Piper -@end itemize - -@item Misc -@itemize @minus -@item -Configure: initial porting from fsf, Chuck Thompson; conversion to autoconf 2, much rewriting, Martin Buchholz -@item -Most initialization-related code: Ben Wing -@item -Internals manual, much of Lisp manual: Ben Wing -@item -FSF synching: initial sync with FSF 19, Richard Mlynarik, further work, Ben Wing -@end itemize +@item Sun +Support for Sparcworks. + +@item ada +Ada language support. + +@item apel +A Portable Emacs Library. Used by XEmacs MIME support. + +@item auctex +Basic TeX/LaTeX support. + +@item bbdb +The Big Brother Data Base: a rolodex-like database program. + +@item build +Build XEmacs from within (UNIX, Windows). + +@item c-support +Basic single-file add-ons for editing C code. + +@item calc +Emacs calculator. + +@item calendar +Calendar and diary support. + +@item cc-mode +C, C++, Objective-C, Java, CORBA IDL, Pike and AWK language support. + +@item clearcase +New Clearcase Version Control for XEmacs (UNIX, Windows). + +@item clearcase +Support for the Clearcase version control system. + +@item cookie +"Fortune cookie"-style messages. Includes Spook (suspicious phrases) +and Yow (Zippy quotes). + +@item crisp +Crisp/Brief emulation. + +@item debug +GUD, gdb, dbx debugging support. + +@item dictionary +Interface to RFC2229 dictionary servers. + +@item dired +The DIRectory EDitor is for manipulating, and running commands on +files in a directory. + +@item docbookide +DocBook editing support. + +@item ecb +Emacs source code browser. + +@item ecrypto +Crypto functionality in Emacs Lisp. + +@item edebug +An Emacs Lisp debugger. + +@item ediff +Interface over GNU patch. + +@item edit-utils +Miscellaneous editor extensions, you probably need this. + +@item edt +DEC EDIT/EDT emulation. + +@item efs +Treat files on remote systems the same as local files. + +@item eieio +Enhanced Implementation of Emacs Interpreted Objects. + +@item elib +Portable Emacs Lisp utilities library. + +@item emerge +Another interface over GNU patch. + +@item erc +ERC is an Emacs InternetRelayChat client. + +@item escreen +Multiple editing sessions withing a single frame (like screen). + +@item eshell +Command shell implemented entirely in Emacs Lisp. + +@item ess +ESS: Emacs Speaks Statistics. + +@item eterm +Terminal emulation. + +@item eudc +Emacs Unified Directory Client (LDAP, PH). + +@item footnote +Footnoting in mail message editing modes. + +@item forms +Forms editing support (obsolete, use Widget instead). + +@item fortran-modes +Fortran support. + +@item fortran-modes +Fortran language support. + +@item frame-icon +Set up mode-specific icons for each frame under XEmacs. + +@item fsf-compat +GNU Emacs compatibility files. + +@item games +Tetris, Sokoban, and Snake. + +@item general-docs +General documentation. Presently, empty. + +@item gnats +XEmacs bug reports. + +@item gnus +The Gnus Newsreader and Mailreader. + +@item haskell-mode +Haskell editing support. + +@item hm--html-menus +HTML editing. + +@item hyperbole +Hyperbole: The Everyday Info Manager. + +@item ibuffer +Advanced replacement for buffer-menu. + +@item idlwave +Editing and Shell mode for the Interactive Data Language. + +@item igrep +Enhanced front-end for Grep. + +@item ilisp +Front-end for interacting with Inferior Lisp (external lisps). + +@item ispell +Spell-checking with GNU ispell. + +@item jde +Integrated Development Environment for Java. + +@item liece +IRC (Internet Relay Chat) client for Emacs. Note, this package is +deprecated and will be removed, use riece instead. + +@item mail-lib +Fundamental lisp files for providing email support. + +@item mailcrypt +Support for messaging encryption with PGP. + +@item mew +Messaging in an Emacs World; a MIME-based email program. + +@item mh-e +The XEmacs Interface to the MH Mail System. + +@item mine +Elisp implementation of the game 'Minehunt'. + +@item misc-games +Other amusements and diversions. + +@item mmm-mode +Support for Multiple Major Modes within a single buffer. + +@item net-utils +Miscellaneous Networking Utilities. + +@item ocaml +Objective Caml editing support. + +@item oo-browser +OO-Browser: The Multi-Language Object-Oriented Code Browser. + +@item ocaml +Objective Caml editing support. + +@item os-utils +Miscellaneous single-file O/S utilities, for printing, archiving, +compression, remote shells, etc. + +@item pc +PC style interface emulation. + +@item pcl-cvs +CVS frontend. + +@item pcomplete +Provides programmatic completion. + +@item perl-modes +Perl support. + +@item pgg +Emacs interface to various PGP implementations. + +@item prog-modes +Support for various programming languages. + +@item ps-print +Printing functions and utilities. + +@item psgml +Validated HTML/SGML editing. + +@item psgml-dtds +A collection of DTDs for psgml. Note that this package is deprecated +and will be removed in the future, most likely Q2/2003. Instead of using +this, you should install needed DTDs yourself. + +@item python-modes +Python language support. + +@item reftex +Emacs support for LaTeX cross-references, citations. + +@item riece +IRC (Internet Relay Chat) client for Emacs. + +@item rmail +An obsolete Emacs mailer. If you do not already use it don't start. + +@item ruby-modes +Ruby support. + +@item sasl +Simple Authentication and Security Layer (SASL) library. + +@item scheme +Front-end support for Inferior Scheme. + +@item semantic +Semantic bovinator (Yacc/Lex for XEmacs). Includes Senator. + +@item sgml +SGML/Linuxdoc-SGML editing. + +@item sh-script +Support for editing shell scripts. + +@item sieve +Manage Sieve email filtering scripts. + +@item slider +User interface tool. + +@item sml-mode +SML editing support. + +@item sounds-au +XEmacs Sun sound files. + +@item sounds-wav +XEmacs Microsoft sound files. + +@item speedbar +Provides a separate frame with convenient references. + +@item strokes +Mouse enhancement utility. + +@item supercite +An Emacs citation tool for News & Mail messages. + +@item texinfo +XEmacs TeXinfo support. + +@item text-modes +Miscellaneous support for editing text files. + +@item textools +Miscellaneous TeX support. + +@item time +Display time & date on the modeline. + +@item tm +Emacs MIME support. Not needed for gnus >= 5.8.0. + +@item tooltalk +Support for building with Tooltalk. + +@item tpu +DEC EDIT/TPU support. + +@item tramp +Remote shell-based file editing. This is similar to EFS or Ange-FTP, +but works with rsh/ssh and rcp/scp. + +@item vc +Version Control for Free systems. + +@item vc-cc +Version Control for ClearCase (UnFree) systems. + +@item vhdl +Support for VHDL. + +@item view-process +A Unix process browsing tool. + +@item viper +VI emulation support. + +@item vm +An Emacs mailer. + +@item w3 +A Web browser. + +@item x-symbol +Semi WYSIWYG for LaTeX, HTML, etc, using additional fonts. + +@item xemacs-base +Fundamental XEmacs support, you almost certainly need this. + +@item xemacs-devel +XEmacs Lisp developer support. This package contains utilities for +supporting Lisp development. It is a single-file package so it may be +tailored. + +@item xlib +Emacs interface to X server. + +@item xslide +XSL editing support. + +@item xslt-process +A minor mode for (X)Emacs which allows running an XSLT processor on a +buffer. + +@item xwem +X Emacs Window Manager. + +@item zenirc +ZENIRC IRC Client. @end table -@subheading SUPPORT - -Currently, support duties are handled by many different people. - -Release managers have been - -@itemize @minus -@item -Stephen Turnbull (April 2001 - present, 21.x - 21.x?) -@item -Vin Shelton? -@item -Steve Youngs (July 2002 - present??, 21.x - 21.x?) -@item -Martin Buchholz (December 1998 - May 2001, 21.x - 21.x?) -@item -Steve Baur (early 1997 - November 1998, 19.15 - 21.0) -@item -Chuck Thompson (June 1994 - September 1996, 19.11 - 19.14) -@item -Jamie Zawinski (April 1991 - June 1994, 19.0 - 19.10) -@end itemize - -The recent overlapping dates are intentional, since two or three trees -are maintained simultaneously at any point. - -Other major support work: - -@itemize @minus -@item -Adrian Aichner wrote and maintains the web site. -@item -Stephen Turnbull has produced many of the beta and semi-stable releases -and has attempted to be the "face" of XEmacs on the newsgroups and -mailing lists. -@item -Steve Youngs currently produces the beta releases (???). -@item -Steve Youngs, Ville Skytta, and now Norbert Koch have taken turns -maintaining the packages. -@item -Vin Shelton maintains the stable releases. -@item -Testing - #### Norbert, Adrian, ??? -@end itemize - -Portraits and email of some of the major developers: - -@itemize @bullet -@item @email{andy@@xemacs.org, Andy Piper} -@html -
Portrait of Andy Piper
-@end html - -@item @email{ben@@xemacs.org, Ben Wing} -@html -
Portrait of Ben Wing
-@end html - -@item @email{cthomp@@xemacs.org, Chuck Thompson} -@html -
Portrait of Chuck Thompson
-@end html - -@item @email{hniksic@@xemacs.org, Hrvoje Niksic} - -@html -
Portrait of Hrvoje Niksic
-@end html - -@item @email{jwz@@jwz.org, Jamie Zawinski} -@html -
Portrait of Jamie Zawinski
-@end html - -@item @email{martin@@xemacs.org, Martin Buchholz} -@html -
Portrait of Martin Buchholz
-@end html - -@item @email{mly@@adoc.xerox.com, Richard Mlynarik} -@html -
Portrait of Richard Mlynarik
-@end html - -@item @email{stephen@@xemacs.org, Stephen Turnbull} - -@item @email{steve@@xemacs.org, Steve Baur} -@html -
Portrait of Steve Baur
-@end html -@end itemize - -Many other people have contributed to XEmacs; this is partially -enumerated in the @samp{About XEmacs} option in the Help menu. - -@node Q1.3.2, Q1.3.3, Q1.3.1, Introduction -@unnumberedsubsec Q1.3.2: Who contributed to this version of the FAQ? - -The current version of this FAQ was created by @email{ben@@xemacs.org, -Ben Wing}. - -@node Q1.3.3, Q1.4.1, Q1.3.2, Introduction -@unnumberedsubsec Q1.3.3: Who contributed to the FAQ in the past? - -This is only a partial list, as many names were lost in a hard disk -crash some time ago. - -@itemize @bullet -@item @email{steve@@xemacs.org, SL Baur} - -@item @email{hniksic@@xemacs.org, Hrvoje Niksic} - -@item @email{binge@@aloft.att.com, Curtis.N.Bingham} - -@item @email{bruncott@@dormeur.inria.fr, Georges Brun-Cottan} - -@item @email{rjc@@cogsci.ed.ac.uk, Richard Caley} - -@item @email{cognot@@ensg.u-nancy.fr, Richard Cognot} - -@item @email{daku@@nortel.ca, Mark Daku} - -@item @email{wgd@@martigny.ai.mit.edu, William G. Dubuque} - -@item @email{eeide@@cs.utah.edu, Eric Eide} - -@item @email{af@@biomath.jussieu.fr, Alain Fauconnet} - -@item @email{cflatter@@nrao.edu, Chris Flatters} - -@item @email{ginsparg@@adra.com, Evelyn Ginsparg} - -@item @email{hall@@aplcenmp.apl.jhu.edu, Marty Hall} - -@item @email{dkindred@@cmu.edu, Darrell Kindred} - -@item @email{dmoore@@ucsd.edu, David Moore} - -@item @email{arup+@@cmu.edu, Arup Mukherjee} - -@item @email{nickel@@prz.tu-berlin.de, Juergen Nickelsen} - -@item @email{powell@@csl.ncsa.uiuc.edu, Kevin R. Powell} - -@item @email{dworkin@@ccs.neu.edu, Justin Sheehy} - -@item @email{stig@@hackvan.com, Stig} - -@item @email{Aki.Vehtari@@hut.fi, Aki Vehtari} -@end itemize - -@unnumberedsec 1.4: Internationalization - -@node Q1.4.1, Q1.4.2, Q1.3.3, Introduction -@unnumberedsubsec Q1.4.1: What is the status of internationalization support aka MULE (including Asian language support)? +@subheading Mule Support (mule) + +MULti-lingual Enhancement. Support for world scripts such as +Latin, Arabic, Cyrillic, Chinese, Japanese, Greek, Hebrew etc. +To use these packages your XEmacs must be compiled with Mule +support. + +@table @asis +@item edict +MULE: Lisp Interface to EDICT, Kanji Dictionary. + +@item egg-its +MULE: Wnn (4.2 and 6) support. SJ3 support. + +@item latin-unity +MULE: find single ISO 8859 character set to encode a buffer. + +@item latin-unity +Unify character sets in a buffer. When characters belong to disjoint +character sets, this attempts to translate the characters so +that they belong to one character set. If the buffer coding system is +not sufficient, this suggests different coding systems. + +@item leim +MULE: Quail. All non-English and non-Japanese language support. + +@item locale +MULE: Localized menubars and localized splash screens. + +@item lookup +Dictionary support. (This isn't an English dictionary program) + +@item mule-base +MULE: Basic Mule support, required for building with Mule. + +@item mule-ucs +MULE: Extended coding systems (including Unicode) for XEmacs. + +@item mule-ucs +Extended coding systems (including Unicode) for XEmacs. + +@item skk +Another Japanese Language Input Method. Can be used without a +separate process running as a dictionary server. +@end table + +@unnumberedsec 1.8: Internationalization + +@node Q1.8.1, Q1.8.2, Q1.7.1, Introduction +@unnumberedsubsec Q1.8.1: What is the status of internationalization support aka MULE (including Asian language support)? Both the stable and development versions of XEmacs include internationalization support (aka MULE). MULE currently (21.4) works on @@ -1672,8 +2540,8 @@ instability of the development tree. Binaries compiled without MULE support run faster than MULE capable XEmacsen. -@node Q1.4.2, Q1.4.3, Q1.4.1, Introduction -@unnumberedsubsec Q1.4.2: How can I help with internationalization? +@node Q1.8.2, Q1.8.3, Q1.8.1, Introduction +@unnumberedsubsec Q1.8.2: How can I help with internationalization? If you would like to help, you may want to join the @email{xemacs-mule@@xemacs.org} mailing list. Especially needed are @@ -1683,24 +2551,24 @@ Translations of the TUTORIAL and man page are welcome, and XEmacs does support multilingual menus, but we have few current translations. -@xref{Q1.2.2, How do I become a Beta Tester?}. - -@node Q1.4.3, Q1.4.4, Q1.4.2, Introduction -@unnumberedsubsec Q1.4.3: How do I type non-ASCII characters? +@xref{Q1.5.2, How do I become a Beta Tester?}. + +@node Q1.8.3, Q1.8.4, Q1.8.2, Introduction +@unnumberedsubsec Q1.8.3: How do I type non-ASCII characters? @xref{Q3.0.6, How can you type in special characters in XEmacs?}, in part 3 of this FAQ, for some simple methods that also work in non-MULE builds of XEmacs (but only for one-octet coded character sets, and mostly for ISO 8859/1). Many of the methods available for Cyrillic -(@pxref{Q1.4.7, How about Cyrillic modes?}) work without MULE. MULE -has more general capabilities. @xref{Q1.4.5, Please explain the +(@pxref{Q1.8.7, How about Cyrillic modes?}) work without MULE. MULE +has more general capabilities. @xref{Q1.8.5, Please explain the various input methods in MULE/XEmacs}. @xref{Q4.0.8, How do I display non-ASCII characters?}, which covers display of non-ASCII characters. -@node Q1.4.4, Q1.4.5, Q1.4.3, Introduction -@unnumberedsubsec Q1.4.4: Can XEmacs messages come out in a different language? +@node Q1.8.4, Q1.8.5, Q1.8.3, Introduction +@unnumberedsubsec Q1.8.4: Can XEmacs messages come out in a different language? The message-catalog support was written but is badly bit-rotted. XEmacs 20 and 21 did @emph{not} support it, and early releases of XEmacs 22 @@ -1718,8 +2586,8 @@ The name of the resource is derived from the non-localized entry by removing punctuation and capitalizing as above. -@node Q1.4.5, Q1.4.6, Q1.4.4, Introduction -@unnumberedsubsec Q1.4.5: Please explain the various input methods in MULE/XEmacs +@node Q1.8.5, Q1.8.6, Q1.8.4, Introduction +@unnumberedsubsec Q1.8.5: Please explain the various input methods in MULE/XEmacs Mule supports a wide variety of input methods. There are three basic classes: Lisp implementations, generic platform support, and library @@ -1811,8 +2679,8 @@ Much of this information was provided by @email{morioka@@jaist.ac.jp, MORIOKA Tomohiko}. -@node Q1.4.6, Q1.4.7, Q1.4.5, Introduction -@unnumberedsubsec Q1.4.6: How do I portably code for MULE/XEmacs? +@node Q1.8.6, Q1.8.7, Q1.8.5, Introduction +@unnumberedsubsec Q1.8.6: How do I portably code for MULE/XEmacs? MULE has evolved rapidly over the last few years, and the original third party patch (for GNU Emacs 19), GNU Emacs 20+, and XEmacs 20+ have quite @@ -1876,8 +2744,8 @@ @end lisp @end quotation -@node Q1.4.7, Q1.4.8, Q1.4.6, Introduction -@unnumberedsubsec Q1.4.7: How about Cyrillic modes? +@node Q1.8.7, Q1.8.8, Q1.8.6, Introduction +@unnumberedsubsec Q1.8.7: How about Cyrillic modes? @email{ilya@@math.ohio-state.edu, Ilya Zakharevich} writes: @@ -1914,8 +2782,8 @@ XEmacs) is @uref{http://www.ibiblio.org/sergei/Software/Software.html} @end quotation -@node Q1.4.8, Q1.4.9, Q1.4.7, Introduction -@unnumberedsubsec Q1.4.8: Does XEmacs support Unicode? +@node Q1.8.8, Q1.8.9, Q1.8.7, Introduction +@unnumberedsubsec Q1.8.8: Does XEmacs support Unicode? To get Unicode support, you need a Mule-enabled XEmacs. @@ -1923,7 +2791,7 @@ don't yet use it as the internal encoding. 21.4 supports Unicode partially -- as an external encoding for files, -processes, and terminals, but without font support. @xref{Q1.4.9, How +processes, and terminals, but without font support. @xref{Q1.8.9, How does XEmacs display Unicode?}. To get Unicode support in 21.4, install Mule-UCS from packages in the usual way, and put @@ -1938,13 +2806,13 @@ that files that are not UTF-8 are being mis-recognized as UTF-8. Install standard national fonts (not Unicode fonts) for all character -sets you use. @xref{Q1.4.9, How does XEmacs display Unicode??}. +sets you use. @xref{Q1.8.9, How does XEmacs display Unicode??}. Mule-UCS also supports 16-bit forms of Unicode (UTF-16). It does not support 31-bit forms of Unicode (UTF-32 or UCS-4). -@node Q1.4.9, Q1.5.1, Q1.4.8, Introduction -@unnumberedsubsec Q1.4.9: How does XEmacs display Unicode? +@node Q1.8.9, , Q1.8.8, Introduction +@unnumberedsubsec Q1.8.9: How does XEmacs display Unicode? Mule doesn't have a Unicode charset internally, so there's nothing to bind a Unicode registry to. It would not be straightforward to create, @@ -1965,158 +2833,6 @@ Real Unicode support will be introduced in XEmacs 22.0. -@unnumberedsec 1.5: Getting Started - -@node Q1.5.1, Q1.5.2, Q1.4.9, Introduction -@unnumberedsubsec Q1.5.1: What is an @file{init.el} or @file{.emacs} and is there a sample one? - -The @file{init.el} or @file{.emacs} file is used to customize XEmacs to -your tastes. Starting in 21.4, the preferred location for the init file -is @file{~/.xemacs/init.el}; in previous versions, it was -@file{~/.emacs}. 21.4 still accepts the old location, but the first -time you run it, it will ask to migrate your file to the new location. -If you answer yes, the file will be moved, and a "compatibility" -@file{.emacs} file will be placed in the old location so that you can -still run older versions of XEmacs, and versions of GNU Emacs, which -expect the old location. The @file{.emacs} file present is just a stub -that loads the real file in @file{~/.xemacs/init.el}. - -No two init files are alike, nor are they expected to be alike, but -that's the point. The XEmacs distribution contains an excellent starter -example in the @file{etc/} directory called @file{sample.init.el} -(starting in 21.4) or @file{sample.emacs} in older versions. Copy this -file from there to @file{~/.xemacs/init.el} (starting in 21.4) or -@file{~/.emacs} in older versions, where @samp{~} means your home -directory, of course. Then edit it to suit. - -You may bring the @file{sample.init.el} or @file{sample.emacs} file into -an XEmacs buffer from the menubar. (The menu entry for it is always -under the @samp{Help} menu, but its location under that has changed in -various versions. Recently, look under the @samp{Samples} submenu.) To -determine the location of the @file{etc/} directory type the command -@kbd{C-h v data-directory @key{RET}}. - -@node Q1.5.2, Q1.5.3, Q1.5.1, Introduction -@unnumberedsubsec Q1.5.2: Where do I put my @file{init.el} file? - -@file{init.el} is the name of the init file starting with 21.4, and is -located in the subdirectory @file{.xemacs/} of your home directory. In -prior versions, the init file is called @file{.emacs} and is located in -your home directory. - -Your home directory under Windows is determined by the @samp{HOME} -environment variable. If this is not set, it defaults to @samp{C:\}. -To set this variable, modify @file{AUTOEXEC.BAT} under Windows 95/98, or -select @samp{Control Panel->System->Advanced->Environment Variables...} -under Windows NT/2000. - -@node Q1.5.3, Q1.5.4, Q1.5.2, Introduction -@unnumberedsubsec Q1.5.3: Can I use the same @file{init.el} with the other Emacs? - -Yes. The sample @file{init.el} included in the XEmacs -distribution will show you how to handle different versions and flavors -of Emacs. - -@node Q1.5.4, Q1.5.5, Q1.5.3, Introduction -@unnumberedsubsec Q1.5.4: Any good XEmacs tutorials around? - -There's the XEmacs tutorial available from the Help Menu under -@samp{Help->Tutorials}, or by typing @kbd{C-h t}. To check whether -it's available in a non-english language, type @kbd{C-u C-h t TAB}, type -the first letters of your preferred language, then type @key{RET}. - -@comment There's an Emacs Lisp tutorial at -@comment -@comment @example -@comment @uref{ftp://prep.ai.mit.edu/pub/gnu/emacs-lisp-intro-1.04.tar.gz}. -@comment @end example -@comment -@comment @email{erik@@petaxp.rug.ac.be, Erik Sundermann} has made a tutorial web -@comment page at -@comment @iftex -@comment @* -@comment @end iftex -@comment @uref{http://petaxp.rug.ac.be/~erik/xemacs/}. - -@node Q1.5.5, Q1.5.6, Q1.5.4, Introduction -@unnumberedsubsec Q1.5.5: May I see an example of a useful XEmacs Lisp function? - -The following function does a little bit of everything useful. It does -something with the prefix argument, it examines the text around the -cursor, and it's interactive so it may be bound to a key. It inserts -copies of the current word the cursor is sitting on at the cursor. If -you give it a prefix argument: @kbd{C-u 3 M-x double-word} then it will -insert 3 copies. - -@lisp -(defun double-word (count) - "Insert a copy of the current word underneath the cursor" - (interactive "*p") - (let (here there string) - (save-excursion - (forward-word -1) - (setq here (point)) - (forward-word 1) - (setq there (point)) - (setq string (buffer-substring here there))) - (while (>= count 1) - (insert string) - (decf count)))) -@end lisp - -The best way to see what is going on here is to let XEmacs tell you. -Put the code into an XEmacs buffer, and do a @kbd{C-h f} with the cursor -sitting just to the right of the function you want explained. Eg. move -the cursor to the SPACE between @code{interactive} and @samp{"*p"} and -hit @kbd{C-h f} to see what the function @code{interactive} does. Doing -this will tell you that the @code{*} requires a writable buffer, and -@code{p} converts the prefix argument to a number, and -@code{interactive} allows you to execute the command with @kbd{M-x}. - -@node Q1.5.6, Q1.5.7, Q1.5.5, Introduction -@unnumberedsubsec Q1.5.6: And how do I bind it to a key? - -To bind to a key do: - -@lisp -(global-set-key "\C-cd" 'double-word) -@end lisp - -Or interactively, @kbd{M-x global-set-key} and follow the prompts. - -@node Q1.5.7, Q1.5.8, Q1.5.6, Introduction -@unnumberedsubsec Q1.5.7: What's the difference between a macro and a function? - -Quoting from the Lisp Reference (a.k.a @dfn{Lispref}) Manual: - -@dfn{Macros} enable you to define new control constructs and other -language features. A macro is defined much like a function, but instead -of telling how to compute a value, it tells how to compute another Lisp -expression which will in turn compute the value. We call this -expression the @dfn{expansion} of the macro. - -Macros can do this because they operate on the unevaluated expressions -for the arguments, not on the argument values as functions do. They can -therefore construct an expansion containing these argument expressions -or parts of them. - -Do not confuse the two terms with @dfn{keyboard macros}, which are -another matter, entirely. A keyboard macro is a key bound to several -other keys. Refer to manual for details. - -@node Q1.5.8, , Q1.5.7, Introduction -@unnumberedsubsec Q1.5.8: What is @code{Custom}? - -@code{Custom} is a system for customizing XEmacs options. - -You can access @code{Advanced (Customize)} from the @code{Options} menu -or invoking one of customize commands by typing eg. -@kbd{M-x customize}, @kbd{M-x customize-face}, -@kbd{M-x customize-variable} or @kbd{M-x customize-apropos}. - -There is also new @samp{browser} mode for Customize. -Try it out with @kbd{M-x customize-browse} - @node Installation, Editing, Introduction, Top @unnumbered 2 Installation and Troubleshooting @@ -2442,11 +3158,11 @@ there is little reason not to use it. The second way to build is the Cygwin port. It takes advantage of -Cygnus emulation library under Win32. @xref{Q1.1.4, What are Cygwin +Cygnus emulation library under Win32. @xref{Q1.2.5, What are Cygwin and MinGW, and do I need them to run XEmacs?}, for more information. A third way is the MinGW port. It uses the Cygwin environment to -build but does not require it at runtime. @xref{Q1.1.4, What are +build but does not require it at runtime. @xref{Q1.2.5, What are Cygwin and MinGW, and do I need them to run XEmacs?}, for more information. @@ -2465,7 +3181,7 @@ some beta testers currently trying to compile with VC.NET, aka version 7.0, but we can't yet report complete success.) For the Cygwin and MinGW versions, you need the Cygwin environment, which comes with GCC, -the compiler used for those versions. @xref{Q1.1.4, What are Cygwin +the compiler used for those versions. @xref{Q1.2.5, What are Cygwin and MinGW, and do I need them to run XEmacs?}, for more information on Cygwin and MinGW. @@ -3195,7 +3911,7 @@ problem for most people. 21.4 implements "portable dumping", which eliminates the problem altogether. We recommend you use the 21.4 binaries, but you can use the 21.1 binaries if you are very paranoid -about stability. @xref{Q1.0.4, Are binaries available?}. +about stability. @xref{Q1.1.2, Are binaries available?}. @node Q2.4.3, Q2.4.4, Q2.4.2, Installation @unnumberedsubsec Q2.4.3: XEmacs won't start without network. @@ -5957,94 +6673,38 @@ section is devoted to advanced customization using XEmacs Lisp. @menu -7.0: Online Help -* Q7.0.1:: How can I get two instances of info? -* Q7.0.2:: How do I add new Info directories? - -7.1: Emacs Lisp and @file{init.el} -* Q7.1.1:: What version of Emacs am I running? -* Q7.1.2:: How can I evaluate Emacs-Lisp expressions? -* Q7.1.3:: @code{(setq tab-width 6)} behaves oddly. -* Q7.1.4:: How can I add directories to the @code{load-path}? -* Q7.1.5:: How to check if a lisp function is defined? -* Q7.1.6:: Can I force the output of @code{(face-list)} to a buffer? - -7.2: Emacs Lisp Programming Techniques -* Q7.2.1:: What is the difference in key sequences between XEmacs and GNU Emacs? -* Q7.2.2:: Can I generate "fake" keyboard events? -* Q7.2.3:: Could you explain @code{read-kbd-macro} in more detail? -* Q7.2.4:: What is the performance hit of @code{let}? -* Q7.2.5:: What is the recommended use of @code{setq}? -* Q7.2.6:: What is the typical misuse of @code{setq}? -* Q7.2.7:: I like the @code{do} form of cl, does it slow things down? -* Q7.2.8:: I like recursion, does it slow things down? -* Q7.2.9:: How do I put a glyph as annotation in a buffer? -* Q7.2.10:: @code{map-extents} won't traverse all of my extents! -* Q7.2.11:: My elisp program is horribly slow. Is there an easy way to find out where it spends time? - -7.3: Mathematics -* Q7.3.1:: What are bignums, ratios, and bigfloats in Lisp? -* Q7.3.2:: XEmacs segfaults when I use very big numbers! -* Q7.3.3:: Bignums are really slow! -* Q7.3.4:: Equal bignums don't compare as equal! What gives? +7.0: Emacs Lisp and @file{init.el} +* Q7.0.1:: What version of Emacs am I running? +* Q7.0.2:: How can I evaluate Emacs-Lisp expressions? +* Q7.0.3:: @code{(setq tab-width 6)} behaves oddly. +* Q7.0.4:: How can I add directories to the @code{load-path}? +* Q7.0.5:: How to check if a lisp function is defined? +* Q7.0.6:: Can I force the output of @code{(face-list)} to a buffer? + +7.1: Emacs Lisp Programming Techniques +* Q7.1.1:: What is the difference in key sequences between XEmacs and GNU Emacs? +* Q7.1.2:: Can I generate "fake" keyboard events? +* Q7.1.3:: Could you explain @code{read-kbd-macro} in more detail? +* Q7.1.4:: What is the performance hit of @code{let}? +* Q7.1.5:: What is the recommended use of @code{setq}? +* Q7.1.6:: What is the typical misuse of @code{setq}? +* Q7.1.7:: I like the @code{do} form of cl, does it slow things down? +* Q7.1.8:: I like recursion, does it slow things down? +* Q7.1.9:: How do I put a glyph as annotation in a buffer? +* Q7.1.10:: @code{map-extents} won't traverse all of my extents! +* Q7.1.11:: My elisp program is horribly slow. Is there an easy way to find out where it spends time? + +7.2: Mathematics +* Q7.2.1:: What are bignums, ratios, and bigfloats in Lisp? +* Q7.2.2:: XEmacs segfaults when I use very big numbers! +* Q7.2.3:: Bignums are really slow! +* Q7.2.4:: Equal bignums don't compare as equal! What gives? @end menu -@unnumberedsec 7.0: Online Help +@unnumberedsec 7.0: Emacs Lisp and @file{init.el} @node Q7.0.1, Q7.0.2, Advanced, Advanced -@unnumberedsubsec Q7.0.1: How can I get two instances of info? - -Before 21.4, you can't. The @code{info} package does not provide for -multiple info buffers. In 21.4, this should be fixed. #### how? - -@node Q7.0.2, Q7.1.1, Q7.0.1, Advanced -@unnumberedsubsec Q7.0.2: How do I add new Info directories? - -You use something like: - -@lisp -(setq Info-directory-list (cons - (expand-file-name "~/info") - Info-default-directory-list)) -@end lisp - -@email{davidm@@prism.kla.com, David Masterson} writes: - -@quotation -Emacs Info and XEmacs Info do many things differently. If you're trying to -support a number of versions of Emacs, here are some notes to remember: - -@enumerate -@item -Emacs Info scans @code{Info-directory-list} from right-to-left while -XEmacs Info reads it from left-to-right, so append to the @emph{correct} -end of the list. - -@item -Use @code{Info-default-directory-list} to initialize -@code{Info-directory-list} @emph{if} it is available at startup, but not -all Emacsen define it. - -@item -Emacs Info looks for a standard @file{dir} file in each of the -directories scanned from #1 and magically concatenates them together. - -@item -XEmacs Info looks for a @file{localdir} file (which consists of just the -menu entries from a @file{dir} file) in each of the directories scanned -from #1 (except the first), does a simple concatenation of them, and -magically attaches the resulting list to the end of the menu in the -@file{dir} file in the first directory. -@end enumerate - -Another alternative is to convert the documentation to HTML with -texi2html and read it from a web browser like Lynx or W3. -@end quotation - -@unnumberedsec 7.1: Emacs Lisp and @file{init.el} - -@node Q7.1.1, Q7.1.2, Q7.0.2, Advanced -@unnumberedsubsec Q7.1.1: What version of Emacs am I running? +@unnumberedsubsec Q7.0.1: What version of Emacs am I running? How can @file{init.el} determine which of the family of Emacsen I am using? @@ -6061,8 +6721,8 @@ (defvar running-xemacs (string-match "XEmacs\\|Lucid" emacs-version)) @end lisp -@node Q7.1.2, Q7.1.3, Q7.1.1, Advanced -@unnumberedsubsec Q7.1.2: How can I evaluate Emacs-Lisp expressions? +@node Q7.0.2, Q7.0.3, Q7.0.1, Advanced +@unnumberedsubsec Q7.0.2: How can I evaluate Emacs-Lisp expressions? I know I can evaluate Elisp expressions from @code{*scratch*} buffer with @kbd{C-j} after the expression. How do I do it from another @@ -6071,8 +6731,8 @@ Press @kbd{M-:} (the default binding of @code{eval-expression}), and enter the expression to the minibuffer. -@node Q7.1.3, Q7.1.4, Q7.1.2, Advanced -@unnumberedsubsec Q7.1.3: @code{(setq tab-width 6)} behaves oddly. +@node Q7.0.3, Q7.0.4, Q7.0.2, Advanced +@unnumberedsubsec Q7.0.3: @code{(setq tab-width 6)} behaves oddly. If you put @code{(setq tab-width 6)} in your @file{init.el} file it does not work! Is there a reason @@ -6081,8 +6741,8 @@ Use @code{setq-default} instead, since @code{tab-width} is all-buffer-local. -@node Q7.1.4, Q7.1.5, Q7.1.3, Advanced -@unnumberedsubsec Q7.1.4: How can I add directories to the @code{load-path}? +@node Q7.0.4, Q7.0.5, Q7.0.3, Advanced +@unnumberedsubsec Q7.0.4: How can I add directories to the @code{load-path}? Here are two ways to do that, one that puts your directories at the front of the load-path, the other at the end: @@ -6109,8 +6769,8 @@ @end lisp @end quotation -@node Q7.1.5, Q7.1.6, Q7.1.4, Advanced -@unnumberedsubsec Q7.1.5: How to check if a lisp function is defined? +@node Q7.0.5, Q7.0.6, Q7.0.4, Advanced +@unnumberedsubsec Q7.0.5: How to check if a lisp function is defined? Use the following elisp: @@ -6134,8 +6794,8 @@ much better more often in more places if it did the above instead of trying to divine its environment from the value of one variable. -@node Q7.1.6, Q7.2.1, Q7.1.5, Advanced -@unnumberedsubsec Q7.1.6: Can I force the output of @code{(face-list)} to a buffer? +@node Q7.0.6, Q7.1.1, Q7.0.5, Advanced +@unnumberedsubsec Q7.0.6: Can I force the output of @code{(face-list)} to a buffer? It would be good having it in a buffer, as the output of @code{(face-list)} is too wide to fit to a minibuffer. @@ -6147,10 +6807,10 @@ simply press @kbd{C-h l} to get the former minibuffer contents in a buffer. -@unnumberedsec 7.2: Emacs Lisp Programming Techniques - -@node Q7.2.1, Q7.2.2, Q7.1.6, Advanced -@unnumberedsubsec Q7.2.1: What is the difference in key sequences between XEmacs and GNU Emacs? +@unnumberedsec 7.1: Emacs Lisp Programming Techniques + +@node Q7.1.1, Q7.1.2, Q7.0.6, Advanced +@unnumberedsubsec Q7.1.1: What is the difference in key sequences between XEmacs and GNU Emacs? @email{clerik@@naggum.no, Erik Naggum} writes; @@ -6182,8 +6842,8 @@ }, and converts it to the internal key representation of the Emacs you use. The function is available both on XEmacs and GNU Emacs. -@node Q7.2.2, Q7.2.3, Q7.2.1, Advanced -@unnumberedsubsec Q7.2.2: Can I generate "fake" keyboard events? +@node Q7.1.2, Q7.1.3, Q7.1.1, Advanced +@unnumberedsubsec Q7.1.2: Can I generate "fake" keyboard events? I wonder if there is an interactive function that can generate @dfn{fake} keyboard events. This way, I could simply map them inside @@ -6203,8 +6863,8 @@ (lambda () (interactive) (cg--generate-char-event 4))) @end lisp -@node Q7.2.3, Q7.2.4, Q7.2.2, Advanced -@unnumberedsubsec Q7.2.3: Could you explain @code{read-kbd-macro} in more detail? +@node Q7.1.3, Q7.1.4, Q7.1.2, Advanced +@unnumberedsubsec Q7.1.3: Could you explain @code{read-kbd-macro} in more detail? The @code{read-kbd-macro} function returns the internal Emacs representation of a human-readable string (which is its argument). @@ -6294,8 +6954,8 @@ use whitespace. @end quotation -@node Q7.2.4, Q7.2.5, Q7.2.3, Advanced -@unnumberedsubsec Q7.2.4: What is the performance hit of @code{let}? +@node Q7.1.4, Q7.1.5, Q7.1.3, Advanced +@unnumberedsubsec Q7.1.4: What is the performance hit of @code{let}? In most cases, not noticeable. Besides, there's no avoiding @code{let}---you have to bind your local variables, after all. Some @@ -6304,8 +6964,8 @@ future implementation), @code{let}-s should be used (nested) in a way to provide the clearest code. -@node Q7.2.5, Q7.2.6, Q7.2.4, Advanced -@unnumberedsubsec Q7.2.5: What is the recommended use of @code{setq}? +@node Q7.1.5, Q7.1.6, Q7.1.4, Advanced +@unnumberedsubsec Q7.1.5: What is the recommended use of @code{setq}? @itemize @bullet @item Global variables @@ -6367,8 +7027,8 @@ @end lisp @end itemize -@node Q7.2.6, Q7.2.7, Q7.2.5, Advanced -@unnumberedsubsec Q7.2.6: What is the typical misuse of @code{setq}? +@node Q7.1.6, Q7.1.7, Q7.1.5, Advanced +@unnumberedsubsec Q7.1.6: What is the typical misuse of @code{setq}? A typical misuse is probably @code{setq}ing a variable that was meant to be local. Such a variable will remain bound forever, never to be @@ -6409,8 +7069,8 @@ ** assignment to free variable flurghoze @end lisp -@node Q7.2.7, Q7.2.8, Q7.2.6, Advanced -@unnumberedsubsec Q7.2.7: I like the @code{do} form of cl, does it slow things down? +@node Q7.1.7, Q7.1.8, Q7.1.6, Advanced +@unnumberedsubsec Q7.1.7: I like the @code{do} form of cl, does it slow things down? It shouldn't. Here is what Dave Gillespie has to say about cl.el performance: @@ -6451,8 +7111,8 @@ function. @end quotation -@node Q7.2.8, Q7.2.9, Q7.2.7, Advanced -@unnumberedsubsec Q7.2.8: I like recursion, does it slow things down? +@node Q7.1.8, Q7.1.9, Q7.1.7, Advanced +@unnumberedsubsec Q7.1.8: I like recursion, does it slow things down? Yes. The Emacs byte-compiler cannot do much to optimize recursion. But think well whether this is a real concern in Emacs. Much of the Emacs @@ -6462,8 +7122,8 @@ Please try not to make your code much uglier to gain a very small speed gain. It's not usually worth it. -@node Q7.2.9, Q7.2.10, Q7.2.8, Advanced -@unnumberedsubsec Q7.2.9: How do I put a glyph as annotation in a buffer? +@node Q7.1.9, Q7.1.10, Q7.1.8, Advanced +@unnumberedsubsec Q7.1.9: How do I put a glyph as annotation in a buffer? Here is a solution that will insert the glyph annotation at the beginning of buffer: @@ -6489,8 +7149,8 @@ name), and inserts the glyph at @code{(point)} instead of @code{(point-min)}. -@node Q7.2.10, Q7.2.11, Q7.2.9, Advanced -@unnumberedsubsec Q7.2.10: @code{map-extents} won't traverse all of my extents! +@node Q7.1.10, Q7.1.11, Q7.1.9, Advanced +@unnumberedsubsec Q7.1.10: @code{map-extents} won't traverse all of my extents! I tried to use @code{map-extents} to do an operation on all the extents in a region. However, it seems to quit after processing a random number @@ -6520,8 +7180,8 @@ nil)) @end lisp -@node Q7.2.11, Q7.3.1, Q7.2.10, Advanced -@unnumberedsubsec Q7.2.11: My elisp program is horribly slow. Is there an easy way to find out where it spends time? +@node Q7.1.11, Q7.2.1, Q7.1.10, Advanced +@unnumberedsubsec Q7.1.11: My elisp program is horribly slow. Is there an easy way to find out where it spends time? @c New @email{hniksic@@xemacs.org, Hrvoje Niksic} writes: @@ -6532,10 +7192,10 @@ where the time is being spent. @end quotation -@unnumberedsec 7.3: Mathematics - -@node Q7.3.1, Q7.3.2, Q7.2.11, Advanced -@unnumberedsubsec Q7.3.1: What are bignums, ratios, and bigfloats in Lisp? +@unnumberedsec 7.2: Mathematics + +@node Q7.2.1, Q7.2.2, Q7.1.11, Advanced +@unnumberedsubsec Q7.2.1: What are bignums, ratios, and bigfloats in Lisp? Thanks to @email{james@@xemacs.org, Jerry James}, XEmacs 21.5.18 and later can use the capabilities of multiple-precision libraries that may @@ -6563,7 +7223,7 @@ @itemize @item Arithmetic can cause a segfault, depending on your MP library -@ref{Q7.3.2, XEmacs segfaults when I use very big numbers!}. +@ref{Q7.2.2, XEmacs segfaults when I use very big numbers!}. @item Terminology is not Common-Lisp-conforming. For example, ``integer'' for @@ -6589,7 +7249,7 @@ can't be ruled out. ``Arbitrary'' precision means precisely what it says. If you work with extremely large numbers, your machine may arbitrarily decide to hand you an unpleasant surprise rather than a -bignum @ref{Q7.3.2, XEmacs segfaults when I use very big numbers!}. +bignum @ref{Q7.2.2, XEmacs segfaults when I use very big numbers!}. To configure with GNU MP, add @samp{--use-number-lib=gmp} @@ -6604,8 +7264,8 @@ than to writing new code, feel free to fill in the gap! -@node Q7.3.2, Q7.3.3, Q7.3.1, Advanced -@unnumberedsubsec Q7.3.2: XEmacs segfaults when I use very big numbers! +@node Q7.2.2, Q7.2.3, Q7.2.1, Advanced +@unnumberedsubsec Q7.2.2: XEmacs segfaults when I use very big numbers! GMP by default allocates temporaries on the stack. If you run out of stack space, you're dead; there is no way that we know of to reliably @@ -6622,8 +7282,8 @@ yet.) -@node Q7.3.3, Q7.3.4, Q7.3.2, Advanced -@unnumberedsubsec Q7.3.3: Bignums are really slow! +@node Q7.2.3, Q7.2.4, Q7.2.2, Advanced +@unnumberedsubsec Q7.2.3: Bignums are really slow! Many Linux distributions compile all their packages for the i386, and this is costly. An optimized version can give you two or three orders @@ -6631,8 +7291,8 @@ See @uref{http://www.swox.com/gmp/gmp-speed.html}.) -@node Q7.3.4, , Q7.3.3, Advanced -@unnumberedsubsec Q7.3.4: Equal bignums don't compare as equal! What gives? +@node Q7.2.4, , Q7.2.3, Advanced +@unnumberedsubsec Q7.2.4: Equal bignums don't compare as equal! What gives? Ah, Grasshopper, I see you are using @code{(eq x y)}. The Bodhisattva CLTL2 warned of the illusion that equal numbers would be @samp{eq}! @@ -6654,6 +7314,7 @@ elsewhere in XEmacs. @menu +8.0: TeX * Q8.0.1:: Is there something better than LaTeX mode? * Q8.0.2:: What is AUCTeX? Where do you get it? * Q8.0.3:: Problems installing AUCTeX. @@ -7010,6 +7671,7 @@ the same directory, or @file{OONEWS} for really old versions. @menu +9.0: Changes * Q9.0.1:: What new features will be in XEmacs soon? * Q9.0.2:: What's new in XEmacs 21.4? * Q9.0.3:: What's new in XEmacs 21.1? @@ -7339,6 +8001,7 @@ to released XEmacsen, but users can apply themselves) are also accepted. @menu +10.0: XEmacs 21.1 * Q10.0.1:: Gnus 5.10 won't display smileys in XEmacs 21.1. @end menu diff -r 7edc33019aa4 -r b7b90f750a78 man/xemacs/help.texi --- a/man/xemacs/help.texi Mon Jan 31 20:01:50 2005 +0000 +++ b/man/xemacs/help.texi Mon Jan 31 20:08:52 2005 +0000 @@ -442,13 +442,12 @@ information. @kbd{C-h C-w} (@code{describe-no-warranty}) displays the full details on the complete absence of warranty for XEmacs. @kbd{C-h n} (@code{view-emacs-news}) displays the file @file{xemacs/etc/NEWS}, -which contains documentation on XEmacs changes arranged chronologically. -@kbd{C-h F} (@code{xemacs-local-faq}) displays local version of the -XEmacs frequently-answered-questions-list. @kbd{C-h t} -(@code{help-with-tutorial}) displays the learn-by-doing XEmacs -tutorial. @kbd{C-h C-c} (@code{describe-copying}) displays the file -@file{xemacs/etc/COPYING}, which tells you the conditions you must obey -in distributing copies of XEmacs. @kbd{C-h C-d} -(@code{describe-distribution}) displays another file named -@file{xemacs/etc/DISTRIB}, which tells you how you can order a copy of -the latest version of XEmacs. +which contains documentation on XEmacs changes arranged +chronologically. @kbd{C-h F} (@code{xemacs-local-faq}) displays the +local version of the XEmacs FAQ (Frequently Answered Questions list). +@kbd{C-h t} (@code{help-with-tutorial}) displays the learn-by-doing +XEmacs tutorial. @kbd{C-h C-c} (@code{describe-copying}) displays the +file @file{xemacs/etc/COPYING}, which tells you the conditions you +must obey in distributing copies of XEmacs. @kbd{C-h C-d} +(@code{describe-distribution} displays the section of the FAQ that +tells you how you can get the latest version of XEmacs. diff -r 7edc33019aa4 -r b7b90f750a78 man/xemacs/new.texi --- a/man/xemacs/new.texi Mon Jan 31 20:01:50 2005 +0000 +++ b/man/xemacs/new.texi Mon Jan 31 20:08:52 2005 +0000 @@ -235,40 +235,75 @@ @cindex version number @example -(cond ((string-match "Lucid" emacs-version) +(cond ((string-match "XEmacs" emacs-version) + ;; + ;; Code for any version of XEmacs goes here. + ;; + )) + +(cond ((not (string-match "XEmacs" emacs-version))) ;; - ;; Code for any version of Lucid Emacs or XEmacs goes here + ;; Code for any version of GNU Emacs goes here. + ;; + )) + +(cond ((and (string-match "XEmacs" emacs-version) + (emacs-version>= 21 4)) + ;; + ;; Code which requires XEmacs version 21.4 or newer goes here ;; )) (cond ((and (string-match "XEmacs" emacs-version) - (or (> emacs-major-version 19) - (>= emacs-minor-version 12))) + (emacs-version>= 21 4 12) + (not (emacs-version>= 21 4 15))) ;; - ;; Code which requires XEmacs version 19.12 or newer goes here + ;; Code which requires exactly XEmacs version 21.4.12 through + ;; 21.4.14, inclusive, goes here. (e.g. A bug was introduced in + ;; 21.4.12 and fixed in 21.4.15 but many of the versions of + ;; XEmacs around in the computer laboratory run those versions, + ;; so I need to introduce a workaround. In such a case, you + ;; should ideally try to conditionalize on something else, + ;; e.g. a feature symbol or a simple test that can be run to + ;; smoke out the bug.) ;; )) -(cond ((>= emacs-major-version 19) +(cond ((and (not (string-match "XEmacs" emacs-version) + (emacs-version>= 20 2)) ;; - ;; Code for any vintage-19 emacs goes here + ;; Code which requires GNU Emacs version 20.2 or newer, but not XEmacs, + ;; goes here ;; )) -(cond ((and (not (string-match "Lucid" emacs-version)) - (= emacs-major-version 19)) - ;; - ;; Code specific to FSF Emacs 19 (not XEmacs) goes here - ;; - )) +@end example + +@emph{NOTE}: @strong{DO} use @code{(emacs-version>= ...)}. @strong{DO NOT} +try to do this yourself using @code{emacs-major-version} and +@code{emacs-minor-version}. You will, with high probability, get it +wrong. Typical attempts to replace @code{(emacs-version>= 21 4)} use + +@example +(and (>= emacs-major-version 21) + (>= emacs-minor-version 4)) +@end example -(cond ((< emacs-major-version 19) - ;; - ;; Code specific to emacs 18 goes here - ;; - )) +which correctly excludes 21.3 and all previous versions, +but also excludes 22.0 through 22.3, 23.0 through 23.3, etc. + +A "more clever" version, as advocated in earlier versions +of this very manual, was like this: + +@example +(or (> emacs-major-version 21) + (>= emacs-minor-version 4)) @end example +which correctly includes 21.4 and all following versions, +but also includes 20.4 through 20.99999, 19.4 through +19.99999, etc. + Alternatively, use @file{.xemacs/init.el} for an init file. @xref{Init File}. Of particular interest for use in files are: diff -r 7edc33019aa4 -r b7b90f750a78 man/xemacs/xemacs.texi --- a/man/xemacs/xemacs.texi Mon Jan 31 20:01:50 2005 +0000 +++ b/man/xemacs/xemacs.texi Mon Jan 31 20:08:52 2005 +0000 @@ -996,27 +996,12 @@ the GNU General Public License that comes with XEmacs and also appears following this section. -The easiest way to get a copy of XEmacs is from someone else who has it. -You need not ask for permission to do so, or tell any one else; just copy -it. - -If you have access to the Internet, you can get the latest version of -XEmacs from the anonymous FTP server @file{ftp.xemacs.org} in the directory -@file{/pub/xemacs}. It can also be found at numerous other archive -sites around the world; check the file @file{etc/DISTRIB} in an XEmacs -distribution for the latest known list. - +To get XEmacs, go to @uref{http://www.xemacs.org/Download/}. @unnumberedsec Getting Other Versions of Emacs -The Free Software Foundation's version of Emacs (called @dfn{FSF Emacs} -in this manual and often referred to as @dfn{GNU Emacs}) is available -by anonymous FTP from @file{prep.ai.mit.edu}. - -Win-Emacs, an older version of XEmacs that runs on Microsoft Windows -and Windows NT, is available by anonymous FTP from @file{ftp.netcom.com} -in the directory @file{/pub/pe/pearl}, or from @file{ftp.cica.indiana.edu} -as the files @file{wemdemo*.zip} in the directory @file{/pub/pc/win3/demo}. +The Free Software Foundation's version of Emacs (@dfn{GNU Emacs}) is +available at @uref{http://www.gnu.org/software/emacs/emacs.html}. @node Intro, Glossary, Distrib, Top @unnumbered Introduction @@ -1025,9 +1010,8 @@ self-documenting, customizable, extensible real-time display editor Emacs. XEmacs provides many powerful display and user-interface capabilities not found in other Emacsen and is mostly upwardly -compatible with GNU Emacs from the Free Software Foundation -(referred to as @dfn{FSF Emacs} in this manual). XEmacs also -comes standard with a great number of useful packages. +compatible with GNU Emacs from the Free Software Foundation. XEmacs +also comes standard with a great number of useful packages. We say that XEmacs is a @dfn{display} editor because normally the text being edited is visible on the screen and is updated automatically as you diff -r 7edc33019aa4 -r b7b90f750a78 nt/ChangeLog --- a/nt/ChangeLog Mon Jan 31 20:01:50 2005 +0000 +++ b/nt/ChangeLog Mon Jan 31 20:08:52 2005 +0000 @@ -1,3 +1,8 @@ +2005-01-31 Ben Wing + + * xemacs.mak (install): + Also copy BUGS, README, COPYING and Installation. + 2005-01-28 Ben Wing * config.inc.samp (COMPFACE_DIR): diff -r 7edc33019aa4 -r b7b90f750a78 nt/xemacs.mak --- a/nt/xemacs.mak Mon Jan 31 20:01:50 2005 +0000 +++ b/nt/xemacs.mak Mon Jan 31 20:08:52 2005 +0000 @@ -1457,8 +1457,16 @@ @echo Installing in $(INSTALL_DIR) ... @echo PlaceHolder > PlaceHolder @$(COPY) $(SRCROOT)\PROBLEMS "$(INSTALL_DIR)\" + @$(COPY) $(SRCROOT)\BUGS "$(INSTALL_DIR)\" + @$(COPY) $(SRCROOT)\README "$(INSTALL_DIR)\" + @$(COPY) $(SRCROOT)\COPYING "$(INSTALL_DIR)\" + @$(COPY) $(SRCROOT)\Installation "$(INSTALL_DIR)\" @$(COPY) PlaceHolder "$(INSTALL_DIR)\lock\" -$(DEL) "$(INSTALL_DIR)\lock\PlaceHolder" +# @$(COPY) $(BLDLIB_SRC)\*.exe "$(INSTALL_DIR)\lib-src\" +# @$(COPY) $(BLDLIB_SRC)\DOC "$(INSTALL_DIR)\lib-src\" +# @$(COPY) $(CONFIG_VALUES) "$(INSTALL_DIR)\lib-src\" +# @$(COPY) $(BLDSRC)\xemacs.exe "$(INSTALL_DIR)\bin\" @$(COPY) $(BLDLIB_SRC)\*.exe "$(INSTALL_DIR)\$(EMACS_CONFIGURATION)\" @$(COPY) $(BLDLIB_SRC)\DOC "$(INSTALL_DIR)\$(EMACS_CONFIGURATION)" @$(COPY) $(CONFIG_VALUES) "$(INSTALL_DIR)\$(EMACS_CONFIGURATION)"