[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Orgmode] Re: Release 6.13
From: |
Sebastian Rose |
Subject: |
Re: [Orgmode] Re: Release 6.13 |
Date: |
Tue, 25 Nov 2008 09:32:41 +0100 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/23.0.60 (gnu/linux) |
Hi Carsten,
Carsten Dominik <address@hidden> 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<---
All the best,
Sebastian
=--- Footnotes: ---------------
[1] There are more `up-to-date issues' in the publishing (e.g. an
#+INCLUDE index.org). Yet, we shouldn't open each and every file
in a project just to be shure to have everything up to date (the
user could still use `touch' or write a publishing function that
does so). This is OK. Org-mode cannot _think_ for people,
publishing a complex WEB project.
[2] I never open my org-notes using the real path. I have link 'notes'
in my home directory pointing to ~/emacs/org/notes/.
[3] Org-mode can't guess - there is no `right' sequence.
--
Sebastian Rose, EMMA STIL - mediendesign, Niemeyerstr.6, 30449 Hannover
Tel.: +49 (0)511 - 36 58 472
Fax: +49 (0)1805 - 233633 - 11044
mobil: +49 (0)173 - 83 93 417
Email: s.rose emma-stil de, sebastian_rose gmx de
Http: www.emma-stil.de