emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Rasmus <rasmus@gmx.us>
To: emacs-orgmode@gnu.org
Subject: Re: [PATCH] org-latex-compile timestamp checks
Date: Fri, 15 Jan 2016 13:13:46 +0100	[thread overview]
Message-ID: <87r3hjf3b9.fsf@gmx.us> (raw)
In-Reply-To: 57F8EBE2-E535-423A-828B-BCB3A2B9F797@gmail.com

Hi Anthony,

Thanks for raising this issue.

Anthony Cowley <acowley@gmail.com> writes:

> I’ve had some trouble with toggling latex fragment previews in a
> document on OS X. It would sometimes work, sometimes not, so I could
> just try a few times until it worked and get on with things. Looking
> into it more, the problem seems to be with the HFS+ filesystem’s
> second granularity on file timestamps. The Org code checks that the
> generated file is not older than a (current-time) obtained before
> starting latex compilation, but the truncated time of the generated
> file can indeed be older in the sub-second fields of the timestamp.
>
> The attached patch simply compares timestamps truncated to 1-second
> precision.

Isn't this a bug in Emacs file-attributes rather than Org?  If so, it
should be fixed in Emacs rather than worked around in Org IMO.

Maybe you could just check the log directly for failures rather than
checking the file attributes, if these are not reliable.

Also, what is the ‘take‘?  I don’t seem to have it in my Emacs...

Rasmus


-- 
Even a three-legged dog has three good legs to lose

next prev parent reply	other threads:[~2016-01-15 12:14 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-14 23:24 [PATCH] org-latex-compile timestamp checks Anthony Cowley
2016-01-15 12:13 ` Rasmus [this message]
2016-01-15 20:34   ` Anthony Cowley
2016-01-16 14:16     ` Nicolas Goaziou
2016-01-16 15:17     ` Rasmus
2016-01-16 23:21       ` Anthony Cowley
2016-01-21  9:54       ` Nicolas Goaziou
2016-01-21 15:53         ` Rasmus
2016-01-26 19:56           ` Anthony Cowley
2016-01-26 22:14             ` Rasmus
2016-01-26 22:20               ` Nicolas Goaziou
2016-01-26 22:25                 ` Rasmus
2016-01-28  9:05                   ` Nicolas Goaziou
2016-01-28 10:10                     ` Rasmus
2016-01-28 15:48                       ` Anthony Cowley

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=87r3hjf3b9.fsf@gmx.us \
    --to=rasmus@gmx.us \
    --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

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).