emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Jack Kamm <jackkamm@gmail.com>
To: paul <paul_lodder@live.nl>, emacs-orgmode@gnu.org
Subject: Re: Bug report: remote file python src output gives FileNotFound (+ suggested fix)
Date: Sat, 28 Nov 2020 09:25:45 -0800	[thread overview]
Message-ID: <878sal4cme.fsf@gmail.com> (raw)
In-Reply-To: <AM0PR04MB526529A6010AC5F5E669B17883FC0@AM0PR04MB5265.eurprd04.prod.outlook.com>

Hi Paul,

I'm unable to reproduce the issue, and believe this issue has already
been fixed in the latest version of org-mode. See this patch [1]. Could
you please upgrade to Org 9.4 and test again?


[1] https://orgmode.org/list/87h7t16red.fsf@pc.i-did-not-set--mail-host-address--so-tickle-me/

paul <paul_lodder@live.nl> writes:

> When working remotely, a python SRC block with a session and :results set to output will return a FileNotFoundError.
> To reproduce this bug:
> 1. Open a .org file remotely
> 2. Insert the following
> #+BEGIN_SRC python :results output :session check
> print("a")
> 3. org-ctrl-c-ctrl-c in the code block
> I already figured out how to fix it:
> In ob-python.el.gz, the function org-babel-python-evaluate-session the let-variable tmp-src-file is made, which contains tramp-prefix when working remotely. But the tramp-prefix is still there here:
> (format org-babel-python--exec-tmpfile tmp-src-file)
> which causes the remotely executed command to still contain the prefix, and hence it cannot find it.
> To fix, the line above could be replaced with
> (format org-babel-python--exec-tmpfile (or (file-remote-p tmp-src-file 'localname) tmp-src-file))
> Hope this helps :) (and many many thanks for org-mode)

      reply	other threads:[~2020-11-28 17:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-23 17:26 Bug report: remote file python src output gives FileNotFound (+ suggested fix) paul
2020-11-28 17:25 ` Jack Kamm [this message]

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:

  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=878sal4cme.fsf@gmail.com \
    --to=jackkamm@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=paul_lodder@live.nl \


* 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


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).