From mboxrd@z Thu Jan 1 00:00:00 1970 From: Carsten Dominik Subject: Re: exporting - filtering Date: Wed, 17 Sep 2008 13:49:19 +0200 Message-ID: References: Mime-Version: 1.0 (Apple Message framework v926) Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1KfvXS-00011k-Q6 for emacs-orgmode@gnu.org; Wed, 17 Sep 2008 07:49:42 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1KfvXQ-00010y-QQ for emacs-orgmode@gnu.org; Wed, 17 Sep 2008 07:49:42 -0400 Received: from [199.232.76.173] (port=41179 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1KfvXQ-00010q-K5 for emacs-orgmode@gnu.org; Wed, 17 Sep 2008 07:49:40 -0400 Received: from postduif.ic.uva.nl ([145.18.40.180]:46787) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1KfvXQ-0001iK-5l for emacs-orgmode@gnu.org; Wed, 17 Sep 2008 07:49:40 -0400 In-Reply-To: List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Richard G Riley Cc: org-mode On Sep 15, 2008, at 12:57 PM, Richard G Riley wrote: > Carsten Dominik writes: > >> Hi Richard, >> >> On Jul 22, 2008, at 1:06 AM, 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. >> >> I have finally been able to get to this message, and I am wondering >> what the logic should be. I think it is rather straight forward to >> mark subtrees that should be *excluded* from export. You can, in >> fact, already do so by starting a tree with the COMMENT keyword, >> which > > How does this affect agenda generation? > >> has exactly this purpose. Granted, a tag or property might be more >> appropriate - the fact that it is a keyword at the beginning of the >> entry has more historic than practical reasons. >> >> The logic for only selecting some trees for inclusion is harder, if >> you think about subtrees that are not top-level. If you mark a level >> 5 subtree for export, what should happen to the hierarchy above it? >> his can get quickly very complex, so I was wondering if you have been >> thinking about a reasonable logic for this. > > The way I personally see the html export is for publication of facts, > figures and ideas. And I tend to find very few of my entries in my org > files are of enough quality in terms of content and format to be > published. > > Assuming we mark/tag for export and to answer your final question: > > If you mark a level five level item for export then you simply export > all headers for its level the other levels before hand. > > Tagging for export is nice since you can have a section where the top > level is tagged for export and all items inherit it too. So two tags > would be ideal export and no_export (or something more ORGish since > you > might with to temporarily repress the publication of certain items > in an > exported block (all tagged as export thanks to the tags inheritance > mechanism). Using tags for selective export is now up in the git repo, and will be part of release 6.7 later this week. - Carsten