I would like to understand more of the internals of
ivy-read. So I tried using edebug to trace some of the helper functions in
ivy.el. However, upon entering edebug, the focus always is in the minibuffer makes it impossible to trace.
A similar question on SE is How to debug helm. Apparently tracing helm code would encounter the same problem. The good news is there is a switch for ease of debug in helm.
I'm wondering if there is a similar switch in ivy. (Or how abo-abo debugs when developing ivy :-)
The link also mentions
Recursive Editing. I've read elisp info node "Edebug recursive editing". But I can't understand what it says.