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:51:40 -0400 Message-ID: References: <87eh93r35b.fsf@gmail.com> <0B394303-79FD-4990-B731-1F3F36FE02E0@gmail.com> <20130905114303.GB2392@kuru.dyndns-at-home.com> <3C681BE5-05DA-41A9-8277-7180063D2642@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]:44610) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VHauN-0003B6-Ah for emacs-orgmode@gnu.org; Thu, 05 Sep 2013 10:51:44 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1VHauM-000526-61 for emacs-orgmode@gnu.org; Thu, 05 Sep 2013 10:51:43 -0400 Received: from mail-ea0-x235.google.com ([2a00:1450:4013:c01::235]:64809) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VHauL-00051u-OC for emacs-orgmode@gnu.org; Thu, 05 Sep 2013 10:51:41 -0400 Received: by mail-ea0-f181.google.com with SMTP id d10so975877eaj.12 for ; Thu, 05 Sep 2013 07:51:40 -0700 (PDT) In-Reply-To: <3C681BE5-05DA-41A9-8277-7180063D2642@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: Carsten Dominik Cc: Org Mode On Thu, Sep 5, 2013 at 7:57 AM, Carsten Dominik wrote: > > On Sep 5, 2013, at 1:43 PM, Suvayu Ali 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 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 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: >>> >>> So in a way this is a "syntax error" message. :) >>> >>> OK, I get that point. Is that behaviour documented? >> >> I think it is more of a "I don't recognise this as special syntax; it >> must be text". In that case, I'm not sure what can be documented, one >> can have infinitely many text blurbs which look very similar to valid >> Org syntax but isn't. >> >> I have noticed quite a few posts on the list with this kind of >> misunderstanding. I think the confusion arises from thinking of special >> keywords like "#+options:", "#+attr_latex:", etc as comments. AFAIU, >> they are not. Lines starting with "#+" are possible keywords, whereas >> lines starting with "# " are comments. (sorry, posted my last msg before I saw the more recent contributions) So how would you suggest org2blog keep track of the relationship between local and uploaded files? Should it define a new keyword (perhaps" #+remote:" )? And if so how is that best done? Quickly looking at "Export Options (12.2) in the manual I don't see a built-in mechanism for defining backend-specific options. Something like "#+ATTR_BLOG: remote" might do the trick, but adding multiple links to such a line would be cumbersome, wouldn't it? Thanks again for your help clarifying this.