From: Carsten Dominik <dominik@science.uva.nl>
To: Sebastian Rose <sebastian_rose@gmx.de>
Cc: emacs-orgmode Org-Mode <emacs-orgmode@gnu.org>
Subject: Re: Re: Release 6.13
Date: Tue, 25 Nov 2008 10:55:06 +0100 [thread overview]
Message-ID: <1157BD73-531A-4A39-8ED6-2EA66427927D@uva.nl> (raw)
In-Reply-To: <874p1wp5na.fsf@kassiopeya.MSHEIMNETZ>
On Nov 25, 2008, at 9:32 AM, Sebastian Rose wrote:
> Hi Carsten,
>
>
> Carsten Dominik <dominik@uva.nl> 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
next prev parent reply other threads:[~2008-11-25 9:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-23 7:20 Release 6.13 Carsten Dominik
2008-11-23 18:24 ` Bernt Hansen
2008-11-24 2:12 ` Sebastian Rose
2008-11-24 21:23 ` Bernt Hansen
2008-11-25 1:31 ` Sebastian Rose
2008-11-25 1:48 ` Sebastian Rose
2008-11-25 4:36 ` Carsten Dominik
2008-11-25 8:32 ` Sebastian Rose
2008-11-25 9:55 ` Carsten Dominik [this message]
2008-11-25 9:56 ` Carsten Dominik
2008-11-25 11:58 ` Bernt Hansen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1157BD73-531A-4A39-8ED6-2EA66427927D@uva.nl \
--to=dominik@science.uva.nl \
--cc=emacs-orgmode@gnu.org \
--cc=sebastian_rose@gmx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).