Re: [O] syntax for blocks that the exporter should not render?

2013-09-05 Thread Nicolas Goaziou
Hello, Carsten Dominik carsten.domi...@gmail.com writes: On 3.9.2013, at 17:32, Matt Price mopto...@gmail.com wrote: Hi, certain lines are not rendered by the org exporter, but are instead interpreted as instructions, e.g.: #+AUTHOR: Matt Price I'm using org2blog/wp, which is only

Re: [O] syntax for blocks that the exporter should not render?

2013-09-05 Thread Carsten Dominik
On Sep 5, 2013, at 12:09 PM, Nicolas Goaziou n.goaz...@gmail.com wrote: Hello, Carsten Dominik carsten.domi...@gmail.com writes: On 3.9.2013, at 17:32, Matt Price mopto...@gmail.com wrote: Hi, certain lines are not rendered by the org exporter, but are instead interpreted as

Re: [O] syntax for blocks that the exporter should not render?

2013-09-05 Thread Suvayu Ali
Hi Carsten, On Thu, Sep 05, 2013 at 01:27:57PM +0200, Carsten Dominik wrote: On Sep 5, 2013, at 12:09 PM, Nicolas Goaziou n.goaz...@gmail.com wrote: #+/home/matt/Matt_headshots/Matt Price/IMG_9367_.jpg http://2013.hackinghistory.ca/wp-content/uploads/2013/08/wpid-IMG_9367_2.jpg I

Re: [O] syntax for blocks that the exporter should not render?

2013-09-05 Thread Carsten Dominik
On Sep 5, 2013, at 1:43 PM, Suvayu Ali fatkasuvayu+li...@gmail.com wrote: Hi Carsten, On Thu, Sep 05, 2013 at 01:27:57PM +0200, Carsten Dominik wrote: On Sep 5, 2013, at 12:09 PM, Nicolas Goaziou n.goaz...@gmail.com wrote: #+/home/matt/Matt_headshots/Matt Price/IMG_9367_.jpg

Re: [O] syntax for blocks that the exporter should not render?

2013-09-05 Thread Jambunathan K
Matt Price mopto...@gmail.com writes: #+ was enough to get org to treat these lines as non-text Try adding a space character after #+.

Re: [O] syntax for blocks that the exporter should not render?

2013-09-05 Thread Carsten Dominik
On Sep 3, 2013, at 5:59 PM, Jambunathan K kjambunat...@gmail.com wrote: Matt Price mopto...@gmail.com writes: #+ was enough to get org to treat these lines as non-text Try adding a space character after #+. Nope, this will not work, see the rest of the thread. - Carsten

Re: [O] syntax for blocks that the exporter should not render?

2013-09-05 Thread Matt Price
On Thu, Sep 5, 2013 at 6:09 AM, Nicolas Goaziou n.goaz...@gmail.com wrote: Hello, Carsten Dominik carsten.domi...@gmail.com writes: On 3.9.2013, at 17:32, Matt Price mopto...@gmail.com wrote: Hi, certain lines are not rendered by the org exporter, but are instead interpreted as

Re: [O] syntax for blocks that the exporter should not render?

2013-09-05 Thread Matt Price
On Thu, Sep 5, 2013 at 7:57 AM, Carsten Dominik carsten.domi...@gmail.com wrote: On Sep 5, 2013, at 1:43 PM, Suvayu Ali fatkasuvayu+li...@gmail.com wrote: Hi Carsten, On Thu, Sep 05, 2013 at 01:27:57PM +0200, Carsten Dominik wrote: On Sep 5, 2013, at 12:09 PM, Nicolas Goaziou

Re: [O] syntax for blocks that the exporter should not render?

2013-09-04 Thread Suvayu Ali
On Tue, Sep 03, 2013 at 11:32:33AM -0400, Matt Price wrote: #+/home/matt/Matt_headshots/Matt Price/IMG_9367_.jpg http://2013.hackinghistory.ca/wp-content/uploads/2013/08/wpid-IMG_9367_2.jpg [...chomp...chomp...chomp...] ignore these lines. I thought that the leading #+ was enough to get

[O] syntax for blocks that the exporter should not render?

2013-09-03 Thread Matt Price
Hi, certain lines are not rendered by the org exporter, but are instead interpreted as instructions, e.g.: #+AUTHOR: Matt Price I'm using org2blog/wp, which is only partially converted to the new exporter. It works pretty well, but not perfectly. It has the neat feature that, when I insert a