John Hendy <jw.hendy@gmail.com> writes:

> Just to comment on the original attempt, block and column (which is |,
> not c which is columnS) are not mutually exclusive. I just did a
> presentation and used both together. I'm not sure on the use-case for
> columnS, but my structure was two side by side columns in a slide:
>
> #+begin_src org
> * slide
> ** col1      :B_block:BMCOL:
>    :PROPERTIES:
>    :BEAMER_env: block
>    :BEAMER_col: 0.5
>    :END:
>
> - list
> - of
> - items
>
> ** col2      :B_block:BMCOL:
>    :PROPERTIES:
>    :BEAMER_env: block
>    :BEAMER_col: 0.5
>    :END:
>
> [[pic]]
> #+end_src
>
> Probably not that helpful, just wanted to clarify that some
> environments are still compatible (in case someone finds this and
> thinks that *all* multiple combos are not possible anymore).

Is it possible that *only B_* environments are mutually exclusive?

Rainer

>
>
> John
>
>
> On Wed, May 25, 2016 at 3:31 PM, Nicolas Goaziou <mail@nicolasgoaziou.fr> wrote:
>> Hello,
>>
>> Rasmus <rasmus@gmx.us> writes:
>>
>>> Not necessarily.  On the top of my head, you could have a column group
>>> with columns inside.  This example used to be possible.  I haven't checked
>>> now.
>>
>> This one is not possible anymore. A column environment implies columns.
>> You can also provide a columns environment explicitly, at a higher
>> level, e.g., to provide specific options.
>>
>> Regards,
>>
>> --
>> Nicolas Goaziou
>>
>

-- 
Rainer M. Krug
email: Rainer<at>krugs<dot>de
PGP: 0x0F52F982