| commit | 60d24c01ea5ade82c156f195cce4abc81027c76a | |
| author | David Maus <dmaus@ictsoc.de> | |
| Sun, 26 Jun 2011 18:02:42 +0000 (26 20:02 +0200) | ||
| committer | Bastien Guerry <bzg@altern.org> | |
| Sun, 3 Jul 2011 11:06:52 +0000 (3 13:06 +0200) | ||
| tree | 9b2e706a0ac374acdb153c95e595766cc0e5912a | treesnapshot (tar.gz zip) |
| parent | c4066dca8e6779abbf9fc3c4619f6e906ab1e68a | commitdiff |
Properly handle relative symlinks when publishing
* org-publish.el (org-publish-cache-ctime-of-src): Properly handle
relative symlinks.
At Thu, 07 Apr 2011 01:11:00 -0400,
Nick Dokos wrote:
>
> org-publish-cache-ctime-of-src tries (but does not always succeed) to
> deal with symlinks: file-symlink-p returns the target as a string, but
> if the target is relative to the symlink, that's not going to fly.
> e.g. if c is a symlink like this
>
> /a/b/c->../d/f
>
> then (file-symlink-p "/a/b/c") -> "../d/f"
> but if the current directory is any place other than /a/b, the target
> will not be found, the file attributes are going to be nil and
> the function will blow up.
* org-publish.el (org-publish-cache-ctime-of-src): Properly handle
relative symlinks.
At Thu, 07 Apr 2011 01:11:00 -0400,
Nick Dokos wrote:
>
> org-publish-cache-ctime-of-src tries (but does not always succeed) to
> deal with symlinks: file-symlink-p returns the target as a string, but
> if the target is relative to the symlink, that's not going to fly.
> e.g. if c is a symlink like this
>
> /a/b/c->../d/f
>
> then (file-symlink-p "/a/b/c") -> "../d/f"
> but if the current directory is any place other than /a/b, the target
> will not be found, the file attributes are going to be nil and
> the function will blow up.
| lisp/org-publish.el | diffblobblamehistory |