Subject: Re: bug#21931: 25.0.50; behaviour of read-directory-name with double slashes

From: Nicolas Richard <[email-masked]>
Date: Mon, 23 Nov 2015 15:14:59 +0100

John Wiegley writes:
>>>>>> Nicolas Richard <[email-masked]> writes:
>
>> ("/tmp/src/" "/" "src/" "/" "/src/" "/")
>> Is this intended ?
>
> What list were you expecting to see? "//" has always meant "start at root" to
> mean, ignoring whatever comes prior. This is how C-x C-f works, and it means
> you don't have to delete any existing default text in order to begin at root.

Indeed, but when constructing a path via (concat foo "/" bar), it can
happen that the result contains //. If this is then used as arg to
read-directory-name, this leads to an unexpected default.

OTOH (info "(elisp) Directory Names") explicitly says that using concat
for constructing paths in this way is wrong, so I guess that this bug
report is void.

Thanks for looking into it, I close it.

Nico.