From: Tyler Smith <tyler@plantarum.ca>
To: John Hendy <jw.hendy@gmail.com>
Cc: Emacs Org-Mode Help <emacs-orgmode@gnu.org>
Subject: Re: default units for graphics in R code blocks
Date: Mon, 30 Mar 2020 13:25:55 -0400 [thread overview]
Message-ID: <87wo7169gc.fsf@plantarum.ca> (raw)
In-Reply-To: <CA+M2ft-gBbOUcbe39Mn=B+So-cu7JAusr8cZaMS2VLPG10VA8w@mail.gmail.com>
Yes, org info is spread wide and thin, and it's hard to tell which
source is the most recent/accurate. I think it might be useful to
consolidate and delete as much as possible, but that's going to be a lot
of work.
The existence of a page called "Library of Babel",
https://orgmode.org/worg/library-of-babel.html that doesn't actually
refer to org-babel seems especially misleading!
In any case, I updated ob-doc-R with the correct info.
Best,
Tyler
John Hendy writes:
> Bummer, that does indeed read pretty straightforwardly about inches.
> Sorry about that.
>
> Thanks for your efforts. I find org documentation challenging at
> times, and am still not clear on worg vs. org. I believe I've asked on
> this list before why those pages exist, as this seems like it should
> be in the org official docs vs. in a sort of tutorial site. It makes
> it tough as you can't find certain header args in the org docs; you
> have to kind of know what you're looking for, or at least that the
> header arg is *only* for, say, R, and not for anything else.
>
> Anyway, thanks for contributing!
>
> Best,
> John
>
> On Mon, Mar 30, 2020 at 11:58 AM Tyler Smith <tyler@plantarum.ca> wrote:
>>
>> John Hendy writes:
>>
>> >
>> > Best to cite exactly which article you're referring to. Trying to look
>> > myself, for example, found me this as the only worg hit from googling
>> > "worg R plotting":
>> > - https://orgmode.org/worg/org-tutorials/org-R/org-R.html
>> > """
>> > Output options
>> > height:1000set height of graphical output in (pixels for png, jpeg,
>> > bmp, tiff; default 480) / (inches for pdf, ps; default 7)
>> > width:1000set width of graphical output in pixels (default 480 for png)
>> > """
>> >
>> The article I was referring to is:
>>
>> https://orgmode.org/worg/org-contrib/babel/languages/ob-doc-R.html
>>
>> The tutorial you found suggests the corrections needed in the one I
>> found; I can do that now!
>>
>> Tyler
>>
>>
>> > It seems that aligns with my recollection, but may very well differ
>> > from the article you found. Thanks for any edits/corrections you make!
>> >
>> > Best regards,
>> > John
>> >
>> >>
>> >> Best,
>> >>
>> >> Tyler
>> >>
>> >>
>> >>
>> >> --
>> >> Tyler Smith
>> >> http://plantarum.ca
>> >>
>>
>>
>> --
>> Tyler Smith
>> http://plantarum.ca
--
Tyler Smith
http://plantarum.ca
prev parent reply other threads:[~2020-03-30 17:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-30 15:44 default units for graphics in R code blocks Tyler Smith
2020-03-30 16:32 ` John Hendy
2020-03-30 16:58 ` Tyler Smith
2020-03-30 17:08 ` John Hendy
2020-03-30 17:25 ` Tyler Smith [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=87wo7169gc.fsf@plantarum.ca \
--to=tyler@plantarum.ca \
--cc=emacs-orgmode@gnu.org \
--cc=jw.hendy@gmail.com \
/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).