From: Michael Albinus <michael.albinus@gmx.de>
To: Jim Porter <jporterbugs@gmail.com>
Cc: 64546@debbugs.gnu.org
Subject: bug#64546: 30.0.50; [PATCH] Add support for explicitly-remote commands in Eshell
Date: Mon, 10 Jul 2023 09:24:54 +0200 [thread overview]
Message-ID: <87bkgk2pq1.fsf@gmx.de> (raw)
In-Reply-To: <30707c49-8d0a-233d-0320-94a66f2e2e75@gmail.com> (Jim Porter's message of "Sun, 9 Jul 2023 12:31:04 -0700")
Jim Porter <jporterbugs@gmail.com> writes:
Hi Jim,
> This patch adds the ability to run a command in Eshell from any host,
> no matter your current directory. For example, you could run
> "/ssh:user@remote:whoami" from a local dir, which would run "whoami"
> over the SSH connection for "user@remote".
Looks nice. But what if I want to run a command on another remote host
with an absolute path? Would "/ssh:user@remote:/usr/bin/whoami" also be
possible?
> Similarly, you could run "/:whoami" to run the local "whoami" even
> from a remote dir.
The same question. What about calling "/:/usr/bin/whoami"?
> +By default, commands like @code{ssh} and @code{sudo} use the external
> +programs by those names, so if you ran @samp{ssh
> +@var{user}@@@var{remote}}, you would end up in the default shell
> +program for @var{user} on @var{remote}, @emph{not} in Eshell. If you
> +prefer to use commands like @code{ssh} but remain in Eshell
> +afterwards, you can enable the optional Tramp extensions (@pxref{Tramp
> +extensions}).
This surprises me. I thought, that only "doas", "su" and "sudo" are built-ins.
Best regards, Michael.
next prev parent reply other threads:[~2023-07-10 7:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-09 19:31 bug#64546: 30.0.50; [PATCH] Add support for explicitly-remote commands in Eshell Jim Porter
2023-07-10 7:24 ` Michael Albinus [this message]
2023-07-10 16:53 ` Jim Porter
2023-07-10 17:38 ` Michael Albinus
2023-07-10 17:54 ` Jim Porter
2023-07-10 19:03 ` Michael Albinus
2023-07-10 19:31 ` Jim Porter
2023-07-10 12:04 ` Eli Zaretskii
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=87bkgk2pq1.fsf@gmx.de \
--to=michael.albinus@gmx.de \
--cc=64546@debbugs.gnu.org \
--cc=jporterbugs@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 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.