[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[O] bug#34891: 25.2; ORG-PUBLISH-FIND-DATE should not use Creation/Publi
[O] bug#34891: 25.2; ORG-PUBLISH-FIND-DATE should not use Creation/Publish date (#+DATE:) in file as a modification timestamp.
Sun, 05 May 2019 11:29:46 +0200
Gnus/5.13 (Gnus v5.13) Emacs/26.2 (gnu/linux)
David Trudgett <address@hidden> writes:
> In an Org mode file, add a #+DATE tag as follows:
> #+DATE: First published: 1 February 2014
> Then initiate a project publish, which publishes (by default) only
> changed files. A date such as the above will not be parsed, so
> ox-publish.el will always publish it, even though it has not changed.
> Using instead a parsable date format (such as 2014-02-01), this date will be
> recognised, and will result in the file never being published, because
> it is treating the date as a modification date instead of a creation date.
> Desired Behaviour:
> ox-publish.el, in function ORG-PUBLISH-FIND-DATE should not be using
> this date to detect modifications, as it will never change, and no
> modifications will be detected for publishing.
I don't understand how you come to this conclusion.
The function responsible for deciding if a file should be published is
`org-publish-cache-file-needs-publishing'. It doesn't call
`org-publish-find-date', but `org-publish-cache-ctime-of-src'. The
latter only uses `file-attribute-modification-time'.
IOW, I think the file is published because you modified since last
|[Prev in Thread]
||[Next in Thread]|
- [O] bug#34891: 25.2; ORG-PUBLISH-FIND-DATE should not use Creation/Publish date (#+DATE:) in file as a modification timestamp.,
Nicolas Goaziou <=