emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: shripad sinari <shripad.sinari@gmail.com>
To: 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 19:46:13 -0700	[thread overview]
Message-ID: <CAA_SOTZ_dM8_X1zL7KQcGp2FX12zY3L+LLxysfYfysZ1DciUVw@mail.gmail.com> (raw)
In-Reply-To: <87obdcverf.fsf@ericabrahamsen.net>

[-- Attachment #1: Type: text/plain, Size: 5287 bytes --]

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.

Shripad
Tucson, AZ

Shripad
Tucson, AZ


On Wed, Apr 17, 2013 at 5:55 PM, Eric Abrahamsen <eric@ericabrahamsen.net>wrote:

> You only sent this to me! :)
>
> On 04/18/13 01:24 AM, shripad sinari 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.
> >
> > Shripad
> > Tucson, AZ
> >
> > On Wed, Mar 20, 2013 at 6:49 PM, Eric Abrahamsen
> > <eric@ericabrahamsen.net> wrote:
> >
> >     Hi Shripad,
> >
> >     My solution still requires named code blocks! That's the only way
> >     you
> >     can make sure the results are put where you want them: between
> >     certain
> >     Latex fragments.
> >
> >     I'm not quite understanding what's going wrong with what you
> >     pasted
> >     below -- do you mean that all the file names are prepended with
> >     ":"? In
> >     that case, try using "raw" instead of "verbatim" as a value for
> >     the
> >     :results key.
> >
> >     Good luck!
> >
> >     E
> >
> >
> >
> >     On 03/20/13 05:25 AM, shripad sinari wrote:
> >     > Hello Eric,
> >     > I am experimenting with your solution and I like it better than
> >     named
> >     > code blocks because it does not interfere with HTML or MD
> >     export.
> >     > However it is not working. Is there something like this that can
> >     be
> >     > done that you know of and how?
> >     >
> >     > #+RESULTS: Files
> >     > #+BEGIN_LaTeX \resizebox{\textwidth}{!}{%
> >     > [1] "Clinical spreadsheet_20130215 diabetes1212-v7_OT edited for
> >     > sample classification.xls"
> >     > [2] "Data spreadsheet_031813 Diabetes study samples set
> >     corrected_ALL
> >     > assays to date_OT.xlsx"
> >     > }
> >     > #+END_LaTeX
> >     >
> >     > because you solution currently produces this output.
> >     >
> >     > here is my code, I have tried the various arguments to the
> >     ":results"
> >     > plist as well:
> >     >
> >     > #+NAME: Files
> >     > #+BEGIN_SRC R :session :exports results :results value verbatim
> >     > replace :tangle yes
> >     > print(list.files(recursive = T, pattern = "*.xls*"))
> >     > #+END_SRC
> >     >
> >     > #+LATEX: \resizebox{\textwidth}{!}{%
> >     > #+RESULTS: Files
> >     > : Clinical spreadsheet_20130215 diabetes1212-v7_OT edited for
> >     sample
> >     > classification.xls
> >     > : Data spreadsheet_031813 Diabetes study samples set
> >     corrected_ALL
> >     > assays to date_OT.xlsx
> >     >
> >     > #+Latex: }
> >     >
> >     > Thanks for your help.
> >     >
> >     > Shripad
> >     > Tucson, AZ
> >     >
> >     > On Mon, Mar 18, 2013 at 5:57 PM, Eric Abrahamsen
> >     > <eric@ericabrahamsen.net> wrote:
> >     >
> >     >
> >     > shripad sinari <shripad.sinari@gmail.com> writes:
> >     >
> >     > > Hello all,
> >     > > Is there a way to scale the text in the latex export of a
> >     > results
> >     > > block produced by a code chunk?
> >     > >
> >     > > Here is the code chunk i am trying to evaluate and export:
> >     > >
> >     > > #+BEGIN_SRC R :session :exports results :results output org
> >     > replace :
> >     > > tangle yes
> >     > > print(list.files(recursive = T, pattern = "*.xls*"))
> >     > > #+END_SRC
> >     > >
> >     > > This prints a list of filenames that are quite long. I need to
> >     > > preserve them as is. Here is the results block:
> >     > >
> >     > > #+END_SRC
> >     > >
> >     > > #+Results:
> >     > > #+BEGIN_SRC org
> >     > > [1] "20130304 Some Spreadsheet/20130215 XXXXXXXXXXX_CB edited
> >     > for
> >     > > sample classification.xls"
> >     > > [2] "20130304 Some Spreadsheet/20130215 XXXXXXXXXXX_CB edited
> >     > for
> >     > > sample classification.xls"
> >     > > [4] "20130304 Some Spreadsheets/20130215 XXXXXXXXXXXXXXXX
> >     > samples
> >     > > results final.xlsx"
> >     > > [5] "20130304 Some Spreadsheets/20130215 XXXXXXXXXXXXXXXX
> >     > results
> >     > > final_formatted.xlsx"
> >     > > [6] "20130304 Some Spreadsheets/20130304 XXXXXXXXXXXXXXXX
> >     > samples
> >     > > results 121109_Rep Aliqs Highlighted.xlsx"
> >     > >
> >     > > #+END_SRC
> >     > >
> >     > > Is there a way for me to define the scaling of the text within
> >     > the
> >     > > results block when this is exported using latex?
> >     >
> >     >
> >     > Jay mentioned how to repeatably wrap the results in latex
> >     markup;
> >     > I'd
> >     > look into the \resizebox in the graphicsx package to make sure
> >     the
> >     > block
> >     > of filenames fits the page. Something like:
> >     >
> >     > #+LATEX: \resizebox{\textwidth}{!}{%
> >     > #+RESULTS: foo
> >     > #+BEGIN_SRC org
> >     > etc...
> >     > #+END_SRC
> >     > #+LATEX: }
> >     >
> >     > Untested, but something like that ought to work...
> >     >
> >     > E
> >     >
> >     >
> >
>

[-- Attachment #2: Type: text/html, Size: 7603 bytes --]

  parent reply	other threads:[~2013-04-18  2:46 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 [this message]
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
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_SOTZ_dM8_X1zL7KQcGp2FX12zY3L+LLxysfYfysZ1DciUVw@mail.gmail.com \
    --to=shripad.sinari@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).