unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: dalanicolai <dalanicolai@gmail.com>
To: Augusto Stoffel <arstoffel@gmail.com>
Cc: 49073@debbugs.gnu.org
Subject: bug#49073: 28.0.50; python-send-to-repl functions misbehave
Date: Sat, 28 Aug 2021 14:56:35 +0200	[thread overview]
Message-ID: <CACJP=3n9umrbSFhrB_hFL60ZPD5UhufXxQ7E3p2mTR=zi79=_A@mail.gmail.com> (raw)
In-Reply-To: <87o89hewgp.fsf@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1851 bytes --]

Thanks for the update! Unfortunately, I actually rarely code in python. It
was
just when I did for a moment, then I noticed this surprising behavior of the
'python-send-repl' functions (which turned out to be partly a Spacemacs
issue,
and partly fixed already through the extra flag for (not) sending the coding
cookie).

About the first 'bug' (showing the input), I was considering the ipython
shell
where one can refer to previous input by its number. But I agree that for
send-to-repl functions printing the input is not a very useful addition.

Looking at the description of the patch, the new behavior looks preferable
to me
as it is generally nice to see some values when sending statements/code
during
interactive development.


On Sat, 28 Aug 2021 at 11:43, Augusto Stoffel <arstoffel@gmail.com> wrote:

> 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?
>

[-- Attachment #2: Type: text/html, Size: 2481 bytes --]

  reply	other threads:[~2021-08-28 12:56 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 [this message]
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

  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='CACJP=3n9umrbSFhrB_hFL60ZPD5UhufXxQ7E3p2mTR=zi79=_A@mail.gmail.com' \
    --to=dalanicolai@gmail.com \
    --cc=49073@debbugs.gnu.org \
    --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 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).