emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: shripad sinari <shripad.sinari@gmail.com>
To: emacs-orgmode@gnu.org
Subject: scaling the text in the results block of some code chunk when exported using LaTeX
Date: Mon, 18 Mar 2013 16:44:23 -0700	[thread overview]
Message-ID: <CAA_SOTaTez6-L=p4UJ8NUrNydYkV0ttbgPn6ZX7aGTLvy+G1oA@mail.gmail.com> (raw)

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

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?

Thank you and regards,

Shripad
Tucson, AZ

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

             reply	other threads:[~2013-03-18 23:44 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-18 23:44 shripad sinari [this message]
2013-03-19  0:26 ` scaling the text in the results block of some code chunk when exported using LaTeX 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
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_SOTaTez6-L=p4UJ8NUrNydYkV0ttbgPn6ZX7aGTLvy+G1oA@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).