From: Augusto Stoffel <arstoffel@gmail.com>
To: "Barton, Mark" <Mark.Barton@disney.com>
Cc: "50514@debbugs.gnu.org" <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: Wed, 15 Sep 2021 08:28:07 +0200 [thread overview]
Message-ID: <875yv2fj48.fsf@gmail.com> (raw)
In-Reply-To: <F54BDD3A-C63C-42EA-A07E-3A12EC3CA913@disney.com> (Mark Barton's message of "Tue, 14 Sep 2021 22:20:48 +0000")
On Tue, 14 Sep 2021 at 22:20, "Barton, Mark" <Mark.Barton@disney.com> wrote:
> On Sep 14, 2021, at 12:31 PM, Augusto Stoffel <arstoffel@gmail.com> wrote:
>
> Great. Then we'll fix the spurious line break problem, which is indeed
> on the Emacs side. But the other is due to ob-python, which may send
> code to the interpreter before the first prompt is printed (this can be
> checked through the variable 'python-shell--first-prompt-received').
>
> Since I don't use org-babel, I'm afraid I can't help with that part…
>
> So I found if I extend the sleep-for in ob-python from 10 ms to 90 ms, my initialization problem is
> “fixed”. I’m not sure why it would take longer than it did before the changes. Possibly an
> interaction with the antivirus software???
This was probably a problem all along, but went unnoticed until now
because 'python-shell-send-string' used to be simpler.
> I have not tried other values, but may be there is a better
> method for ob-python to determine it is safe than using a sleep-for.
One thing that might work is to block until the shell is ready with something like
(run-python)
(with-current-buffer *the-shell-buffer*
(while (not python-shell--first-prompt-received)
(accept-process-output (get-buffer-process (current-buffer)))))
next prev parent reply other threads:[~2021-09-15 6:28 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
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 [this message]
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=875yv2fj48.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).