From: Ihor Radchenko <yantar92@posteo.net>
To: "Rudolf Adamkovič" <rudolf@adamkovic.org>
Cc: Aitenate <aitenate@outlook.com>, emacs-orgmode@gnu.org
Subject: Re: Generating the filename from name and file-ext for blocks with side-effects
Date: Thu, 26 Dec 2024 09:29:22 +0000 [thread overview]
Message-ID: <87a5ciyeq5.fsf@localhost> (raw)
In-Reply-To: <m2jzbmluiw.fsf@adamkovic.org>
Rudolf Adamkovič <rudolf@adamkovic.org> writes:
>> The aim is to not need to define a filename for each image, to minimise
>> the boilerplate.
>
> +1 This should be built into Org and enabled by default.
>
> I currently generate image names with a custom snippet, but it gets
> trying and should not be necessary in the first place.
Do you want to create a patch providing this functionality?
> Instead, Org should generate a unique file name automatically, similar
> to how tangle ':comments' work, and use that as the default value for
> the ':file` argument, getting rid of the dreaded error message
>
> org-babel-execute:LANG: You need to specify a :file parameter
Do you want to extend `org-babel-generate-file-param' to return
something even when src block is not named and :file-ext is not given?
But how will you know the desired extension?
--
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>
next prev parent reply other threads:[~2024-12-26 9:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-23 21:58 Generating the filename from name and file-ext for blocks with side-effects Aitenate
2024-12-25 15:30 ` Ihor Radchenko
2024-12-25 19:03 ` Aitenate
2024-12-26 8:26 ` Rudolf Adamkovič
2024-12-26 9:29 ` Ihor Radchenko [this message]
2024-12-26 9:08 ` Ihor Radchenko
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=87a5ciyeq5.fsf@localhost \
--to=yantar92@posteo.net \
--cc=aitenate@outlook.com \
--cc=emacs-orgmode@gnu.org \
--cc=rudolf@adamkovic.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).