all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
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 15:04:52 +0300	[thread overview]
Message-ID: <83y1jo7z17.fsf@gnu.org> (raw)
In-Reply-To: <30707c49-8d0a-233d-0320-94a66f2e2e75@gmail.com> (message from Jim Porter on Sun, 9 Jul 2023 12:31:04 -0700)

> Date: Sun, 9 Jul 2023 12:31:04 -0700
> From: Jim Porter <jporterbugs@gmail.com>
> 
> 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". Similarly, you could run 
> "/:whoami" to run the local "whoami" even from a remote dir. (The latter 
> syntax is just piggybacking off of quoted file names, which otherwise 
> have no special meaning in Eshell.)
> 
> Prior to the main patch, I also added a bit of documentation about how 
> remote access works in Eshell. These are separate commits so that, if we 
> wanted, we could backport the first patch to the Emacs 29 branch.

Documentation improvements and fixes are always welcome on the release
branch, as long as they describe the behavior of the branch.

Thanks.





      parent reply	other threads:[~2023-07-10 12:04 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
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 [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=83y1jo7z17.fsf@gnu.org \
    --to=eliz@gnu.org \
    --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.