Subject: bug#13033: 24.3.50; regression: read-file-name-internal handles "~" wrong

From: Eli Zaretskii <[email-masked]>
Date: Fri, 30 Nov 2012 21:01:10 +0200

> From: Stefan Monnier <[email-masked]>
> Date: Fri, 30 Nov 2012 12:00:32 -0500
> Cc: [email-masked]
> 
> Now you say that (read-file-name-internal "~" 'file-exists-p nil)
> returns "~/dradams/" and I can't understand where the additional
> slash comes from.

Windows doesn't support ~FOO specifications, because there's no
practical way of getting at the home directory of another user.  See
expand-file-name ('getpwnam' on w32.c returns NULL for any user name
but the current user's).

This explains ~/, but where "dradams" comes back after that is
probably explained by what the completion code does, being confused by
the above.