emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Carsten Dominik <carsten.dominik@gmail.com>
To: JBash <bashveank@gmail.com>
Cc: emacs-orgmode Mode <emacs-orgmode@gnu.org>
Subject: Re: Beamer support - 2nd round
Date: Tue, 8 Dec 2009 18:21:30 +0100	[thread overview]
Message-ID: <53CBEBAE-B3B3-4920-BF0A-DBF011CF9194@gmail.com> (raw)
In-Reply-To: <407c66ac0912071215l7cd65139lac138fe890fabbd7@mail.gmail.com>


On Dec 7, 2009, at 9:15 PM, JBash wrote:
>
> This is not working quite right for me...
> I pulled the latest beamer branch from git this morning and  
> installed it.  I am getting the export to latex, but no columns in  
> the beamer (tex) and resulting pdf file.  There is a title frame, a  
> TOC (blank) frame, and then a single frame titled "This is the first  
> structural section".  All other elements are nested itemized lists  
> on that single slide.
>
> I manually copied the org-beamer.el file to my site-lisp area.  Is  
> that supposed to be installed along with the other org files?
>
> I had also previously defined org-latex-export-classes, and have  
> removed that from my .emacs file.
>
> I am also seeing an unexpected error the *second* (and subsequent)  
> time I export (without changes to the org file) to to PDFabout a  
> column-width function:
>
> Select command:
> Exporting to PDF...
> Exporting to LaTeX...
> org-beamer-open-column: Symbol's function definition is void: org- 
> beamer-add-units-to-column-width

Ah, I changed the name of this function, but not in all places, sorry  
about that.

Fixed now.

- Carsten

>
> If I restart emacs, I can export again (1 time) without these errors.
>
> If this points to something obvious in my configuration, please let  
> me know.  I suspect I have something strangely configured, as no one  
> else is having these issues.
>
> Thanks,
> Jerry

- Carsten

  parent reply	other threads:[~2009-12-08 17:21 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-03 16:10 Beamer support - 2nd round Carsten Dominik
2009-12-04 18:34 ` Eric S Fraga
2009-12-04 23:31   ` Daniel Martins
2009-12-04 23:45     ` Nick Dokos
2009-12-05  0:04       ` Daniel Martins
2009-12-05  0:16         ` Nick Dokos
2009-12-05  8:05         ` Carsten Dominik
2009-12-05 14:34           ` Daniel Martins
2009-12-07 20:15           ` JBash
2009-12-07 20:29             ` JBash
2009-12-07 21:34               ` Daniel Martins
2009-12-08 17:21             ` Carsten Dominik [this message]
2009-12-08 17:52               ` JBash
2009-12-08 23:04                 ` Carsten Dominik
2009-12-05 17:10   ` Carsten Dominik
     [not found]     ` <87vdgkcg0d.wl%ucecesf@ucl.ac.uk>
2009-12-06 23:51       ` Carsten Dominik
2009-12-06 13:13 ` Magnus Henoch
2009-12-06 13:24   ` Magnus Henoch
2009-12-08 17:21   ` Carsten Dominik
2009-12-10 21:32 ` Adam Spiers
2009-12-14  8:11   ` Carsten Dominik
2009-12-18 11:12     ` Adam Spiers

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=53CBEBAE-B3B3-4920-BF0A-DBF011CF9194@gmail.com \
    --to=carsten.dominik@gmail.com \
    --cc=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).