From: Daniel Clemente <n142857@gmail.com>
To: Org-mode ml <emacs-orgmode@gnu.org>
Subject: org-publish doesn't republish if you delete the .html files
Date: Sun, 10 May 2009 21:27:53 +0200 [thread overview]
Message-ID: <87ab5koj0m.fsf@gmail.com> (raw)
Hi; with org 6.26trans:
1. Publish a project you have configured with org-publish, concretely one that places the .html files locally beside the .org files.
2. While exporting, Org creates its own data in ~/.org-timestamps to cache things
3. Delete the new .html which have been created
4. Try to publish the same project again
5. Org-publish skips the file: Skipping unmodified file /home/dc/patata/index.org
I think that most people would expect the .html files to be created again.
Now users are expected to delete ~/.org-timestamps manually, which is not obvious.
Org could check for the .html files first, and if they are not present, always create them. Even if this check involves access to a remote server, I think it is worth it at access time, since it assures republishing (and otherwise, you get nothing).
Full event log:
,----
| Saving file /home/dc/patata/index.html...
| Wrote /home/dc/patata/index.html
| Exporting... done
| Saving file /home/dc/.org-timestamps/X24bafcf2c400ea6b5088e9afd58c590112bccd0c...
| Wrote /home/dc/.org-timestamps/X24bafcf2c400ea6b5088e9afd58c590112bccd0c
| Delete * [2 files] (y or n)
| 1 of 2 deletions
| 2 of 2 deletions
| 2 deletions done
| Select command:
| Skipping unmodified file /home/dc/patata/temas.org
| Skipping unmodified file /home/dc/patata/index.org
| Updating buffer list...done
| Commands: m, u, t, RET, g, k, S, D, Q; q to quit; h for help
| Mark saved where search started
| Mark set
`----
Thanks,
Daniel
next reply other threads:[~2009-05-10 19:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-10 19:27 Daniel Clemente [this message]
2009-05-12 8:30 ` org-publish doesn't republish if you delete the .html files Carsten Dominik
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=87ab5koj0m.fsf@gmail.com \
--to=n142857@gmail.com \
--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).