emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Alex Bennée" <alex.bennee@linaro.org>
To: Peter Salazar <cycleofsong@gmail.com>
Cc: org-mode <emacs-orgmode@gnu.org>
Subject: Re: Change in ox export for #+DATE keywords
Date: Sat, 08 Aug 2015 08:20:20 +0100	[thread overview]
Message-ID: <87lhdmw8jv.fsf@linaro.org> (raw)
In-Reply-To: <CAE+_6TzLnN8SBv7NPFHDYZsMoPHQ3NSKuoA=xGTXr3KCBE_u-w@mail.gmail.com>


Peter Salazar <cycleofsong@gmail.com> writes:

> As I mentioned, I'm getting that same error, not just with #+DATE but also
> with #+TITLE, #+AUTHOR, etc. Any one of these is sufficient to break export
> for me.

Yeah further poking has shown they have all broken. I can't quite follow
the logic of the patch as to what the new parse is expecting.

>
> On Fri, Aug 7, 2015 at 3:59 PM, Alex Bennée <alex.bennee@linaro.org> wrote:
>
>> Hi,
>>
>> 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. I think this changed as of:
>>
>> ae9db17482a183e5613428c3abf1c691f86b4ac0
>>
>> I'm not quite sure what the new "parse" is expecting. If I change it to
>> a datestamp I see breakage on other lines like the title:
>>
>> apply: Wrong type argument: listp, #("My presentation title" 0 26 (:parent
>> (#0)))
>>
>> So what form am I meant to be using for these options and why the change?
>>
>> --
>> Alex Bennée
>>
>>

-- 
Alex Bennée

  reply	other threads:[~2015-08-08  7:20 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 [this message]
2015-08-08  7:27 ` Nicolas Goaziou
2015-08-08  8:15   ` Alex Bennée
2015-08-08  9:35     ` Nicolas Goaziou
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=87lhdmw8jv.fsf@linaro.org \
    --to=alex.bennee@linaro.org \
    --cc=cycleofsong@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).