Re: exporting - filtering

From: Carsten Dominik <dominik@uva.nl>
To: Richard G Riley <rileyrgdev@googlemail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: exporting - filtering
Date: Wed, 23 Jul 2008 16:22:43 -0700	[thread overview]
Message-ID: <9FD3A668-8836-4834-B33E-4B807749BDD3@uva.nl> (raw)
In-Reply-To: <setzei6c9a.fsf@richardriley.net>

Hi

I do like the idea of a tag for selecting the subtrees that should be  
exported.  I will not have time to implement this before september.   
However, if someone wants to try:  `org-export-preprocess-hook' runs  
in a temporary buffer containing the document to export.  You could  
use org-map-entry to iterate over the trees in that buffer and kill  
those that do not have the tag......

- Carsten

On Jul 21, 2008, at 4:36 PM, Richard G Riley wrote:

> Russell Adams <RLAdams@AdamsInfoServ.Com> writes:
>
>> On Tue, Jul 22, 2008 at 01:06:57AM +0200, Richard G Riley wrote:
>>>
>>> When publishing/exporting can I limit certain sections to only  
>>> exported
>>> if they are tagged for export? e.g I have a normal org mode  
>>> hierarchy
>>> for my web page but then import a task based org file and then  
>>> only have
>>> some of those published? If not I think it would be nice addition  
>>> some
>>> time in the future.
>>
>> That sounds like a neat idea. You can always open a portion of the
>> tree in another window ( C-c C-x b ) and then hit export, I do that
>> all the time.
>>
>> I do think it would be interesting if a property could modify whether
>> or not to include an item (or its children) in export.
>>
>> Ideas?
>
>
> The main reason of course is to filter out the dross from pages of  
> tasks
> and notes.
>
> Something like a property on #include which specifies the tag to  
> INCLUDE
> in the export.
>
> e.g
>
> #+import "~/orgfiles/tasks.org" includetag:export-web recursive:no
>
> or somesuch.
>
> Maybe simpler are properties on the top of a org file of the form
>
> #+export-tag: export-web
>
> Since #import currently does not check for a timestamp it tends not to
> get republished unless the parent file is changed. So a top property
> might be better so any "lists" imported from ones tasks is really a  
> link
> click away (normal org link).
>
> I dont know how practical these ideas are but maybe they can start the
> ball rolling or prompt someone to suggest an existing method? Having  
> to
> manually open a tree portion and exporting it isnt really practical  
> when using
> project publishing.
>
>
> _______________________________________________
> Emacs-orgmode mailing list
> Remember: use `Reply All' to send replies to the list.
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode