GNU bug report logs -
#32304
27.0.50; tramp-tests issue with double slash
Previous Next
Reported by: Ken Brown <kbrown <at> cornell.edu>
Date: Sun, 29 Jul 2018 15:55:01 UTC
Severity: normal
Found in version 27.0.50
Fixed in version 27.1
Done: Michael Albinus <michael.albinus <at> gmx.de>
Bug is archived. No further changes may be made.
Full log
View this message in rfc822 format
[Message part 1 (text/plain, inline)]
Your bug report
#32304: 27.0.50; tramp-tests issue with double slash
which was filed against the emacs package, has been closed.
The explanation is attached below, along with your original report.
If you require more details, please reply to 32304 <at> debbugs.gnu.org.
--
32304: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=32304
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems
[Message part 2 (message/rfc822, inline)]
Version: 27.1
Eli Zaretskii <eliz <at> gnu.org> writes:
>> Should be fixed now in master. Could you, pls recheck? (I haven't tested
>> on MS Windows today)
>
> Thanks, it works now as expected.
Thanks for checking, I'm closing the bug.
Best regards, Michael.
[Message part 3 (message/rfc822, inline)]
[Message part 4 (text/plain, inline)]
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
that):
(should
(string-equal
(substitute-in-file-name "/method:host://foo") "/method:host:/foo"))
(should
(string-equal (substitute-in-file-name "/method:host:/path///foo")
"/foo"))
(should
(string-equal (substitute-in-file-name "/method:host://~foo") "/~foo"))
Here are the corresponding evaluations:
(substitute-in-file-name "/method:host://foo")
"/method:host://foo"
(substitute-in-file-name "/method:host:/path///foo")
"//foo"
(substitute-in-file-name "/method:host://~foo")
"//~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")
"//foo"
(substitute-in-file-name "/path///foo")
"//foo"
(substitute-in-file-name "//~foo")
"//~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.
Ken
[0001-Adjust-expected-results-on-a-tramp-test.patch (text/plain, attachment)]
This bug report was last modified 6 years and 290 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.