Jonas Bernoulli <jo...@bernoul.li> writes:
> I run org-babel-execute-buffer from a Makefile and the output is quite
> noisy, forcing me to filter out some output using grep -v so that I am
> still able to spot any unexpected output that indicates some issue.
>
> Now that I have started using post-processing code blocks, the output
> has gotten even more noisy and unfortunately filtering out the unwanted
> additions is not possible.
>
> Currently all arguments to post-processing blocks are printed to
> stdout. I am not able to filter them out using grep because this
> output seems to be split across multiple lines, so a regexp like
> "^(" only matches parts of the noise.
>
> It is unclear whether the arguments were printed on purpose. It might
> be useful to do so at times for debugging purposes, but generally they
> make things harder, by obscuring output one would want to notice.
I suspect that it is remnants of previous code re-factoring in
5e0db0798. The old code used `print' for pretty-printing :results pp.
> The second commit addresses a cosmetic, but somewhat related,
> annoyance.
>
> Jonas Bernoulli (2):
> Don't print arguments of post-process arguments to stdout
> Begin messages about executing code blocks with a capital letter
>
> lisp/ob-awk.el | 2 +-
> lisp/ob-core.el | 2 +-
> lisp/ob-emacs-lisp.el | 2 +-
> lisp/ob-groovy.el | 2 +-
> lisp/ob-maxima.el | 2 +-
> lisp/ob-sed.el | 2 +-
> 6 files changed, 6 insertions(+), 6 deletions(-)
Applied onto main with amendments to commit messages.
Please refer to
https://orgmode.org/worg/org-contribute.html#commit-messages in future.
https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=2f4de60980b6b10770696c4ee0b610d0e96ab575
https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=fc8e375b9bd2685690e6ec9f0cc6ed078a6e938f
--
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>
