From: Michael Albinus <michael.albinus@gmx.de>
To: Aidan Gauland <aidalgol@fastmail.net>
Cc: emacs-devel@gnu.org
Subject: Re: Remote process execution
Date: Thu, 24 Jun 2021 20:01:50 +0200 [thread overview]
Message-ID: <87lf6zqgz5.fsf@gmx.de> (raw)
In-Reply-To: <78bb834c-4338-6ee3-1df4-9f774a1410bc@fastmail.net> (Aidan Gauland's message of "Wed, 23 Jun 2021 10:29:03 +1200")
Aidan Gauland <aidalgol@fastmail.net> writes:
Hi Aidan,
> I am trying to modify a third-party package to work over TRAMP, and I
> am stuck on `call-process-region'. I seem to be able to use
> `process-file' as a drop-in replacement for `call-process', but there
> does not appear to be any substitute for `call-process-region'. I did
> find `tramp-call-process-region' (and `tramp-call-process'), but these
> functions seem to be redundant, since they just call the process on
> the local host, which is what the non-tramp versions of these
> functions do already.
Like call-process, call-process-region does not support remote
directories. As you say, there is process-file, which does this with the
same arguments as call-process.
tramp-call-process and tramp-call-process-region are internal
functions. Their docstrings say clearly, that they are based on
call-process and call-process-region, respectively.
> Can anyone offer advice on modifying code that uses
> `call-process-region' to handle remote-command-execution in TRAMP
> buffers?
What you are looking for is an implementation for
process-file-region. That does not exist (yet?), AFAIK.
> Regards,
> Aidan Gauland
Best regards, Michael.
next prev parent reply other threads:[~2021-06-24 18:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-22 22:29 Remote process execution Aidan Gauland
2021-06-24 18:01 ` Michael Albinus [this message]
2021-06-24 20:24 ` Tomas Hlavaty
2021-06-26 18:37 ` Philipp
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=87lf6zqgz5.fsf@gmx.de \
--to=michael.albinus@gmx.de \
--cc=aidalgol@fastmail.net \
--cc=emacs-devel@gnu.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).