From: Jack Kamm <jackkamm@gmail.com>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: Nasser Alkmim <nasser.alkmim@gmail.com>, emacs-orgmode@gnu.org
Subject: Re: Async Python src block behavior with :dir header property
Date: Fri, 02 Feb 2024 17:20:25 -0800 [thread overview]
Message-ID: <87mssi8ht2.fsf@gmail.com> (raw)
In-Reply-To: <87msskmm47.fsf@localhost>
Ihor Radchenko <yantar92@posteo.net> writes:
> The patch generally looks reasonable, although I am slightly concerned
> about interaction between :dir and session we describe in the manual:
>
> When ‘dir’ is used with ‘session’, Org sets the starting directory
> for a new session. But Org does not alter the directory of an already
> existing session.
I agree it's a problem -- if there are multiple blocks with the same
session but different ":dir" arguments, then a ":file" result of the
second block will be relative to the wrong :dir.
This seems like a longstanding problem, and affects both async and
non-async session blocks.
Ideally, ":dir" should be set at session level rather than block
level. This could be done via PROPERTY if there is only one session in
the file or subtree, but there isn't a mechanism for this more
generally.
Perhaps the simplest solution is to add a check to org-lint, requiring
all blocks with the same session to have the same :dir.
next prev parent reply other threads:[~2024-02-03 1:21 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-31 7:29 Async Python src block behavior with :dir header property Nasser Alkmim
2024-01-31 11:23 ` Ihor Radchenko
2024-01-31 12:17 ` Nasser Alkmim
2024-01-31 12:47 ` Ihor Radchenko
2024-01-31 15:00 ` Nasser Alkmim
2024-01-31 16:21 ` Ihor Radchenko
2024-02-01 4:16 ` Jack Kamm
2024-02-01 8:40 ` Nasser Alkmim
2024-02-01 11:59 ` Ihor Radchenko
2024-02-03 1:20 ` Jack Kamm [this message]
2024-02-03 15:51 ` Ihor Radchenko
2024-02-04 1:26 ` Jack Kamm
2024-02-04 16:30 ` Ihor Radchenko
2024-02-05 0:59 ` Jack Kamm
2024-02-05 14:10 ` Ihor Radchenko
2024-02-06 6:56 ` Jack Kamm
2024-02-06 14:06 ` Ihor Radchenko
2024-02-08 3:08 ` Jack Kamm
2024-02-08 15:43 ` Ihor Radchenko
2024-02-08 17:46 ` Bruno Barbier
2024-02-10 18:14 ` Jack Kamm
2024-02-10 21:01 ` Ihor Radchenko
2024-02-13 9:43 ` Nasser Alkmim
2024-02-13 14:31 ` 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=87mssi8ht2.fsf@gmail.com \
--to=jackkamm@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=nasser.alkmim@gmail.com \
--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).