From mboxrd@z Thu Jan 1 00:00:00 1970 From: Aidan Gauland Subject: Re: org-publish not publishing changed files Date: Tue, 22 Mar 2011 02:00:27 +0000 (UTC) Message-ID: References: <20110319011622.GA11088@neko> <3366.1300498384@alphaville.dokosmarshall.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Return-path: Received: from [140.186.70.92] (port=36796 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Q1qtn-0002Is-Ov for emacs-orgmode@gnu.org; Mon, 21 Mar 2011 22:00:44 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Q1qtn-0004f3-1T for emacs-orgmode@gnu.org; Mon, 21 Mar 2011 22:00:43 -0400 Received: from lo.gmane.org ([80.91.229.12]:46863) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Q1qtm-0004ey-Qw for emacs-orgmode@gnu.org; Mon, 21 Mar 2011 22:00:43 -0400 Received: from list by lo.gmane.org with local (Exim 4.69) (envelope-from ) id 1Q1qtk-0001nI-Fo for emacs-orgmode@gnu.org; Tue, 22 Mar 2011 03:00:40 +0100 Received: from 39-134-148-118.nzcomms.co.nz ([39-134-148-118.nzcomms.co.nz]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 22 Mar 2011 03:00:40 +0100 Received: from aidalgol by 39-134-148-118.nzcomms.co.nz with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 22 Mar 2011 03:00:40 +0100 List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: emacs-orgmode@gnu.org Nick Dokos 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