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.
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(-)
--
2.37.3
