Hi,
one week ago I reported that export to latex/beamer refuses to export,
and the reason where it did not do it was, according to my email
BMCOL
(slides that contained that derailed the export terminally).
In the meantime, I found one line that, when removed, solves the
problem. In that sense, one might say, it's not BMCOL which is the
problem but the the combination. The problematic ``feature interaction''
is with the package
(require 'ox-extra)
which in itself does not cause the damage, but if I add
(ox-extras-activate '(ignore-headlines))
then that kills the export. Note: there had been a time when that still
worked.
PS: I tested it on the very latest git-pull (org-mode-version 9.1.6) and
emacs-24.3.1 (but I had similar problems for emacs-25, only that I did
not veryfy that it's the same line with ``ox-extra'' that causes the
trouble, but it's more than plausible).
>>>>> "Martin" == Martin Steffen <mstef...@ifi.uio.no> writes:
Martin> Thanks a lot, it may be that my emacs suffers some
Martin> ``package-overload'', i.e., maybe it's due to an
Martin> interference with some other lisp stuff I load.
Martin> I just wanted to hear if it's known to be a current glitch
Martin> of the export-beamer thing, before I try to drill down
Martin> (especially since the priority is to make he slides compile
Martin> again rather than trouble-shooting..... [I just escape to
Martin> native-latex for multi-cols for now]
Martin> When done with the presentation, I will try to narrow it
Martin> down, cutting down also on the amount of slides (because
Martin> currently is a long and complex thing, which I cannot expect
Martin> others to trawls for abnormalitiees ;-)
Martin> Martin
>>>>> "Eric" == Eric S Fraga <esfli...@gmail.com> writes:
Eric> On Wednesday, 14 Feb 2018 at 10:39, Martin Steffen wrote:
>>> Hi,
>>>
>>> since recently I have a problem with exporting org-beamer-mode,
>>> the culprit presumably
Eric> [...]
>>> It seems that the BMCOL is the culprit, org-beamer still export
>>> a complicated and long document (as it did before), but probably
>>> a recent update made it stumble over that particular element.
Eric> Works fine for me with org up to date from git. Not sure what
Eric> to suggest. What happens with emacs -Q and loading in org
Eric> with no customizations?
Eric> -- Eric S Fraga via Emacs 27.0.50, Org
Eric> release_9.1.6-118-g134243
