[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [O] Restrict include to some backend

From: Clément Pit--Claudel
Subject: Re: [O] Restrict include to some backend
Date: Wed, 14 Sep 2016 08:21:36 -0400
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0

On 2016-09-14 07:55, Kaushal Modi wrote:
> On Mon, Sep 12, 2016 at 11:14 PM Clément Pit--Claudel <address@hidden 
> <mailto:address@hidden>> wrote:
>     Sure thing :) Here it is:
> Thanks! This works great! I added it to `org-export-before-processing-hook'.

Glad to hear that :)

> I did not understand why you mentioned: "I call this before calling 
> `org-latex-export-to-latex'.".

Back when I wrote this I was starting out with Org-mode, I was in a hurry, and 
I didn't know about org-export-before-processing-hook :) So instead I had a 
larger ELisp script that opened the file, ran this filter, then called 
org-latex-export-to-latex :)

> I plan to add a "not" condition to this. That way, with below:
> #+BEGIN_ONLY tex
> foo
> #+END_ONLY tex  
> bar
> #+END_EXCEPT tex  
> foo will be exported only for tex, and for every other backend, bar will be 
> exported.

Looks good. Maybe using the same syntax for both would be good though; 
something like "BEGIN_ONLY tex" and "BEGIN_ONLY :not tex" maybe?

We could probably get rid of the "tex" part after the END_ONLY, and change 
"tex" to "latex" for consistency with BEGIN_EXPORT :)


Attachment: signature.asc
Description: OpenPGP digital signature

reply via email to

[Prev in Thread] Current Thread [Next in Thread]