Hi Carsten,
Carsten Dominik carsten.domi...@gmail.com writes:
I have not looked at you patch. But the orgx files are produced for
index and sitemap (I think) purposes. If a site has many files and the
index get recreated after republishing a single changed file, the orgx
files would be
On Jul 28, 2011, at 11:25 AM, Bastien wrote:
Hi Carsten,
Carsten Dominik carsten.domi...@gmail.com writes:
I have not looked at you patch. But the orgx files are produced for
index and sitemap (I think) purposes. If a site has many files and the
index get recreated after republishing
Hi Carsten,
Carsten Dominik carsten.domi...@gmail.com writes:
Yes. I think the include mechanism was so that people could write
their own wrapper file in their own style around the index.
I am CCing Stefan who was the driving force behind the index development,
he might have a comment.
I
Dear Bastian,
dear Carsten,
we have just re-organized parts of our software documentation (Org-mode
exlusively, of course) and I had a colophon section in mind with all Org
source files and a short description of our workflow (it might be ready in a
few days). Here is a link to the index page:
Hi Nathan,
Nathan Neff nathan.n...@gmail.com writes:
I've recently started using org-mode to export to html,
and I have empty .orgx files laying around in my directory.
Is there a way have the publish routine delete these .orgx files after
exporting,
or is there a way to specify that they
On 27.7.2011, at 14:37, Bastien wrote:
Hi Nathan,
Nathan Neff nathan.n...@gmail.com writes:
I've recently started using org-mode to export to html,
and I have empty .orgx files laying around in my directory.
Is there a way have the publish routine delete these .orgx files after
I've recently started using org-mode to export to html,
and I have empty .orgx files laying around in my directory.
Is there a way have the publish routine delete these .orgx files after
exporting,
or is there a way to specify that they should be created in ~/tmp or
something like that?
I can
