From mboxrd@z Thu Jan 1 00:00:00 1970 From: Matt Price Subject: Re: syntax for blocks that the exporter should not render? Date: Thu, 5 Sep 2013 10:40:30 -0400 Message-ID: References: <87eh93r35b.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:41634) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VHajZ-00079w-Nn for emacs-orgmode@gnu.org; Thu, 05 Sep 2013 10:40:35 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1VHajY-0001i4-Gb for emacs-orgmode@gnu.org; Thu, 05 Sep 2013 10:40:33 -0400 Received: from mail-ea0-x230.google.com ([2a00:1450:4013:c01::230]:47962) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VHajY-0001hh-9E for emacs-orgmode@gnu.org; Thu, 05 Sep 2013 10:40:32 -0400 Received: by mail-ea0-f176.google.com with SMTP id q16so951780ead.35 for ; Thu, 05 Sep 2013 07:40:30 -0700 (PDT) In-Reply-To: <87eh93r35b.fsf@gmail.com> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Nicolas Goaziou Cc: Org Mode , Carsten Dominik On Thu, Sep 5, 2013 at 6:09 AM, Nicolas Goaziou wrote: > Hello, > > Carsten Dominik writes: > >> On 3.9.2013, at 17:32, Matt Price 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 partially converted to the new >>> exporter. It works pretty well, but not perfectly. It has the neat >>> feature that, when I insert a link to a local image, it will upload >>> that image to wordpress and link to the uploaded file. TO keep track >>> of the location of those images, it writes lines like this to the org >>> file: >>> >>> #+/home/matt/Matt_headshots/Matt Price/IMG_9367_.jpg >>> http://2013.hackinghistory.ca/wp-content/uploads/2013/08/wpid-IMG_9367_2.jpg >>> >>> Recently I've noticed that these lines are actually being rendered by >>> the underlying html exporter before export. >> >> I don't think this is the right behavior, such lines should not be rendered. >> Suvayu is right, with a space after the # they are treated as commendt, but I think >> they should also be ignored with the plus. >> >> Nicolas, what is the reasoning behind rendering them? > > Because this isn't valid Org syntax, so it is treated as regular text > (i.e. a paragraph). Something similar happens for unbalanced blocks: > > * H > > #+begin_example > > * H2 > > In the example above, "#+begin_example" is treated as a paragraph. > > In both cases, silently ignoring them could cause more trouble that it > would solve. Nicolas, can you help clarify under what conditions it's appropriate to use the #+ syntax, and when to use '#' on its own? I think org2blog/wp uses #+ precisely in order to mark those comments as org-related. If you cna just tell me what the appropriate behaviour is I will submit a patch to puneeth. m > > > Regards, > > -- > Nicolas Goaziou