unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Michael Albinus <michael.albinus@gmx.de>
To: Dmitry Gutov <dmitry@gutov.dev>
Cc: Spencer Baugh <sbaugh@janestreet.com>,
	 emacs-devel@gnu.org, johnw@gnu.org,  spwhitton@spwhitton.name
Subject: Re: Native OS pipelines in eshell and Emacs
Date: Wed, 29 May 2024 10:01:04 +0200	[thread overview]
Message-ID: <871q5lgi7z.fsf@gmx.de> (raw)
In-Reply-To: <a5a7363c-811d-4a66-b035-f281ba0b8fdc@gutov.dev> (Dmitry Gutov's message of "Wed, 29 May 2024 05:08:19 +0300")

Dmitry Gutov <dmitry@gutov.dev> writes:

Hi Dmitry,

>> Unfortunately this is almost impossibly hard.  But, I actually have
>> worked extensively on doing this specific impossible thing (remote
>> process APIs that are powerful enough to do this) so I will eventually
>> try to implement them for Emacs and TRAMP.  It would allow full
>> make-process support in TRAMP as well as a make-pipe-process which
>> represents a pipe existing on a remote system.
>
> On the remote, it would be fine if the pipe is not direct between such
> processes, but goes through the shell, or maybe some other processes as
> well (maybe a temp file?). That would still be faster than doing the
> round-trip.

If both processes are on different remote hosts, you have the problem
how to transfer the tmpfile from one host to the other. You have no
knowledge how these two hosts see each other.

A special case is if both hosts are accessed via Tramp's scp method, and
you can use the tramp-use-scp-direct-remote-copying user option.
See (info "(tramp) Ssh setup")

Best regards, Michael.



  reply	other threads:[~2024-05-29  8:01 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-28 14:42 Native OS pipelines in eshell and Emacs Spencer Baugh
2024-05-28 16:33 ` Jim Porter
2024-05-28 18:38   ` Spencer Baugh
2024-05-28 19:56     ` Jim Porter
2024-05-29  1:21 ` Dmitry Gutov
2024-05-29  1:43   ` Spencer Baugh
2024-05-29  2:08     ` Dmitry Gutov
2024-05-29  8:01       ` Michael Albinus [this message]
2024-05-29 10:31         ` Dmitry Gutov
2024-05-29  7:53     ` Michael Albinus

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=871q5lgi7z.fsf@gmx.de \
    --to=michael.albinus@gmx.de \
    --cc=dmitry@gutov.dev \
    --cc=emacs-devel@gnu.org \
    --cc=johnw@gnu.org \
    --cc=sbaugh@janestreet.com \
    --cc=spwhitton@spwhitton.name \
    /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).