From: Eli Zaretskii <eliz@gnu.org>
To: michael.albinus@gmx.de
Cc: 25183@debbugs.gnu.org, npostavs@users.sourceforge.net
Subject: bug#25183: 26.0.50; expanding quoted file name on w32
Date: Sat, 24 Dec 2016 14:52:17 +0200 [thread overview]
Message-ID: <8337hdzdz2.fsf@gnu.org> (raw)
In-Reply-To: <83eg1bbxp5.fsf@gnu.org> (message from Eli Zaretskii on Tue, 13 Dec 2016 18:28:22 +0200)
> Date: Tue, 13 Dec 2016 18:28:22 +0200
> From: Eli Zaretskii <eliz@gnu.org>
> Cc: 25183@debbugs.gnu.org, npostavs@users.sourceforge.net
>
> > From: Michael Albinus <michael.albinus@gmx.de>
> > Date: Tue, 13 Dec 2016 09:30:18 +0100
> > Cc: 25183@debbugs.gnu.org
> >
> > It is not an annoyance coming from a user's bug report; I've stumbled
> > over this when running tramp-tests.el under many different environments.
> >
> > (expand-file-name "/:/~/path/./file") => "/:c:/~/path/file"
> >
> > looks better, althoug the volume drive would still disturb me. But
> > that's my personal preference, the result might be OK on MS Windows.
> >
> > Eli?
>
> I will look into this in a couple of days.
Sorry for the delay.
I looked into this, and I indeed think there might be a problem here.
I agree that "~" should not be expanded for file names escaped with
"/:", but before I propose a solution, I think we should decide
whether the "/:" escape should cause the rest be expanded "as usual",
i.e. produce an absolute file name after "/:" for local file names,
minus the "~" expansion. Currently, Unix file names are not expanded
because '/' as the first character makes them look as absolute file
names. MS-Windows specific code, OTOH, looks under the hood, and does
expand the rest.
IOW, the question is whether on Windows we should have this:
(expand-file-name "/:~/path/./file") => "/:c:/~/path/file"
or this:
(expand-file-name "/:~/path/./file") => "/:~/path/file"
If we want the former, then maybe the Unix code should be fixed to
produce "/:/~/path/file" in that case.
Thoughts?
next prev parent reply other threads:[~2016-12-24 12:52 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 [this message]
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
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=8337hdzdz2.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).