GNU bug report logs - #32304
27.0.50; tramp-tests issue with double slash

Previous Next

Package: emacs;

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


Message #50 received at 32304 <at> debbugs.gnu.org (full text, mbox):

From: Michael Albinus <michael.albinus <at> gmx.de>
To: Andy Moreton <andrewjmoreton <at> gmail.com>
Cc: 32304 <at> debbugs.gnu.org
Subject: Re: bug#32304: 27.0.50; tramp-tests issue with double slash
Date: Tue, 31 Jul 2018 22:57:53 +0200
Andy Moreton <andrewjmoreton <at> gmail.com> writes:

Hi Andy,

> POSIX specifies that "//" is handled in an implementation defined
> manner, so Cygwin and Windows are not really special.
>
> See POSIX section 4.13 Pathname Resolution:
>
>     A pathname consisting of a single <slash> shall resolve to the root
>     directory of the process. A null pathname shall not be successfully
>     resolved. If a pathname begins with two successive <slash> characters,
>     the first component following the leading <slash> characters may be
>     interpreted in an implementation-defined manner, although more than two
>     leading <slash> characters shall be treated as a single <slash>
>     character.

But the Emacs implementation handles only Cygwin and MS Windows as
special. This is POSIX conform, because it declares this as
implementation specific.

The question is, whether Tramp should follow this. It does

(substitute-in-file-name "/ssh::/a///b") => "/b"

Maybe, it shall return on Cygwin and MS-Windows

(substitute-in-file-name "/ssh::/a///b") => "//b"

Don't know. Is this too sophisticated?

Best regards, Michael.




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.