From: Nick Dokos <ndokos@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: [BUG] src code block header does not override buffer-wide header in property
Date: Wed, 29 Jun 2016 14:04:34 -0400 [thread overview]
Message-ID: <87furvg9cd.fsf@alphaville.usersys.redhat.com> (raw)
In-Reply-To: alpine.OSX.2.20.1606290939290.749@charles-berrys-macbook.local
"Charles C. Berry" <ccberry@ucsd.edu> writes:
> Not a bug. See below.
>
> On Wed, 29 Jun 2016, Nick Dokos wrote:
>
>> This was reported on SO:
>>
>> http://stackoverflow.com/questions/37414837/org-mode-overwriting-globals-properties-in-block-headers
>>
>> The ECM is as follows:
>>
>> --8<---------------cut here---------------start------------->8---
>> #+PROPERTY: header-args :results silent
>>
>> #+BEGIN_SRC elisp
>> ;; this one is silent
>> (setq foo "bar)
>> #+END_SRC
>>
>> #+BEGIN_SRC elisp :results output
>> ;; this one is being outputted
>> (princ "foo")
>> #+END_SRC
>> --8<---------------cut here---------------end--------------->8---
>>
>> The second code block *should* output "foo" as its result, but it does
>> not: the :results silent header in the property seems to be in conrol.
>
> Maybe you meant
>
> #+BEGIN_SRC elisp :results output replace :exports both
> ;; this one is being outputted
> (princ "foo")
> #+END_SRC
>
OK - I can never remember the meaning of all the results permutations
but replace does reverse the result of silent (I don't care about export
in this case).
>
> i.e. export code and results and replace the existing result or insert a
> new result.
>
> See (info "(org) results") and scroll down to the 'Handling' paragraph.
>
Thanks for the reference - I obviously need to re-read this a few times.
--
Nick
prev parent reply other threads:[~2016-06-29 18:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-29 5:23 [BUG] src code block header does not override buffer-wide header in property Nick Dokos
2016-06-29 16:47 ` Charles C. Berry
2016-06-29 18:04 ` Nick Dokos [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=87furvg9cd.fsf@alphaville.usersys.redhat.com \
--to=ndokos@gmail.com \
--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).