You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Use #+NAME: result-value to store the result of an :async shell block's execution.
Run the block and wait for execution to finish and the result to be displayed
Pass that result to another shell block with :var input_var=result-value and write code to print the value of that variable in the block.
Run the block and observe that the value passed is not the value of the first block's execution and instead #<process emacs> or possible #<process emacs <n>>
In the case of python (and possibly other languages) this breaks the code necessary to store the value. As a result, attempting to execute a block with a variable set by an async block will lead to a SyntaxError. I'm including this note because the first keywords I googled for related to this error, before I realized it was a broader issue.
Checklist
troubleshooting.org
bufferExpected Behavior
I can use
#+NAME:
and:var
to pass the result of one block to another block even if the first block is:async
Actual Behavior
Even after the block finishes executing and the result is shown,
#<process emacs>
is stored under the name of the block. For example:Steps to Reproduce
#+NAME: result-value
to store the result of an:async
shell block's execution.:var input_var=result-value
and write code to print the value of that variable in the block.#<process emacs>
or possible#<process emacs <n>>
Troubleshooting Artifacts
troubleshooting.org and a direct link to the raw troubleshooting.org file that shows the results of the blocks.
Note
In the case of python (and possibly other languages) this breaks the code necessary to store the value. As a result, attempting to execute a block with a variable set by an async block will lead to a SyntaxError. I'm including this note because the first keywords I googled for related to this error, before I realized it was a broader issue.
The text was updated successfully, but these errors were encountered: