Re: edebug breaks pre,post-command-hook

[Stefan Monnier]

> ***************
> *** 2241,2248 ****
  
>           ;; Save the outside value of executing macro.  (here??)
>           (edebug-outside-executing-macro executing-kbd-macro)
> !         (edebug-outside-pre-command-hook pre-command-hook)
> !         (edebug-outside-post-command-hook post-command-hook))
>       (unwind-protect
>           (let (;; Don't keep reading from an executing kbd macro
>                 ;; within edebug unless edebug-continue-kbd-macro is
> --- 2241,2250 ----
  
>           ;; Save the outside value of executing macro.  (here??)
>           (edebug-outside-executing-macro executing-kbd-macro)
> !         (edebug-outside-pre-command-hook
> !          (cons (current-buffer) pre-command-hook))
> !         (edebug-outside-post-command-hook
> !          (cons (current-buffer) post-command-hook)))
>       (unwind-protect
>           (let (;; Don't keep reading from an executing kbd macro
>                 ;; within edebug unless edebug-continue-kbd-macro is

I think edebug should not try to reproduce the behavior of `let'
which was already hard to implement once.

How about just doing

(let ((pre-command-hook pre-command-hook)
      (post-command-hook post-command-hook))
  ...)

instead of fiddling with edebug-outside-pre-command-hook ?
Or if we need to remember the value outside, then

(let ((pre-command-hook pre-command-hook)
      (post-command-hook post-command-hook)
      (edebug-outside-pre-command-hook pre-command-hook)
      (edebug-outside-post-command-hook post-command-hook))
  ...)



-- Stefan