From ef14c259334e1f024b445e3b015bb8015e3a1e96 Mon Sep 17 00:00:00 2001 From: Karl Heuer Date: Tue, 6 Jun 1995 19:21:15 +0000 Subject: *** empty log message *** --- lispref/edebug.texi | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'lispref/edebug.texi') diff --git a/lispref/edebug.texi b/lispref/edebug.texi index f32b516199e..5aec9f96f46 100644 --- a/lispref/edebug.texi +++ b/lispref/edebug.texi @@ -214,7 +214,7 @@ must tell it; @xref{Instrumenting Macro Calls}, for details. definition in a way that does not instrument. There are two ways of evaluating forms that never instrument them: from a file with @code{load}, and from the minibuffer with @code{eval-expression} -(@kbd{M-ESC}). +(@kbd{M-:}). If Edebug detects a syntax error while instrumenting, it leaves point at the erroneous code and signals an @code{invalid-read-syntax} error. @@ -626,7 +626,7 @@ Evaluate expression @var{exp} in the context outside of Edebug (@code{edebug-eval-expression}). That is, Edebug tries to minimize its interference with the evaluation. -@item M-@key{ESC} @var{exp} @key{RET} +@item M-: @var{exp} @key{RET} Evaluate expression @var{exp} in the context of Edebug itself. @item C-x C-e -- cgit v1.2.1