From: "Barton, Mark" <Mark.Barton@disney.com>
To: Augusto Stoffel <arstoffel@gmail.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: Sun, 12 Sep 2021 17:00:06 +0000 [thread overview]
Message-ID: <21C76818-63E5-4DC9-A60D-2BEF33813A18@disney.com> (raw)
In-Reply-To: <87pmteb1ef.fsf@gmail.com>
> On Sep 12, 2021, at 2:15 AM, Augusto Stoffel <arstoffel@gmail.com> wrote:
>
> What if you (setq comint-max-line-length 0)?
>
> If that solves the problem, you could try to find the biggest value that
> still works for you (256 or 512 would be probable candidates).
>
I tried setting it to zero and I got the same results where I need to use C-g the first time for that python session buffer and then subsequent evaluations of python using that already established session via the named session src block header work as expected. Just in case 0 meant no limit to the max length, I also tried setting it to 1 and got the same results.
I will see if I can learn how to trace the execution on my system to determine what is different between the first evaluation and then the working subsequent ones.
next prev parent reply other threads:[~2021-09-12 17:00 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 [this message]
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=21C76818-63E5-4DC9-A60D-2BEF33813A18@disney.com \
--to=mark.barton@disney.com \
--cc=50514@debbugs.gnu.org \
--cc=arstoffel@gmail.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).