From: Lars Ingebrigtsen <larsi@gnus.org>
To: Augusto Stoffel <arstoffel@gmail.com>
Cc: "Barton, Mark" <Mark.Barton@disney.com>,
"50514@debbugs.gnu.org" <50514@debbugs.gnu.org>
Subject: bug#50514: 28.0.50; org inline call to python src block req C-g to break
Date: Wed, 15 Sep 2021 10:02:47 +0200 [thread overview]
Message-ID: <87k0jiuuzc.fsf@gnus.org> (raw)
In-Reply-To: <87k0jjq79k.fsf@gmail.com> (Augusto Stoffel's message of "Tue, 14 Sep 2021 21:36:23 +0200")
Augusto Stoffel <arstoffel@gmail.com> writes:
> Lars, can you install the attached patch, which solves the parts of this
> issue which originate in my recent changes? The patch also does the
> correct thing w.r.t. the text fields in the comint, something I was
> unaware of until yesterday.
Yup; pushed to Emacs 28 now.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2021-09-15 8:02 UTC|newest]
Thread overview: 28+ 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
2021-09-14 19:36 ` Augusto Stoffel
2021-09-15 8:02 ` Lars Ingebrigtsen [this message]
2022-08-25 15:12 ` Lars Ingebrigtsen
2022-08-26 13:30 ` Ihor Radchenko
2022-08-27 13:16 ` Lars Ingebrigtsen
2022-08-27 14:11 ` Ihor Radchenko
2022-08-27 18:56 ` Barton, Mark
2022-08-27 21:31 ` Mark Barton
2022-08-28 0:38 ` Barton, Mark
2022-08-28 1:30 ` Ihor Radchenko
2022-08-28 1:56 ` Barton, Mark
2022-08-28 2:55 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87k0jiuuzc.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=50514@debbugs.gnu.org \
--cc=Mark.Barton@disney.com \
--cc=arstoffel@gmail.com \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.