From: Brian Wightman <MidLifeXis@wightmanfam.org>
To: Holger Hoefling <hhoeflin@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Not overwriting unchanged source code files when tangling
Date: Fri, 18 Nov 2011 08:23:18 -0600 [thread overview]
Message-ID: <CALbR621AVfjwnjOWmvBDQvx5XjJO-uUsK+S1HQMn2iP15BEgwg@mail.gmail.com> (raw)
In-Reply-To: <CAFDswJtsPiuF3Ofb+QDvRWDtZSJ6zqvx2PfA2tXOC6PA=5qGHQ@mail.gmail.com>
On Fri, Nov 18, 2011 at 7:17 AM, Holger Hoefling <hhoeflin@gmail.com> wrote:
> I have a problem/request for org-mode and was looking for help. I am using
> org-mode to write source code files and tangle them out. I want to compile
> them using make. My problem now is that org-mode overwrites the old files
> every time I tangle them out, therefore also updating the time stamp - even
> if nothing has changed. Subsequently, when I run make, everything gets
> recompiled, not just the changed source code files as all time stamps have
> changed.
>
> Is there an option for org-mode to only overwrite source code files that get
> tangled out if they have truly changed?
I believe that to do this, you would need to have a dependency tree of
the nodes contributing to the output (perhaps already exists), and
recursively mark any node that refers to a node that changed as dirty.
You would also have to store last update times on each node so that
they could be compared to each output file, contributing to the
determination of needing a regeneration or not.
From a make standpoint, if you were to have each node in a file (I am
not recommending this), make already has the smarts to handle this.
It just becomes unwieldy to manage from an editing perspective.
Perhaps a way to deal with this would be to tangle to a different
directory, and then sync any changes into your compilation source
directory. If you would update the compilation directory only when
something differs from the tangle directory, then make could handle it
from that point on.
Brian
next prev parent reply other threads:[~2011-11-18 14:23 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-18 13:17 Not overwriting unchanged source code files when tangling Holger Hoefling
2011-11-18 14:23 ` Brian Wightman [this message]
2011-11-18 16:46 ` Tom Prince
2011-11-18 17:14 ` Brian Wightman
2011-11-18 14:27 ` Sebastien Vauban
2011-11-18 17:02 ` Carsten Dominik
2011-11-18 17:28 ` Brian Wightman
2011-11-18 19:42 ` Eric Schulte
2011-11-18 20:10 ` Achim Gratz
2011-11-18 20:24 ` Eric Schulte
2011-11-19 0:49 ` Holger Hoefling
2011-11-18 19:01 ` Holger Hoefling
2011-11-18 19:32 ` Nick Dokos
2011-11-19 0:51 ` Holger Hoefling
2011-11-19 4:00 ` Nick Dokos
2011-11-19 6:58 ` Holger Hoefling
2011-11-19 18:32 ` Holger Hoefling
2011-11-22 21:17 ` Allen S. Rout
2011-11-22 21:43 ` Nick Dokos
2011-11-19 18:06 ` cberry
2011-11-18 19:51 ` Achim Gratz
-- strict thread matches above, loose matches on Subject: below --
2011-11-19 15:31 Rustom Mody
2011-11-19 15:51 ` Rustom Mody
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CALbR621AVfjwnjOWmvBDQvx5XjJO-uUsK+S1HQMn2iP15BEgwg@mail.gmail.com \
--to=midlifexis@wightmanfam.org \
--cc=emacs-orgmode@gnu.org \
--cc=hhoeflin@gmail.com \
/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
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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.