emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Ferdinand Pieper <fer@pie.tf>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: emacs-orgmode@gnu.org
Subject: Re: Possible bugs in org-babel-temp-stable-file
Date: Sun, 23 Oct 2022 13:27:47 +0200	[thread overview]
Message-ID: <87h6zu7pak.fsf@pie.tf> (raw)
In-Reply-To: <87ilkbqjbs.fsf@localhost> (Ihor Radchenko's message of "Sun, 23 Oct 2022 04:01:43 +0000")

Ihor Radchenko <yantar92@posteo.net> writes:

> Fixed now.
> https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=69e3a4db3d0c54b4165761f56523da4962eff74c

Seems good, thanks.

>> It could also be nice to add an extra argument to force the use of
>> the local org-babel-temporary-stable-directory for remote files.
>
> I am not sure if it is a good idea.
> On remote files, default-directory often points to the remote making
> `shell-command' and similar run code on remote machine. It may not work
> well with local temporary directory.

I think you are right. Something like this could only be relevant for local files which execute code on remote locations (e.g. babel via the :dir argument) and require remote temp files instead of local ones. But that seems like too much of an edge case to support. If necessary a user could easily solve it with a small wrapper, that sets default-directory accordingly.



  reply	other threads:[~2022-10-24  4:25 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-16 12:17 [PATCH] Add light argument to org-babel-lob-get-info Ferdinand Pieper
2022-10-17  9:10 ` Ihor Radchenko
2022-10-18 16:15   ` Ferdinand Pieper
2022-10-19  7:01     ` Ihor Radchenko
2022-10-22 15:28       ` Possible bugs in org-babel-temp-stable-file (was: [PATCH] Add light argument to org-babel-lob-get-info) Ferdinand Pieper
2022-10-23  4:01         ` Ihor Radchenko
2022-10-23 11:27           ` Ferdinand Pieper [this message]
2022-10-24  4:12             ` Possible bugs in org-babel-temp-stable-file Ihor Radchenko
2022-10-24  7:49               ` Ferdinand Pieper
2022-10-24  8:24                 ` 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=87h6zu7pak.fsf@pie.tf \
    --to=fer@pie.tf \
    --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).