Open ramos opened 1 year ago
See #93 and #96. It would be nice to have this fixed.
I would also love to see this fixed!
I solved the issue forcing the org repo to be in sync with the last release. It seems that master (that is the development branch) suffers from this issue.
https://github.com/jwiegley/emacs-async/issues/165 points out the issue with async.el. Replacing utf-8-auto with utf-8 in async.el (used by ob-async.el) makes it work with emacs 29.1 again.
Issue also happening in emacs 28.1, org 9.6.24 ob-async 20210428.2052. @mhandugan how would we replace the utf-8 in async.el? Do we then need to byte-compile it? Can someone suggest a step-by-step fix? Thanks.
Actually I've just checked and am using async 1.9.8 which already has this change implemented, and so this is definitely not the root cause of the issue!
It works fine for me in Emacs 29.3 and ob-async 20210428.20521
, tested with both async 20231105.1713
(version installed as dependency) and 20240323.1912
(installed explicitly for the purpose of testing this).
Thanks @astahlman . I've found that the issue is related to ob-julia-vterm. Whenever I activate it all blocks with async (of julia or any other language) output this error message. Bizarre
Checklist
troubleshooting.org
bufferThe result of the troubleshooting.org guide is that all non async blocks work. All async blocks fail with message: (note: I had to change
incf
forcl-incf
).Expected Behavior
working async blocks
Actual Behavior
All async blocks fail with message:
Steps to Reproduce
Troubleshooting Artifacts
(Copy-paste the contents of your
troubleshooting.org
buffer into a gist and add the link here)