From: John Hendy <jw.hendy@gmail.com>
To: shripad sinari <shripad.sinari@gmail.com>
Cc: Orgmode Mailing List <emacs-orgmode@gnu.org>
Subject: Re: scaling the text in the results block of some code chunk when exported using LaTeX
Date: Wed, 17 Apr 2013 22:13:05 -0500 [thread overview]
Message-ID: <CA+M2ft8Ez1M-2jRvAskt8NPrCJS70157L0mrT2BqcyOtOkL4Jg@mail.gmail.com> (raw)
In-Reply-To: <CAA_SOTZ_dM8_X1zL7KQcGp2FX12zY3L+LLxysfYfysZ1DciUVw@mail.gmail.com>
On Wed, Apr 17, 2013 at 9:46 PM, shripad sinari
<shripad.sinari@gmail.com> wrote:
> Hello all,
> A quick update. Only the named block solution from Jay Kerns currently
> works. I have tried out variants of other proposed solutions here but none
> worked.
> Thanks for your help and sorry for the delay in getting back on this one.
> Shripad.
>
I didn't really follow this thread, but I resize things a decent
amount, but not with \resizebox. It's true that you need named source
blocks so that after the first C-c C-c on the babel block, you can add
options and still have it recognized as the results container for that
particular block. Something like this:
#+name: test
#+begin_src R :exports results :results output :wrap latex
a <- 1:10
a
#+end_src
#+latex: \LARGE
#+RESULTS: test
#+BEGIN_latex
[1] 1 2 3 4 5 6 7 8 9 10
#+END_latex
#+latex: \normalsize
I don't actually use the above that much, but tend to size plots
appropriately with something like the following, which is essentially
the same principle (how to pass latex options to the results of code
block results while having Org still recognize where to put updated
results):
#+begin_center
#+attr_latex: :width 8cm
#+RESULTS: test
[[file.pdf]]
#+end_center
Just thought I'd add another option...
John
> Shripad
> Tucson, AZ
>
> Shripad
> Tucson, AZ
>
next prev parent reply other threads:[~2013-04-18 3:13 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-18 23:44 scaling the text in the results block of some code chunk when exported using LaTeX shripad sinari
2013-03-19 0:26 ` Jay Kerns
2013-03-19 1:07 ` Thomas S. Dye
2013-03-19 2:08 ` shripad sinari
2013-03-19 0:57 ` Eric Abrahamsen
[not found] ` <CAA_SOTZwUcdvt4tbQTV5PLWxSE=C6vZ0k+bBEshHXG8FkFaK0g@mail.gmail.com>
[not found] ` <871ub9frnp.fsf@ericabrahamsen.net>
[not found] ` <CAA_SOTZoqTufBQkckeBXJoiJe6j+TqWqa=PiSWJQ3Xn35h2bhA@mail.gmail.com>
[not found] ` <87obdcverf.fsf@ericabrahamsen.net>
2013-04-18 2:46 ` shripad sinari
2013-04-18 3:13 ` John Hendy [this message]
2013-04-18 3:43 ` shripad sinari
2013-04-18 3:53 ` John Hendy
2013-04-18 3:57 ` shripad sinari
2013-04-18 4:12 ` shripad sinari
2013-04-18 4:18 ` John Hendy
2013-04-18 4:20 ` shripad sinari
2013-04-18 4:25 ` John Hendy
2013-04-18 4:59 ` shripad sinari
2013-04-18 3:50 ` Eric Schulte
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+M2ft8Ez1M-2jRvAskt8NPrCJS70157L0mrT2BqcyOtOkL4Jg@mail.gmail.com \
--to=jw.hendy@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=shripad.sinari@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).