Re: [Orgmode] Re: [babel] exports, caching, remote execution

2010-09-19 Thread Eric Schulte
Hi Tom, This turned out to be a fairly complicated issue. During export of a narrowed region the narrowed region will be coppied to a temporary buffer, when exporting from the buffer all buffer-wide, and headline-wide parameters which are not included in the region are ignored. This results in

Re: [Orgmode] Re: [babel] exports, caching, remote execution

2010-08-25 Thread Eric Schulte
Hi Tom, Thanks for pointing this out. It appears that during export the code block is evaluated in an altered version of the original buffer in which (for some reason) Babel is sometimes not able to find properties which are tucked away in either a #+Babel: line at the top of the file, or as

[Orgmode] Re: [babel] exports, caching, remote execution

2010-08-19 Thread Tom Short
Eric Schulte schulte.eric at gmail.com writes: Hi Austin, Austin Frank austin.frank at gmail.com writes: Hey all-- Two (hopefully quick) questions: 1) Does the exporter respect the :cache argument? When I evaluate a buffer, I can tell that cached blocks are not re-run, as

[Orgmode] Re: [babel] exports, caching, remote execution

2010-06-17 Thread Austin Frank
Eric-- Thanks for the reply. On Thu, Jun 17 2010, Eric Schulte wrote: I believe the exporter does respect caching, the following minimal example worked (i.e. was not re-run) for me on export to html. Could you provide an example that demonstrates the problem? Yes, I'll keep an eye on this