bug-gnu-emacs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#33201: 26.1; Edebug doesn't work on closures with edebug-unwrap-resu


From: Eli Zaretskii
Subject: bug#33201: 26.1; Edebug doesn't work on closures with edebug-unwrap-results
Date: Thu, 01 Nov 2018 22:18:40 +0200

> Date: Thu, 1 Nov 2018 19:59:18 +0000
> Cc: address@hidden, address@hidden, address@hidden
> From: Alan Mackenzie <address@hidden>
> 
> It seems like in Emacs 26.1 edebug can't be reliably used with
> edebug-unwrap-results non-nil because there's always a chance it will
> encounter the symbol `closure', at which point it errors out.
> [`closure' is wierd, because it has a meaning, yet has none of a
> function, a value, a property list.]

I understand, but why does this make it a "major" problem?  The only
major problem in Edebug I could understand is if Edebug could not be
used at all in some popular situation.  FWIW, I never set
edebug-unwrap-results non-nil, and I'm a happy "Edebugger".

> > I can: it's quite complex, and even includes gratuitous refactoring of
> > 'cond' as 'pcase'.
> 
> OK.  How about me doing a simpler, but less lazy fix which would just
> add handling of `closure' into the existing cond form?

That's one thing; the other is why do we need to change edebug-unwrap1
as well?  AFAIU, that takes care of a separate issue, right?





reply via email to

[Prev in Thread] Current Thread [Next in Thread]