[Top][All Lists]

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

Re: [Orgmode] deleting hidden parts of sparse trees

From: Dan Davison
Subject: Re: [Orgmode] deleting hidden parts of sparse trees
Date: Tue, 8 Jul 2008 20:04:58 +0100
User-agent: Mutt/1.5.18 (2008-05-17)

On Tue, Jul 08, 2008 at 10:28:04AM -0700, Carsten Dominik wrote:
> Hi Dan, this is very interesting.
> Maybe you would like to write a little document how you use Org for this 
> purpose, what your setup is, why you chose Org to do this etc and put it 

Yep, I'd be happy to. (It was somewhat pretentious of me to call my
personal collection of random photos of flowers a 'database', but
still happy to.)


> up on the web?  I'd happily link to it from the Org webpages - we need 
> more of these examples.
> - Carsten
> On Jul 8, 2008, at 10:20 AM, Dan Davison wrote:
>> On Mon, Jul 07, 2008 at 09:48:37AM -0700, Carsten Dominik wrote:
>>> On Jul 7, 2008, at 9:44 AM, Carsten Dominik wrote:
>> <...>
>>>> Do I need to mention that this will be a dangerous operation,  
>>>> deleting
>>>> lots of invisible text?  You might find out only ater it is too late
>>>> to recover.
>>> Even much more dangerous then I thought, the command shown above
>>> actually deletes anything covered by overlays, not only outline
>>> overlays.  Just one misplaced parenthesis......
>>> Here is the corrected version.
>>> (defun outline-delete-invisible ()
>>>  "Delete all text covered by overlays with `invisible' property
>>> `outline'."
>>>  (interactive)
>>>  (let ((ovls (overlays-in (point-min) (point-max))) o)
>>>    (while (setq o (pop ovls))
>>>      (and (eq (overlay-get o 'invisible) 'outline)
>>>        (delete-region (overlay-start o) (overlay-end o))))))
>> Excellent! Thanks for the lesson.
>> My motivation for the request is as follows. I have a 'master' org
>> file (a database of plant photos arranged in a taxonomic hierarchy),
>> and I want to publish it as html, together with html versions of
>> various sparse trees derived from that master file according to tag
>> matching criteria etc. One option would be to write my own publishing
>> function, that creates each sparse tree and calls org-export-visible
>> on it. But I'd be recoding a load of stuff that has already been
>> addressed by org-publish. However, with the new function, I can create
>> the org-files corresponding to the sparse trees, and then let
>> org-publish-org-to-html deal with the master and the derived org files
>> in one go, which is a much better solution IMO.
>> DAn
>> p.s. warning heeded: I copy to a temp buffer, create sparse tree
>> and delete invisible in there.

reply via email to

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