emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Eric S Fraga <e.fraga@ucl.ac.uk>
To: Avdi Grimm <groups@inbox.avdi.org>
Cc: Org Mode List <emacs-orgmode@gnu.org>
Subject: Re: [dev] About a beamer back-end
Date: Mon, 18 Jun 2012 08:50:55 +0100	[thread overview]
Message-ID: <87ipep83ds.fsf@ucl.ac.uk> (raw)
In-Reply-To: <CA+XG7-jV_XOvEbbzECiJtokG3VMK6aJ0sAdwgk-kZxM-o=C5_A@mail.gmail.com> (Avdi Grimm's message of "Fri, 15 Jun 2012 12:47:21 -0400")

Avdi Grimm <groups@inbox.avdi.org> writes:

> On Fri, Jun 15, 2012 at 12:41 PM, suvayu ali <fatkasuvayu+linux@gmail.com>
>  wrote:
>
>> With this syntax it would be very easy to write both really long (40-50
>> frames) as well as quick and short presentations.
>>
>
> I've only been using Org and Beamer for a little while, but if I understand
> it correctly this sounds preferable.

Well, I will have to chime in with a contrary view.  I like using
headlines to define blocks, and I use blocks on almost every frame.  I
have the following reasons for preferring a headline approach:

- the proposed approach does not easily (at all?) cater for blocks
  within blocks

- ease of hiding of content: org for me is still primarily an outliner!

- being able to re-arrange content in a frame quickly (M-<up>, etc.)

- within frames, there is no other use for lower level headlines.  Using
  these for blocks seems appropriate.  What else could they be used for?

Obviously, I would adapt to whatever is provided.

Thanks in advance in any case!  I look forward to beamer support in the
new exporter.
-- 
: Eric S Fraga, GnuPG: 0xC89193D8FFFCF67D
: in Emacs 24.1.50.1 and Org release_7.8.11-69-ga2fd96

  reply	other threads:[~2012-06-18  8:49 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-15 15:08 [dev] About a beamer back-end Nicolas Goaziou
2012-06-15 16:41 ` suvayu ali
2012-06-15 16:47   ` Avdi Grimm
2012-06-18  7:50     ` Eric S Fraga [this message]
2012-06-18 12:35       ` suvayu ali
2012-06-19 13:21       ` Nicolas Goaziou
2012-06-19 21:04         ` Eric S Fraga
2012-06-20  6:23           ` Greg Tucker-Kellogg
2012-06-20 11:55             ` Sebastien Vauban
2012-06-20 15:20               ` Eric S Fraga
2012-06-21 14:37           ` Nicolas Goaziou
2012-06-21 14:51             ` Sebastien Vauban
2012-06-21 16:03               ` Nicolas Goaziou
     [not found]                 ` <87obocodo7.fsf-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2012-06-21 21:14                   ` **: " Sebastien Vauban
2012-06-25 22:39                     ` Andreas Leha
2012-06-21 14:55             ` Rasmus
2012-06-21 15:56               ` Nicolas Goaziou
2012-06-21 16:36                 ` Rasmus
2012-06-21 16:49             ` suvayu ali
2012-06-22  7:54             ` Eric S Fraga
2012-06-18  6:32 ` Daniel Bausch
2012-06-18 10:17 ` Rasmus
2012-06-18 10:35   ` Sebastien Vauban
2012-06-18 12:00     ` Rasmus
2012-06-28 10:40 ` Andreas Leha
2012-06-28 10:47   ` suvayu ali
2012-06-28 10:50     ` Andreas Leha

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=87ipep83ds.fsf@ucl.ac.uk \
    --to=e.fraga@ucl.ac.uk \
    --cc=emacs-orgmode@gnu.org \
    --cc=groups@inbox.avdi.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).