From: Aidan Gauland <aidalgol@no8wireless.co.nz>
To: emacs-orgmode@gnu.org
Subject: Re: org-publish not publishing changed files
Date: Tue, 22 Mar 2011 02:00:27 +0000 (UTC) [thread overview]
Message-ID: <loom.20110322T025735-339@post.gmane.org> (raw)
In-Reply-To: 3366.1300498384@alphaville.dokosmarshall.org
Nick Dokos <nicholas.dokos <at> hp.com> writes:
> org uses timestamps to figure out which files need publishing
> (see section 13.4 of the Org manual) and they may have gotten
> curdled somehow. You can force publication by giving a second
> argument to org-publish (if you called it interactively, you
> could do that by giving it a prefix arg):
>
> (org-publish "aidalgolland" t)
>
> Or you can try getting rid of the timestamps (they are stored
> in the directory named in the variable org-publish-timestamp-directory
> (by default "~/.org-timestamps/") and publish again.
>
> If you can figure out *why* they got out of sync, that would be
> a bonus and worth a post here, particularly if you can identify
> a bug in the code.
How can I get the timestamps in a more human-readable format? I keep
having this problem (and no symlinks involved) and keep having to wipe
the timestamps directory (a royal nuisance).
--Aidan
next prev parent reply other threads:[~2011-03-22 2:00 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-02 9:08 Override export filename Aidan Gauland
2010-11-02 15:44 ` Giovanni Ridolfi
2010-11-02 18:04 ` Aidan Gauland
[not found] ` <aidalgol@no8wireless.co.nz>
2010-11-02 18:35 ` Nick Dokos
2010-11-05 0:57 ` Aidan Gauland
2011-03-19 1:33 ` org-publish not publishing changed files Nick Dokos
2011-03-19 2:19 ` Suvayu Ali
2011-03-20 11:30 ` David Maus
2011-03-20 11:47 ` Suvayu Ali
2011-03-22 2:00 ` Aidan Gauland [this message]
2011-03-22 6:18 ` Nick Dokos
2011-03-22 7:32 ` Aidan Gauland
2011-03-22 14:17 ` Nick Dokos
2011-04-01 19:56 ` Aidan Gauland
-- strict thread matches above, loose matches on Subject: below --
2011-03-19 1:16 Aidan Gauland
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=loom.20110322T025735-339@post.gmane.org \
--to=aidalgol@no8wireless.co.nz \
--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).