From: JBash <bashveank@gmail.com>
To: emacs-orgmode Mode <emacs-orgmode@gnu.org>
Subject: Fwd: Exporting subtree as beamer presentation
Date: Mon, 4 Jan 2010 13:26:16 -0500 [thread overview]
Message-ID: <407c66ac1001041026x74ec452u80c98f96cb15a31d@mail.gmail.com> (raw)
In-Reply-To: <407c66ac1001041021o340f2004x2145e1468556be8c@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1218 bytes --]
Sorry - With attachments this time.
project1.org has the embedded presentation (CDR Presentation), and
cdr1.orgis that subtree placed in a separate file, adjusting the
settings
accordingly).
Thanks,
Jerry
---------- Forwarded message ----------
From: JBash <bashveank@gmail.com>
Date: Mon, Jan 4, 2010 at 1:21 PM
Subject: Exporting subtree as beamer presentation
To: emacs-orgmode Mode <emacs-orgmode@gnu.org>
Hi,
How do I export a beamer presentation, embedded as a subtree in an org file?
I have attached a file with subtree properties defined as described on the
worg page - http://orgmode.org/worg/org-tutorials/org-beamer.php.
I expected 'C-c C-e 1 d' to do it, but the export is a article
documentclass, and is the entire document rather than just the subtree.
If I cut and paste the subtree to a separate file, and define the export
settings for beamer at the top of the file, I get the expected results
(documentclass[presentation]{beamer} (using C-c C-e d, since I am now have
the entire file, rather than a subtree).
I'm not sure if I have the properties defined improperly, or if I'm not
using the right command to export the subtree.
(Using 6.33trans, updated from git this morning.)
Thanks,
Jerry
[-- Attachment #1.2: Type: text/html, Size: 1663 bytes --]
[-- Attachment #2: project1.org --]
[-- Type: application/octet-stream, Size: 1937 bytes --]
* Project 1
** Project Notes for Design
Tasks, Notes, Analysis
*** PDR Discussion
*** PDR Presentation
** Project Notes for Development
More Tasks, Notes and Analysis
*** CDR Discussion
Notes, Tasks, Highlights, Issues, Status
*** CDR Presentation
:PROPERTIES:
:LaTeX_CLASS: beamer
:BEAMER_FRAME_LEVEL: 2
:LaTeX_CLASS_OPTIONS: [presentation]
:BEAMER_HEADER_EXTRA: \usetheme{Madrid}\usecolortheme{default}
:COLUMNS: %40ITEM %10BEAMER_env(Env) %10BEAMER_envargs(Env Args) %4BEAMER_col(Col) %8BEAMER_extra(Extra)
:TITLE: Project 1 CDR Presentation
:END:
**** Overview
***** Welcome and Introduction
- Agenda
- Team
- System
- Hardware
- Software
- Test
- PM
- Programmatic Status
**** Update Development and Status
***** Hardware Development
****** HW Module 1 :B_block:
:PROPERTIES:
:BEAMER_env: block
:END:
- Requirements
- Design
- Status
****** HW Module 2 :B_block:
:PROPERTIES:
:BEAMER_env: block
:END:
- Requirements
- Design
- Status
***** Software Development
:PROPERTIES:
:END:
****** CS Module 1 :B_block:
:PROPERTIES:
:BEAMER_env: block
:END:
- Requirements
- Design
- Status
****** CS Module 2 :B_block:
:PROPERTIES:
:BEAMER_env: block
:END:
- Requirements
- Design
- Status
**** Integration Planning
***** Component Delivery
- Status of various compenents and modules
***** Component / Module Testing
- Hardware and software testing
***** System Integration Plan
****** Integration of components :B_block:
:PROPERTIES:
:BEAMER_env: block
:END:
- Acceptance Test and Delivery
**** Programmatic
***** Programatic Content :B_alertblock:
:PROPERTIES:
:BEAMER_env: alertblock
:END:
- Program Stuff
** Implementation Phase
** Integration Phase
[-- Attachment #3: cdr1.org --]
[-- Type: application/octet-stream, Size: 1705 bytes --]
#+LaTeX_CLASS: beamer
#+BEAMER_FRAME_LEVEL: 3
#+LaTeX_CLASS_OPTIONS: [presentation]
#+BEAMER_HEADER_EXTRA: \usetheme{Madrid}\usecolortheme{default}
#+COLUMNS: %40ITEM %10BEAMER_env(Env) %10BEAMER_envargs(Env Args) %4BEAMER_col(Col) %8BEAMER_extra(Extra)
#+TITLE: Project 1 CDR Presentation
* CDR Presentation
:PROPERTIES:
:COLUMNS: %40ITEM %10BEAMER_env(Env) %10BEAMER_envargs(Env Args) %4BEAMER_col(Col) %8BEAMER_extra(Extra)
:END:
** Overview
*** Welcome and Introduction
- Agenda
- Team
- System
- Hardware
- Software
- Test
- PM
- Programmatic Status
** Update Development and Status
*** Hardware Development
**** HW Module 1 :B_block:
:PROPERTIES:
:BEAMER_env: block
:END:
- Requirements
- Design
- Status
**** HW Module 2 :B_block:
:PROPERTIES:
:BEAMER_env: block
:END:
- Requirements
- Design
- Status
*** Software Development
:PROPERTIES:
:END:
**** CS Module 1 :B_block:
:PROPERTIES:
:BEAMER_env: block
:END:
- Requirements
- Design
- Status
**** CS Module 2 :B_block:
:PROPERTIES:
:BEAMER_env: block
:END:
- Requirements
- Design
- Status
** Integration Planning
*** Component Delivery
- Status of various compenents and modules
*** Component / Module Testing
- Hardware and software testing
*** System Integration Plan
**** Integration of components :B_block:
:PROPERTIES:
:BEAMER_env: block
:END:
- Acceptance Test and Delivery
** Programmatic
*** Programatic Content
**** Programmatic Stuff :B_alertblock:
Very important point
:PROPERTIES:
:BEAMER_env: alertblock
:END:
[-- Attachment #4: Type: text/plain, Size: 201 bytes --]
_______________________________________________
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode
next prev parent reply other threads:[~2010-01-04 18:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-04 18:21 Exporting subtree as beamer presentation JBash
2010-01-04 18:26 ` JBash [this message]
2010-01-05 11:26 ` Fwd: " Carsten Dominik
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=407c66ac1001041026x74ec452u80c98f96cb15a31d@mail.gmail.com \
--to=bashveank@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).