From: Augusto Stoffel <arstoffel@gmail.com>
To: "Barton, Mark" <Mark.Barton@disney.com>
Cc: 50514@debbugs.gnu.org, Lars Ingebrigtsen <larsi@gnus.org>
Subject: bug#50514: 28.0.50; org inline call to python src block req C-g to break
Date: Sat, 11 Sep 2021 15:26:00 +0200 [thread overview]
Message-ID: <87wnnnjlav.fsf@gmail.com> (raw)
In-Reply-To: <24B9F777-2B69-45FD-ADBB-11E7A18F7A9A@disney.com> (Mark Barton's message of "Fri, 10 Sep 2021 23:06:55 +0000")
[-- Attachment #1: Type: text/plain, Size: 784 bytes --]
On Fri, 10 Sep 2021 at 23:06, "Barton, Mark" <Mark.Barton@disney.com> wrote:
> With the Test.org file below, if I C-c C-c on the call_file_date it will echo “Shell native completion is
> enabled” and Emacs will not respond until I hit C-g. If I immediately C-c C-c again, it will echo
> “Inline error: multiline result cannot be used” and Emacs responds normally to commands
> without C-g to break out. The problem is only when I use session in the property line. If I comment
> out the property line then it works. My original file uses dozens of python src blocks that require
> the session
Hi Mark,
does the patch below solve the problem for you?
If it does, then I know why it happens and I can suggest the Org people
a slightly more robust solution.
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: ob-python.diff --]
[-- Type: text/x-patch, Size: 577 bytes --]
diff --git a/lisp/org/ob-python.el b/lisp/org/ob-python.el
index 7911205d08..e3714964b7 100644
--- a/lisp/org/ob-python.el
+++ b/lisp/org/ob-python.el
@@ -352,7 +352,7 @@ org-babel-python--send-string
org-babel-python-eoe-indicator
string-buffer))
(accept-process-output (get-buffer-process (current-buffer))))
- (org-babel-chomp (substring string-buffer 0 (match-beginning 0))))))
+ (org-babel-chomp (substring string-buffer 1 (match-beginning 0))))))
(defun org-babel-python-evaluate-session
(session body &optional result-type result-params)
next prev parent reply other threads:[~2021-09-11 13:26 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-10 23:06 bug#50514: 28.0.50; org inline call to python src block req C-g to break Barton, Mark
2021-09-11 13:04 ` Lars Ingebrigtsen
2021-09-11 13:26 ` Augusto Stoffel [this message]
2021-09-12 6:22 ` Barton, Mark
2021-09-12 6:51 ` Augusto Stoffel
2021-09-12 8:27 ` Barton, Mark
2021-09-12 9:15 ` Augusto Stoffel
2021-09-12 17:00 ` Barton, Mark
2021-09-12 20:04 ` Barton, Mark
2021-09-14 6:42 ` Augusto Stoffel
2021-09-14 17:54 ` Barton, Mark
2021-09-14 18:29 ` Augusto Stoffel
2021-09-14 19:25 ` Barton, Mark
2021-09-14 19:31 ` Augusto Stoffel
2021-09-14 22:20 ` Barton, Mark
2021-09-15 6:28 ` Augusto Stoffel
2021-09-14 19:36 ` Augusto Stoffel
2021-09-15 8:02 ` Lars Ingebrigtsen
2022-08-25 15:12 ` Lars Ingebrigtsen
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.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87wnnnjlav.fsf@gmail.com \
--to=arstoffel@gmail.com \
--cc=50514@debbugs.gnu.org \
--cc=Mark.Barton@disney.com \
--cc=larsi@gnus.org \
/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.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).