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: Tue, 31 Dec 2024 17:50:44 +0000 [thread overview]
Message-ID: <87ed1nhhcb.fsf@localhost> (raw)
In-Reply-To: <m2zfkcx380.fsf@adamkovic.org>
Rudolf Adamkovič <rudolf@adamkovic.org> writes:
>>> (image-type "...-59b9176e65c9.svg") => svg
>>
>> Why do you think that the output file is always an image? It may not
>> be. It can be anything.
>
> I do not think that. I specifically addressed the non-image case: the
> file would retain the `out' extension.
Reasonable.
> But, we could be smart about other file types as well, if we use
> e.g. `file', like `dired-show-file-type' does.
Yes. Although there is another possible problem - current
implementation computes file _before_ the code block is evaluated. In
fact, this thread started from exactly this scenario - get the file name
before it appears on disk. And we have no clue about what will be inside
the file at that point.
--
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-31 17:49 UTC|newest]
Thread overview: 10+ 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
2024-12-27 13:56 ` Rudolf Adamkovič
2024-12-27 14:01 ` Ihor Radchenko
2024-12-30 21:36 ` Rudolf Adamkovič
2024-12-31 17:50 ` 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=87ed1nhhcb.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).