I often find myself just taking a "async by default"-approach, e.g. by setting :async at the buffer-level. But sometimes I'll run into issues with whatever command I'm running, in which case I will have to disable :async, and then re-run the block in sync-mode to get the error message.
Note that #86 is also helpful in this regard, but even with that you might be losing useful output prior to error which is then subsequently dropped since only stderr is captured.
Hence, this PR introduces, in similar vein to many other header-args in Org, the ability to set :async no to disable async.
I often find myself just taking a "async by default"-approach, e.g. by setting
:async
at the buffer-level. But sometimes I'll run into issues with whatever command I'm running, in which case I will have to disable:async
, and then re-run the block in sync-mode to get the error message.Note that #86 is also helpful in this regard, but even with that you might be losing useful output prior to error which is then subsequently dropped since only
stderr
is captured.Hence, this PR introduces, in similar vein to many other header-args in Org, the ability to set
:async no
to disable async.Thoughts?