* viper-cmd.el (viper-prefix-commands): make into a defconst.

[gnu-emacs] / lisp / cmuscheme.el

diff --git a/lisp/cmuscheme.el b/lisp/cmuscheme.el
index c0539d465a0a18ec3f2c2720caa36e271b67d8d7..03cd8ee4d9cffa3fd3f81f03c5ec825a4a6f7246 100644 (file)
--- a/lisp/cmuscheme.el
+++ b/lisp/cmuscheme.el
@@ -1,6 +1,6 @@
-;;; cmuscheme.el --- Scheme process in a buffer. Adapted from tea.el.
+;;; cmuscheme.el --- Scheme process in a buffer. Adapted from tea.el
 
-;; Copyright (C) 1988, 1994, 1997 Free Software Foundation, Inc.
+;; Copyright (C) 1988, 1994, 1997, 2004  Free Software Foundation, Inc.
 
 ;; Author: Olin Shivers <olin.shivers@cs.cmu.edu>
 ;; Maintainer: FSF
@@ -47,19 +47,19 @@
 ;; character to the scheme process.  Cmuscheme mode does *not* provide this
 ;; functionality. If you are a cscheme user, you may prefer to use the
 ;; xscheme.el/cscheme -emacs interaction.
-;; 
+;;
 ;; Here's a summary of the pros and cons, as I see them.
 ;; xscheme: Tightly integrated with inferior cscheme process!  A few commands
 ;;          not in cmuscheme. But. Integration is a bit of a hack.  Input
 ;;          history only keeps the immediately prior input. Bizarre
 ;;          keybindings.
-;; 
+;;
 ;; cmuscheme: Not tightly integrated with inferior cscheme process.  But.
 ;;            Carefully integrated functionality with the entire suite of
 ;;            comint-derived CMU process modes. Keybindings reminiscent of
 ;;            Zwei and Hemlock. Good input history. A few commands not in
 ;;            xscheme.
-;;  
+;;
 ;; It's a tradeoff. Pay your money; take your choice. If you use a Scheme
 ;; that isn't Cscheme, of course, there isn't a choice. Xscheme.el is *very*
 ;; Cscheme-specific; you must use cmuscheme.el.  Interested parties are
@@ -140,9 +140,9 @@
   (define-key map [switch]
     '("Switch to Scheme" . switch-to-scheme))
   (define-key map [com-def-go]
-    '("Compile Definitiion & Go" . scheme-compile-definition-and-go))
+    '("Compile Definition & Go" . scheme-compile-definition-and-go))
   (define-key map [com-def]
-    '("Compile Definitiion" . scheme-compile-definition))
+    '("Compile Definition" . scheme-compile-definition))
   (define-key map [send-def-go]
     '("Evaluate Last Definition & Go" . scheme-send-definition-and-go))
   (define-key map [send-def]
@@ -352,7 +352,7 @@ next one.")
 (defun scheme-load-file (file-name)
   "Load a Scheme file FILE-NAME into the inferior Scheme process."
   (interactive (comint-get-source "Load Scheme file: " scheme-prev-l/c-dir/file
-                                 scheme-source-modes t)) ; T because LOAD
+                                 scheme-source-modes t)) ; t because `load'
                                                           ; needs an exact name
   (comint-check-source file-name) ; Check to see if buffer needs saved.
   (setq scheme-prev-l/c-dir/file (cons (file-name-directory    file-name)
@@ -366,7 +366,7 @@ next one.")
   (interactive (comint-get-source "Compile Scheme file: "
                                  scheme-prev-l/c-dir/file
                                  scheme-source-modes
-                                 nil)) ; NIL because COMPILE doesn't
+                                 nil)) ; nil because COMPILE doesn't
                                         ; need an exact name.
   (comint-check-source file-name) ; Check to see if buffer needs saved.
   (setq scheme-prev-l/c-dir/file (cons (file-name-directory    file-name)
@@ -432,9 +432,10 @@ for a minimal, simple implementation.  Feel free to extend it.")
 This is a good place to put keybindings."
   :type 'hook
   :group 'cmuscheme)
-       
+
 (run-hooks 'cmuscheme-load-hook)
 
 (provide 'cmuscheme)
 
+;; arch-tag: e8795f4a-c496-45a2-97b4-8e0f2a2c57d2
 ;;; cmuscheme.el ends here