Initial import from MIT Scheme

commit 41967043bf1019564f0dbcfa61a92773d1e37037 subdirectory src/edwin

some packaging scripts omitted
This commit is contained in:
Lassi Kortela 2021-04-26 14:53:20 +03:00
commit fa8c0263cd
171 changed files with 74230 additions and 0 deletions

7
AUTHORS Normal file
View File

@ -0,0 +1,7 @@
To find out what should go in this file, see "Information For
Maintainers of GNU Software" (maintain.texi), the section called
"Recording Changes".
Matt Birkholz The conversion to a plugin, the monitor-
world command.
The MIT/GNU Scheme Team The original EDWIN option.

482
COPYING Normal file
View File

@ -0,0 +1,482 @@
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
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.
<one line to give the library's name and a brief idea of what it does.>
Copyright (C) <year> <name of author>
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 Library General Public
License along with this library; 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.
<signature of Ty Coon>, 1 April 1990
Ty Coon, President of Vice
That's all there is to it!

7
ChangeLog Normal file
View File

@ -0,0 +1,7 @@
-*-Text-*-
Please see the git commit log:
$ git clone git://git.savannah.gnu.org/mit-scheme.git whatever
$ cd whatever/
$ git log origin/master -- src/edwin/ | more

28
NEWS Normal file
View File

@ -0,0 +1,28 @@
mit-scheme-edwin NEWS -- history of user-visible changes.
Copyright (C) 1986, 1987, 1988, 1989, 1990, 1991, 1992, 1993, 1994,
1995, 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005,
2006, 2007, 2008, 2009, 2010, 2011, 2012, 2013, 2014, 2015, 2016,
2017, 2018, 2019, 2020 Massachusetts Institute of Technology
This file is part of MIT/GNU Scheme.
MIT/GNU Scheme 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 of the
License, or (at your option) any later version.
MIT/GNU Scheme 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 MIT/GNU Scheme; if not, write to the Free Software
Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA
02110-1301, USA.
mit-scheme-edwin 3.117 - Matt Birkholz, 2018-10-09
==================================================
Initial plugin-ification.

47
README Normal file
View File

@ -0,0 +1,47 @@
The EDWIN option.
This option extends Scheme with a source code (text) editor. It is
built in the GNU standard way:
./configure ...
make all
make check
make install
The last command will attempt to create a subdirectory in the first
directory on Scheme's library path. If that directory is not writable
by you, super-user privileges may be required.
You can put a writable directory at the front of your Scheme's library
path by setting the MITSCHEME_LIBRARY_PATH environment variable and
creating a short optiondb file.
mkdir ~/.mit-scheme-x86-64
echo "(further-load-options #t)" > ~/.mit-scheme-x86-64/optiondb.scm
export MITSCHEME_LIBRARY_PATH=\
~/.mit-scheme-x86-64:/usr/local/lib/mit-scheme-x86-64
make install
To use: call the global `edit' procedure, or specify --edit on the
Scheme command line. For more information see the MIT/GNU Scheme
User's Manual.
Notes on the Edwin sources:
If you want to add a new file to the source tree, you need to
modify the following three files:
decls.scm
ed-ffi.scm
edwin.pkg
If the file should be loaded into the default edwin band, you must also
edit the file:
edwin.ldr
If the file is to be autoloaded, you must edit the file:
loadef.scm
So, in either case, you have to change four files.

786
TUTORIAL Normal file
View File

@ -0,0 +1,786 @@
Copyright (c) 1985 Free Software Foundation, Inc; See end for conditions.
You are looking at the Emacs tutorial. It has been enhanced to
include features important to Edwin.
Emacs commands generally involve the CONTROL key (sometimes labelled
CTRL or CTL) or the META key (sometimes labelled EDIT). Rather than
write out META or CONTROL each time we want you to prefix a character,
we'll use the following abbreviations:
C-<chr> means hold the CONTROL key while typing the character <chr>
Thus, C-f would be: hold the CONTROL key and type f.
M-<chr> means hold the META or EDIT key down while typing <chr>.
If there is no META or EDIT key, type <ESC>, release it,
then type the character <chr>. "<ESC>" stands for the
key labelled "ALT" or "ESC".
Important note: to end the Emacs session, type C-x C-c. (Two characters.)
The characters ">>" at the left margin indicate directions for you to
try using a command. For instance:
<<Blank lines inserted here by startup of help-with-tutorial>>
>> Now type C-v (View next screen) to move to the next screen.
(go ahead, do it by depressing the control key and v together).
From now on, you'll be expected to do this whenever you finish
reading the screen.
Note that there is an overlap when going from screen to screen; this
provides some continuity when moving through the file.
The first thing that you need to know is how to move around from
place to place in the file. You already know how to move forward a
screen, with C-v. To move backwards a screen, type M-v (depress the
META key and type v, or type <ESC>v if you don't have a META or EDIT
key).
>> Try typing M-v and then C-v to move back and forth a few times.
SUMMARY
-------
The following commands are useful for viewing screenfuls:
C-v Move forward one screenful
M-v Move backward one screenful
C-l Clear screen and redisplay everything
putting the text near the cursor at the center.
(That's control-L, not control-1.
There is no such character as control-1.)
>> Find the cursor and remember what text is near it.
Then type a C-l.
Find the cursor again and see what text is near it now.
BASIC CURSOR CONTROL
--------------------
Getting from screenful to screenful is useful, but how do you
reposition yourself within a given screen to a specific place?
There are several ways you can do this. One way (not the best, but
the most basic) is to use the commands Previous, Backward, Forward
and Next. As you can imagine these commands (which are given to
Emacs as C-p, C-b, C-f, and C-n respectively) move the cursor from
where it currently is to a new place in the given direction. Here,
in a more graphical form are the commands:
(P)REVIOUS line, C-p
:
:
(B)ACKWARD, C-b .... Current cursor position .... (F)ORWARD, C-f
:
:
(N)EXT line, C-n
>> Move the cursor to the line in the middle of that diagram
and type C-l to see the whole diagram centered in the screen.
Rather than using these keys, you may find it easier at first to use
the cursor motion keys with the triangles on them (on the bottom right
of the keyboard).
>> Move the cursor around using the cursor motion keys.
>> Move into the line with C-f's and then up with C-p's.
See what C-p does when the cursor is in the middle of the line.
Lines are separated by Newline characters. For most applications
there should normally be a Newline character at the end of the text,
as well, but it is up to you to make sure of this. A file can
validly exist without a Newline at the end.
>> Try to C-b at the beginning of a line. Do a few more C-b's.
Then do C-f's back to the end of the line and beyond.
When you go off the top or bottom of the screen, the text beyond
the edge is shifted onto the screen so that your instructions can
be carried out while keeping the cursor on the screen.
>> Try to move the cursor off the bottom of the screen with C-n and
see what happens.
If moving by characters is too slow, you can move by words. M-f
(Meta-f) moves forward a word and M-b moves back a word.
>> Type a few M-f's and M-b's. Intersperse them with C-f's and C-b's.
Notice the parallel between C-f and C-b on the one hand, and M-f and
M-b on the other hand. Very often Meta characters are used for
operations related to English text whereas Control characters operate
on the basic textual units that are independent of what you are
editing (characters, lines, etc). There is a similar parallel between
lines and sentences: C-a and C-e move to the beginning or end of a
line, and M-a and M-e move to the beginning or end of a sentence.
>> Try a couple of C-a's, and then a couple of C-e's.
Try a couple of M-a's, and then a couple of M-e's.
See how repeated C-a's do nothing, but repeated M-a's keep moving
farther. Do you think that this is right?
Two other simple cursor motion commands are M-< (Meta Less-than),
which moves to the beginning of the file, and M-> (Meta Greater-than),
which moves to the end of the file. You probably don't need to try
them, since finding this spot again will be boring. On most terminals
the "<" is above the comma and you must use the shift key to type it.
On these terminals you must use the shift key to type M-< also;
without the shift key, you would be typing M-comma.
The location of the cursor in the text is also called "point". To
paraphrase, the cursor shows on the screen where point is located in
the text.
Here is a summary of simple moving operations including the word and
sentence moving commands:
C-f Move forward a character
C-b Move backward a character
M-f Move forward a word
M-b Move backward a word
C-n Move to next line
C-p Move to previous line
C-a Move to beginning of line
C-e Move to end of line
M-a Move back to beginning of sentence
M-e Move forward to end of sentence
M-< Go to beginning of file
M-> Go to end of file
>> Try all of these commands now a few times for practice.
Since the last two will take you away from this screen,
you can come back here with M-v's and C-v's. These are
the most often used commands.
Like all other commands in Emacs, these commands can be given
arguments which cause them to be executed repeatedly. The way you
give a command a repeat count is by typing C-u and then the digits
before you type the command. If you have a META or EDIT key, you can
omit the C-u if you hold down the META or EDIT key while you type the
digits. This is easier, but we recommend the C-u method because it
works on any terminal.
For instance, C-u 8 C-f moves forward eight characters.
>> Try giving a suitable argument to C-n or C-p to come as close
as you can to this line in one jump.
The only apparent exception to this is the screen moving commands,
C-v and M-v. When given an argument, they scroll the screen up or
down by that many lines, rather than screenfuls. This proves to be
much more useful.
>> Try typing C-u 8 C-v now.
Did it scroll the screen up by 8 lines? If you would like to
scroll it down you can give an argument to M-v.
STOPPING EDWIN
--------------
If you incorrectly type a command, C-g will quit what it was doing
and allow you to enter it in again from scratch. Use C-g to discard
a numeric argument or the beginning of a command that you don't want
to finish. In Scheme or REPL mode, you can cancel a Scheme
evaluation by typing C-c C-c. You can tell if Scheme is evaluating
something by looking at the run-light for the word Eval instead of
Listen.
>> Type C-u 100 to make a numeric arg of 100, then type C-g.
Now type C-f. How many characters does it move?
If you have typed an <ESC> by mistake, you can get rid of it
with a C-g.
INSERTING AND DELETING
----------------------
If you want to insert text, just type it. Characters which you can
see, such as A, 7, *, etc. are taken by Emacs as text and inserted
immediately. Type <Return> (the carriage-return key) to insert a
Newline character.
You can delete the last character you typed by typing <Back space>.
More generally, <Back space> deletes the character immediately before the
current cursor position.
>> Do this now, type a few characters and then delete them
by typing <Back space> a few times. Don't worry about this file
being changed; you won't affect the master tutorial. This is just
a copy of it.
>> Now start typing text until you reach the right margin, and keep
typing. When a line of text gets too big for one line on the
screen, the line of text is "continued" onto a second screen line.
The backslash at the right margin indicates a line which has
been continued.
>> Use <Back space> to delete the text until the line fits on one screen
line again. The continuation line goes away.
>> Move the cursor to the beginning of a line and type <Back space>.
This deletes the newline before the line and merges the line onto the
previous line. The resulting line may be too long to fit, in which
case it has a continuation line.
>> Type <Return> to reinsert the Newline you deleted.
Remember that most Emacs commands can be given a repeat count;
this includes characters which insert themselves.
>> Try that now -- type C-u 8 * and see what happens.
You've now learned the most basic way of typing something in
Emacs and correcting errors. You can delete by words or lines
as well. Here is a summary of the delete operations:
<Delete> delete the character just before the cursor
C-d delete the next character after the cursor
M-<Delete> kill the word immediately before the cursor
M-d kill the next word after the cursor
C-k kill from the cursor position to end of line
M-k kill to the end of the current sentence
Notice that <Delete> and C-d vs M-<Delete> and M-d extend the parallel
started by C-f and M-f (well, <Delete> isn't really a control
character, but let's not worry about that). C-k and M-k are like C-e
and M-e, sort of, in that lines are opposite sentences.
Now suppose you kill something, and then you decide that you want to
get it back? Well, whenever you kill something bigger than a
character, Emacs saves it for you. To yank it back, use C-y. You
can kill text in one place, move elsewhere, and then do C-y; this is
a good way to move text around. Note that the difference
between "Killing" and "Deleting" something is that "Killed" things
can be yanked back, and "Deleted" things cannot. Generally, the
commands that can destroy a lot of text save it, while the ones that
attack only one character, or nothing but blank lines and spaces, do
not save.
For instance, type C-n a couple times to postion the cursor
at some line on this screen.
>> Do this now, move the cursor and kill that line with C-k.
Note that a single C-k kills the contents of the line, and a second
C-k kills the line itself, and make all the other lines move up. If
you give C-k a repeat count, it kills that many lines AND their
contents.
The text that has just disappeared is saved so that you can
retrieve it. To retrieve the last killed text and put it where
the cursor currently is, type C-y.
>> Try it; type C-y to yank the text back.
Think of C-y as if you were yanking something back that someone
took away from you. Notice that if you do several C-k's in a row
the text that is killed is all saved together so that one C-y will
yank all of the lines.
>> Do this now, type C-k several times.
Now to retrieve that killed text:
>> Type C-y. Then move the cursor down a few lines and type C-y
again. You now see how to copy some text.
What do you do if you have some text you want to yank back, and then
you kill something else? C-y would yank the more recent kill. But
the previous text is not lost. You can get back to it using the M-y
command. After you have done C-y to get the most recent kill, typing
M-Y replaces that yanked text with the previous kill. Typing M-y
again and again brings in earlier and earlier kills. When you
have reached the text you are looking for, you can just go away and
leave it there. If you M-y enough times, you come back to the
starting point (the most recent kill).
>> Kill a line, move around, kill another line.
Then do C-y to get back the second killed line.
Then do M-y and it will be replaced by the first killed line.
Do more M-y's and see what you get. Keep doing them until
the second kill line comes back, and then a few more.
If you like, you can try giving M-y positive and negative
arguments.
Evaluating Scheme Expressions
-----------------------------
Now that you can insert characters, you can type expressions and have
them evaluated. Read through this sequence of steps and then try
them out.
1. Type: C-x b *scheme* to get into an evaluation buffer.
2. Type: (+ 1 5)
3. Type: C-x C-e to evaluate the expression. Make sure the point
is after the closing paren.
4. Notice that the result is always printed into the *scheme*
buffer.
5. Type: M-p to access the history. Change a 5 to a 10 and
evaluate the new expression agian.
6. Type: C-x b TUTORIAL to get back to this screen.
>> Now try these steps out.
UNDO
----
Any time you make a change to the text and wish you had not done so,
you can undo the change (return the text to its previous state)
with the undo command, C-x u. Normally, C-x u undoes one command's
worth of changes; if you repeat the C-x u several times in a row,
each time undoes one more command. There are two exceptions:
commands that made no change (just moved the cursor) do not count,
and self-inserting characters are often lumped together in groups
of up to 20. This is to reduce the number of C-x u's you have to type.
>> Kill this line with C-k, then type C-x u and it should reappear.
C-_ is another command for undoing; it is just the same as C-x u
but easier to type several times in a row. The problem with C-_ is
that on some keyboards it is not obvious how to type it. That is
why C-x u is provided as well. On some DEC terminals, you can type
C-_ by typing / while holding down CTRL. Illogical, but what can
you expect from DEC?
Giving a numeric argument to C-_ or C-x u is equivalent to repeating
it as many times as the argument says.
FILES
-----
In order to make the text you edit permanent, you must put it in a
file. Otherwise, it will go away when your invocation of Emacs goes
away. You put your editing in a file by "finding" the file. What
finding means is that you see the contents of the file in your Emacs;
and, loosely speaking, what you are editing is the file itself.
However, the changes still don't become permanent until you "save" the
file. This is so you can have control to avoid leaving a half-changed
file around when you don't want to. Even then, Emacs leaves the
original file under a changed name in case your changes turn out
to be a mistake.
If you look near the bottom of the screen you will see a line that
begins and ends with dashes, and contains the string "Edwin: TUTORIAL".
Your copy of the Emacs tutorial is called "TUTORIAL". Whatever
file you find, that file's name will appear in that precise
spot.
The commands for finding and saving files are unlike the other
commands you have learned in that they consist of two characters.
They both start with the character Control-x. There is a whole series
of commands that start with Control-x; many of them have to do with
files, buffers, and related things, and all of them consist of
Control-x followed by some other character.
Another thing about the command for finding a file is that you have
to say what file name you want. We say the command "reads an argument
from the terminal" (in this case, the argument is the name of the
file). After you type the command
C-x C-f Find a file
Emacs asks you to type the file name. It echoes on the bottom
line of the screen. You are using the minibuffer now! this is
what the minibuffer is for. When you type <Return> to end the
file name, the minibuffer is no longer needed, so it disappears.
>> Type C-x C-f, then type C-g. This cancels the minibuffer,
and also cancels the C-x C-f command that was using the
minibuffer. So you do not find any file.
In a little while the file contents appear on the screen. You can
edit the contents. When you wish to make the changes permanent,
issue the command
C-x C-s Save the file
The contents of Emacs are written into the file. The first time you
do this, the original file is renamed to a new name so that it
is not lost. The new name is made by appending "~" to the end
of the original file's name.
When saving is finished, Emacs prints the name of the file written.
You should save fairly often, so that you will not lose very much
work if the system should crash.
>> Type C-x C-s, saving your copy of the tutorial.
This should print "Wrote .../TUTORIAL" at the bottom of the screen.
On VMS it will print "Wrote ...[...]TUTORIAL."
To make a new file, just find it "as if" it already existed. Then
start typing in the text. When you ask to "save" the file, Emacs
will really create the file with the text that you have inserted.
From then on, you can consider yourself to be editing an already
existing file.
BUFFERS
-------
If you find a second file with C-x C-f, the first file remains
inside Emacs. You can switch back to it by finding it again with
C-x C-f. This way you can get quite a number of files inside Emacs.
The object inside Emacs which holds the text read from one file
is called a "buffer." Finding a file makes a new buffer inside Emacs.
To see a list of the buffers that exist in Emacs, type
C-x C-b List buffers
>> Try C-x C-b now.
See how each buffer has a name, and it may also have a file name
for the file whose contents it holds. Some buffers do not correspond
to files. For example, the buffer named "*Buffer List*" does
not have any file. It is the buffer which contains the buffer
list that was made by C-x C-b. ANY text you see in an Emacs window
has to be in some buffer.
>> Type C-x 1 to get rid of the buffer list.
If you make changes to the text of one file, then find another file,
this does not save the first file. Its changes remain inside Emacs,
in that file's buffer. The creation or editing of the second file's
buffer has no effect on the first file's buffer. This is very useful,
but it also means that you need a convenient way to save the first
file's buffer. It would be a nuisance to have to switch back to
it with C-x C-f in order to save it with C-x C-s. So we have
C-x s Save some buffers
C-x s goes through the list of all the buffers you have
and finds the ones that contain files you have changed.
For each such buffer, C-x s asks you whether to save it.
EXTENDING THE COMMAND SET
-------------------------
There are many, many more Emacs commands than could possibly be put
on all the control and meta characters. Emacs gets around this with
the X (eXtend) command. This comes in two flavors:
C-x Character eXtend. Followed by one character.
M-x Named command eXtend. Followed by a long name.
These are commands that are generally useful but used less than the
commands you have already learned about. You have already seen two
of them: the file commands C-x C-f to Find and C-x C-s to Save.
Another example is the command to tell Emacs that you'd like to stop
editing and get rid of Emacs. The command to do this is C-x C-c.
(Don't worry; it offers to save each changed file before it kills the
Emacs.)
C-z is the usual way to exit Emacs, because it is always better not to
kill the Emacs if you are going to do any more editing. On systems
which allow it, C-z exits from Emacs to the shell but does not destroy
the Emacs; if you use the C shell, you can resume Emacs with the `fg'
command (or, more generally, with `%emacs', which works even if your
most recent job was some other). On systems where suspending is not
possible, C-z creates a subshell running under Emacs to give you the
chance to run other programs and return to Emacs afterward, but it
does not truly "exit" from Emacs. In this case, the shell command
`exit' is the usual way to get back to Emacs from the subshell.
You would use C-x C-c if you were about to log out. You would
also use it to exit an Emacs invoked under mail handling programs
and other random utilities, since they may not believe you have
really finished using the Emacs if it continues to exist.
There are many C-x commands. The ones you know are:
C-x C-f Find file.
C-x C-s Save file.
C-x C-b List buffers.
C-x C-c Quit Emacs.
C-x u Undo.
Named eXtended commands are commands which are used even less
frequently, or commands which are used only in certain modes. These
commands are usually called "functions". An example is the function
replace-string, which globally replaces one string with another. When
you type M-x, Emacs prompts you at the bottom of the screen with
M-x and you should type the name of the function you wish to call; in
this case, "replace-string". Just type "repl s<TAB>" and Emacs will
complete the name. End the command name with <Return>.
Then type the two "arguments"--the string to be replaced, and the string
to replace it with--each one ended with a Return.
>> Move the cursor to the blank line two lines below this one.
Then type M-x repla s<Return>changed<Return>altered<Return>.
Notice how this line has changed: you've replaced
the word c-h-a-n-g-e-d with "altered" wherever it occured
after the cursor.
MODE LINE
---------
If Emacs sees that you are typing commands slowly it shows them to you
at the bottom of the screen in an area called the "echo area." The echo
area contains the bottom line of the screen. The line immediately above
it is called the MODE LINE. The mode line says something like
--**--Emacs: TUTORIAL (Fundamental)----58%-------------
This is a very useful "information" line.
You already know what the filename means--it is the file you have
found. What the --NN%-- means is that NN percent of the file is
above the top of the screen. If the top of the file is on the screen,
it will say --TOP-- instead of --00%--. If the bottom of the file is
on the screen, it will say --BOT--. If you are looking at a file so
small it all fits on the screen, it says --ALL--.
The stars near the front mean that you have made changes to the text.
Right after you visit or save a file, there are no stars, just dashes.
The part of the mode line inside the parentheses is to tell you what
modes you are in. The default mode is Fundamental which is what you
are in now. It is an example of a "major mode". There are several
major modes in Emacs for editing different languages and text, such
as Scheme mode, Text mode, etc. At any time one and only one major
mode is active, and its name can always be found in the mode line
just where "Fundamental" is now. Each major mode makes a few
commands behave differently. For example, there are commands for
creating comments in a program, and since each programming language
has a different idea of what a comment should look like, each major
mode has to insert comments differently. Each major mode is the name
of an extended command, which is how you get into the mode. For
example, M-X fundamental-mode is how to get into Fundamental mode.
If you are going to be editing Scheme code, you should probably use
Text Mode.
>> Type M-x scheme-mode<Return>.
To get documentation on your current major mode, type C-h m.
>> Use C-u C-v once or more to bring this line near the top of screen.
>> Type C-h m, to see how Scheme mode differs from Fundamental mode.
>> Type C-x 1 to remove the documentation from the screen.
Major modes are called major because there are also minor modes.
They are called minor because they aren't alternatives to the major
modes, just minor modifications of them. Each minor mode can be
turned on or off by itself, regardless of what major mode you are in,
and regardless of the other minor modes. So you can use no minor
modes, or one minor mode, or any combination of several minor modes.
SEARCHING
---------
Emacs can do searches for strings (these are groups of contiguous
characters or words) either forward through the file or backward
through it. To search for the string means that you are trying to
locate it somewhere in the file and have Emacs show you where the
occurrences of the string exist. This type of search is somewhat
different from what you may be familiar with. It is a search that is
performed as you type in the thing to search for. The command to
initiate a search is C-s for forward search, and C-r for reverse
search. BUT WAIT! Don't do them now. When you type C-s you'll
notice that the string "I-search" appears as a prompt in the echo
area. This tells you that Emacs is in what is called an incremental
search waiting for you to type the thing that you want to search for.
<ESC> terminates a search.
>> Now type C-s to start a search. SLOWLY, one letter at a time,
type the word 'cursor', pausing after you type each
character to notice what happens to the cursor.
>> Type C-s to find the next occurrence of "cursor".
>> Now type <Delete> four times and see how the cursor moves.
>> Type <ESC> to terminate the search.
Did you see what happened? Emacs, in an incremental search, tries to
go to the occurrence of the string that you've typed out so far. To go
to the next occurrence of 'cursor' just type C-s again. If no such
occurrence exists Emacs beeps and tells you that it is a failing
search. C-g would also terminate the search.
If you are in the middle of an incremental search and type <Delete>,
you'll notice that the last character in the search string is erased
and the search backs up to the last place of the search. For
instance, suppose you currently have typed 'cu' and you see that your
cursor is at the first occurrence of 'cu'. If you now type <Delete>,
the 'u' on the search line is erased and you'll be repositioned in the
text to the occurrence of 'c' where the search took you before you
typed the 'u'. This provides a useful means for backing up while you
are searching.
If you are in the middle of a search and happen to type a control
character (other than a C-s or C-r, which tell Emacs to search for the
next occurrence of the string), the search is terminated.
The C-s starts a search that looks for any occurrence of the search
string AFTER the current cursor position. But what if you want to
search for something earlier in the text? To do this, type C-r for
Reverse search. Everything that applies to C-s applies to C-r except
that the direction of the search is reversed.
RECURSIVE EDITING LEVELS
------------------------
Sometimes you will get into what is called a "recursive editing
level". This is indicated by square brackets in the mode line,
surrounding the parentheses around the major mode name. For
example, you might see [(Fundamental)] instead of (Fundamental).
To get out of the recursive editing level, type
M-x top-level<Return>.
>> Try that now; it should display "Back to top level"
at the bottom of the screen.
In fact, you were ALREADY at top level (not inside a recursive editing
level) if you have obeyed instructions. M-x top-level does not care;
it gets out of any number of recursive editing levels, perhaps zero,
to get back to top level.
You can't use C-g to get out of a recursive editing level because C-g
is used for discarding numeric arguments and partially typed commands
WITHIN the recursive editing level.
WINDOWS
-------
Emacs can have several windows, each displaying its own text.
At this stage it is better not to go into the techniques of
using multiple windows. But you do need to know how to get
rid of extra windows that may appear to display help or
output from certain commands. It is simple:
C-x 1 One window (i.e., kill all other windows).
That is Control-x followed by the digit 1.
C-x 1 makes the window which the cursor is in become
the full screen, by getting rid of any other windows.
>> Move the cursor to this line and type C-u 0 C-l.
>> Type Control-h k Control-f.
See how this window shrinks, while a new one appears
to display documentation on the Control-f command.
>> Type C-x 1 and see the documentation listing window disappear.
GETTING MORE HELP
-----------------
In this tutorial we have tried to supply just enough information to
get you started using Emacs. There is so much available in Emacs that
it would be impossible to explain it all here. However, you may want
to learn more about Emacs since it has numerous desirable features
that you don't know about yet. Emacs has a great deal of internal
documentation. All of these commands can be accessed through
the character Control-h, which we call "the Help character"
because of the function it serves.
To use the HELP features, type the C-h character, and then a
character saying what kind of help you want. If you are REALLY lost,
type C-h ? and Emacs will tell you what kinds of help it can give.
If you have typed C-h and decide you don't want any help, just
type C-G to cancel it.
The most basic HELP feature is C-h c. Type C-h, a c, and a
command character or sequence, and Emacs displays a very brief
description of the command.
>> Type C-h c Control-p.
The message should be something like
C-p runs the command previous-line
This tells you the "name of the function". That is important in
writing Lisp code to extend Emacs; it also is enough to remind
you of what the command does if you have seen it before but did
not remember.
Multi-character commands such as C-x C-s and (if you have no META or
EDIT key) <ESC>v are also allowed after C-h c.
To get more information on the command, use C-h k instead of C-h c.
>> Type C-h k Control-p.
This displays the documentation of the function, as well as its name,
in an Emacs window. When you are finished reading the output, type
C-x 1 to get rid of the help text. You do not have to do this right
away. You can do some editing based on the help text before you type
C-x 1.
Here are some other useful C-h options:
C-h f Describe a function. You type in the name of the
function.
>> Try typing C-h f previous-line<Return>.
This prints all the information Emacs has about the
function which implements the C-P command.
C-h a Command Apropos. Type in a keyword and Emacs will list
all the commands whose names contain that keyword.
These commands can all be invoked with Meta-x.
For some commands, Command Apropos will also list a one
or two character sequence which has the same effect.
>> Type C-h a file<Return>. You will see a list of all M-x commands
with "file" in their names. You will also see commands
like C-x C-f and C-x C-w, listed beside the command names
find-file and write-file.
CONCLUSION
----------
Remember, to exit Emacs permanently use C-x C-c. To exit to a shell
temporarily, so that you can come back in, use C-z.
This tutorial is meant to be understandable to all new users, so if
you found something unclear, don't sit and blame yourself - complain!
COPYING
-------
This tutorial descends from a long line of Emacs tutorials
starting with the one written by Stuart Cracraft for the original Emacs.
This version of the tutorial, like GNU Emacs, is copyrighted, and
comes with permission to distribute copies on certain conditions:
Copyright (c) 1985 Free Software Foundation
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 altered them.
The conditions for copying Emacs itself are slightly different
but in the same spirit. Please read the file COPYING and then
do give copies of GNU Emacs to your friends.
Help stamp out software obstructionism ("ownership") by using,
writing, and sharing free software!

30
edwin.cbf Normal file
View File

@ -0,0 +1,30 @@
#| -*-Scheme-*-
Copyright (C) 1986, 1987, 1988, 1989, 1990, 1991, 1992, 1993, 1994,
1995, 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005,
2006, 2007, 2008, 2009, 2010, 2011, 2012, 2013, 2014, 2015, 2016,
2017, 2018, 2019, 2020 Massachusetts Institute of Technology
This file is part of MIT/GNU Scheme.
MIT/GNU Scheme 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 of the License, or (at
your option) any later version.
MIT/GNU Scheme 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 MIT/GNU Scheme; if not, write to the Free Software
Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301,
USA.
|#
;;;; Script to incrementally compile the editor (from .bins)
(fluid-let ((compiler:coalescing-constant-warnings? #f))
(compile-directory "."))

261
edwin.ldr Normal file
View File

@ -0,0 +1,261 @@
#| -*-Scheme-*-
Copyright (C) 1986, 1987, 1988, 1989, 1990, 1991, 1992, 1993, 1994,
1995, 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005,
2006, 2007, 2008, 2009, 2010, 2011, 2012, 2013, 2014, 2015, 2016,
2017, 2018, 2019, 2020 Massachusetts Institute of Technology
This file is part of MIT/GNU Scheme.
MIT/GNU Scheme 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 of the License, or (at
your option) any later version.
MIT/GNU Scheme 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 MIT/GNU Scheme; if not, write to the Free Software
Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301,
USA.
|#
;;; program to load package contents
;;; **** This program (unlike most .ldr files) is not generated by a program.
(declare (usual-integrations))
(lambda (package/loader key-alist)
(let ((to-avoid-list (if (file-exists? "edwin.bad")
(fasload "edwin.bad")
'()))
(bad-environment-tag '*bad-environment*))
(let ((->environment
(lambda (spec)
(if (name->package spec)
(->environment spec)
(cons bad-environment-tag spec)))))
(define (load file env)
(cond ((string-member? file to-avoid-list)
(newline)
(write-string "* skipping ")
(write-string file)
false)
((and (pair? env)
(eq? (car env) bad-environment-tag))
(error "Attempting to load into non-existent package"
file (cdr env)))
(else (package/loader file env)
true)))
(define (load-set files env)
(if (null? files)
true
(let ((val (load (car files) env)))
(boolean-and val (load-set (cdr files) env)))))
(define (load-set-and-initialize! files env)
(and (load-set files env)
((access initialize-package! env))))
(define (lookup var)
(cond ((assq var key-alist) => cdr)
(else false)))
(define (load-case var alist env)
(for-each (lambda (key/file)
(and (eq? (lookup var) (car key/file))
(load (cdr key/file) env)))
alist))
(define string-member? (member-procedure string=?))
(define (boolean-and a b) (and a b))
(if (memq (lookup 'os-type) '(unix nt))
(begin
(load-option 'subprocess)
(load-option 'synchronous-subprocess)))
(load-option 'rb-tree)
(load-option 'hash-table)
(load-option 'regular-expression)
(load-option 'mime-codec)
(let ((environment (->environment '(edwin))))
(load "utils" environment)
(load "adapters" (->environment '(edwin adapters)))
(load "string" (->environment '(edwin string)))
(load "nvector" environment)
(load "ring" environment)
(load "strtab" environment)
(load "strpad" environment)
(load "macros" (->environment '(edwin macros)))
(load "class" environment)
(load "clscon" (->environment '(edwin class-constructor)))
(load "clsmac" (->environment '(edwin class-macros)))
(load "xform"
(->environment
'(edwin class-macros transform-instance-variables)))
(load "paths" environment)
(load "struct" environment)
(load "grpops" (->environment '(edwin group-operations)))
(load "txtprp" (->environment '(edwin text-properties)))
(load "regops" environment)
(load "motion" environment)
(load "search" environment)
(load "image" environment)
(load "comman" environment)
(load "docstr" environment)
(if (not (memq (lookup 'os-type) '(dos nt)))
(set! (access *external-doc-strings?* environment) #f))
(load "comtab" (->environment '(edwin comtab)))
(load "modes" environment)
(load "buffer" environment)
(load "bufset" environment)
(load "display" (->environment '(edwin display-type)))
(load "screen" (->environment '(edwin screen)))
(let ((environment (->environment '(edwin window))))
(load "window" environment)
(load "utlwin" environment)
(load "bufwin" environment)
(load "bufwfs" environment)
(load "bufwiu" environment)
(load "bufwmc" environment)
(load "comwin" (->environment '(edwin window combination)))
(load "modwin" environment)
(load "buffrm" environment)
(load "edtfrm" environment))
(load "calias" environment)
(load "edtstr" environment)
(load "editor" environment)
(load "curren" environment)
;; "undo" must be loaded after "editor":
(load "undo" (->environment '(edwin undo)))
(load "simple" environment)
(load "debuge" environment)
(load "modlin" (->environment '(edwin modeline-string)))
(load "input" (->environment '(edwin keyboard)))
(load "prompt" (->environment '(edwin prompt)))
(load "comred" (->environment '(edwin command-reader)))
(load "bufinp" (->environment '(edwin buffer-input-port)))
(load "bufout" (->environment '(edwin buffer-output-port)))
(load "winout" (->environment '(edwin window-output-port)))
(load "things" environment)
(load "tparse" environment)
(load "syntax" environment)
(load "regexp" (->environment '(edwin regular-expression)))
(load "comatch" environment)
(load "keyparse" (->environment '(edwin keyparser)))
(load "linden" (->environment '(edwin lisp-indentation)))
(case (lookup 'os-type)
((unix)
(load "unix" environment))
((dos nt)
(load "dos" environment)
(load "dosfile" environment)))
(load "fileio" environment)
(let ((env (->environment '(edwin screen console-screen))))
(load-set-and-initialize! '("termcap" "tterm") env)
(if (memq (lookup 'os-type) '(dos nt))
(begin
(load "ansi" env)
(if (load "bios" env)
((access bios-initialize-package! env))))))
(case (lookup 'os-type)
((nt)
(load-set-and-initialize! '("win32")
(->environment '(edwin screen win32)))
(load-set-and-initialize! '("key-w32")
(->environment '(edwin win32-keys))))
((unix)
(load "xterm" (->environment '(edwin screen x-screen)))))
(load-case 'os-type
'((unix . "process")
(dos . "dosproc")
(nt . "process"))
(->environment '(edwin process)))
(load "mousecom" environment)
(case (lookup 'os-type)
((nt) (load "win32com" (->environment '(edwin win-commands)))))
;; debug depends on button1-down defined in mousecom
(load "debug" (->environment '(edwin debugger)))
(let ((env (->environment '(edwin dired))))
(load "dired" env)
(case (lookup 'os-type)
((unix) (load "dirunx" env))
((nt) (load "dirw32" env))))
(load "abbrev" environment)
(load "argred" (->environment '(edwin command-argument)))
(load "autold" environment)
(load "autosv" environment)
(load "basic" environment)
(load "bufcom" environment)
(load "bufmnu" (->environment '(edwin buffer-menu)))
(load "c-mode" environment)
(load "javamode" environment)
(load "cinden" (->environment '(edwin c-indentation)))
(load "comhst" environment)
(load "comint" environment)
(load "compile" environment)
(load "dabbrev" environment)
(load "evlcom" environment)
(load "filcom" environment)
(load "fill" environment)
(load "hlpcom" environment)
(load "info" (->environment '(edwin info)))
(load "intmod" (->environment '(edwin inferior-repl)))
(load "keymap" (->environment '(edwin command-summary)))
(load "kilcom" environment)
(load "kmacro" environment)
(load "lincom" environment)
(load "lspcom" environment)
(load "malias" (->environment '(edwin mail-alias)))
(load "motcom" environment)
(load "occur" (->environment '(edwin occurrence)))
(load "outline" environment)
;;(load "rcs" (->environment '(edwin rcs)))
(load "reccom" (->environment '(edwin rectangle)))
(load "regcom" (->environment '(edwin register-command)))
(load "replaz" environment)
(load "rfc822" (->environment '(edwin rfc822)))
(load "rmail" (->environment '(edwin rmail)))
(load "rmailsum" (->environment '(edwin rmail)))
(load "rmailsrt" (->environment '(edwin rmail)))
(load "schmod" environment)
(load "sendmail" (->environment '(edwin sendmail)))
(load "sercom" environment)
(load "iserch" (->environment '(edwin incremental-search)))
(load "shell" environment)
(load "tagutl" (->environment '(edwin tags)))
(load "texcom" environment)
(load "htmlmode" environment)
(load "diff" (->environment '(edwin diff)))
(load "rcsparse" (->environment '(edwin rcs-parse)))
(load "vc" (->environment '(edwin vc)))
(load "vc-rcs" (->environment '(edwin vc)))
(load "vc-cvs" (->environment '(edwin vc)))
(load "vc-svn" (->environment '(edwin vc)))
(load "vc-bzr" (->environment '(edwin vc)))
(load "vc-git" (->environment '(edwin vc)))
(load "wincom" environment)
(load "scrcom" environment)
(load "modefs" environment)
(load "loadef" environment)
#|
(load-set-and-initialize! '("bochser" "bochsmod")
(->environment '(edwin bochser)))
|#
(load "notify" environment)
(load "world-monitor" environment)
(if (access *external-doc-strings?* environment)
(begin
(set! (access *external-doc-strings?* environment) false)
(warn "Remember to use ``dump-doc-strings''!")))))))

1928
edwin.pkg Normal file

File diff suppressed because it is too large Load Diff

93
edwin.sf Normal file
View File

@ -0,0 +1,93 @@
#| -*-Scheme-*-
Copyright (C) 1986, 1987, 1988, 1989, 1990, 1991, 1992, 1993, 1994,
1995, 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005,
2006, 2007, 2008, 2009, 2010, 2011, 2012, 2013, 2014, 2015, 2016,
2017, 2018, 2019, 2020 Massachusetts Institute of Technology
This file is part of MIT/GNU Scheme.
MIT/GNU Scheme 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 of the License, or (at
your option) any later version.
MIT/GNU Scheme 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 MIT/GNU Scheme; if not, write to the Free Software
Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301,
USA.
|#
(load-option 'cref)
(if (not (name->package '(edwin)))
(let ((package-set (package-set-pathname "edwin")))
(if (not (file-modification-time<? "edwin.pkg" package-set))
(cref/generate-trivial-constructor "edwin"))
(construct-packages-from-file (fasload package-set))))
(if (lexical-unreferenceable? (->environment '(edwin string))
'string?)
(begin
(fluid-let ((sf/default-syntax-table (->environment '(edwin))))
(sf-conditionally "string"))
(receive (scm bin spec) (sf/pathname-defaulting "string" #f #f)
scm spec
(load bin '(edwin string)))))
(if (lexical-unreferenceable? (->environment '(edwin class-constructor))
'class-descriptors)
(begin
(let ((sf-and-load
(lambda (files package)
(fluid-let ((sf/default-syntax-table (->environment '())))
(sf-conditionally files))
(for-each (lambda (file)
(receive (scm bin spec)
(sf/pathname-defaulting file #f #f)
scm spec
(load bin package)))
files))))
(sf-and-load '("macros") '(edwin macros))
(sf-and-load '("clsmac") '(edwin class-macros))
(sf-and-load '("xform")
'(edwin class-macros transform-instance-variables))
(sf-and-load '("class") '(edwin))
(sf-and-load '("clscon") '(edwin class-constructor)))))
(let ((read-class-definitions
(lambda (filename)
(if (environment-bound? system-global-environment 'with-notification)
(with-notification
(lambda (port)
(write-string "Pre-loading class definitions from " port)
(write filename port))
(lambda ()
(syntax* (read-file (string-append filename ".scm"))
(->environment '(edwin window)))))
(begin
(fresh-line)
(write-string "Pre-loading class definitions from ")
(write filename)
(syntax* (read-file (string-append filename ".scm"))
(->environment '(edwin window)))
(write-string " -- done")
(newline))))))
(read-class-definitions "window")
(read-class-definitions "utlwin")
(read-class-definitions "modwin")
(read-class-definitions "bufwin")
(read-class-definitions "comwin")
(read-class-definitions "buffrm")
(read-class-definitions "edtfrm"))
(load "decls")
(cref/generate-constructors "edwin")
(sf-conditionally "edwin.ldr")

634
edwin/abbrev.scm Normal file
View File

@ -0,0 +1,634 @@
#| -*-Scheme-*-
Copyright (C) 1986, 1987, 1988, 1989, 1990, 1991, 1992, 1993, 1994,
1995, 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005,
2006, 2007, 2008, 2009, 2010, 2011, 2012, 2013, 2014, 2015, 2016,
2017, 2018, 2019, 2020 Massachusetts Institute of Technology
This file is part of MIT/GNU Scheme.
MIT/GNU Scheme 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 of the License, or (at
your option) any later version.
MIT/GNU Scheme 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.