Mercurial > hg > xemacs-beta

comparison man/xemacs/building.texi @ 3260:020e42010015

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
[xemacs-hg @ 2006-02-26 14:28:34 by michaels] 2006-02-26 Mike Sperber <mike@xemacs.org> * xemacs/building.texi (External Lisp): Document that `run-lisp' needs the os-utils package.
author michaels
date Sun, 26 Feb 2006 14:28:38 +0000
parents 7844ab77b582
children 7c7262c47538
comparison
equal deleted inserted replaced
3259:59f24c2a31ac 3260:020e42010015
578 be evaluated. You can also pass changed function definitions directly from 578 be evaluated. You can also pass changed function definitions directly from
579 the Emacs buffers in which you edit the Lisp programs to the inferior Lisp 579 the Emacs buffers in which you edit the Lisp programs to the inferior Lisp
580 process. 580 process.
581 581
582 @findex run-lisp 582 @findex run-lisp
583 To run an inferior Lisp process, type @kbd{M-x run-lisp}. This runs the 583 To run an inferior Lisp process, type @kbd{M-x run-lisp}.
584 (You need to the @file{os-utils} package installed for this.) This runs the
584 program named @code{lisp}, the same program you would run by typing 585 program named @code{lisp}, the same program you would run by typing
585 @code{lisp} as a shell command, with both input and output going through an 586 @code{lisp} as a shell command, with both input and output going through an
586 Emacs buffer named @samp{*lisp*}. In other words, any ``terminal output'' 587 Emacs buffer named @samp{*lisp*}. In other words, any ``terminal output''
587 from Lisp will go into the buffer, advancing point, and any ``terminal 588 from Lisp will go into the buffer, advancing point, and any ``terminal
588 input'' for Lisp comes from text in the buffer. To give input to Lisp, go 589 input'' for Lisp comes from text in the buffer. To give input to Lisp, go