From: Carsten Dominik <carsten.dominik@gmail.com>
To: "Sébastien Vauban" <wxhgmqzgwmuf@spammotel.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Re: New beamer support
Date: Wed, 6 Jan 2010 15:23:30 +0100 [thread overview]
Message-ID: <CCE6A655-3917-4674-97CE-8989D9874395@gmail.com> (raw)
In-Reply-To: <871vi3nypg.fsf@mundaneum.com>
On Jan 6, 2010, at 2:35 PM, Sébastien Vauban wrote:
> Hi Carsten,
>
> Carsten Dominik wrote:
>> On Jan 6, 2010, at 11:59 AM, Sébastien Vauban wrote:
>>>
>>> Shouldn't `("@" "\\alert{%s}" nil)' be added by default?
>>
>> Hmm, I am not sure, because \alert is of course not defined in
>> normal LaTeX
>> export. And maybe it would even be better to redifine bold emphasis
>> as alert
>> for beamer export?
>
> For me, bold and alert are 2 different beasts. Some beamer styles
> even display
> them differently (different colors, for example). Better would be
> not to mix
> them, IMHO.
>
>
>>>>> - How to get "frame breaks", without modifying the resulting TeX
>>>>> file (by
>>>>> adding a frame option `allowframebreaks' -- similar to the
>>>>> `fragile'
>>>>> option)?
>>>>
>>>> Just put [allowframebreaks] into the :BEAMER_envargs: property of
>>>> the node that becomes the frame.
>>>
>>> That does work. Thanks.
>>>
>>> However, couldn't we have that on by default on all nodes? For
>>> sure, some
>>> people won't remark some text is cut off in the output beamer
>>> presentation,
>>> when the option is not set.
>>
>> I believe turning this on for all frames has drawbacks, like
>> loosing overlay capability?
>
> I'm not sure I understand the point but...
>
>
>> However, I guess it does make sense to have a global variable to
>> set default options for frames, I guess. I'll put that on my list.
>
> OK. Thanks.
>
>
>>> By the way, how are we supposed to add that property in the most
>>> easiest
>>> manner? I never really used column view, but I have troubles when
>>> using it
>>> here.
>>>
>>> On the node where I want to add that property, I do:
>>> - `C-c C-x C-c' to enter column view
>>> - `right' (arrow) to go in the second column
>>> - `e' to edit the property
>>> ... but I'm put in a tag selection menu... What am I doing wrong?
>>
>> That happens at the BEAMER_env property and give you a way to
>> select the
>> environment with a single key, for example `e b' for block. If you
>> move the
>> cursor to the field for env args, e will give you a prompt where
>> you can
>> edit.
>
> Whether in org-mode or in org-beamer-mode, when typing `e' on the
> second
> column, it opens the tag selection interface in the minibuffer. But,
> here,
> what I'm trying to add is a property, not a tag...?
Indeed you are changing the tag, but the property will change along
with it (check it!). The idea is that the property is *tracked* by
a tag, to make the current value constantly visible. I use the tag
interface just because it exists and is simple to use.
>
> Pressing TAB allows me free edition, but what's inserted at the node
> is a
> tag...
Which will cause a change in the property as well, I believe. I know
it is confusing - but once you've got your head around this, it will be
very useful.
>
> PS- An idea: wouldn't it be good (*iff* easily feasible) to load
> org-beamer-mode when opening an Org file whose LaTeX class is beamer?
That could be done, but you can also set the startup option.
But yes, it is one more think to remember...
- Carsten
next prev parent reply other threads:[~2010-01-06 14:23 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-06 9:46 New beamer support Sébastien Vauban
2010-01-06 10:06 ` Carsten Dominik
2010-01-06 10:59 ` Sébastien Vauban
2010-01-06 12:36 ` Carsten Dominik
2010-01-06 13:35 ` Sébastien Vauban
2010-01-06 14:23 ` Carsten Dominik [this message]
2010-01-06 14:31 ` Carsten Dominik
2010-01-06 15:35 ` Sébastien Vauban
2010-01-06 17:32 ` Carsten Dominik
2010-01-06 15:47 ` Sébastien Vauban
2010-01-06 17:34 ` Carsten Dominik
2010-01-07 9:38 ` Sébastien Vauban
2010-01-07 10:35 ` Carsten Dominik
2010-01-07 10:56 ` Sébastien Vauban
2010-01-06 11:13 ` Christian Lasarczyk
2010-01-06 11:57 ` Carsten Dominik
2010-01-06 13:06 ` Sébastien Vauban
2010-01-06 11:40 ` Eric S Fraga
2010-01-06 13:03 ` Sébastien Vauban
2010-01-06 13:25 ` Carsten Dominik
2010-01-06 16:22 ` Sébastien Vauban
2010-01-06 17:33 ` Carsten Dominik
2010-01-07 8:41 ` Sébastien Vauban
2010-01-07 14:39 ` Darlan Cavalcante Moreira
2010-01-07 15:43 ` Carsten Dominik
2010-01-07 16:16 ` Sébastien Vauban
2010-01-07 18:03 ` Darlan Cavalcante Moreira
2010-01-07 18:18 ` Carsten Dominik
2010-01-07 19:24 ` Sébastien Vauban
2010-01-07 16:48 ` Carsten Dominik
2010-01-07 8:54 ` Sébastien Vauban
2010-01-07 9:26 ` Carsten Dominik
2010-01-07 9:47 ` Sébastien Vauban
2010-01-07 10:00 ` Carsten Dominik
2010-01-07 10:21 ` Sébastien Vauban
2010-01-07 10:33 ` Carsten Dominik
2010-01-07 11:23 ` Sébastien Vauban
2010-01-07 11:30 ` [beamer] Order in preamble Sébastien Vauban
2010-01-07 13:15 ` Carsten Dominik
2010-01-07 15:54 ` Sébastien Vauban
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=CCE6A655-3917-4674-97CE-8989D9874395@gmail.com \
--to=carsten.dominik@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=wxhgmqzgwmuf@spammotel.com \
/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).