From mboxrd@z Thu Jan  1 00:00:00 1970
From: Suvayu Ali <fatkasuvayu+linux@gmail.com>
Subject: Re: More generic taskjuggler export proposal
Date: Sun, 14 Apr 2013 14:51:06 +0200
Message-ID: <20130414125106.GB11647@kuru.dyndns-at-home.com>
References: <515C901D.50500@web.de>
 <87obdjvqv2.fsf@sbs.ch>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Return-path: <emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([208.118.235.92]:45478)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <fatkasuvayu+linux@gmail.com>) id 1URMOo-0000h1-Be
	for emacs-orgmode@gnu.org; Sun, 14 Apr 2013 08:51:15 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <fatkasuvayu+linux@gmail.com>) id 1URMOl-0006GM-So
	for emacs-orgmode@gnu.org; Sun, 14 Apr 2013 08:51:14 -0400
Received: from mail-we0-x231.google.com ([2a00:1450:400c:c03::231]:57749)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <fatkasuvayu+linux@gmail.com>) id 1URMOl-0006Em-Ml
	for emacs-orgmode@gnu.org; Sun, 14 Apr 2013 08:51:11 -0400
Received: by mail-we0-f177.google.com with SMTP id o7so888700wea.8
	for <emacs-orgmode@gnu.org>; Sun, 14 Apr 2013 05:51:10 -0700 (PDT)
Content-Disposition: inline
In-Reply-To: <87obdjvqv2.fsf@sbs.ch>
List-Id: "General discussions about Org-mode." <emacs-orgmode.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/emacs-orgmode>
List-Post: <mailto:emacs-orgmode@gnu.org>
List-Help: <mailto:emacs-orgmode-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=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: emacs-orgmode@gnu.org

Hi Christian,

On Fri, Apr 12, 2013 at 03:08:17PM +0200, Christian Egli wrote:
> Buddy Butterfly <buddy.butterfly@web.de> writes:
> > Here I would suggest that one can place this data inbetween
> >
> >  #+BEGIN_TASKJUGGLER
> >  #+END_TASKJUGGLER
> 
> This is something I'd like to add support for. I just never got around
> to look at how this could be implemented. It has some implications as
> you could destroy your otherwise valid tjp file. But it might cover some
> of your use cases above. Do you know how this could be done in the new
> exporter?

I believe you can use the :export-block property when defining the
backend to specify blocks.

Quoting from the docstring of org-export-define-backend:

  :export-block

    String, or list of strings, representing block names that
    will not be parsed.  This is used to specify blocks that will
    contain raw code specific to the back-end.  These blocks
    still have to be handled by the relative `export-block' type
    translator.

Hope this helps,

-- 
Suvayu

Open source is the future. It sets us free.