Allow disabling :async by setting :async no
#90
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I often find myself just taking a "async by default"-approach, e.g. by setting
:asyncat 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
stderris captured.Hence, this PR introduces, in similar vein to many other header-args in Org, the ability to set
:async noto disable async.Thoughts?