bug#36490: 26.1; directory-files-recursively breaks when it encounters a directory named "~"

[Erik Hahn]

On 08/07/19 23:08, Lars Ingebrigtsen wrote:
> The doc string continues with further confusion:
>
> ---
> See also the function ‘substitute-in-file-name’.
> ---
>
> See it for...  what?  For further expansions this function is going to
> do?

It is related in that it also chokes on files named "~":

(substitute-in-file-name "/tmp/~") => "~"

Its doc string is also wrong. It says

> If ‘/~’ appears, all of FILENAME through that ‘/’ is discarded.

but

(substitute-in-file-name "/tmp/~foo") => "/tmp/~foo"