![[BACK]](/cvsweb/icons/back.gif){kind=icon}
Return to emacs.1 CVS log ![[TXT]](/cvsweb/icons/text.gif){kind=icon}
![[DIR]](/cvsweb/icons/dir.gif){kind=icon}
Up to [CSRG BSD Unix] / 43BSD / contrib / emacs / etc|
Return to emacs.1 CVS log | Up to [CSRG BSD Unix] / 43BSD / contrib / emacs / etc |
1.1 root 1:
2: .TH EMACS 1 "5 March 1986"
3: .UC 4
4: .SH NAME
5: emacs \- GNU project Emacs
6: .SH SYNOPSIS
7: .B emacs
8: [file ...]
9: .br
10: .SH DESCRIPTION
11: .I GNU Emacs
12: is a new version of Emacs written by the author of the original
13: (PDP-10) Emacs, Richard Stallman. Its user functionality encompasses
14: anything any other Emacs does, and it is easily extensible since it is
15: written in a version of Lisp specifically designed to support editing.
16: Stallman encourages you to improve and extend Emacs, and urges that
17: you contribute your extensions to the GNU library. Eventually GNU
18: (Gnu's Not Unix) will be a complete replacement for Berkeley Unix, all
19: of which everyone will be able to use free.
20: .PP
21: .I GNU Emacs
22: has extensive interactive self-documentation. Control-h (backspace or
23: C-h) runs the self-documentation (Help) function. Help Tutorial (C-h
24: t) requests an interactive tutorial which can teach beginners the
25: fundamentals of Emacs in a few minutes. Help Apropos (C-h a) helps
26: you find a command given its functionality, Help Character (C-h c)
27: describes a given character's effect, Help Function (C-h f) describes
28: a given Lisp function specified by name, and Help Where-is (C-h w)
29: lets you specify a function and tells you what keys are bound to it.
30: .PP
31: .I GNU Emacs's
32: Undo can undo several steps of modification to your buffers, so it is
33: easy to recover from editing mistakes.
34: .PP
35: .I GNU Emacs's
36: many special packages handle mail reading (RMail) and sending (Mail),
37: outline editing (Outline), compiling (Compile), running subshells
38: within Emacs windows (Shell), running a Lisp read-eval-print loop
39: (Lisp-Interaction-Mode), and automated psychotherapy (Doctor).
40: .PP
41: There is an extensive reference manual, but
42: users of other Emacses
43: should have little trouble adapting even
44: without a copy. Users new to Emacs will be able
45: to use basic features fairly rapidly by studying the tutorial and
46: using the self-documentation features.
47: .PP
48: .SH DISTRIBUTION
49: GNU Emacs is free; anyone may redistribute copies of GNU Emacs to
50: anyone under the terms stated in the GNU Emacs General Public License,
51: a copy of which accompanies each copy of GNU Emacs and which also
52: appears in the reference manual.
53: .PP
54: Copies of GNU Emacs may sometimes be received packaged with
55: distributions of Unix systems, but it is never included in the scope
56: of any license covering those systems. Such inclusion would violate
57: the terms on which distribution is permitted. In fact, the primary
58: purpose of the General Public License is to prohibit anyone from
59: attaching any other restrictions to redistribution of GNU Emacs.
60: .PP
61: You can order printed copies of the GNU Emacs Manual for $15.00/copy
62: postpaid from the Free Software Foundation, which develops GNU software
63: (contact them for quantity prices on the manual). Their address is:
64: .nf
65: Free Software Foundation
66: 1000 Mass Ave.
67: Cambridge, MA 02138
68: .fi
69: Your local Emacs maintainer might also have copies available. As
70: with all software and publications from FSF, everyone is permitted to
71: make and distribute copies of the Emacs manual. The TeX source to the
72: manual is also included in the Emacs source distribution.
73: .PP
74: .SH FILES
75: /usr/src/new/emacs/src - C source files and object files
76:
77: /usr/new/lib/emacs/lisp - Lisp source files and compiled files
78: that define most editing commands. Some are preloaded;
79: others are autoloaded from this directory when used.
80:
81: /usr/new/lib/emacs/man - sources for the Emacs reference manual.
82:
83: /usr/new/lib/emacs/etc - various programs that are used with
84: GNU Emacs, and some files of information.
85:
86: /usr/new/lib/emacs/etc/DOC.* - contains the documentation
87: strings for the Lisp primitives and preloaded Lisp functions
88: of GNU Emacs. They are stored here to reduce the size of
89: Emacs proper.
90:
91: /usr/new/lib/emacs/etc/DIFF discusses GNU Emacs vs. Twenex Emacs;
92: .br
93: /usr/new/lib/emacs/etc/CCADIFF discusses GNU Emacs vs. CCA Emacs;
94: .br
95: /usr/new/lib/emacs/etc/GOSDIFF discusses GNU Emacs vs. Gosling Emacs.
96: .br
97: /usr/new/lib/emacs/etc/SERVICE lists people offering various services
98: to assist users of GNU Emacs, including education, troubleshooting,
99: porting and customization.
100: .br
101: These files also have information useful to anyone wishing to write
102: programs in the Emacs Lisp extension language, which has not yet been fully
103: documented.
104:
105: /usr/new/lib/emacs/info - files for the Info documentation browser
106: (a subsystem of Emacs) to refer to. Currently not much of Unix
107: is documented here, but the complete text of the Emacs reference
108: manual is included in a convenient tree structured form.
109:
110: /usr/new/lib/emacs/lock - holds lock files that are made for all
111: files being modified in Emacs, to prevent simultaneous modification
112: of one file by two users.
113:
114: /usr/src/new/emacs/cpp - the GNU cpp, needed for building Emacs on
115: certain versions of Unix where the standard cpp cannot handle long
116: names for macros.
117:
118: /usr/src/new/emacs/shortnames - facilities for translating long names to
119: short names in C code, needed for building Emacs on certain versions
120: of Unix where the C compiler cannot handle long names for functions
121: or variables.
122: .PP
123: .SH BUGS
124: There is a mailing list, [email protected] on the internet
125: (ucbvax!prep.ai.mit.edu!bug-gnu-emacs on UUCPnet), for reporting Emacs
126: bugs and fixes. But before reporting something as a bug, please try
127: to be sure that it really is a bug, not a misunderstanding or a
128: deliberate feature. We ask you to read the section ``Reporting Emacs
129: Bugs'' near the end of the reference manual (or Info system) for hints
130: on how and when to report bugs. Also, include the version number of
131: the Emacs you are running in \fIevery\fR bug report that you send in.
132:
133: Do not expect a personal answer to a bug report. The purpose of reporting
134: bugs is to get them fixed for everyone in the next release, if possible.
135: For personal assistance, look in the SERVICE file (see above) for
136: a list of people who offer it.
137:
138: Please do not send anything but bug reports to this mailing list.
139: Send other stuff to [email protected] (or the
140: corresponding UUCP address). For more information about Emacs mailing
141: lists, see the file /usr/new/lib/emacs/etc/MAILINGLISTS. Bugs tend
142: actually to be fixed if they can be isolated, so it is in your
143: interest to report them in such a way that they can be easily
144: reproduced.
145: .PP
146: Bugs that I know about are: shell will not work with programs
147: running in Raw mode.
148:
This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.