GNU bug report logs -
#70792
30.0.50; [PATCH] Add Eshell support for expanding absolute file names within the current remote connection
Previous Next
Full log
Message #68 received at 70792 <at> debbugs.gnu.org (full text, mbox):
Eli Zaretskii <eliz <at> 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 <at> host:/:<something>" makes <something> "local" on
>> "/method:user <at> 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 <at> 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.
The intention of file name quoting is to suppress file name handlers of
any kind.
"/:/method:user <at> host:/foo/bar.gz" makes "/method:user <at> host:/foo/bar.gz"
a literal file name, not to be transferred to any file name handler.
"/method:user <at> 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.
Best regards, Michael.
This bug report was last modified 1 year and 33 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.