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

Previous Next

Package: emacs;

Reported by: Michael Albinus <michael.albinus <at> gmx.de>

Date: Mon, 12 Dec 2016 15:55:02 UTC

Severity: normal

Found in version 26.0.50

Done: Michael Albinus <michael.albinus <at> gmx.de>

Bug is archived. No further changes may be made.

Full log


View this message in rfc822 format

From: Eli Zaretskii <eliz <at> gnu.org>
To: Noam Postavsky <npostavs <at> users.sourceforge.net>
Cc: 25183 <at> debbugs.gnu.org, michael.albinus <at> gmx.de
Subject: bug#25183: 26.0.50; expanding quoted file name on w32
Date: Sat, 24 Dec 2016 20:00:32 +0200
> 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?

> >> As I've said in https://debbugs.gnu.org/cgi/bugreport.cgi?bug=25183#29,
> >> currently "/:~/foo" is a kind of paradoxical file name, being
> >> both/neither relative nor absolute.
> >
> > file-name-absolute-p is not smart enough to handle this case with the
> > rigor we are discussing, so I don't think this aspect is important for
> > the purposes of this discussion.  The "/:" quoting was chosen because
> > it fools file-name-absolute-p, so the above is not surprising.
> 
> I don't think file-name-absolute-p is relevant.

We are in agreement about that.




This bug report was last modified 8 years and 195 days ago.

Previous Next


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