emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Darlan Cavalcante Moreira <darcamo@gmail.com>
To: e.fraga@ucl.ac.uk
Cc: "Łukasz Stelmach" <lukasz.stelmach@iem.pw.edu.pl>, emacs-orgmode@gnu.org
Subject: Re: Re: latex export and beamer columns
Date: Thu, 26 Nov 2009 16:54:06 -0300	[thread overview]
Message-ID: <4b0edcf3.0905c00a.1be5.1e1f@mx.google.com> (raw)
In-Reply-To: <87k4xdb0ts.wl%ucecesf@ucl.ac.uk>


Maybe a simpler notation could be used instead direct latex since we are talking
about official support for beamer in org-mode. For instance

,----
| * Teste beamer: This is a Section
| *** Teste beamer: This is a Subsection
| ***** This is the frame title
|       Frame content
| 
| ***** This is the frame title of another frame
| #+\{0.4
|       - This is an item
|       - This is an item too
| #+\\0.6
|       - Another item
|       - Another one
|       - One more item
|         \note[item]{lala}
| #+\}
`----

The "#+\{" comment indicates the beginning of a columns environment and the
"0.4" the width (0.4\textwidth) of the first column. The "#+\\0.6" comment
creates another column and the "#+\}" comment closes the columns
environment. I'm not saying this is the best way, but IMHO this is better than
using #+latex commands directly, since beamer support in org-mode will be
official. Also, this will export nicely to standard latex and HTML. Using
"#+latex:" could cause problems when exporting to standard latex and using
headings as suggested in other E-mails here could me exporting to anything
different from beamer unnatural.

If this syntax or something similar is used, I'd like to request only two thinks
in addition:
  1) the items in the different columns should be exported to different
     itemize environments when exporting to standard latex (similarly to HTML). If
     they are exported to the same environment it can be confusing.
  2) It would be nice if the width could be optional. If there are columns whose
     width is not specified then org could sum the widths that were specified
     and distribute the remaining among the columns whose width is not
     specified. For instance, in a frame with 3 columns I could specify the
     width of one column as 0.4 and leave the others unspecified. Org should
     then choose a width of 0.3 for the remaining two columns.


- Darlan Cavalcante


At Thu, 26 Nov 2009 18:25:19 +0000,
Eric S Fraga <ucecesf@ucl.ac.uk> wrote:
> 
> At Thu, 26 Nov 2009 02:52:04 +0100,
> Łukasz Stelmach wrote:
> > 
> > I've just tried something simplier and IMHO more flexible (widths).
> > 
> > --8<---------------cut here---------------start------------->8---
> > * The Title
> > ** The Section
> > *** The Frame
> > #+latex: \begin{columns}[t]
> > #+latex: \column{.5\textwidth}
> >    - My point
> >    - Your point
> > #+latex: \column{.5\textwidth}
> > Conclusion
> > #+latex: \end{columns}
> > --8<---------------cut here---------------end--------------->8---
> > 
> > Unfortunately the the plain list is not recognized and converted to
> > itemize. When I remove the "#+latex: \begin|end" stuff then the list
> > looks as it should.
> 
> 
> (note that my response has probably been superseded by Carsten's
> recent message regarding beamer support in org mode but this still
> might be of some interest)
> 
> 
> I am not sure what to say!  IMO, it's not simpler although I guess it
> could be more flexible.  However, you say it doesn't work?
> 
> One alternative based on your approach is to define begin and end
> commands for the columns environment that avoid using "\begin" and
> "\end" which org interprets.  Maybe something like this:
> 
> --8<---------------cut here---------------start------------->8---
> #+LaTeX_CLASS: beamer 
> 
> #+latex: \newcommand{\BC}{\begin{columns}[t]}
> #+latex: \newcommand{\EC}{\end{columns}}
> 
> * The main section
> *** An interesting slide
>     \BC
>     #+latex: \column{0.4\textwidth}
>     - an item with enough text to show the width of the column
>     - another item
>     #+latex: \column{0.6\textwidth}
>     - an item with enough text to show the width of the column
>     - and yet another
>     \EC
> --8<---------------cut here---------------end--------------->8---
> 
> which appears to work just fine.  Whether it's simpler or not depends
> on what you want.  I like using org headlines to be able to hide
> individual columns and to be able to move them around easily.
> 
> 
> _______________________________________________
> Emacs-orgmode mailing list
> Please use `Reply All' to send replies to the list.
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode

      reply	other threads:[~2009-11-26 19:54 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-21 12:49 latex export and beamer columns Eric S Fraga
2009-11-21 13:34 ` Carsten Dominik
2009-11-22 12:12   ` Eric S Fraga
2009-11-22 15:15     ` Eric S Fraga
2009-11-22 15:29       ` Matt Lundin
2009-11-22 19:31         ` Eric S Fraga
2009-11-23 13:55       ` Carsten Dominik
2009-11-23 22:15         ` Eric S Fraga
2009-11-24  0:02           ` Daniel Martins
2009-11-24  6:55           ` Carsten Dominik
2009-11-24  8:36             ` Eric S Fraga
2009-11-24  8:49             ` Eric S Fraga
2009-11-24  8:59               ` Carsten Dominik
2009-11-24 18:02                 ` Eric S Fraga
2009-11-25  6:28                   ` Carsten Dominik
2009-11-25  9:27                     ` Eric S Fraga
2009-11-25 18:03                     ` Eric S Fraga
2009-11-25 23:25                       ` Carsten Dominik
2009-11-26  8:16                         ` Eric S Fraga
2009-11-26  9:05                           ` Carsten Dominik
2009-11-26 10:33                             ` Eric S Fraga
2009-11-23 14:53     ` Sébastien Vauban
2009-11-21 16:33 ` Thomas S. Dye
2009-11-22 12:00   ` Eric S Fraga
2009-11-26  1:52 ` Łukasz Stelmach
2009-11-26 18:25   ` Eric S Fraga
2009-11-26 19:54     ` Darlan Cavalcante Moreira [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=4b0edcf3.0905c00a.1be5.1e1f@mx.google.com \
    --to=darcamo@gmail.com \
    --cc=e.fraga@ucl.ac.uk \
    --cc=emacs-orgmode@gnu.org \
    --cc=lukasz.stelmach@iem.pw.edu.pl \
    /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).