4.8.2 Evaluation commands

Evaluate Defun

Editor Command

Argument: None
Key sequence: +Ctrl+X

Evaluates the current top-level form. If the current point is between two forms, the previous form is evaluated.

Re-evaluate Defvar

Editor Command

Argument: None
Key sequence: None

Evaluates the current top-level form if it is adefvar. If the current point is between two forms, the previous form is evaluated. The form is treated as if the variable is not bound.

Evaluate Expression

Editor Command

Argument: expression
Key sequence:Esc+Escexpression

Evaluates expression. The expression to be evaluated is typed into the Echo Area and the result of the evaluation is displayed there also.

Evaluate Region

Editor Command

Argument: None
Key sequence: None

Evaluates the Lisp forms in the region between the current point and the mark.

Evaluate Buffer

Editor Command

Argument: None
Key sequence: None

Evaluates the Lisp forms in the current buffer.

Load File

Editor Command

Argument: file
Key sequence: None

Loads file into the current eval server, so that all Lisp forms in the file are evaluated.

Toggle Error Catch

Editor Command

Argument: None
Key sequence: None

Toggles error catching for expressions evaluated in the editor. By default, if there is an error in an expression evaluated in the editor, a Notifier window is opened which provides the user with a number of options, including debug, re-evaluation and aborting of the editor command. However, this behavior can be changed by usingToggle Error Catch, so that in the event of an error, the error message is printed in the Echo Area, and the user is given no restart or debug options.

Evaluate Buffer Changed Definitions

Editor Command

Argument: None
Key sequence: None

Evaluates definitions that have been changed in the current buffer during the current LispWorks session (useBuffer Changed Definitions on page 106 to see which definitions have changed). A prefix argument equal to the value ofPrefix-Argument-Default causes evaluation of definitions changed since last evaluated. A prefix argument of 1 causes evaluation of definitions changed since last saved.

Evaluate Changed Definitions

Editor Command

Argument: None
Key sequence: None

Evaluates definitions in all Lisp buffers that have been changed during the current LispWorks session. The effect of prefixes is the same as forEvaluate Buffer Changed Definitions.

Evaluate System Changed Definitions

Editor Command

Argument: system
Key sequence: None

Evaluates definitions that have been changed in system during the current LispWorks session.

---

LispWorks Editor User Guide - 15 Oct 1998

Generated with Harlequin WebMaker