From: shripad sinari <shripad.sinari@gmail.com>
To: John Hendy <jw.hendy@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 21:12:35 -0700 [thread overview]
Message-ID: <CAA_SOTbKrnfHxB4wqdoN8qGJWrvKsm2gCvnFjvZEKOPJiLDy8Q@mail.gmail.com> (raw)
In-Reply-To: <CAA_SOTYQAnei3s=eCPSiwXumDV3k7QdCeRE2h8Pwdxw7+iYY1w@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 4506 bytes --]
Hello John,
I think I figured out what the issue is. Whenever I have the code chunks
outside a headline for example:
### This does not work ###
#+TITLE: *scratch*
#+AUTHOR: Shripad Sinari
#+DATE: 2013-04-17 Wed
#+DESCRIPTION:
#+KEYWORDS:
#+LANGUAGE: en
#+OPTIONS: H:6 num:t toc:t \n:nil @:t ::t |:t ^:t -:t f:t *:t <:t
#+OPTIONS: TeX:t LaTeX:t skip:nil d:nil todo:t pri:nil tags:not-in-toc
#+INFOJS_OPT: view:nil toc:nil ltoc:t mouse:underline buttons:0 path:
http://orgmode.org/org-info.js
#+EXPORT_SELECT_TAGS: export
#+EXPORT_EXCLUDE_TAGS: noexport
#+LINK_UP:
#+LINK_HOME:
#+XSLT:
#+NAME: test1
#+BEGIN_SRC R :results output latex :exports results
a <- 1:10
a
#+END_SRC
#+LATEX: \tiny
#+RESULTS: test1
#+LATEX: \normalsize
############################
However just placing the code chunks under a headline works:
#### The following works ####
#+TITLE: *scratch*
#+AUTHOR: Shripad Sinari
#+DATE: 2013-04-17 Wed
#+DESCRIPTION:
#+KEYWORDS:
#+LANGUAGE: en
#+OPTIONS: H:6 num:t toc:t \n:nil @:t ::t |:t ^:t -:t f:t *:t <:t
#+OPTIONS: TeX:t LaTeX:t skip:nil d:nil todo:t pri:nil tags:not-in-toc
#+INFOJS_OPT: view:nil toc:nil ltoc:t mouse:underline buttons:0 path:
http://orgmode.org/org-info.js
#+EXPORT_SELECT_TAGS: export
#+EXPORT_EXCLUDE_TAGS: noexport
#+LINK_UP:
#+LINK_HOME:
#+XSLT:
* N1
#+NAME: test1
#+BEGIN_SRC R :results output latex :exports results
a <- 1:10
a
#+END_SRC
#+LATEX: \tiny
#+RESULTS: test1
#+LATEX: \normalsize
##############################################
Note the headline =* N1= is the only change between the two codes.
Regards,
Shripad
Tucson, AZ
On Wed, Apr 17, 2013 at 8:57 PM, shripad sinari <shripad.sinari@gmail.com>wrote:
> Hello John,
> I am able to get your test.org to do size change but not my test file.
> Please find it attached herewith. I am sure it is setup issue now.
> Thanks,
> Shripad.
>
> Shripad
> Tucson, AZ
>
>
> On Wed, Apr 17, 2013 at 8:53 PM, John Hendy <jw.hendy@gmail.com> wrote:
>
>> On Wed, Apr 17, 2013 at 10:43 PM, shripad sinari
>> <shripad.sinari@gmail.com> wrote:
>> > Hello John,
>> > I have tried this with text but it does not seem to resize the text.
>> Infact
>> > what gets resized is the "#+RESULTS: test" and the rest of the stuff
>> after
>> > that to the #+end_center. It might work for images but does not for
>> text.
>>
>> You must have a setup or installation issue. See the attached .org and
>> resultant .pdf for me.
>>
>> What's in your #+options line (or setupfile)? I'm wondering if you
>> don't have something like =tex:t= or =LaTeX:t= which might be required
>> to pass the commands through?
>>
>>
>> Best regards,
>> John
>>
>>
>> > Regards,
>> > Shripad.
>> >
>> > Shripad
>> > Tucson, AZ
>> >
>> >
>> > On Wed, Apr 17, 2013 at 8:13 PM, John Hendy <jw.hendy@gmail.com> wrote:
>> >>
>> >> 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
>> >> >
>> >
>> >
>>
>
>
[-- Attachment #2: Type: text/html, Size: 7248 bytes --]
next prev parent reply other threads:[~2013-04-18 4:12 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
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 [this message]
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=CAA_SOTbKrnfHxB4wqdoN8qGJWrvKsm2gCvnFjvZEKOPJiLDy8Q@mail.gmail.com \
--to=shripad.sinari@gmail.com \
--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).