emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Rudolf Adamkovič" <rudolf@adamkovic.org>
To: Ihor Radchenko <yantar92@posteo.net>
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: Fri, 27 Dec 2024 14:56:19 +0100	[thread overview]
Message-ID: <m2ttapz0u4.fsf@adamkovic.org> (raw)
In-Reply-To: <87a5ciyeq5.fsf@localhost>

Ihor Radchenko <yantar92@posteo.net> writes:

> [...] and :file-ext is not given?  But how will you know the desired
> extension?

Oh, I missed that.  My local hack assumes `.svg', but that is not enough
for the general use case.

Perhaps, we could save as `$BASENAME.out', detect the image format, and
then rename to `$BASENAME.svg', for example.  If the file is not an
image, we leave it as `.out'.

We can detect the image type with `image-type':

  (image-type "...-59b9176e65c9.svg") => svg

If the above is sufficient, the problem reduces to:

  how to compute the `$BASENAME'?

[`org-babel-tangle-comment-format-beg' does something similar.]

Rudy
-- 
"One can begin to reason only when a clear picture has been formed in
the imagination."
--- Walter Warwick Sawyer, Mathematician's Delight, 1943

Rudolf Adamkovič <rudolf@adamkovic.org> [he/him]
http://adamkovic.org


  reply	other threads:[~2024-12-27 13:57 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č [this message]
2024-12-27 14:01           ` Ihor Radchenko
2024-12-30 21:36             ` Rudolf Adamkovič
2024-12-31 17:50               ` Ihor Radchenko
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=m2ttapz0u4.fsf@adamkovic.org \
    --to=rudolf@adamkovic.org \
    --cc=aitenate@outlook.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=yantar92@posteo.net \
    /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).