Browse Source

Doc fixes for publishing to source directory

Carsten Dominik 15 years ago
parent
commit
eef99e9abd
2 changed files with 10 additions and 1 deletions
  1. 5 0
      doc/ChangeLog
  2. 5 1
      doc/org.texi

+ 5 - 0
doc/ChangeLog

@@ -1,3 +1,8 @@
+2009-08-04  Carsten Dominik  <carsten.dominik@gmail.com>
+
+	* org.texi (Publishing action): Improve documentation of file
+	names when publishing to the source directory.
+
 2009-08-03  Carsten Dominik  <carsten.dominik@gmail.com>
 2009-08-03  Carsten Dominik  <carsten.dominik@gmail.com>
 
 
 	* org.texi (Clean view): Document `org-indent-mode'.
 	* org.texi (Clean view): Document `org-indent-mode'.

+ 5 - 1
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
 and/or @code{:htmlized-source}.  This will produce @file{file.org} and
 @file{file.org.html} in the publishing
 @file{file.org.html} in the publishing
 directory@footnote{@file{file-source.org} and @file{file-source.org.html} if
 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
 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
 @code{org-publish-attachment}.  For non-Org files, you always need to
 specify the publishing function:
 specify the publishing function: