emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Russell Adams <RLAdams@AdamsInfoServ.Com>
To: Org Mode List <emacs-orgmode@gnu.org>
Subject: Latex export & Prosper Presentation
Date: Fri, 26 Sep 2008 11:33:57 -0500	[thread overview]
Message-ID: <20080926163357.GS11943@thinkpad.adamsinfoserv.com> (raw)

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

I've gotten a basic export to Prosper working for a presentation I'm
writing to give this weekend.

Here is the extra portion for .emacs:
(setq org-export-latex-classes (cons '("prosper"
     "% BEGIN Prosper Defaults
\\documentclass[pdf, contemporain]{prosper}
\\usepackage[utf8]{inputenc}
\\usepackage[T1]{fontenc}
\\usepackage[colorlinks,linkcolor=blue]{hyperref}
% END Prosper Defaults

"
     ("\\begin{slide}{%s}" . "\\begin{slide}{%s}"))
                                     org-export-latex-classes))

Unfortunately it doesn't appear that I can add a closure for the
slide, so a manual "\end{slide}" must go at the end of each.

Attached is the sample presentation, and it compiles after export
with:

latex Backups.tex && dvips Backups.dvi && ps2pdf Backups.ps

The pdflatex command doesn't work with Prosper.

Enjoy!

------------------------------------------------------------------
Russell Adams                            RLAdams@AdamsInfoServ.com

PGP Key ID:     0x1160DCB3           http://www.adamsinfoserv.com/

Fingerprint:    1723 D8CA 4280 1EC9 557F  66E8 1154 E018 1160 DCB3

[-- Attachment #2: Backups.org --]
[-- Type: text/plain, Size: 723 bytes --]

#+LaTeX_CLASS: prosper
#+TITLE:     Linux Backups
#+AUTHOR:    Russell Adams
#+EMAIL:     rladams@adamsinfoserv.com
#+DATE:      <2008-09-26 Fri>
#+LANGUAGE:  en
#+OPTIONS:   H:3 num:t toc:nil \n:t @:t ::t |:t ^:t -:t f:t *:t TeX:t LaTeX:nil skip:nil d:nil tags:not-in-toc
#+INFOJS_OPT: view:nil toc:nil ltoc:t mouse:underline buttons:0 path:http://orgmode.org/org-info.js


* Linux Backup

| a | B | C |
|---+---+---|
| 1 | 2 | 3 |

\end{slide}

* cp

Yadda

 - A
 - B
 - C

\end{slide}

* tar

Yadda

 - A
 - B
 - C

\end{slide}

* Amanda

Yadda

 - A
 - B
 - C

\end{slide}

* rsnapshot

Yadda

 - A
 - B
 - C

\end{slide}

* Duplicity

Yadda

 - A
 - B
 - C

\end{slide}

* BackupPC

Yadda

 - A
 - B
 - C

\end{slide}

[-- Attachment #3: Type: text/plain, Size: 204 bytes --]

_______________________________________________
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

             reply	other threads:[~2008-09-26 16:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-26 16:33 Russell Adams [this message]
2008-10-04  5:22 ` Latex export & Prosper Presentation Daniel J. Sinder
2008-10-14 18:46   ` Carsten Dominik
2008-10-04 16:36 ` 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=20080926163357.GS11943@thinkpad.adamsinfoserv.com \
    --to=rladams@adamsinfoserv.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).