From: Eli Zaretskii <eliz@gnu.org>
To: Michael Albinus <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: Mon, 26 Dec 2016 17:58:15 +0200 [thread overview]
Message-ID: <831swuy960.fsf@gnu.org> (raw)
In-Reply-To: <87vau8nt2b.fsf@gmx.de> (message from Michael Albinus on Sun, 25 Dec 2016 12:31:40 +0100)
> From: Michael Albinus <michael.albinus@gmx.de>
> Cc: 25183@debbugs.gnu.org, npostavs@users.sourceforge.net
> Date: Sun, 25 Dec 2016 12:31:40 +0100
>
> (expand-file-name "/:~/path/./file") => "/:~/path/file"
>
> looks proper to me.
That's proper on Unix, but on MS-Windows it will look like a
non-absolute file name, which might break things.
> Prepending "c:/" moves the file to another location
> on the c: drive, perhaps.
It should use CWD, not necessarily c:/. See below.
> What does (expand-file-name "/:dir/path/./file") ?
It produces "/:CURDIR/dir/path/file", where CURDIR is the current
default directory, including the drive letter. My current way of
thinking is to produce the same when "dir" is replaced with "~". Is
that acceptable, in particular for Tramp?
Thanks.
next prev parent reply other threads:[~2016-12-26 15:58 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
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 [this message]
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=831swuy960.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).