Open MasonProtter opened 3 years ago
Thank you for the suggestion. I didn't know InteractiveErrors.jl. It looks very useful. Let me check how it works.
Could you elaborate on the actual workflow you want? How do you want to interact with source blocks and how should it be improved by using includet?
Currently, code gets entered with
include
which makes sense, but I just learned today about https://github.com/MichaelHatherly/InteractiveErrors.jl which makes me wish that the code was entered usingRevise.includet
so that I could interactively explore errors in the code more readily using the REPL.Great package btw, I'm happy this exists, having to use IJulia and emacs-jupyter is a bit of a pain.