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 17:31:47 +0200 [thread overview]
Message-ID: <867ghf7eos.fsf@somewhere.org> (raw)
In-Reply-To: 87y59vsqkm.fsf@gmail.com
Hello Nicolas,
Nicolas Goaziou wrote:
> "Sebastien Vauban" writes:
>> Nicolas Goaziou wrote:
>>> 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:
>>
>> ** {10}(3,3) :textpos1:
>>
>> Contents to position
>> at some (x,y) coordinates...
>
> Correct.
I think this is quite elegant...
With what you say below, we then have 3 different solutions (at least) for new
environments:
- the one above, where you add a new environment definition (but, then, it's
kind of private for your own files; difficult to share)
- the Org special blocks, ancient way, which you've fixed
#+begin_myenv{2cm}
Contents...
#+end_myenv
- the Org special blocks, new way, with the OPTIONS
#+LaTeX_ATTR: :options {2cm}
#+begin_myenv{2cm}
Contents...
#+end_myenv
Now, a big question: outside the fact that some such "standards" (like
"texpos1") would have to be added IMHO as default Beamer environments, what
about standard LaTeX?
I think normal, then, to wanna get that same behavior in the LaTeX backend.
How to do that? I'm a bit puzzled by the differences to get some similar
results...
- In LaTeX, you have the inline tasks which can be used to insert blocks, but
not the system where you create blocks by adding an "ignoreheading" heading,
right?
- In Beamer, we have both? And, for whatever reason (which must escape me),
we tend to prefer the "ignoreheading" for closing a block.
In my latest slides, I've been quite disturbed by how much "pure LaTeX" I've
finally inserted in my slides, for inserting TikZ nodes to render boxes. I had
the impression to write LaTeX inside an Org file; and that's not the right
approach:
- too much LaTeX tag overload,
- no HTML equivalent for the contents of my boxes -- while, as presented here
above for the "textpos", even in HTML, it'd be quite nice.
- no Org syntax usable: inside my boxes (TikZ nodes), I had to use \textbf for
bold, not the stars...
Now, there are, once again, other extra solutions: MACRO and Org Babel calls.
Too much solutions...
>> 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?
>
> No. I fixed it ten days ago (dffdc49).
OK, thanks!
Best regards,
Seb
--
Sebastien Vauban
next prev parent reply other threads:[~2013-06-27 15:31 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 [this message]
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=867ghf7eos.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).