From: Augusto Stoffel <arstoffel@gmail.com>
To: 49073@debbugs.gnu.org
Cc: dalanicolai@gmail.com, ben@sturm.com.au
Subject: bug#49073: 28.0.50; python-send-to-repl functions misbehave
Date: Sat, 26 Feb 2022 17:24:11 +0100 [thread overview]
Message-ID: <87ilt1iok4.fsf@gmail.com> (raw)
In-Reply-To: <87h78mfs3p.fsf@sturm.com.au> (Ben Sturmfels via's message of "Sat, 26 Feb 2022 10:23:38 +1100")
On Sat, 26 Feb 2022 at 10:23, Ben Sturmfels via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org> wrote:
> On Thu, 17 Jun 2021, dalanicolai@gmail.com wrote:
>
>> This is a combined bug report for two unrelated but still somewhat
>> related bugs.
>>
>> - The first bug is that when using `python-send-to-repl` functions, the
>> input does not get printed in the REPL buffer.
This is by design. It's not too hard to copy the evaluated code to the
comint buffer, and I toyed a bit with it, eventually concluding that
it's not all that great of a feature.
As to the second point mentioned in the original message of this bug
(“for various setups, even the output does not get printed properly”), I
can't observe this, so a minimal recipe to reproduce would be
appreciated.
>
> This seems similar to bug#29592: 25.3; python does not print input or
> output in the inferior process.
>
> https://debbugs.gnu.org/cgi/bugreport.cgi?bug=29592
next prev parent reply other threads:[~2022-02-26 16:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-17 14:53 bug#49073: 28.0.50; python-send-to-repl functions misbehave dalanicolai
2021-08-28 9:43 ` Augusto Stoffel
2021-08-28 12:56 ` dalanicolai
2022-02-25 23:23 ` Ben Sturmfels via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-02-26 16:24 ` Augusto Stoffel [this message]
2022-02-27 23:07 ` Ben Sturmfels via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-02-28 9:10 ` 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=87ilt1iok4.fsf@gmail.com \
--to=arstoffel@gmail.com \
--cc=49073@debbugs.gnu.org \
--cc=ben@sturm.com.au \
--cc=dalanicolai@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 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).