emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Brian Wightman <MidLifeXis@wightmanfam.org>
To: Tom Prince <tom.prince@ualberta.net>
Cc: Holger Hoefling <hhoeflin@gmail.com>, emacs-orgmode@gnu.org
Subject: Re: Not overwriting unchanged source code files when tangling
Date: Fri, 18 Nov 2011 11:14:29 -0600	[thread overview]
Message-ID: <CALbR623hMWzCQXShJeY0vP7UM-L30q9teHPBi0ZERNCBxPN7bg@mail.gmail.com> (raw)
In-Reply-To: <874ny19y4o.fsf@hermes.hocat.ca>

On Fri, Nov 18, 2011 at 10:46 AM, Tom Prince <tom.prince@ualberta.net> wrote:
> On Fri, 18 Nov 2011 08:23:18 -0600, Brian Wightman <MidLifeXis@wightmanfam.org> wrote:
>> 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.
>
> The tangle mechanism could probably handle this autoatically. i.e. not
> saving a file if the contents are identical.

If there is not a lot of extra memory / time overhead associated with
this, I could see this being a valid approach.  I would request that,
if implemented, this be placed behind an on/off switch.

The makefile could also handle this with something along these lines
(correct the leading space -> tab conversion as well as proper macro
definitions):

tangleflag: totangle.org
   $(TANGLECOMMAND) totangle.org
   $(TOUCH) tangleflag

syncflag: tangleflag
   $(SYNCCOMMAND) sourcedir tangledir
   $(TOUCH) syncflag

--Brian

  reply	other threads:[~2011-11-18 17:14 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
2011-11-18 16:46   ` Tom Prince
2011-11-18 17:14     ` Brian Wightman [this message]
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

  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=CALbR623hMWzCQXShJeY0vP7UM-L30q9teHPBi0ZERNCBxPN7bg@mail.gmail.com \
    --to=midlifexis@wightmanfam.org \
    --cc=emacs-orgmode@gnu.org \
    --cc=hhoeflin@gmail.com \
    --cc=tom.prince@ualberta.net \
    /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 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).