Re: Impossible to edebug stuff that calls auth-source?

[Lars Ingebrigtsen <larsi@gnus.org>]

Andreas Schwab <schwab@linux-m68k.org> writes:

> defclass probably needs a debug declaration (*Note (elisp) Instrumenting
> Macro Calls::).

Hm...

The doc says:

---
   If a macro has no Edebug specification, neither through a `debug'
declaration nor through a `def-edebug-spec' call, the variable
`edebug-eval-macro-args' comes into play.

 -- User Option: edebug-eval-macro-args
     This controls the way Edebug treats macro arguments with no
     explicit Edebug specification.  If it is `nil' (the default), none
     of the arguments is instrumented for evaluation.  Otherwise, all
     arguments are instrumented.
---

And it is nil, so shouldn't edebug just ignore this?  And I haven't
actually asked edebug to instrument any of the auth-source functions,
just functions that eventually lead to auth-source being called, so
edebug shouldn't know about that stuff anyway, should it?  *scratches
head*


-- 
(domestic pets only, the antidote for overdose, milk.)
  larsi@gnus.org * Lars Magne Ingebrigtsen