From: Greg Minshall <email@example.com>
To: Max Nikulin <firstname.lastname@example.org>
Subject: Re: tangle option to not write a file with same contents?
Date: Fri, 29 Oct 2021 20:58:23 +0300 [thread overview]
Message-ID: <email@example.com> (raw)
> > 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?
> Are you going to celebrate a decade of the feature request?
> I agree with you, make is wide spread and fast tool that is really
> convenient in simple cases.
hah -- i should have waited a few weeks!
> Some hash-based build systems are mentioned in that thread. Since that
> time more more similar tools have appeared, e.g. buck,
> reimplementations of DJB's redo https://cr.yp.to/redo.html
i think different people will settle on different build tools.
> It seems `compare-buffer-substrings` has more logic than just byte to
> byte comparison. Is it to handle alternatives for unicode character
> alternatives? For tangled buffer it should be size that is checked
you are right, it definitely makes sense to look first at size. (which
is what, e.g., rsync(1) does.) also, probably i needn't have mentioned
`compare-buffer-substrings` -- i was really just trying to suggest
"simple" (which maybe i anti-did?).
next prev parent reply other threads:[~2021-10-29 17:59 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-28 4:04 tangle option to not write a file with same contents? Greg Minshall
2021-10-29 16:21 ` Max Nikulin
2021-10-29 17:58 ` Greg Minshall [this message]
2021-10-30 15:13 ` Max Nikulin
2021-10-30 16:13 ` Greg Minshall
2022-05-07 8:05 ` Max Nikulin
2022-05-08 4:42 ` [PATCH] " Ihor Radchenko
2022-05-17 15:39 ` Max Nikulin
2022-05-30 3:14 ` Ihor Radchenko
2022-05-31 16:07 ` Max Nikulin
2022-06-03 7:04 ` Ihor Radchenko
2022-06-07 3:47 ` Tom Gillespie
2022-06-01 13:18 ` Greg Minshall
2022-09-12 17:36 ` Org version mismatch -- hooray! Greg Minshall
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:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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).