unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Noam Postavsky <npostavs@users.sourceforge.net>
Cc: michael.albinus@gmx.de, 25183@debbugs.gnu.org
Subject: bug#25183: 26.0.50; expanding quoted file name on w32
Date: Sat, 24 Dec 2016 20:00:32 +0200	[thread overview]
Message-ID: <83pokhxl4v.fsf@gnu.org> (raw)
In-Reply-To: <CAM-tV--vXEYSELyU6LeXcwLQG4iBOqMAWgSZECnWZMGNPWh9uw@mail.gmail.com> (message from Noam Postavsky on Sat, 24 Dec 2016 12:43:24 -0500)

> From: Noam Postavsky <npostavs@users.sourceforge.net>
> Date: Sat, 24 Dec 2016 12:43:24 -0500
> Cc: Michael Albinus <michael.albinus@gmx.de>, 25183@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.





  reply	other threads:[~2016-12-24 18:00 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-12 15:54 bug#25183: 26.0.50; expanding quoted file name on w32 Michael Albinus
2016-12-12 16:48 ` Eli Zaretskii
2016-12-12 16:54   ` Michael Albinus
2016-12-12 18:11     ` Drew Adams
2016-12-12 18:17       ` Drew Adams
2016-12-13  0:39     ` Noam Postavsky
2016-12-13  1:08       ` Glenn Morris
2016-12-13  1:10         ` Glenn Morris
2016-12-13  1:33         ` npostavs
2016-12-13  8:30           ` Michael Albinus
2016-12-13 16:28             ` Eli Zaretskii
2016-12-24 12:52               ` Eli Zaretskii
2016-12-24 13:57                 ` npostavs
2016-12-24 16:06                   ` Eli Zaretskii
2016-12-24 17:43                     ` Noam Postavsky
2016-12-24 18:00                       ` Eli Zaretskii [this message]
2016-12-24 18:51                         ` npostavs
2016-12-27  8:17                           ` Eli Zaretskii
2016-12-25 11:31                 ` Michael Albinus
2016-12-26 15:58                   ` Eli Zaretskii
2016-12-26 16:19                     ` Michael Albinus
2016-12-27  8:14                       ` Eli Zaretskii
2016-12-27  9:56                         ` Michael Albinus
2017-01-27  9:51                           ` Michael Albinus

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83pokhxl4v.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=25183@debbugs.gnu.org \
    --cc=michael.albinus@gmx.de \
    --cc=npostavs@users.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).