From mboxrd@z Thu Jan 1 00:00:00 1970 From: Carsten Dominik Subject: Re: Re: Release 6.13 Date: Tue, 25 Nov 2008 10:55:06 +0100 Message-ID: <1157BD73-531A-4A39-8ED6-2EA66427927D@uva.nl> References: <87od06gv1u.fsf@gollum.intra.norang.ca> <8763mch9pu.fsf@kassiopeya.MSHEIMNETZ> <871vx0h8xz.fsf@kassiopeya.MSHEIMNETZ> <56464B2D-DDAD-4FCD-B895-A398880ABC12@uva.nl> <874p1wp5na.fsf@kassiopeya.MSHEIMNETZ> Mime-Version: 1.0 (Apple Message framework v929.2) 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 1L4udW-00077N-3w for emacs-orgmode@gnu.org; Tue, 25 Nov 2008 04:55:14 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1L4udU-00075E-Cj for emacs-orgmode@gnu.org; Tue, 25 Nov 2008 04:55:13 -0500 Received: from [199.232.76.173] (port=55193 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1L4udU-000753-6R for emacs-orgmode@gnu.org; Tue, 25 Nov 2008 04:55:12 -0500 Received: from ug-out-1314.google.com ([66.249.92.169]:28338) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1L4udT-0000WY-Nv for emacs-orgmode@gnu.org; Tue, 25 Nov 2008 04:55:12 -0500 Received: by ug-out-1314.google.com with SMTP id 36so1129635uga.17 for ; Tue, 25 Nov 2008 01:55:10 -0800 (PST) In-Reply-To: <874p1wp5na.fsf@kassiopeya.MSHEIMNETZ> 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: Sebastian Rose Cc: emacs-orgmode Org-Mode On Nov 25, 2008, at 9:32 AM, Sebastian Rose wrote: > Hi Carsten, > > > Carsten Dominik writes: >> Hi Sebastian, >> >> it seems to me thatt his patch depends on the projects in >> org-publish-projects-alist to be defined in a certain order, >> with the components first, and the big "parent" projects later. >> So maybe you need to iterate the dolist loop until it stabilizes. > >> Also, I guess a "component" could be part of several "parents"? >> Hmm, maybe not a likely setup. OK, les not worry about this issue. > > org-publish-get-project-from-filename always returned the first > matching > project. It still does so, but if one or more composite projects are > found, of which the files project is a component, the last composite > is > returned instead. In that, it still does what it always did. > > Yes, this depends on a certain kind of setup. But it's the setup from > the example in the docs, so I feel people will most likely use > that. Since one has to provide the `:publishing-function', the only > way to > publish static content (e.g. images) AND dynamic content is to > provide a > composite project. > > > The issue came up with org-exp-blocks.el [1]. ditaa blocks contain > text, > that is changed, just to update an image. I never ran into this, > simply > because I never used `C-c C-e P' [2]. > > > The publishing of a composite project depends on the sequence of it's > `:components' anyway [3]. > > Maybe this should be mentioned in the docs at the end of section > 13.2.2? > > => --->8----------------------------->8----------------------------- > >8--- > 'The `:components' in "website" are guaranteed to be published in the > sequence provided.' > <= > ---8<-----------------------------8<-----------------------------8<--- I think it fits better at the end of 13.1.1, where it is located now. Thanks. - Carsten