emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: zwz <zhangweize@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: [beamer] source code in two column
Date: Thu, 22 Sep 2011 19:15:08 +0800	[thread overview]
Message-ID: <87ipok7rr7.fsf@gmail.com> (raw)
In-Reply-To: 87y5xhaq8s.fsf@ucl.ac.uk

Eric S Fraga <e.fraga@ucl.ac.uk> writes:

> zwz <zhangweize@gmail.com> writes:
>
>> I use org to make presentations for C class.
>> Sometimes the code is quite long. And I want to arrange it in two
> column
>> so that it will be presented in one slide.
>>
>> I wonder how to do it easily using org-export. 
>> My current setting just hides the code that beyond the page in one
>> column.
>>
>> Best regards,
>> zwz 
>
> I cannot help you directly in that I don't know how to /flow/ text (or
> code) from one column to the next.  I don't think it is actually
> possible in beamer.
>
> However, it *is* straightforward to flow text from one slide to the next
> by simply adding =allowframebreaks= to the beamer environment
> arguments.  For instance,
>
> #+begin_src org
> *** Code example
>     :PROPERTIES:
>     :BEAMER_envargs: [allowframebreaks]
>     :END:
> #+LATEX: {\scriptsize
> #+begin_example
>    <code goes here>
> #+end_example
> #+LATEX: }
> #+end_src
>
> The slides will automatically be numbered using roman numerals should
> more than one slide (aka frame in beamer speak) be required.
>
> I use latex directives to make the font a little smaller to ensure that
> lines with within the slide width-wise.
>
> HTH,
> eric
It is a nice workaround.
But here in my org file, I have to put the "allowframebreaks" in level
two headlines (probably because of my setting #+BEAMER_FRAME_LEVEL: 2), 
otherwise it does not take effect.

  reply	other threads:[~2011-09-22 11:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-22  8:52 [beamer] source code in two column zwz
2011-09-22  9:19 ` Eric S Fraga
2011-09-22 11:15   ` zwz [this message]
2011-09-22 11:33     ` Eric S Fraga

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=87ipok7rr7.fsf@gmail.com \
    --to=zhangweize@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).