|
From: | Max Nikulin |
Subject: | Re: [FR] Display stderr contents after executing shell blocks (even when stdout :results output is requested) (was: Org 9.6-pre and Bash sessions) |
Date: | Sat, 29 Oct 2022 18:58:30 +0700 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.2.2 |
On 29/10/2022 11:05, Ihor Radchenko wrote:
As explained in the above quote, it may be reasonable to display stderr in the shell (and possibly other) src blocks upon execution. + Stderr may contain important information even if the code block succeeds - Displaying stderr will raise *Error* buffer, which may or may not be expected or desired. What do you think?
I agree that stderr may be important. I would not mind to have a buffer that combines both stderr and stdout (maybe fontified). Despite order of messages in separate streams is not strictly defined, it still may shed some light on the reason what went wrong.
[Prev in Thread] | Current Thread | [Next in Thread] |