From: Ken Brown <kbrown@cornell.edu>
To: Michael Albinus <michael.albinus@gmx.de>,
Andy Moreton <andrewjmoreton@gmail.com>
Cc: 32304@debbugs.gnu.org
Subject: bug#32304: 27.0.50; tramp-tests issue with double slash
Date: Tue, 31 Jul 2018 18:07:29 -0400 [thread overview]
Message-ID: <f1cb1d0e-2a66-a5fa-988e-769f776be6a7@cornell.edu> (raw)
In-Reply-To: <87sh3zi0mm.fsf@gmx.de>
On 7/31/2018 4:57 PM, Michael Albinus wrote:
> The question is, whether Tramp should follow this. It does
>
> (substitute-in-file-name "/ssh::/a///b") => "/b"
This seems right to me. After all, the repeated slash is not at the
beginning of the (total) file name.
> Maybe, it shall return on Cygwin and MS-Windows
>
> (substitute-in-file-name "/ssh::/a///b") => "//b"
I can't think of any situation where this would be useful.
Ken
next prev parent reply other threads:[~2018-07-31 22:07 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-29 15:54 bug#32304: 27.0.50; tramp-tests issue with double slash Ken Brown
2018-07-29 16:27 ` Michael Albinus
2018-07-29 16:47 ` Ken Brown
2018-07-29 16:55 ` Michael Albinus
2018-07-29 17:00 ` Ken Brown
2018-07-30 10:43 ` Michael Albinus
2018-07-30 12:17 ` Ken Brown
2018-07-30 14:45 ` Eli Zaretskii
2018-07-30 20:50 ` Michael Albinus
2018-07-31 2:34 ` Eli Zaretskii
2018-07-31 5:00 ` Michael Albinus
2018-08-08 13:48 ` Michael Albinus
2018-08-08 14:35 ` Eli Zaretskii
2018-08-08 14:42 ` Eli Zaretskii
2018-08-08 18:06 ` Michael Albinus
2018-08-09 12:24 ` Michael Albinus
2018-08-09 15:18 ` Eli Zaretskii
2018-08-10 7:27 ` Michael Albinus
2018-08-08 15:26 ` Michael Albinus
2018-08-08 15:57 ` Eli Zaretskii
2018-07-31 4:58 ` Michael Albinus
2018-07-29 17:26 ` Eli Zaretskii
2018-07-30 8:26 ` Michael Albinus
2018-07-31 14:46 ` Andy Moreton
2018-07-31 20:57 ` Michael Albinus
2018-07-31 22:07 ` Ken Brown [this message]
2018-08-01 20:51 ` Michael Albinus
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=f1cb1d0e-2a66-a5fa-988e-769f776be6a7@cornell.edu \
--to=kbrown@cornell.edu \
--cc=32304@debbugs.gnu.org \
--cc=andrewjmoreton@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).