From: Eric Schulte <schulte.eric@gmail.com>
To: Achim Gratz <Stromeko@nexgo.de>
Cc: emacs-orgmode@gnu.org
Subject: Re: [Babel] [Bug] Cache
Date: Fri, 06 Dec 2013 19:29:02 -0700 [thread overview]
Message-ID: <87ob4t2xxz.fsf@gmail.com> (raw)
In-Reply-To: 87k3fhkb1c.fsf@Rainer.invalid
[-- Attachment #1: Type: text/plain, Size: 471 bytes --]
Achim Gratz <Stromeko@nexgo.de> writes:
> Eric Schulte writes:
>> In that thread we agreed that the expansion of no-web references
>> *should* be included in code blocks for hashing, but no-one has had the
>> time to implement this.
>
> I think we may have discussed this before, but if you make the hashes
> dependent on the possibly recursive noweb expansions
What is a recursive noweb expansion? I think of the following, which
will cause errors in any situation.
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: recursive.org --]
[-- Type: text/x-org, Size: 107 bytes --]
#+name: a
#+begin_src sh
echo "hi <<b>>"
#+end_src
#+name: b
#+begin_src sh
echo "hi <<a>>"
#+end_src
[-- Attachment #3: Type: text/plain, Size: 753 bytes --]
> this would require that all expansions be re-computed all the time or
> you would need to discern which of the expansions are "pure"
> (i.e. depend only on their arguments, functional-style), which have
> session semantics and which of the ones that have session semantics
> should possibly not be re-evaluated. I'm not sure that opening this
> can of worms is worth the trouble.
>
I still (and I think this was my issue last time) don't see how noweb
expansions are more complicated than :var arguments. That said I agree
that this is an edge case, and I certainly don't have time to make this
change (which you right could be complex) at the moment.
Best,
>
>
> Regards,
> Achim.
--
Eric Schulte
https://cs.unm.edu/~eschulte
PGP: 0x614CA05D
prev parent reply other threads:[~2013-12-07 2:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-21 11:13 [Babel] [Bug] Cache Sebastien Vauban
2013-11-22 15:03 ` Eric Schulte
2013-12-02 15:46 ` Sebastien Vauban
2013-12-06 19:15 ` Eric Schulte
2013-12-06 19:57 ` Achim Gratz
2013-12-06 20:04 ` Sebastien Vauban
2013-12-07 2:29 ` Eric Schulte [this message]
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=87ob4t2xxz.fsf@gmail.com \
--to=schulte.eric@gmail.com \
--cc=Stromeko@nexgo.de \
--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
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).