-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Export results "Executing..." placeholder #20
Comments
Hello thank you for using this package, and your kind word! I confirmed the issue. I usually disable code block evaluation on export with I will check how it can be fixed. As a workaround for the time being, you might want to disable evaluation on export with the above option, if it is ok for your workflow. |
A feasible approach for this is to ensure that blocks whose results are to be exported are re-evaluated synchronously when exporting. |
Hi, I'm experiencing the same issue.
how would one do that? Thank you for the work you've put into this great package! |
Ah, that is about how I should modify the code to address this issue. I posted that as a note to myself. I do intend to implement it but it's not done yet... Sorry for the confusion. Anyway, thank you for using this package and for your kind words! |
Ah! I got my hopes up that there was an arcane Org Babel option to force synchronous evaluation on export. Thanks for clarifying the situation! |
Thanks for this package, the best ob-julia experience I've had for editing and running blocks!
The issue is on export; the results (
:exports both
) don't get updated when the block is finished executing, and so each results block (in the PDF/Word/HTML) looks like "Executing... 9ae38f91".This is on emacs 29.0.60 and the current MELPA ob-julia-vterm.
The text was updated successfully, but these errors were encountered: