From: Michael Albinus <michael.albinus@gmx.de>
To: Jim Porter <jporterbugs@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: [RFC] Explicity-remote commands in Eshell
Date: Mon, 06 Mar 2023 09:09:57 +0100 [thread overview]
Message-ID: <87fsaie1wq.fsf@gmx.de> (raw)
In-Reply-To: <0298a618-645c-a0c0-172b-9a0491462959@gmail.com> (Jim Porter's message of "Sun, 5 Mar 2023 18:35:43 -0800")
Jim Porter <jporterbugs@gmail.com> writes:
Hi Jim,
> Instead, I think we could make this easier:
>
> /ssh:user@somewhere:remote-command | local-command
>
> What do people think of the above syntax? It's a little bit different
> from the usual Tramp syntax, since the local part shouldn't be
> expanded using 'expand-file-name'; it's an executable somewhere on the
> remote $PATH. I can't think of any problems with supporting this
> syntax in Eshell[1], but I'm interested to hear others' thoughts.
I've skimmed over the patch, and there's nothing to object from Tramp
pov. I'm not a regular Eshell user, so I don't know how useful it will
be.
One remark: Why don't you allow remoteness everywhere? Sth like
--8<---------------cut here---------------start------------->8---
/ssh:user@somewhere:remote-command | /ssh:another-user@elsewhere:another-remote-command
--8<---------------cut here---------------end--------------->8---
This even with multiple pipes in a row. Mixed with local commands. And
using just the shorter version "command", which means a local or remote
command according to default-directory.
"/:command" is a nice trick, btw :-)
Best regards, Michael.
next prev parent reply other threads:[~2023-03-06 8:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-06 2:35 [RFC] Explicity-remote commands in Eshell Jim Porter
2023-03-06 8:09 ` Michael Albinus [this message]
2023-03-06 16:10 ` John Wiegley
2023-03-06 22:07 ` Jim Porter
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=87fsaie1wq.fsf@gmx.de \
--to=michael.albinus@gmx.de \
--cc=emacs-devel@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.