From: Jonas Bernoulli <jonas@bernoul.li>
To: emacs-orgmode@gnu.org
Subject: [PATCH 0/2] Don't print arguments of post-process arguments to stdout
Date: Thu, 6 Oct 2022 13:43:44 +0200 [thread overview]
Message-ID: <20221006114346.23926-1-jonas@bernoul.li> (raw)
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
next reply other threads:[~2022-10-06 11:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-06 11:43 Jonas Bernoulli [this message]
2022-10-06 11:43 ` [PATCH 1/2] Don't print arguments of post-process arguments to stdout Jonas Bernoulli
2022-10-06 11:43 ` [PATCH 2/2] Begin messages about executing code blocks with a capital letter Jonas Bernoulli
2022-10-07 5:55 ` [PATCH 0/2] Don't print arguments of post-process arguments to stdout Ihor Radchenko
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20221006114346.23926-1-jonas@bernoul.li \
--to=jonas@bernoul.li \
--cc=emacs-orgmode@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).