From: Eric S Fraga <ucecesf@ucl.ac.uk>
To: Tassilo Horn <tassilo@member.fsf.org>
Cc: emacs-orgmode@gnu.org
Subject: Re: Re: Columns with LaTeX beamer export
Date: Tue, 06 Jul 2010 21:47:35 +0100 [thread overview]
Message-ID: <87ocekxrpz.wl%ucecesf@ucl.ac.uk> (raw)
In-Reply-To: <87hbkcbdx5.fsf@thinkpad.tsdh.de>
[-- Attachment #1: Type: text/plain, Size: 1554 bytes --]
On Tue, 06 Jul 2010 21:36:38 +0200, Tassilo Horn <tassilo@member.fsf.org> wrote:
>
> Eric S Fraga <ucecesf@ucl.ac.uk> writes:
>
> Hi Eric,
>
> >> But my real question was concerning the point
> >>
> >> Columns without additional outline structure
> >>
> >> in http://orgmode.org/worg/org-tutorials/org-beamer.php. Especially
> >> the sentence "The column ends at the next entry with such a
> >> property." makes me head-shaking. How can there be a next entry in
> >> that frame, if I don't add an additional outline structure?
> >
> > I didn't write this but I think this means that if one column starts
> > at, say, a 2nd level heading (**), the end of content for that column
> > is the next heading at the same level, or the end of the frame (i.e. a
> > heading at a higher level (*)).
>
> Well, but then I do have an outline structure. At least that "Columns
> without additional outline structure" headline sounded to me like I
> could have something like this completely hypothetical stuff.
>
> --8<---------------cut here---------------start------------->8---
> * My 2 Column Frame
> :PROPERTIES:
> :BEAMER_env: columns
> :BEAMER_col: 0.5 0.5
> :END:
>
> - left col text
> - more left col text
>
> - right col text
> - more right col text
> --8<---------------cut here---------------end--------------->8---
>
> Bye,
> Tassilo
I'm sorry Tassilo but I do not understand your point. Lists are not
part of an outline structure so there is only one outline component in
this example.
Maybe others can chime in here...
[-- Attachment #2: Type: text/plain, Size: 75 bytes --]
--
Eric S Fraga
GnuPG: 8F5C 279D 3907 E14A 5C29 570D C891 93D8 FFFC F67D
[-- Attachment #3: Type: text/plain, Size: 201 bytes --]
_______________________________________________
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
next prev parent reply other threads:[~2010-07-06 20:47 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-06 7:46 Columns with LaTeX beamer export Tassilo Horn
2010-07-06 15:08 ` Eric S Fraga
2010-07-06 19:04 ` Tassilo Horn
2010-07-06 19:22 ` Eric S Fraga
2010-07-06 19:36 ` Tassilo Horn
2010-07-06 20:47 ` Eric S Fraga [this message]
2010-07-07 6:52 ` Tassilo Horn
2010-07-07 7:01 ` Carsten Dominik
2010-07-07 7:14 ` Tassilo Horn
2010-07-07 7:56 ` Carsten Dominik
2010-07-07 8:25 ` Tassilo Horn
2010-07-07 10:38 ` Eric S Fraga
2010-07-07 10:43 ` Carsten Dominik
2010-07-07 11:02 ` Tassilo Horn
2010-07-07 11:19 ` Eric S Fraga
2010-07-08 5:58 ` Tassilo Horn
2010-07-08 8:11 ` Eric S Fraga
2010-07-08 10:10 ` Tassilo Horn
2010-07-07 8:00 ` Carsten Dominik
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=87ocekxrpz.wl%ucecesf@ucl.ac.uk \
--to=ucecesf@ucl.ac.uk \
--cc=e.fraga@ucl.ac.uk \
--cc=emacs-orgmode@gnu.org \
--cc=tassilo@member.fsf.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).