emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Jack Kamm <jackkamm@gmail.com>
To: ian martins <ianxm@jhu.edu>, Philip Blagoveschensky <philip@crabman.me>
Cc: emacs-orgmode@gnu.org
Subject: Re: Bug: org-babel python with :results value sends function definition with a statement after a for loop to the shell incorrectly [9.3.6 (9.3.6-elpa @ /home/username/.emacs.d/elpa/org-9.3.6/)]
Date: Sat, 10 Oct 2020 16:57:05 -0700	[thread overview]
Message-ID: <87362lws6m.fsf@gmail.com> (raw)
In-Reply-To: <87blkbv7su.fsf@gmail.com>

Checking back in on this since Org 9.4 has been released. This issue
should be fixed now, and my tests corroborate this. If you're still
experiencing this problem after updating, please let me know.


Jack Kamm <jackkamm@gmail.com> writes:

>> I redid the test but loaded the lastest org-mode and there was no
>> error. This means you probably don't need to debug this. It has been
>> fixed in the latest version, but the fix hasn't been updated in the
>> elpa package yet.  you can either wait for the next release or pull
>> the latest code from the repo.
> Thanks for checking this Ian, I believe that this issue would have been
> fixed by this patch:
> https://orgmode.org/list/87pnfdo88v.fsf@gmail.com/
> But I've been too swamped to check.

  reply	other threads:[~2020-10-10 23:57 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-30 11:09 Bug: org-babel python with :results value sends function definition with a statement after a for loop to the shell incorrectly [9.3.6 (9.3.6-elpa @ /home/username/.emacs.d/elpa/org-9.3.6/)] Philip Blagoveschensky
2020-07-06 12:57 ` ian martins
2020-07-06 19:18   ` Philip Blagoveschensky
2020-07-07 11:31     ` ian martins
2020-07-19 15:33       ` Jack Kamm
2020-10-10 23:57         ` Jack Kamm [this message]
  -- strict thread matches above, loose matches on Subject: below --
2020-07-01 16:55 Philip Blagoveschensky
2020-07-01 18:48 ` Andreas Röhler
2020-07-01 19:05 ` ian martins

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=87362lws6m.fsf@gmail.com \
    --to=jackkamm@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=ianxm@jhu.edu \
    --cc=philip@crabman.me \


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