Re: [O] Change in ox export for #+DATE keywords

Alex Bennée writes: > Nicolas Goaziou writes: > >> Alex Bennée writes: >> >>> Nicolas Goaziou writes: 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 mayb

Re: [O] Change in ox export for #+DATE keywords

Nicolas Goaziou writes: > Alex Bennée writes: > >> Nicolas Goaziou writes: >> >>> Hello, >>> >>> Alex Bennée 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

Re: [O] Change in ox export for #+DATE keywords

Alex Bennée writes: > Nicolas Goaziou writes: > >> Hello, >> >> Alex Bennée 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. >> >> F

Re: [O] Change in ox export for #+DATE keywords

Nicolas Goaziou writes: > Hello, > > Alex Bennée 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. D

Re: [O] Change in ox export for #+DATE keywords

Hello, Alex Bennée 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? Rega

Re: [O] Change in ox export for #+DATE keywords

Peter Salazar 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 t

Re: [O] Change in ox export for #+DATE keywords

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. On Fri, Aug 7, 2015 at 3:59 PM, Alex Bennée wrote: > Hi, > > I've been using org-mode as a source for my presentations but exporting > br

[O] Change in ox export for #+DATE keywords

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 e