view README @ 42490:0715d86d229c

Extensive changes to support multiple xscheme buffers: (run-scheme): Break up into new functions to facilitate starting processes in other buffers. (xscheme-start, xscheme-read-command-line): New functions. (start-scheme, select-scheme) (default-xscheme-runlight) (global-set-scheme-interaction-buffer) (local-set-scheme-interaction-buffer) (local-clear-scheme-interaction-buffer) (exit-scheme-interaction-mode) (verify-xscheme-buffer): New functions. (xscheme-process-name, xscheme-buffer-name) (xscheme-runlight): New internal vars. (default-xscheme-runlight): New const. (xscheme-start-process): Add args for the process/buffer names. (reset-scheme): Pass process/buffer names. (scheme-interaction-mode): Initialize new local vars. (reset-scheme, xscheme-send-string-2, xscheme-process-running-p) (xscheme-select-process-buffer, xscheme-process-buffer) (xscheme-send-region, xscheme-send-char, xscheme-send-interrupt) (xscheme-goto-output-point, xscheme-write-message-1): Use new var xscheme-process-name. (xscheme-start-process): Initialize xscheme-process-name and xscheme-buffer-name in the process buffer. Pass buffer name to xscheme-modeline-initialize. (xscheme-modeline-initialize): Add argument to specify buffer name for mode-line vars. (xscheme-process-sentinel): Make sure sentinel is run in the process buffer so it sees its local vars. (xscheme-process-filter-initialize, xscheme-set-runlight): More elaborate logic to handle multiple-buffer mode lines. (xscheme-enter-input-wait): Re-enable control-G handler upon entering input wait. (scheme-interaction-mode): Add arg to preserve local vars. (xscheme-enter-interaction-mode) (xscheme-enter-debugger-mode): Preserve local vars. (xscheme-start-process): Clobber local vars. (scheme-interaction-mode-commands): Allow end user to add commands to scheme-interaction-mode keymap. (scheme-interaction-mode-commands-alist): New variable. (xscheme-send-string): Don't use insert-before-markers. Implement a per-buffer kill ring: (xscheme-insert-expression) (xscheme-rotate-yank-pointer, xscheme-yank) (xscheme-yank-pop, xscheme-yank-push): New functions. (xscheme-expressions-ring) (xscheme-expressions-ring-yank-pointer) (xscheme-expressions-ring-max): New variables. (xscheme-send-string-1): Call xscheme-insert-expression to save expression in ring. (xscheme-yank-previous-send): Now an alias for xscheme-yank. (xscheme-previous-send): Deleted variable. (xscheme-send-string-2, xscheme-send-char, xscheme-send-proceed, xscheme-send-control-g-interrupt): Use process-send-string rather than send-string. (xscheme-send-region): Insert a newline after an expression that is submitted in the interaction buffer, for consistency with recent changes to Edwin. (xscheme-delete-output): New function mimics comint-delete-output. (xscheme-last-input-end): New internal variable. (xscheme-process-filter-output): Update xscheme-last-input-end. (xscheme-send-control-g-interrupt): Make sure that xscheme-control-g-disabled-p is looked up in the right buffer. (xscheme-enable-control-g): Clear C-g message if visible. (xscheme-control-g-message-string): New internal var. (xscheme-send-control-g-interrupt): Use new var. (xscheme-send-control-g-interrupt, xscheme-send-interrupt): Delay after sending interrupt in order to work around race condition. (xscheme-send-control-g-interrupt, xscheme-send-interrupt) (xscheme-send-char): Use xscheme-send-char rather than send-string to send single char. (xscheme-process-filter, xscheme-process-filter-alist): Add support for evaluating expressions outside of the call-excursion. (xscheme-process-filter:string-action-noexcursion): New func. (xscheme-write-value): Change output string to match that used by Edwin. (xscheme-coerce-prompt): Don't write a space after a command prompt. The PROMPT-FOR-COMMAND- procedures will take care of this for us. (reset-scheme): Delete process after killing it.

This directory tree holds version 21.1.50 of GNU Emacs, the extensible,
customizable, self-documenting real-time display editor.

You may encounter bugs in this release.  If you do, please report
them; your bug reports are valuable contributions to the FSF, since
they allow us to notice and fix problems on machines we don't have, or
in code we don't use often.  See the file BUGS for more information on
how to report bugs.

See the file etc/NEWS for information on new features and other
user-visible changes in recent versions of Emacs.

The file INSTALL in this directory says how to bring up GNU Emacs on
various systems, once you have loaded the entire subtree of this
directory.

The file etc/PROBLEMS contains information on many common problems that
occur in building, installing and running Emacs.

Reports of bugs in Emacs should be sent to the mailing list
[e-mail].  See the "Bugs" section of the Emacs
manual for more information on how to report bugs.  (The file `BUGS'
in this directory explains how you can find and read that section
using the Info files that come with Emacs.)  See `etc/MAILINGLISTS'
for more information on mailing lists relating to GNU packages.

The `etc' subdirectory contains several other files, named in capital
letters, which you might consider looking at when installing GNU
Emacs.

The file `configure' is a shell script to acclimate Emacs to the
oddities of your processor and operating system.  It creates the file
`Makefile' (a script for the `make' program), which automates the
process of building and installing Emacs.  See INSTALL for more
detailed information.

The file `configure.in' is the input used by the autoconf program to
construct the `configure' script.  Since Emacs has some configuration
requirements that autoconf can't meet directly, and for historical
reasons, `configure.in' uses an unholy marriage of custom-baked
configuration code and autoconf macros.  If you want to rebuild
`configure' from `configure.in', you will need to install a recent
version of autoconf and GNU m4.

The file `Makefile.in' is a template used by `configure' to create
`Makefile'.

The file `make-dist' is a shell script to build a distribution tar
file from the current Emacs tree, containing only those files
appropriate for distribution.  If you make extensive changes to Emacs,
this script will help you distribute your version to others.

There are several subdirectories:

`src'       holds the C code for Emacs (the Emacs Lisp interpreter and
            its primitives, the redisplay code, and some basic editing 
            functions).
`lisp'      holds the Emacs Lisp code for Emacs (most everything else).
`leim'      holds the library of Emacs input methods, Lisp code and 
            auxiliary data files required to type international characters
            which can't be directly produced by your keyboard.
`lib-src'   holds the source code for some utility programs for use by or
            with Emacs, like movemail and etags.
`etc'       holds miscellaneous architecture-independent data files
            Emacs uses, like the tutorial text and the Zippy the Pinhead
            quote database.  The contents of the `lisp', `leim', `info',
            `man', `lispref', and `lispintro' subdirectories are
            architecture-independent too.
`info'      holds the Info documentation tree for Emacs.
`man'       holds the source code for the Emacs Manual.  If you modify the
            manual sources, you will need the `makeinfo' program to produce
            an updated manual.  `makeinfo' is part of the GNU Texinfo
            package; you need version 4.0 or later of Texinfo.
`lispref'   holds the source code for the Emacs Lisp reference manual.
`lispintro' holds the source code for the Introduction to Programming
            in Emacs Lisp manual.

`msdos'     holds configuration files for compiling Emacs under MSDOG.
`vms'       holds instructions and useful files for running Emacs under VMS.
`nt'        holds various command files and documentation files that pertain
            to building and running Emacs on Windows 9X/ME/NT/2000/XP.
`mac'       holds instructions, sources, and other useful files for building
            and running Emacs on the Mac.

   Building Emacs on non-Posix platforms requires to install tools
that aren't part of the standard distribution of the OS.  The
platform-specific README files and installation instructions should
list the required tools.