From: "Berry, Charles" <ccberry@health.ucsd.edu>
To: Rens Oliemans <hallo@rensoliemans.nl>
Cc: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: [BUG] Header-args :results output of code block don't take precedence above headline header-args [9.6 (release_9.6-32-gc59d6d @ /tmp/org/org-mode/lisp/)]
Date: Fri, 9 Dec 2022 18:01:52 +0000 [thread overview]
Message-ID: <B385DA57-C61E-4365-AA0F-4E74C2F9441A@health.ucsd.edu> (raw)
In-Reply-To: <878rjj3y2n.fsf@cardano.mail-host-address-is-not-set>
Rens,
This is not a bug. Seee below.
> On Dec 7, 2022, at 9:47 AM, Rens Oliemans <hallo@rensoliemans.nl> wrote:
>
> Hi all,
>
> A code block with ":results output" as header argument still has its
> output silenced if it's inside a headline with ":results none". MWE:
>
> 1. Create an .org file with the following content:
>
> * Sub-tree with =:results none=
> :PROPERTIES:
> :header-args: :results none
> :END:
>
> #+BEGIN_SRC bash :results output
> echo "is silent"
> #+END_SRC
This is the correct handling.
See (info "(org) Results of Evaluation").
`output' is a `Collection' option. `none' is a `Handling' option.
If you want to override a `Handling' option you need another `Handling' option. e.g.
#+BEGIN_SRC bash :results output replace
echo "is silent"
#+END_SRC
HTH,
Chuck
prev parent reply other threads:[~2022-12-09 18:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-07 17:47 [BUG] Header-args :results output of code block don't take precedence above headline header-args [9.6 (release_9.6-32-gc59d6d @ /tmp/org/org-mode/lisp/)] Rens Oliemans
2022-12-09 18:01 ` Berry, Charles [this message]
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=B385DA57-C61E-4365-AA0F-4E74C2F9441A@health.ucsd.edu \
--to=ccberry@health.ucsd.edu \
--cc=emacs-orgmode@gnu.org \
--cc=hallo@rensoliemans.nl \
/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).