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: Sat, 29 Jun 2013 10:05:13 +0200 [thread overview]
Message-ID: <86r4fle406.fsf@somewhere.org> (raw)
In-Reply-To: 878v1trfi1.fsf@gmail.com
Hello Nicolas,
Nicolas Goaziou wrote:
> "Sebastien Vauban" writes:
>
>>> No. I fixed it ten days ago (dffdc49).
>>
>> Though I'm now on Org-mode version 8.0.3 (release_8.0.3-295-g91a4c8), pulled
>> this morning, I don't see it fixed.
>
> I realize that the patch won't fix it. This patch was introduced to
> allow something like:
>
> #+begin_figure*
> ...
> #+end_figure*
>
> again. But it still expects the same string after the "begin_" and the
> "end_". In this case strings are different because of the arguments to
> the environment.
>
> Therefore, the correct way to set this is using the #+attr_latex line,
> as in your first case.
>
> I hope it is less confusing now.
It is. And one solution is enough... ;-)
Moreover, I guess putting the arguments on a LaTeX line makes it more
portable: what would happen with those arguments for HTML, for example? Here,
a simple "mychangemargin" DIV won't hurt.
Best regards,
Seb
--
Sebastien Vauban
prev parent reply other threads:[~2013-06-29 8:05 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
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 [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=86r4fle406.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).