emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: "Alex Bennée" <alex.bennee@linaro.org>
Cc: emacs-orgmode@gnu.org
Subject: Re: Change in ox export for #+DATE keywords
Date: Sat, 08 Aug 2015 11:35:17 +0200	[thread overview]
Message-ID: <87egjeazsa.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <87k2t6w60m.fsf@linaro.org> ("Alex \=\?utf-8\?Q\?Benn\=C3\=A9e\=22's\?\= message of "Sat, 08 Aug 2015 09:15:05 +0100")

Alex Bennée <alex.bennee@linaro.org> writes:

> Nicolas Goaziou <mail@nicolasgoaziou.fr> writes:
>
>> Hello,
>>
>> Alex Bennée <alex.bennee@linaro.org> writes:
>>
>>> I've been using org-mode as a source for my presentations but exporting
>>> broke today following an ELPA update. It seems the line:
>>>
>>> #+DATE: KVM Forum 2015
>>>
>>> Is no longer acceptable.
>>
>> FWIW, I export it without an error. Do you use a custom export
>> back-end?
>
> I'm using ox-reveal (for Reveal.js). I'm finding it hard to trigger an
> actual backtrace so maybe the problem is there.

I've had a cursory look at ox-reveal.el[fn:1]. There is a strange thing,
indeed. In `org-reveal-template', line 888, (plist-get info :author)
should be wrapped within (org-export-data ...).

However, it is not related to your error. Therefore, I suspect an
installation problem on your side.

Regards,

[fn:1] https://github.com/yjwen/org-reveal/blob/master/ox-reveal.el 

  reply	other threads:[~2015-08-08  9:33 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-07 19:59 Change in ox export for #+DATE keywords Alex Bennée
2015-08-08  3:51 ` Peter Salazar
2015-08-08  7:20   ` Alex Bennée
2015-08-08  7:27 ` Nicolas Goaziou
2015-08-08  8:15   ` Alex Bennée
2015-08-08  9:35     ` Nicolas Goaziou [this message]
2015-08-08 12:04       ` Alex Bennée
2015-08-08 12:11         ` Alex Bennée

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=87egjeazsa.fsf@nicolasgoaziou.fr \
    --to=mail@nicolasgoaziou.fr \
    --cc=alex.bennee@linaro.org \
    --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).