emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Aidan Gauland <aidalgol@no8wireless.co.nz>
To: emacs-orgmode@gnu.org
Subject: Re: org-publish not publishing changed files
Date: Fri, 1 Apr 2011 19:56:20 +0000 (UTC)	[thread overview]
Message-ID: <loom.20110401T214706-78@post.gmane.org> (raw)
In-Reply-To: 8771.1300803448@alphaville.dokosmarshall.org

Nick Dokos <nicholas.dokos <at> hp.com> writes:
> Aidan Gauland <aidalgol <at> no8wireless.co.nz> wrote:
> > Yes it does.  Sorry, I should have worded that differently.  I meant
> > that I have been repeatedly wiping ~/.org-timestamps/ in hopes that it
> > will not get screwed up again and think none of my files have changed,
> > and never re-publishes changed files (after an initial org-publish
> > operation).  I think I have run into a bug in org-mode and I really
> > want to track it down, so I thought the best place to start would be
> > to look at what the timestamps are (in a human-readable format).
> > 
> 
> OK - thanks. I started taking a look at the code, but I'm not getting
> anywhere fast, so the more eyes we can have on it the better.

Actually, we can forget about the timestamps.  I finally figured out
what circumstances under which this bug happens: I am trying to export
from a system where some of the symlinks in the project are broken.

Here's my setup: I sync my home directory on my laptop and desktop
computers using Unison.  In my project, I have symlinks to files in
~/images/, but since my laptop hard drive has less capacity than the
one in my desktop, I only keep ~/images/ on my desktop.  As a result
of this setup, some symlinks in my org-mode project are broken on my
laptop.  When I publish my project on my desktop, where no symlinks
are broken, org-publish behaves as expected; when I publish the same
project on my laptop, where some symlinks are broken, org-publish
appears to succeed, but publishes no changes.

I am really sorry for such a delayed response, but my university
semester started up again, which has been really hectic because of the
Feburary Christchurch earthquake.

Kind regards,
Aidan Gauland

  reply	other threads:[~2011-04-01 19:56 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
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 [this message]
  -- 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.20110401T214706-78@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).