From mboxrd@z Thu Jan 1 00:00:00 1970 From: Carsten Dominik Subject: Re: exporting - filtering Date: Mon, 15 Sep 2008 10:22:48 +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 1Kf9MH-0003x6-QN for emacs-orgmode@gnu.org; Mon, 15 Sep 2008 04:22:57 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Kf9MC-0003wA-VZ for emacs-orgmode@gnu.org; Mon, 15 Sep 2008 04:22:57 -0400 Received: from [199.232.76.173] (port=42982 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Kf9MC-0003w7-Rb for emacs-orgmode@gnu.org; Mon, 15 Sep 2008 04:22:52 -0400 Received: from ey-out-1920.google.com ([74.125.78.144]:5401) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1Kf9MC-0003Yy-FC for emacs-orgmode@gnu.org; Mon, 15 Sep 2008 04:22:52 -0400 Received: by ey-out-1920.google.com with SMTP id 4so878921eyg.24 for ; Mon, 15 Sep 2008 01:22:51 -0700 (PDT) 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 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 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. - Carsten