emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Eric S Fraga <ucecesf@ucl.ac.uk>
To: Tassilo Horn <tassilo@member.fsf.org>
Cc: emacs-orgmode@gnu.org, Carsten Dominik <carsten.dominik@gmail.com>
Subject: Re: Re: Columns with LaTeX beamer export
Date: Wed, 07 Jul 2010 11:38:21 +0100	[thread overview]
Message-ID: <87vd8r8tlu.wl%ucecesf@ucl.ac.uk> (raw)
In-Reply-To: <201007071025.01015.tassilo@member.fsf.org>

[-- Attachment #1: Type: text/plain, Size: 943 bytes --]

On Wed, 7 Jul 2010 10:25:00 +0200, Tassilo Horn <tassilo@member.fsf.org> wrote:
> 
> On Wednesday 07 July 2010 09:56:49 Carsten Dominik wrote:
> 
> > > I think every property is explained in the info docs, and Eric's
> > > tutorial shows some nice and well explained examples, so the
> > > org-beamer.org file could be deleted.
> > 
> > If you want, please go ahead and make these changes.  The link in
> > Erics tutorial should then point to the manual section, not the
> > preliminary documentation.
> 
> I deleted the obsolete org-beamer.org and added a link to the beamer
> class manual section to Eric's tutorial.  So Worg should be ok now.
> 
> Bye,
> Tassilo

Excellent.  Thanks!

And, yes, I'd forgotten about the historical nature of the first
document you looked at!  Although it was done not so long ago,
Carsten's proper implementation of beamer support within org allowed
me to very quickly *forget* about the hacks I had done...

[-- 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

  reply	other threads:[~2010-07-07 10:38 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
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 [this message]
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=87vd8r8tlu.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 \
    --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).