From: Eric S Fraga <ucecesf@ucl.ac.uk>
To: Carsten Dominik <carsten.dominik@gmail.com>
Cc: emacs-orgmode Mode <emacs-orgmode@gnu.org>
Subject: Re: Beamer support - 2nd round
Date: Fri, 04 Dec 2009 18:34:51 +0000 [thread overview]
Message-ID: <87ljhi1tbo.wl%ucecesf@ucl.ac.uk> (raw)
In-Reply-To: <F6A8EBB0-721C-4D58-A4B0-93ED254D51C2@gmail.com>
At Thu, 3 Dec 2009 17:10:44 +0100,
Carsten Dominik wrote:
> after carefully listening to all your comments and thinking
> things through more thoroughly, here is now my second attempt
> to define beamer support in Org-mode.
Carsten,
Thanks for this! After learning a bit about git branches (more than I
probably wanted to know ;-) and a bit more about org mode columns
view, I can say that I like what you have done. I've been playing
with your sample file for a short while and it looks a good design
which seems to support everything /I/ would want and does so in an
easy way (especially the combination of the new C-c C-b special
org-beamer command and columns view).
I've run into a few niggles but I need to play some more (probably
over the weekend) to see whether some of them are my fault or due to
bugs in the code. However, some immediate niggles or suggestions are:
- I need to be able to specify arguments for columns (i.e. the
environment, not specific columns), specifically
often [t] to make two columns align vertically
- I don't understand what the difference between opt and envargs is.
In fact, I see no reference to BEAMER_opt in the document you wrote
yet your example has opt as one of the column view specifications.
- it would be nice if when a column heading is also a block heading,
that the tags generated (which, by the way, is a really nice
feature) include both block and column tags to make it easy to spot
the column aspect.
You'll probably be hearing from me soon again!
Oh, and thanks for the separate email showing me how to do my page 100
with the new setup. How to do it was actually quite clear from the
example you gave in the other message. Very straightforward and does
work nicely.
Thanks again,
eric
next prev parent reply other threads:[~2009-12-04 18:35 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 [this message]
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
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=87ljhi1tbo.wl%ucecesf@ucl.ac.uk \
--to=ucecesf@ucl.ac.uk \
--cc=carsten.dominik@gmail.com \
--cc=e.fraga@ucl.ac.uk \
--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).