Re: Generating the filename from name and file-ext for blocks with side-effects

[Ihor Radchenko]

Aitenate <aitenate@outlook.com> writes:

>>> ~:var outFile=(alist-get :file (nth 2 (org-babel-get-src-block-info
>>> 't)))~
>> 
>> Seems right, but I do not understand why you would need such thing.
>> 
> The aim is to not need to define a filename for each image, to minimise 
> the boilerplate. Org has a mechanism for this, but it only works when 
> Org creates the file.
>
> Using a combination of noweb and file header arguments, with a property 
> drawer, I was able to have each code block only require a unique name 
> and the image code. That is except, because the image library creates 
> the file, I need to specify a var to give a filename. Hence, I poked 
> around until I found a way to use the computed filename.

Thanks for the explanation!
I do see how this can be useful.

> Based on your response, maybe I'm doing something unusual. In which 
> case, it's not surprising I couldn't find a more obvious way.

AFAIK, most people just specify the file names manually.
I suspect that it is mostly because the part of Org manual explaining
this is not easy to understand.

-- 
Ihor Radchenko // yantar92,
Org mode maintainer,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>