Shuhei Kadowaki

can you try on the latest Weave version ?:

in this environment your example works: ```julia plotenv) pkg> st Status `...` [91a5bcdd] Plots v1.3.1 ``` so, let's try to create a separate environment that only contains `Plots` and try...

ah, so you're weaving a script. then it might be Weave itself causes the problem. I'll take a look at this later

okay, so my current guess is that [this line](https://github.com/JunoLab/Weave.jl/blob/daec0e618f391e4ea97e59ea7039d2b69f68950e/src/plots.jl#L28) causes this problem. well this doesn't happen on macOS (I'm using), but I'm sure that code should be refactored into more...

fwiw, do you have some special setup for plotting in your startup script ?

I'm still on a way to find a solution, but here is my understanding: - the error you faced seems happen if [this method](https://github.com/JunoLab/Weave.jl/blob/master/src/plots.jl#L16-L37) gets called - but I found...

addressed on the current master: except our YAML header doesn't accept `options.args`. now inline code inside YAML will be evaluated _after_ all the chunks are evaluated, so you can have...

`Base.display(::Weave.Report, ...)` is only called for chunk outputs, as for markdown parts, we translate them into HTML by using `Markdown` stdlib.

> but since `y` is not active Enzyme can actually differentiate the code. Now this PR handles this very simple case with a very simple activity analysis (one that just...

As for the integration, I found this: `debug> @trace` within Juno REPL also includes stacktraces of logics within https://github.com/JunoLab/Atom.jl/blob/master/src/repl.jl, like: ```julia [1] f(::Int64) at none:7 [2] top-level scope at none:0...