[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: tangle option to not write a file with same contents?

From: Max Nikulin
Subject: Re: tangle option to not write a file with same contents?
Date: Sat, 7 May 2022 15:05:14 +0700
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.8.1

A couple additional notes for the case that someone will find this thread in future.

On 28/10/2021 11:04, Greg Minshall wrote:

i wonder if it would be reasonable to add an option such that, when
tangling, `org-babel-tangle` would not write a file with the
already-existing contents of the target file?

this would be helpful, e.g., for those of us who use make(1)-based work

It was not obvious for me earlier that it should be namely an *option*, not just change of behavior, since e.g. `org-babel-load-file' relies on timestamp comparison of the source .org file and the derived .el file. I am unsure concerning default value of such setting.

It was an issue with `org-file-newer-than-p' that reminded me about this thread.

P.S. Timestamp comparison is not always reliable to determine whether prerequisite has not been updated. Earlier python had timestamp of .py file saved in the header of compiled .pyc files, but at some moment they switched to hash.

PEP 552 – Deterministic pycs

reply via email to

[Prev in Thread] Current Thread [Next in Thread]