emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Sebastien Vauban" <sva-news-D0wtAvR13HarG/iDocfnWg@public.gmane.org>
To: emacs-orgmode-mXXj517/zsQ@public.gmane.org
Subject: Re: Help with beamer environments + org-special-blocks!
Date: Thu, 27 Jun 2013 12:03:52 +0200	[thread overview]
Message-ID: <864ncj50qf.fsf@somewhere.org> (raw)
In-Reply-To: 87obatt068.fsf@gmail.com

Hello Nicolas,

Nicolas Goaziou wrote:
> "Sebastien Vauban" writes:
>> Vikas Rawal wrote:
>
>>> For example, if I use the following:
>>>
>>> (add-to-list 'org-beamer-environments-extra
>>>              '("textpos1" "w" "\\begin{textblock}%h \\visible %a {" "}
>>> \\end{textblock}"))
>>>
>>> and write the headline as {10}(3,3), I get \{10\}(3,3) in beamer
>>> export rather than {10}(3,3).
>
> I think we should changes some environment placeholders:
>
>   + Introduce %r which would stand for the raw headline (without any
>     processing)
>   + %H and %U would use the raw headline text instead.
>
> The previous definition would become:
>
>   '("textpos1" "w" "\\begin{textblock}%r \\visible %a {" "} \\end{textblock}")
>
> WDYT?

I'm not sure to understand. Where would he put his options?  Directly on the
heading line, with no "text", then?

Something like this:

--8<---------------cut here---------------start------------->8---
** {10}(3,3)                                           :textpos1:

Contents to position
at some (x,y) coordinates...
--8<---------------cut here---------------end--------------->8---

>>   #+begin_myenvironment{3}                \#+begin\_myenvironment\{3\}
>>   Test of a new                           Test of a new
>>   environment.                            environment.
>>   #+end_myenvironment                     \#+end\_myenvironment
>
> This should work with a recent Org.

What do you call a recent Org?  I'm blocked on commit 26a9b02, from May 27th,
as long as the #+SETUPFILE: bug is not fixed (fontification is broken).

So, is that one (4 weeks old) a recent Org?

> There is also:
>
>   #+attr_latex: :options {3}
>   #+begin_myenvironment
>   Test of a new
>   environment
>   #+end_myenvironment

Aahh!  I wasn't aware (enough) of that way to pass my arguments to my own
environments. Thanks a lot, that works like a charm!

Best regards,
  Seb

-- 
Sebastien Vauban

  reply	other threads:[~2013-06-27 10:03 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-20  8:09 Help with beamer environments Vikas Rawal
2013-06-26 13:53 ` Help with beamer environments + org-special-blocks! Sebastien Vauban
2013-06-26 14:29   ` Nicolas Goaziou
2013-06-27 10:03     ` Sebastien Vauban [this message]
2013-06-27 12:09       ` Nicolas Goaziou
2013-06-27 15:31         ` Sebastien Vauban
2013-06-27 16:18           ` Nicolas Goaziou
2013-06-29 12:45           ` Nicolas Goaziou
2013-06-28  9:48         ` Sebastien Vauban
2013-06-28 23:18           ` Nicolas Goaziou
2013-06-29  8:05             ` Sebastien 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=864ncj50qf.fsf@somewhere.org \
    --to=sva-news-d0wtavr13harg/idocfnwg@public.gmane.org \
    --cc=emacs-orgmode-mXXj517/zsQ@public.gmane.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).