From: Michael Albinus <michael.albinus@gmx.de>
To: Spencer Baugh <sbaugh@janestreet.com>
Cc: Dmitry Gutov <dmitry@gutov.dev>,
emacs-devel@gnu.org, johnw@gnu.org, spwhitton@spwhitton.name
Subject: Re: Native OS pipelines in eshell and Emacs
Date: Wed, 29 May 2024 09:53:20 +0200 [thread overview]
Message-ID: <875xuxgikv.fsf@gmx.de> (raw)
In-Reply-To: <CAO=BR8M3UFX_+guDB9qaPvW_D0Egca8k1a6GVn_45Sc6ms-Esw@mail.gmail.com> (Spencer Baugh's message of "Tue, 28 May 2024 21:43:54 -0400")
Spencer Baugh <sbaugh@janestreet.com> writes:
Hi Spencer,
> It would be doubly interesting if we manage to implement it so
> that Tramp would be able to connect two processes directly without
> round-tripping the i/o from the remote host to local and back to
> remote. That's a major source of latency in project-find-regexp
> on remote.
>
> 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.
Much appreciated! A while ago, on a boring rainy day, I thought about
adding "Implement remote make-pipe-process" to my TODO. I didn't because
I have no idea yet how to do.
Best regards, Michael.
prev parent reply other threads:[~2024-05-29 7:53 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
2024-05-29 10:31 ` Dmitry Gutov
2024-05-29 7:53 ` Michael Albinus [this message]
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=875xuxgikv.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 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.