From: James Harkins <jamshark70@gmail.com>
To: Nicolas Goaziou <n.goaziou@gmail.com>
Cc: Emacs-orgmode@gnu.org
Subject: Re: New beamer export error with top-level TODOs
Date: Sat, 2 Mar 2013 12:13:20 +0800 [thread overview]
Message-ID: <CAFniQ7VF+=ua4yXiZUkopQ3UJOLcb2jmL3yieh3kNgsKmqzsUw@mail.gmail.com> (raw)
In-Reply-To: <87obf3o2lp.fsf@gmail.com>
On Fri, Mar 1, 2013 at 6:07 PM, Nicolas Goaziou <n.goaziou@gmail.com> wrote:
> Hello,
>
> James Harkins <jamshark70@gmail.com> writes:
>
>> In the *new* beamer exporter, if I have a top level heading with a
>> TODO keyword, LaTeX chokes on the exported .tex file.
>
> It should be fixed in master. Could you confirm it?
Yes, fixed, thank you!
BTW, now that I'm actually using the new exporter, (despite my
complaints at first) I find it an improvement over the old beamer
exporter. The org representation of the LaTeX structure seems cleaner
and more consistent. While I would have liked to use my old
presentations without much editing, it's well worth the effort.
A concrete example: Often, I want to have a column of bullet list on
the left and an image on the right. In the old exporter, the columns
had to be marked by headlines, which produced a bullet point. So then,
I had to display silly things like:
> Screenshot ( ">" represents the bullet)
Image below
In the new exporter, a column is still a headline, but that turns into
a block and a headline is hidden. So this:
*** Right column (screenshot) :BMCOL:
:PROPERTIES:...
[[./img/whatever.png]]
Displays perfectly cleanly, no extra junk in the PDF. (And the image
even inherits the column width, which the old exporter did not do
nicely IIRC.)
TL;DR -- I take back most of what I said before :)
hjh
prev parent reply other threads:[~2013-03-02 4:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-01 9:17 New beamer export error with top-level TODOs James Harkins
2013-03-01 10:07 ` Nicolas Goaziou
2013-03-02 4:13 ` James Harkins [this message]
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='CAFniQ7VF+=ua4yXiZUkopQ3UJOLcb2jmL3yieh3kNgsKmqzsUw@mail.gmail.com' \
--to=jamshark70@gmail.com \
--cc=Emacs-orgmode@gnu.org \
--cc=jamshark70@dewdrop-world.net \
--cc=n.goaziou@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).