From: Jay Kerns <gjkernsysu@gmail.com>
To: shripad sinari <shripad.sinari@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: scaling the text in the results block of some code chunk when exported using LaTeX
Date: Mon, 18 Mar 2013 20:26:29 -0400 [thread overview]
Message-ID: <CAFiLVraJwtbg6kOrpeg4w7hU_TnRWe9B5Jo0k2e0uAZtDQhQJA@mail.gmail.com> (raw)
In-Reply-To: <CAA_SOTaTez6-L=p4UJ8NUrNydYkV0ttbgPn6ZX7aGTLvy+G1oA@mail.gmail.com>
Hello Shripad,
On Mon, Mar 18, 2013 at 7:44 PM, shripad sinari
<shripad.sinari@gmail.com> wrote:
[snip]
> Is there a way for me to define the scaling of the text within the results
> block when this is exported using latex?
[snip]
I don't know of a way to scale /within/ the code block, but does
this work instead?
#+NAME: foo
#+BEGIN_SRC R :session :exports results :results output org replace :tangle yes
print(list.files(recursive = T, pattern = "*.xls*"))
#+END_SRC
\scriptsize
#+RESULTS: foo
#+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
\normalsize
I learned just yesterday that the 'naming code blocks' trick is very
handy for things like this. Here is halfway through the thread where
this was discussed:
http://lists.gnu.org/archive/html/emacs-orgmode/2013-03/msg01268.html
See also John Hendy's comments later in the thread.
I hope this helps,
--
Jay
next prev parent reply other threads:[~2013-03-19 0:26 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 [this message]
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=CAFiLVraJwtbg6kOrpeg4w7hU_TnRWe9B5Jo0k2e0uAZtDQhQJA@mail.gmail.com \
--to=gjkernsysu@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).