liberte@M.CS.UIUC.EDU (Daniel LaLiberte) (11/23/88)
From: Eric L. Raible <raible@orville.nas.nasa.gov> After getting the error "Invalid function: (progn (edebug ...)))" edebugging even the simplest cond (defun foo () (cond (t (message "yes")))) I made a guess and changed the 'list' in edebug-cond to a 'cons'. I think that this is the correct fix. Dan? Absolutely correct. Sorry folks. I had fixed a different problem with conds, but I messed up. My first note didnt explain why edebug is great and people where asking, why bother? Well, it allows you to step through your source code in the buffer in which you edit it, and set breakpoints at any expression. ================ In case you missed it: *** /u/of/raible/.emacs-lib/edebug.el Tue Nov 22 13:40:39 1988 --- /u/of/raible/.emacs-lib/edebug.el~ Mon Nov 21 10:34:27 1988 *************** *** 365,371 (error "Bad condition in cond") (forward-char 1) ; \( (prog1 ! (cons (edebug-sexp) (if (eq 'rparen (edebug-next-token-class)) nil --- 365,371 ----- (error "Bad condition in cond") (forward-char 1) ; \( (prog1 ! (list (edebug-sexp) (if (eq 'rparen (edebug-next-token-class)) nil