From: Augusto Stoffel <arstoffel@gmail.com>
To: dalanicolai@gmail.com
Cc: 49073@debbugs.gnu.org
Subject: bug#49073: 28.0.50; python-send-to-repl functions misbehave
Date: Sat, 28 Aug 2021 11:43:02 +0200 [thread overview]
Message-ID: <87o89hewgp.fsf@gmail.com> (raw)
In-Reply-To: <1aed416d4a4c84b688a893c1832a7ae076f10ffb.camel@gmail.com> (dalanicolai@gmail.com's message of "Thu, 17 Jun 2021 16:53:02 +0200")
On Thu, 17 Jun 2021 at 16:53, 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.
> - The second bug is that for various setups, even the output does not
> get printed properly.
>
See the patch in https://debbugs.gnu.org/cgi/bugreport.cgi?bug=49822#45
for a proposed solution to the second problem.
As to the first problem (not echoing the input): I think this would be
pretty hard to implement in a dumb terminal. You could try running the
Python shell in a terminal emulator (term or vterm) and write a macro to
paste regions of text into it. In any case, echoing the input also
seems to be a somewhat unconventional behavior. I don't think I would
want that.
PS: By 'python-send-to-repl' I assume you mean the 'python-shell-send-*'
family of commands, or do you refer to some external package?
next prev parent reply other threads:[~2021-08-28 9:43 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 [this message]
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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87o89hewgp.fsf@gmail.com \
--to=arstoffel@gmail.com \
--cc=49073@debbugs.gnu.org \
--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 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.