From eef99e9abd085d2b08cb5d588ca1f69b7ef07a56 Mon Sep 17 00:00:00 2001 From: Carsten Dominik Date: Tue, 4 Aug 2009 16:09:03 +0200 Subject: [PATCH] Doc fixes for publishing to source directory --- doc/ChangeLog | 5 +++++ doc/org.texi | 6 +++++- 2 files changed, 10 insertions(+), 1 deletion(-) diff --git a/doc/ChangeLog b/doc/ChangeLog index 3ebda999b..36a969319 100644 --- a/doc/ChangeLog +++ b/doc/ChangeLog @@ -1,3 +1,8 @@ +2009-08-04 Carsten Dominik + + * org.texi (Publishing action): Improve documentation of file + names when publishing to the source directory. + 2009-08-03 Carsten Dominik * org.texi (Clean view): Document `org-indent-mode'. diff --git a/doc/org.texi b/doc/org.texi index 0e5fd96ea..7c5c8c547 100644 --- a/doc/org.texi +++ b/doc/org.texi @@ -9562,7 +9562,11 @@ but with @i{archived}, @i{commented}, and @i{tag-excluded} trees removed, use and/or @code{:htmlized-source}. This will produce @file{file.org} and @file{file.org.html} in the publishing directory@footnote{@file{file-source.org} and @file{file-source.org.html} if -source and publishing directories are equal.}. Other files like images only +source and publishing directories are equal. Note that with this kind of +setup, you need to add @code{:exclude "-source\\.org"} to the project +definition in @code{org-publish-project-alist} to avoid that the published +source files will be considered as new org files the next time the project is +published.}. Other files like images only need to be copied to the publishing destination, for this you may use @code{org-publish-attachment}. For non-Org files, you always need to specify the publishing function: -- 2.11.4.GIT