From: John Hendy <jw.hendy@gmail.com>
To: John Hendy <jw.hendy@gmail.com>, myq larson <myq@wordish.org>,
emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: Bug: Org Bable: Set R-specific buffer-wide graphics headers == no R src block eval [8.2.10 (8.2.10-1-g8b63dc-elpa @ /home/user/.emacs.d/elpa/org-20141027/)]
Date: Sun, 2 Nov 2014 16:58:20 -0600 [thread overview]
Message-ID: <CA+M2ft8bBoVRr_7zttrj7+uY7z4hF6yuHBkK6UMJ+SD=nNv1mQ@mail.gmail.com> (raw)
In-Reply-To: <874muhgqly.fsf@nicolasgoaziou.fr>
On Sun, Nov 2, 2014 at 4:55 PM, Nicolas Goaziou <mail@nicolasgoaziou.fr> wrote:
> Hello,
>
> John Hendy <jw.hendy@gmail.com> writes:
>
>> It's up to someone else regarding whether or not the #+property
>> behavior is desired. I wondered what two subsequent #+options lines
>> would do, for example, and they appear to be cumulative. For example:
>>
>> #+options: toc:nil
>> #+options: num:nil
>>
>> Yielded both results even though the default contains both. An analog
>> would have been for my document to retain a toc but with no section
>> numbers. So, *something's* different between how these behave.
>
> See
>
> (info "(org) Property syntax")
>
> in particular, the "var+" syntax.
Awesome! Indeed, myq, this works, for reference:
#+PROPERTY: header-args:R :exports results
#+PROPERTY: header-args :results output graphics
#+PROPERTY: header-args:R+ :width 800
Also, don't forget to =C-c C-c= on these arguments (just one of them
in your preamble) to make sure they're updated before trying another
export. (Only mentioning this as I often forget and then think
something didn't work...)
John
>
>
> Regards,
>
> --
> Nicolas Goaziou
prev parent reply other threads:[~2014-11-02 22:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-01 4:50 Bug: Org Bable: Set R-specific buffer-wide graphics headers == no R src block eval [8.2.10 (8.2.10-1-g8b63dc-elpa @ /home/user/.emacs.d/elpa/org-20141027/)] myq larson
2014-11-02 22:50 ` John Hendy
2014-11-02 22:55 ` Nicolas Goaziou
2014-11-02 22:58 ` John Hendy [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='CA+M2ft8bBoVRr_7zttrj7+uY7z4hF6yuHBkK6UMJ+SD=nNv1mQ@mail.gmail.com' \
--to=jw.hendy@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=myq@wordish.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).