emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Sebastian Rose <sebastian_rose@gmx.de>
To: Carsten Dominik <dominik@uva.nl>
Cc: emacs-orgmode Org-Mode <emacs-orgmode@gnu.org>
Subject: Re: Re: Release 6.13
Date: Tue, 25 Nov 2008 09:32:41 +0100	[thread overview]
Message-ID: <874p1wp5na.fsf@kassiopeya.MSHEIMNETZ> (raw)
In-Reply-To: <56464B2D-DDAD-4FCD-B895-A398880ABC12@uva.nl> (Carsten Dominik's message of "Tue, 25 Nov 2008 05:36:35 +0100")

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<---




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

  reply	other threads:[~2008-11-25  8:30 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 [this message]
2008-11-25  9:55           ` Carsten Dominik
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=874p1wp5na.fsf@kassiopeya.MSHEIMNETZ \
    --to=sebastian_rose@gmx.de \
    --cc=dominik@uva.nl \
    --cc=emacs-orgmode@gnu.org \
    /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).