From: Michael Albinus <michael.albinus@gmx.de>
To: Eli Zaretskii <eliz@gnu.org>
Cc: andrewjmoreton@gmail.com, Mark.Barton@disney.com,
emacs-devel@gnu.org, schwab@linux-m68k.org,
monnier@iro.umontreal.ca, 49822@debbugs.gnu.org, larsi@gnus.org,
Augusto Stoffel <arstoffel@gmail.com>
Subject: Re: bug#49822: master e32c7d2: Change Python eval to send directly instead of using temporary files
Date: Wed, 08 Sep 2021 09:02:39 +0200 [thread overview]
Message-ID: <87sfyfbldc.fsf@gmx.de> (raw)
In-Reply-To: <83pmtknqlq.fsf@gnu.org> (Eli Zaretskii's message of "Tue, 07 Sep 2021 22:16:33 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
Hi,
>> I'm sitting at machine A but my inferior process is running on
>> machine B and the machines talk via SSH.
>
> You mean, you run a remote subprocess via Tramp?
>
>> There are several steps in the communication here: Emacs -> SSH client
>> -> SSH server -> inferior process. Each step has potential limitations.
>> If the SSH server talks to the inferior process via a PTY (I'm just
>> pondering, and I don't know if this is usual setup or not), then we
>> would have to take machine B's PTY restrictions into account, which
>> would defeat the purpose of knowing the exact characteristics of machine
>> A's PTYs.
>
> I don't see how B's PTY restrictions are relevant, but maybe Micheal
> will (assuming you are talking about remote subprocesses).
Tramp tries to handle such cases. But of course, a respective test
wouldn't hurt. It could be on the machine which has shown the
limitations, accessing it via "/ssh::".
Best regards, Michael.
next prev parent reply other threads:[~2021-09-08 7:02 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20210903122828.16890.65271@vcs0.savannah.gnu.org>
[not found] ` <20210903122829.EAAC220B71@vcs0.savannah.gnu.org>
2021-09-03 23:04 ` master e32c7d2: Change Python eval to send directly instead of using temporary files Stefan Monnier
2021-09-04 9:49 ` bug#49822: " Augusto Stoffel
2021-09-04 13:52 ` Stefan Monnier
2021-09-05 6:13 ` Barton, Mark
2021-09-05 7:46 ` bug#49822: " Augusto Stoffel
2021-09-05 8:10 ` Augusto Stoffel
2021-09-05 17:18 ` bug#49822: " Mark Barton
2021-09-05 17:33 ` Mark Barton
2021-09-05 17:46 ` Augusto Stoffel
2021-09-05 7:41 ` bug#49822: " Lars Ingebrigtsen
2021-09-05 16:36 ` Andreas Schwab
2021-09-05 18:40 ` Augusto Stoffel
2021-09-06 7:43 ` Michael Albinus
2021-09-06 8:40 ` Andreas Schwab
2021-09-06 11:23 ` Michael Albinus
2021-09-06 11:53 ` Andreas Schwab
2021-09-06 12:00 ` Michael Albinus
2021-09-06 16:08 ` Augusto Stoffel
[not found] ` <855f9eaf1b1d39bb9325d0a88e7f66c0ba0b45d0.camel@gmail.com>
2021-09-06 22:15 ` Andy Moreton
2021-09-07 7:18 ` Andreas Schwab
2021-09-07 17:37 ` Augusto Stoffel
2021-09-07 17:48 ` Eli Zaretskii
2021-09-07 17:59 ` Augusto Stoffel
2021-09-07 18:19 ` Eli Zaretskii
2021-09-07 18:13 ` Augusto Stoffel
2021-09-07 18:31 ` Eli Zaretskii
2021-09-07 19:00 ` Augusto Stoffel
2021-09-07 19:16 ` Eli Zaretskii
2021-09-08 7:02 ` Michael Albinus [this message]
2021-09-08 3:17 ` Barton, Mark
2021-09-08 5:09 ` Augusto Stoffel
2021-09-08 7:50 ` Lars Ingebrigtsen
2021-09-08 14:05 ` Augusto Stoffel
2021-09-09 13:48 ` 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=87sfyfbldc.fsf@gmx.de \
--to=michael.albinus@gmx.de \
--cc=49822@debbugs.gnu.org \
--cc=Mark.Barton@disney.com \
--cc=andrewjmoreton@gmail.com \
--cc=arstoffel@gmail.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=larsi@gnus.org \
--cc=monnier@iro.umontreal.ca \
--cc=schwab@linux-m68k.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).