From: Eli Zaretskii <eliz@gnu.org>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: jporterbugs@gmail.com, 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: Thu, 09 May 2024 22:02:54 +0300 [thread overview]
Message-ID: <86bk5e6c69.fsf@gnu.org> (raw)
In-Reply-To: <878r0i4zge.fsf@gmx.de> (message from Michael Albinus on Thu, 09 May 2024 20:22:57 +0200)
> From: Michael Albinus <michael.albinus@gmx.de>
> Cc: jporterbugs@gmail.com, 70792@debbugs.gnu.org
> Date: Thu, 09 May 2024 20:22:57 +0200
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> Hi Eli,
>
> >> FTR, we *have* already two different kinds of quoting. "/:<something>"
> >> makes <something> local, whatever syntax it has (for example, Tramp file
> >> name syntax).
> >>
> >> "/method:user@host:/:<something>" makes <something> "local" on
> >> "/method:user@host:" whatever syntax it has.
> >
> > There's a fine nuance here: "/:" does NOT make a file name locale, it
> > prevents interpreting it as remote due to the "/something:" construct
> > in it. "/:" does NOT change the semantics of "/foo/bar/baz", it only
> > changes the semantics of "/method:user@host:/foo/bar".
>
> The intenmtion of file name quoting isn't to make a file name local or
> remote. This is just a side-effect in case of Tramp.
I agree (and tried to say the same in different words).
> The intention of file name quoting is to suppress file name handlers of
> any kind.
I agree.
> "/:/method:user@host:/foo/bar.gz" makes "/method:user@host:/foo/bar.gz"
> a literal file name, not to be transferred to any file name handler.
>
> "/method:user@host:/:/foo/bar.gz" keeps the Tramp file name handler
> active, but makes "/:/foo/bar.gz" a literal file name "/foo/bar.gz" on
> the remote machine. This suppresses the jka-compr-handler, for example.
>
> Likely, you mean the same, but I wanted to say it explicitly.
Yes, we agree.
Which is why I think using /: for "escaping to local" in Eshell is
confusing and should not be done.
next prev parent reply other threads:[~2024-05-09 19:02 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 [this message]
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
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=86bk5e6c69.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=70792@debbugs.gnu.org \
--cc=jporterbugs@gmail.com \
--cc=michael.albinus@gmx.de \
/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).