GNU bug report logs - #25183
26.0.50; expanding quoted file name on w32

Previous Next

Full log

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

From: npostavs <at> users.sourceforge.net
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: michael.albinus <at> gmx.de, 25183 <at> debbugs.gnu.org
Subject: Re: bug#25183: 26.0.50; expanding quoted file name on w32
Date: Sat, 24 Dec 2016 13:51:14 -0500

Eli Zaretskii <eliz <at> gnu.org> writes:

>> From: Noam Postavsky <npostavs <at> users.sourceforge.net>
>> Date: Sat, 24 Dec 2016 12:43:24 -0500
>> Cc: Michael Albinus <michael.albinus <at> gmx.de>, 25183 <at> debbugs.gnu.org
>> 
>> >>     (expand-file-name "/:~/path/./file") => (error "/: quoting relative file name")
>> >
>> > expand-file-name doesn't signal errors, and I don't think it would be
>> > a good idea to have it start doing that.
>> 
>> I think the status quo (leaving it inconsistent) is okay too (garbage
>> in, garbage out).
>
> But expansion of "~" in the Windows build should be bypassed in this
> case, don't you agree?

In the case of "/:~/whatever" I think any output is fine, since the
input is meaningless.  Avoiding ~-expansion is okay, though I don't
think it's actually a problem either way.

For reference, on a GNU system, doing

$ echo xx > '~'
$ emacs -Q '/:~'

opens up the $HOME directory, even though the "~" is not expanded by
`expand-file-name'.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.