Control where files are emitted during block eval

Control where files are emitted during block eval

[George Mauer]

[-- Attachment #1: Type: text/plain, Size: 539 bytes --]

I would like to create a playground.org file inside my node project where I
will put bits of code that I'm playing with during development.

The problem is that when I actually evaluate a source block it gets written
into a temporary location that I do not control - I therefore cannot
`require` my project's node modules as they will not be found.

Is there a way to control the location the temp file is written? Maybe -
assuming it uses `with-temp-file` - a way to control its directory and file
name generation algorithm via a header?

[-- Attachment #2: Type: text/html, Size: 654 bytes --]

Re: Control where files are emitted during block eval

[Bastien]

Hi George,

George Mauer <gmauer@gmail.com> writes:

> I would like to create a playground.org file inside my node project
> where I will put bits of code that I'm playing with during
> development.
>
> The problem is that when I actually evaluate a source block it gets
> written into a temporary location that I do not control - I therefore
> cannot `require` my project's node modules as they will not be found.
>
> Is there a way to control the location the temp file is written?
> Maybe - assuming it uses `with-temp-file` - a way to control its
> directory and file name generation algorithm via a header?

One problem is that *every* ob-*.el in Org uses with-temp-file for
executing source code.

Also, it seems to be a very peculiar use case, so I would not go
for a new org-with-temp-file macro allowing such control, but that
maybe something you want to explore?

-- 
 Bastien