[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#32304: 27.0.50; tramp-tests issue with double slash

From: Ken Brown
Subject: bug#32304: 27.0.50; tramp-tests issue with double slash
Date: Sun, 29 Jul 2018 11:54:10 -0400
User-agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1

The following parts of tramp-test04-substitute-in-file-name are failing
on Cygwin (and probably also on MS-Windows, but I can't easily test

    (substitute-in-file-name "/method:host://foo") "/method:host:/foo"))
(string-equal (substitute-in-file-name "/method:host:/path///foo") "/foo"))
   (string-equal (substitute-in-file-name "/method:host://~foo") "/~foo"))

Here are the corresponding evaluations:

(substitute-in-file-name "/method:host://foo")

(substitute-in-file-name "/method:host:/path///foo")

(substitute-in-file-name "/method:host://~foo")

This is a consequence of the fact that Tramp calls
substitute-in-file-name on the local part of the file name:

(substitute-in-file-name "//foo")

(substitute-in-file-name "/path///foo")

(substitute-in-file-name "//~foo")

"//" has a special meaning at the beginning of a file name on Cygwin and
MS-Windows; see the comment near the beginning of
search_embedded_absfilename.  So I don't think there's a real bug here.
Maybe the expected result of the test should simply be adjusted, as in
the attached patch.  Someone who builds on MS-Windows would have to
check this.


Attachment: 0001-Adjust-expected-results-on-a-tramp-test.patch
Description: Text document

reply via email to

[Prev in Thread] Current Thread [Next in Thread]