emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Graham Smith <myotisone@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Org babel R Help
Date: Sun, 21 Mar 2010 17:45:58 +0000	[thread overview]
Message-ID: <2c75873c1003211045p1a51020blfe7d5c4eee552b61@mail.gmail.com> (raw)
In-Reply-To: <878w9liwpq.fsf@stats.ox.ac.uk>

Dan

> So I believe we do understand the situation. The question is how do we
> improve it. First the facts:

> As for improvements, it is tempting to think that
>
> 1. org-babel should automatically insert the ATTR_LaTeX line in
>   accordance with :width and :height when creating latex output.
> 2. org-babel should keep existing ATTR_LaTeX lines attached to their
>   respective figures (contra Graham's thread linked above)
>
> I've had a brief look and doubtless all this is possible. It brings up
> issues of what units :width and :height are assumed to be in (e.g. just
> because R uses inches for pdf() doesn't mean that anyone else thinks
> that's a sensible decision). And we have to be a careful because it
> means altering what org-babel considers to be part of its results.

Now that I know what is happening I am reasonably content with it as it is.

However, it would seem to make sense that :width and :height commands
"should" relate to the image size in the compiled pdf.  And it would
also make sense that these should be consistently in mm, regardless of
file format.

Graham

      reply	other threads:[~2010-03-21 17:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-19  8:01 Org babel R Help Joseph Cole
2010-03-19 14:30 ` Dan Davison
     [not found]   ` <5084fc611003210151x41850afcg36b275679ae76acb@mail.gmail.com>
2010-03-21  9:18     ` Joseph Cole
2010-03-21  9:53       ` Graham Smith
2010-03-21 14:19         ` Dan Davison
2010-03-21 17:45           ` Graham 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=2c75873c1003211045p1a51020blfe7d5c4eee552b61@mail.gmail.com \
    --to=myotisone@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).