From: Jim Porter <jporterbugs@gmail.com>
To: Sean Whitton <spwhitton@spwhitton.name>
Cc: 70792@debbugs.gnu.org
Subject: bug#70792: 30.0.50; [PATCH] Add Eshell support for expanding absolute file names within the current remote connection
Date: Mon, 6 May 2024 11:37:06 -0700 [thread overview]
Message-ID: <3940954c-a0e7-e10c-2291-9c9392dda37f@gmail.com> (raw)
In-Reply-To: <fb5d7849-9aa4-665d-a34e-4d60243f78b5@gmail.com>
On 5/6/2024 11:28 AM, Jim Porter wrote:
> Yes, but this breaks in non-obvious ways if Eshell's "cp" implementation
> falls back to the external program. For example, today:
>
> ~ $ cp file /ssh:remote:~/file # copies "file" to a remote host
> ~ $ cp -b file /ssh:remote:~/file
> /usr/bin/cp: cannot create regular file '/ssh:remote:~/file': No such
> file or directory
>
> Or the second line might work if you get unlucky, or pass --parents, or...
By "work" here, I mean, "cp will copy the file, but to a place you
likely didn't intend."
next prev parent reply other threads:[~2024-05-06 18:37 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-05 20:58 bug#70792: 30.0.50; [PATCH] Add Eshell support for expanding absolute file names within the current remote connection Jim Porter
2024-05-06 11:14 ` Eli Zaretskii
2024-05-06 18:13 ` Jim Porter
2024-05-06 18:43 ` Eli Zaretskii
2024-05-06 20:05 ` Jim Porter
2024-05-07 2:01 ` Jim Porter
2024-05-07 11:55 ` Eli Zaretskii
2024-05-07 18:54 ` Jim Porter
2024-05-08 13:20 ` Eli Zaretskii
2024-05-08 16:13 ` Jim Porter
2024-05-08 18:32 ` Eli Zaretskii
2024-05-08 18:57 ` Jim Porter
2024-05-09 18:14 ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-09 18:53 ` Eli Zaretskii
2024-05-09 19:10 ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-09 20:30 ` Jim Porter
2024-05-09 22:15 ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-09 22:28 ` Jim Porter
2024-05-10 5:45 ` Eli Zaretskii
2024-05-10 19:35 ` Jim Porter
2024-05-13 7:39 ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-16 2:12 ` Jim Porter
2024-05-08 18:17 ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-08 18:49 ` Eli Zaretskii
2024-05-09 18:22 ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-09 19:02 ` Eli Zaretskii
2024-05-07 8:12 ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-06 16:56 ` Sean Whitton via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-06 17:59 ` Eli Zaretskii
2024-05-06 18:28 ` Jim Porter
2024-05-06 18:37 ` Jim Porter [this message]
2024-05-07 8:50 ` Sean Whitton via Bug reports for GNU Emacs, the Swiss army knife of text editors
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=3940954c-a0e7-e10c-2291-9c9392dda37f@gmail.com \
--to=jporterbugs@gmail.com \
--cc=70792@debbugs.gnu.org \
--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 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).