From: Eli Zaretskii <eliz@gnu.org>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: 25183@debbugs.gnu.org
Subject: bug#25183: 26.0.50; expanding quoted file name on w32
Date: Mon, 12 Dec 2016 18:48:18 +0200 [thread overview]
Message-ID: <83eg1dccvh.fsf@gnu.org> (raw)
In-Reply-To: <87a8c1xhwh.fsf@gmx.de> (message from Michael Albinus on Mon, 12 Dec 2016 16:54:06 +0100)
> From: Michael Albinus <michael.albinus@gmx.de>
> Date: Mon, 12 Dec 2016 16:54:06 +0100
>
>
> Expanding a quoted file name works wrong on w32 systems. With Emacs
> running on ‘gnu/linux’, there is
>
> (expand-file-name "/:~/path/./file")
> => "/:~/path/file"
>
> This is correct. With Emacs running on ‘windows-nt’, there is
>
> (expand-file-name "/:~/path/./file")
> => "/:c:/Users/lb01177/AppData/Roaming/path/file"
Try
(expand-file-name "/:c:/~/path/./file")
expand-file-name needs to produce an absolute file name, and a file
name that begins with a "~" isn't.
IOW, I believe this is a feature. If you think it isn't, please
explain why.
next prev parent reply other threads:[~2016-12-12 16:48 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 [this message]
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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83eg1dccvh.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=25183@debbugs.gnu.org \
--cc=michael.albinus@gmx.de \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.