From: Suvayu Ali <fatkasuvayu+linux@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Custom column environment in beamer export
Date: Tue, 16 Jun 2015 11:42:34 +0200 [thread overview]
Message-ID: <20150616094234.GB12806@chitra.no-ip.org> (raw)
In-Reply-To: <87ioaovc3y.fsf@gmx.us>
On Tue, Jun 16, 2015 at 12:30:09AM +0200, Rasmus wrote:
> Suvayu Ali <fatkasuvayu+linux@gmail.com> writes:
>
> > * Fitting technique :B_minipage:
> > :PROPERTIES:
> > :BEAMER_env: minipage
> > :BEAMER_arg: 0.1\linewidth
> > :END:
> > +/cFit/+
>
> The closest would probably be something like
>
> (add-to-list 'org-beamer-environments-extra
> '("minipage"
> "m"
> "\\begin{minipage}%o%a\n\\structure{%h}"
> "\\end{minipage}"))
>
> Which would afford you something like
>
> * slide
> ** Fitting technique :B_minipage:
> :PROPERTIES:
> :BEAMER_env: minipage
> :BEAMER_OPT: [t]{0.1\linewidth}
> :BEAMER_ACT: <5>
> :END:
> /cFit/
Well, I would rather keep the formatting in the org file, so no
\structure in the template. But otherwise your suggestion seems exactly
what I need :).
> Unfortunately, BEAMER_OPTs are wrapped in square brackets thanks to
> org-beamer--normalize-argument, so the above won't actually work (see
> org-beamer--format-block). From the looks of it I'd be willing to call it
> a bug, but Nicolas may have had something in mind.
I was thinking the same. That's why I felt the need for the old
BEAMER_arg property!
> Perhaps these days it would be nice to allow the third element of
> org-beamer-environments-extra to be a λ taking either the object or so.
> Then again, perhaps this is an overkill and too low-level.
This might be nice, but as you say could be overkill. Although, there
are a few other cases which is harder to use with the current syntax.
Take minipage as an example, it takes 3 optional arguments[1].
Presently there is no way of dealing with something like that. Removing
the autowrapping of brackets would allow such cases, but it would
probably break a few Org files in the wild. From that perspective, a
lambda might be the way to go.
> Personally, I'd use a block, e.g.
>
> #+attr_latex: :options [t]{.1\textwidth}
> #+begin_minipage
> Cfit
> #+end_minipage
Nice idea. I have never really explored using blocks (other than for
raw latex), maybe I should ...
Thanks,
Footnotes:
[1] https://en.wikibooks.org/wiki/LaTeX/Boxes#minipage_and_parbox
--
Suvayu
Open source is the future. It sets us free.
next prev parent reply other threads:[~2015-06-16 9:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-15 22:00 Custom column environment in beamer export Suvayu Ali
2015-06-15 22:30 ` Rasmus
2015-06-16 9:42 ` Suvayu Ali [this message]
2015-06-16 11:57 ` Nicolas Goaziou
2015-06-16 12:37 ` Suvayu Ali
2015-06-16 12:52 ` Rasmus
2015-06-16 13:33 ` Nicolas Goaziou
2015-06-16 14:33 ` Suvayu Ali
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=20150616094234.GB12806@chitra.no-ip.org \
--to=fatkasuvayu+linux@gmail.com \
--cc=emacs-orgmode@gnu.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).